Direction for where you are. Designed for where you're going.

Technology strategy is two different conversations in the same room. We see systems, architecture, sequencing, interdependencies. The business sees a laptop that doesn't log in, a proposal that took three applications to assemble, a CFO staring down a renewal they don't understand. Both views are correct. The job of a strategic direction is to bridge them.

The bridge is almost always language. When we talk to the ops lead about tenant configuration, the conversation goes nowhere. When we talk about the ten minutes every morning her team loses to a login prompt, and what a three-year plan does to that ten minutes, the conversation goes everywhere. The work is the same. The frame decides whether it gets funded.

What the business wants, underneath all of it, is two things. They want to work better — more of the day spent on the work, less spent fighting the tools that enable it. And they want confidence in the systems they're running on: the quiet certainty that when you click the link, something reasonable happens.

The standard advisory pattern is familiar. Consultants collect information, disappear for a few weeks, come back with a polished presentation, walk the leadership team through it, and leave. The plan is theirs until it's not — until the CFO has to defend a line item at a board meeting, the ops lead has to execute it on a Monday, or the owner has to answer "why are we doing this now" to a room full of skeptics. A plan nobody in the room helped write is a plan the room quietly distances itself from the moment pressure arrives.

We work the other way. The plan is drafted in the room, with the people who'll have to live with it — the owner, the CFO, the operations lead, whoever holds the IT role. We bring the technical shape, the translation layer, and the pattern memory from other engagements. They bring the organizational reality, the constraints nobody thinks to document, and the history that explains why the obvious answer won't survive contact with Tuesday. The version that emerges is less tidy at the edges than something a consultancy would present in a conference room. It is also something the people who have to defend it actually wrote — which is the only kind of polish that holds up once they have to.

The horizon is three years. Not a rolling eighteen-month view, not a ten-year aspiration. Three years is the distance a small or mid-sized business can honestly plan to, with enough room for sequencing and enough discipline to force real trade-offs. Beyond that is guesswork dressed up as a commitment. Shorter than that is just next week, repeated.

What comes out of all of this is direction. Not something external that the business has to adopt, but a point of view the leadership team already owns the logic of, because they helped build it. Whatever form the work takes on the way there, that's the part that lasts.

A strategic-direction engagement is deliberately contained. We've watched too many businesses commit to nine-month advisory programs that never produce a decision anyone will act on. The point of this work is to get the plan right quickly, then let the business move — not to keep ourselves in the room.

The arc is five steps. They happen in order for a reason.

One — the questionnaire. Short, async, completed by the business before we meet. It surfaces the current-state picture in a form the operators control, without burning meeting time on facts. It also means we don't sit in a room waiting for someone to email the controller and ask what the renewal calendar looks like. When clients can't give us their time, the questionnaire earns their time.

Two — the current-state review. What's actually deployed, what's under contract, what's accruing technical debt disguised as operational cost. We read the environment the way a new owner would, not the way IT presents it internally. The gap between those two readings is usually the first chapter of the plan.

Three — the working session. Half day or full day, with the people who will have to defend the plan in the room — the owner, the CFO, the ops lead, whoever plays the IT role. We use metaphors. We use real examples from the business. We translate capital outlay into operating cost and back, out loud, until everyone in the room can do the math. A draft plan is on the wall before the day ends.

Four — closure and handoff. Everyone who'll have to defend the direction has seen every version of it, written their name on the decisions they committed to, and knows what they're accountable for over the first ninety days. The direction isn't handed to them at the end — it's already theirs, because they helped draft it along the way.

Five — the quarterly. A sixty-minute review, four times a year, sometimes more. What moved. What slipped. What changed in the business that the plan needs to bend around. A roadmap that isn't revisited in quarter two is already decorative. This is the cadence that keeps it alive — and usually the point at which we become the fractional CIO the business doesn't want to hire full-time.

What a strategic-direction engagement actually delivers is the capacity to decide. Before the engagement, every IT question stalls on the same sentence — "we should probably figure out the bigger picture first." After, the bigger picture is figured out. The next tool, the next hire, the next vendor pitch shows up and the business can say yes or no on its own merits, against a direction the leadership team already owns. Nothing is reactive anymore. Nothing has to be rebuilt from scratch every time someone asks a budget question.

That is the whole deliverable. Direction. Enough clarity to run the business like one that's three sizes larger than it is — to make the calls a grown-up company would make, before the company has grown up. And when it does grow up, the transition feels almost boring, because the posture was already in place before the growth arrived.