Most stalled initiatives do not need more technology. They need a decision.

When a technology programme loses momentum, adding people or capability can feel like a concrete response. Before making that commitment, establish what the team is actually waiting for. A deferred choice about scope, ownership or operating practice can hold up work that the existing team is capable of delivering.

Technical constraints deserve investigation. So do the decisions surrounding them. A useful diagnosis makes both visible and identifies which one needs attention next.

Find the choice behind the recurring issue

Look at the issues that return to the steering group. Ask what would allow each one to close. A resource shortage might require a priority decision between initiatives. A disputed requirement might require agreement on the business outcome. A delayed integration might require someone to choose which system owns the information.

Four questions help expose these gaps:

Can the sponsor and team describe the intended business change in the same terms?
Are leaders asking for outcomes that compete for the same capacity or require incompatible choices?
Which issues keep returning without an accountable decision-maker?
What could the team complete with its current resources if a specific choice were resolved?

These questions are a starting point for diagnosis. They help distinguish work that needs additional technical effort from work waiting for a mandate.

Make scope and ownership visible

Consider a hypothetical engineering business introducing a common job-management system across several offices. The software configuration is progressing, but agreement on estimating, approvals and reporting keeps slipping. Each office expects to preserve its existing process while executives expect comparable information across the business.

The team cannot resolve that conflict through configuration alone. It needs a decision about which practices will be common, where local variation is acceptable and who can approve exceptions.

The sponsor might choose a shared minimum process with local variations outside it. It might begin with one office to test the proposed model. It might narrow the initiative to reporting while leaving job execution unchanged. Each choice creates different work, costs and benefits.

Until a direction is agreed, additional configuration may create more versions to reconcile. The next useful intervention is to bring the operational owners together with a clear choice and enough evidence to assess it.

Check the technical evidence

Avoid treating every delay as a governance problem. An integration may genuinely require specialist work. A migration may expose data defects. A proposed solution may be unable to meet an essential requirement.

Ask the delivery team to explain the constraint, the evidence behind it and the options for addressing it. Establish what is known, what remains uncertain and which investigation would reduce that uncertainty.

Then connect the constraint to a business choice. If resolving it would increase cost or delay the outcome, does the sponsor want to fund the work, change scope or reconsider the approach? Technical advice should make that judgement easier.

Sometimes the evidence supports adding capability. Make that investment against a defined task, expected result and acceptance point. The diagnosis should explain why the extra capability addresses the blockage.

Put a decision in front of the right person

Write the required choice in a sentence that can be answered. For the job-management example: which processes must be shared across offices before the first rollout, and who can authorise local exceptions?

Give the decision-maker credible options, their consequences and a recommendation. Identify the operational leaders who need to contribute and the person with authority to resolve disagreement. A meeting with interested stakeholders can provide evidence; the accountable person still needs to make the choice.

Record the decision and its boundaries. Explain which requirements follow from it, which work ends and which questions remain open. If the chosen option needs more evidence first, define the investigation and the date for returning to the decision.

Turn the decision into the next 90 days

Translate the direction into a few priorities with owners, dependencies and measurable milestones. In the hypothetical example, those priorities might be agreeing the common process, preparing one office and testing whether its reporting serves the intended management decisions.

Match the work to available capacity. Remove or defer activities that no longer support the direction so the team can focus. Establish how unresolved issues will reach someone able to decide them.

Review progress against the business outcome as well as completed tasks. If the direction is clear but the plan remains incomplete, define the work needed to make it executable. If the plan is sound but leadership capacity is missing, assign that responsibility explicitly.

Start with the three issues that have appeared most often in recent progress discussions. For each, identify the evidence needed, the choice required and the accountable person. Resolve those choices before deciding whether a larger team or another technology investment will move the initiative forward.