Most technology money fixes the wrong layer.
Every organization already knows what it has to be good at. Almost none of them have written that down separately from how they happen to do it today. The gap between those two sentences is where the budget quietly goes.
Three questions, and you can answer all of them without us.
This takes about two minutes and needs nothing open except your own memory and, for the last one, your accounts payable.
Name what you must be good at
Not a department or a tool. The thing that has to work or the mission does not happen.“Bringing on a new client without anything falling through.”
Now say how you do it today
The actual mechanics, including the undocumented ones. Be honest about how much of it lives in one person's head.“A shared sheet, and Dana remembers the rest.”
Open your last three purchases
The last three pieces of technology you paid for. For each one, ask which of those two layers it touched.“All three were the second one.”
Nearly everyone finds the same thing. All three purchases touched the second layer. None of them made a weak capability strong. That is not a lapse in judgment, and it is not a story about wasted money. It is that almost nobody is selling the other layer, so almost nobody is shopping for it.
You have been buying furniture.Which is fine, right up until the kitchen is the thing that is missing.
Capabilities are the rooms. Processes are the furniture.
We call these two things by their proper names because the rest of our work depends on keeping them apart. You can rearrange furniture for years. If there is no kitchen, you are still eating out.
Stable, and rarely written down
What the organization has to be able to do reliably for the mission to happen. It was true five years ago and it will be true in five more.
- See a patient without hunting for their history
- Bring on a new client without anything falling through
- Get funding out the door on time
- Answer honestly when a regulator asks
Changeable, and where the invoices land
The current mechanics. Processes are worth improving, and they are usually what a vendor is quoting for, because they are easy to scope and easy to bill.
- A shared spreadsheet and a Tuesday call
- The one person who remembers how it is really done
- Whichever system was set up first and stayed
- A folder of PDFs nobody has opened since the audit
The expensive decisions do not sit inside a box.
Once the capabilities are named, something else shows up. Every organization we assess can point at the boxes and tell you who owns each one. Almost none of them can do that for the lines between the boxes, and the lines are where the costly decisions actually land.
Five domains. Ten lines between them. Every box has an owner already. Who owns the lines?
- TECHNOLOGY · DATAThe system of record changed, and nobody told the people who report out of it.
- TECHNOLOGY · RISK & AIA vendor switched an AI feature on inside software you already pay for, and no one set a policy.
- TECHNOLOGY · PROGRAMSThe work runs on a tool chosen by whoever set it up, not by what the work needs.
- TECHNOLOGY · GROWTHThe website collects information the rest of the organization cannot use.
- DATA · RISK & AIYour CRM holds the records a breach would expose, and nobody has decided who may see them.
- DATA · PROGRAMSYour outcome reporting and your database disagree about what counts as a client.
- DATA · GROWTHThe mailing list and the billing record are two different truths about the same person.
- RISK & AI · PROGRAMSThe service depends on one person's knowledge, and there is no continuity plan.
- RISK & AI · GROWTHA campaign promises something the organization cannot safely deliver.
- PROGRAMS · GROWTHGrowth targets are set without asking whether delivery can absorb them.
Where this comes from. None of the above is invented. It is the working method of outcome-driven enterprise architecture, a discipline large organizations pay a great deal for, known in that world as BODEA.
We have taken out the parts that only make sense at ten thousand employees and kept the part that works at forty: start from the outcome, work back to what the organization has to be capable of, and only then talk about systems. If that lineage matters to you, we have written it up properly, and we will go as deep as you like on the call. If it does not, nothing above changes.
Run those three questions with someone who does this daily.
We will walk your own answers back with you and say plainly whether there is a capability worth fixing. Sometimes there is not.