When you need advisory, delivery, or both

Most technology problems in a growing business look identical from the outside: something important is not moving. What differs is why it is not moving, and that difference decides what kind of help actually works.

Buy the wrong one and you get an expensive version of what you already had. A team that lacks direction, given more hands, produces more of the wrong thing faster. A team that knows exactly what to build, given another strategy deck, gets a slide with their own conclusions on it.

The diagnostic question

Ask the people closest to the work a single question: if we cleared your calendar for a month, would you know what to build?

If the answer is a confident yes, and the thing still is not shipping, you have a delivery problem. If the answer is a pause, a look sideways, or three different answers from three people, you have a clarity problem. No amount of extra capacity fixes the second one.

What a clarity problem actually looks like

• Two systems do overlapping jobs and nobody will decide which one wins
• A vendor renewal is coming and the honest answer to "should we keep this?" is a shrug
• Every quarter's priorities are last quarter's priorities, with dates moved
• A rewrite keeps getting proposed, and nobody can articulate what it would fix
• Leadership and the technical team describe the same problem in incompatible language

These are decision problems wearing a technology costume. They do not need more engineers. They need someone with the standing to make a call, write down why, and be accountable for it — which is what fractional technology leadership is for.

What a delivery problem actually looks like

• The roadmap is clear and agreed, and the queue is not moving
• One person is the bottleneck on everything and knows it
• A migration has been eighty percent done for five months
• The team is competent and busy, and the important work is losing to the urgent work

Here the thinking is done. What is missing is hands, sequencing, and someone whose only job is to finish. Advisory would be an insult — they already know what to do.

The blended case, which is most cases

In practice the honest answer is usually "some of both, in a specific order." Two or three weeks of assessment produces a decision and a sequence; delivery work then executes against it. The important part is that the advisory portion is bounded — it produces a decision and then it ends. Advisory that never converts into execution is a subscription to being told things.

The failure mode to watch for is the reverse: delivery work that starts before the decision is made. It always feels faster in week one and always costs more by week ten, because the first real fork in the road exposes that nobody agreed on the destination.

A practical way to start

If you genuinely cannot tell which one you have, start with the smallest possible piece of advisory: a fixed-scope assessment with a written recommendation at the end. Not a retainer, not a strategy engagement — a defined piece of work with a deliverable you can act on or ignore.

If the recommendation tells you something you already knew, you had a delivery problem and you have lost very little finding out. If it tells you something uncomfortable, you just avoided spending a delivery budget on the wrong target.