Strategy work delivers a direction. Execution work delivers a build. A decision only holds once it's been checked at both altitudes, and most engagements only check one.
Decision-Making
Two Shapes of Outside Help
Outside operations help tends to come in one of two shapes. One delivers strategy: a smart deck, a target operating model, a set of recommendations everyone nods at. The other delivers execution: a configured platform, a migrated database, an automation that does exactly what the ticket said. Both can be good work on their own terms. Both, on their own, tend to leave the same gap.
Why Each One Leaves the Same Gap
The strategy version tends to fall apart at ground level. The deck says change your pricing and packaging, and on the market research alone, it's the right call. What it doesn't say is how you'd move existing customers off the old pricing, what the change means for the day-to-day work in sales and finance, or whether you have the capacity to build what the new packaging depends on. Until someone works those questions out against the day-to-day, the recommendation is a direction, not a decision.
The execution version has the opposite problem. The implementer builds what was asked for, and often builds it well. But nobody on that engagement is being paid to ask whether the thing being automated should exist at all, whether the definition being encoded contradicts the one the finance team uses, or what happens to the workflow sitting next to this one. One corner of the operation gets cleaned up while the questions around it stay open.
The differentiator in this work isn't offering strategy and implementation as two phases of one contract. It's the moving between them, sometimes within the same meeting. A decision only holds if it clears both altitudes at once: it has to make sense against where the business is going, and it has to work for the person who does the thing every Tuesday. You can't check both from one altitude. You have to go down to the detail, back up to the strategy, and down again, until the answer is the same at both levels.
A decision has to make sense against where the business is going, and it has to work for the person who does the thing every Tuesday.
What This Looked Like on One Engagement
At the strategy level, the goal was easy to state: a reliable picture of the client's revenue, including what counted as recurring. The work started when we sat down with the list of products and had to name categories. Some of what looked like revenue turned out to be pass-through: charged to the customer at the same cost the company was paying for it. The same product turned out to mean two different things to two different people. And at the end of the exercise, we realized there were products that had been left off entirely. None of that shows up in a deck, and all of it changed what the final picture looked like. Skip the strategy and you've tidied the surface. Skip the detail and you've built a system that encodes an argument nobody resolved.
That back-and-forth is the actual work. It's why I don't hand off a deck and leave, and why I don't just build whatever the ticket says. What a client ends up with is a set of decisions that work at both levels, and a system built to match them.
Check It at Both Altitudes
If your last fix came out of a deck or a ticket queue and didn't hold, it was probably only ever checked at one altitude. The test is whether it still makes sense to the person doing the thing every Tuesday. If you're curious about where things may have fallen down, I'm here to discuss.
