Start With the Impact, Not the Technology

I've noticed that conversations about transformation have a tendency to start with technology. 

Questions such as: 

"Can we automate this process?"

"Should we move to an ERP?"

"What can AI do for us?"

"Which platform should we use?"

These are all valid questions. But I don't think they're the questions we should be asking first.

The first question should be much simpler: 

What are we actually trying to improve or achieve?

That may sound obvious, but I've seen how easy it is for organizations to get caught up in the technology before they have clearly defined the problem they are trying to solve. You wake up one day and your tech stack's as thick as the Yellow Pages sitting on top of a Jenga tower.

A new system can certainly make things faster. Automation can reduce repetitive work. AI can open up possibilities that weren't practical a few years ago.

But none of those things, by themselves, mean that an organization has actually transformed.

Purpose

Why do we exist? What are we trying to accomplish?

This is the part that is sometimes skipped because everyone assumes the answer is obvious.

A nonprofit might say that it wants a better donor management system. A church might want to improve how it manages its members and volunteers. A business might want to automate its order processing.

But those are solutions or activities, not necessarily the desired outcome.

What does “better donor management” actually mean?

More timely follow-up? Better donor retention? Less administrative work? Better visibility for leadership?

The answer matters because it changes what you should build.

Process

Once we understand the desired outcome, we need to understand how the work actually gets done.

This is where things can get a bit interesting.

The process documented on paper is often not the process people actually follow.

There may be spreadsheets, email threads, workarounds, manual reconciliations, undocumented approval steps, or one person who somehow knows exactly what needs to happen next.

Replacing all of that with a new system doesn't automatically make the process better.

Sometimes it just makes the existing process digital.

People

Processes don't operate by themselves. Obvious ba?

People perform them, make decisions within them, approve things, work around them, and sometimes quietly keep them functioning when the official process doesn't.

This is also where organizational change becomes important.

A system can be technically capable of doing something and still fail to deliver the expected result if the people using it don't understand why the change is happening, disagree with the new process, or don't have clear ownership of the work.

While tech can enable change, it cannot create organizational alignment by itself.

Data

Then there's the data. 

What information do we need to make the process work? Is the information accurate? Is it securely accessible? Who owns it? How is it maintained? Can we actually use it to make decisions?

This is one reason why technology projects sometimes uncover problems that were already there. The new system didn't create the data problem. It simply made the data problem harder to ignore.

Technology

Only now do I want to have the technology conversation.

Which system is appropriate? Should this be automated? Would an ERP help? Can AI handle part of the process? What integrations are required?

There are plenty of good technology questions to ask. But by this point, we have some context for answering them.

We're no longer asking:

“What can this technology do?”

We're asking:

“What does the organization need this technology to do?”

That's a very different conversation.

And then we get to impact

This is the part I think is easiest to overlook.

We implement the system. The project goes live. Users are trained. The automation runs. The dashboard looks good. Everyone celebrates.

But did the organization actually become better? That's the test.

For a nonprofit, moving to a new system may actually create more administrative work at first. There may be more fields to complete, more processes to follow, more controls to observe, and more discipline required around how data is entered and maintained.

That can feel counterintuitive. After all, didn't we implement the system to make things easier?

But the immediate increase in effort can be an investment in something the spreadsheet environment often made difficult to provide: consistent, structured, accessible, and auditable data.

The payoff comes later, when the organization can finally answer questions that used to require digging through multiple spreadsheets, emails, and someone's institutional memory.

The convenience isn't necessarily in doing less work today. It's in making better use of the work and data you've accumulated tomorrow.

And eventually, that can translate into something more meaningful. If the organization can spend less time searching for information, reconciling spreadsheets, or figuring out which version of the data is correct, those resources can instead go toward serving beneficiaries, improving programs, or advancing the mission.

That's impact.

The same principle applies to commercial organizations. If an automation saves 100 hours a month but creates new errors that someone has to fix, was it really an improvement? If an ERP gives management more reports but doesn't help them make better decisions, did the organization really transform?

If an AI tool allows employees to produce twice as much content but nobody knows whether the content is actually helping achieve the organization's objectives, what exactly have we improved? 

Technology can produce activity. Transformation should produce outcomes.

AI makes this even more important

The arrival of Artificial Intelligence makes starting with impact even more important, not less. AI is making it possible to automate, generate, analyze, summarize and execute things that previously required considerably more time and effort. While that's exciting, it also creates a new reflex:

Just because we can do something, we start looking for a reason to do it.

I think the order should be reversed. Start with the outcome. Then determine what needs to change. Then determine where technology, including AI, can help.

• AI can expand what an organization can do.

• Purpose helps determine what it should do.

• And impact tells us whether it was worth doing.

Technology is not the destination

I don't think technology is the enemy of transformation. Quite the contrary.

I've spent years working with business processes, enterprise applications, data and technology. I have seen firsthand how the right system can make a significant difference to how an organization operates.

The problem is not technology. The problem is starting there.

When we start with technology, we can end up designing the organization around what the software happens to be capable of doing.

When we start with the desired outcome, we can make technology work in service of what the organization actually needs.

That's why I keep coming back to: Purpose → Process → People → Data → Technology → Impact

It's not a software implementation methodology. It's a way of asking better questions. And perhaps the most important question is the first one:

What are we actually trying to make better?

Because technology can help an organization move faster. 

It just can't tell the organization where it should be going.