The title suggests a dramatic divide between winning and lagging firms. In practice, leadership quality is visible in ordinary programme decisions: whether somebody resolves a dependency, whether mixed evidence is examined, whether a sponsor remains available and whether a team has authority within understood boundaries.
Technology, delivery partners, funding and organisational capability all affect outcomes. Leadership behaviour is one part of that system, and it is the part senior teams can change directly.
Approving the budget and attending the kick-off do not complete sponsorship. Digital investment continues to require business decisions after delivery begins. A team cannot take responsibility for an outcome while leadership retains unclear vetoes, withholds access or disappears when priorities conflict.
Five behaviours that support useful progress
Ask what is stuck and listen to the answer
The source article described a senior partner who regularly asked the project lead one question: “What’s the thing that’s most stuck right now?” The strength of the question is its focus on the work rather than presentation.
A leader does not need to solve every technical constraint. They should identify which problems require authority, organisational attention or a change to the investment case. Ask what evidence supports the diagnosis and what the team has already tried. Avoid turning a candid answer into blame; teams learn quickly which risks are safe to surface.
Curiosity should have a consequence. If the same blocker appears at three reviews without a decision or escalation, repeated questioning has become theatre.
Treat early imperfection according to its risk
Early versions help teams learn when they are shown to appropriate users under controlled conditions. They may be incomplete, visually rough or limited in scope. Leaders can ask what the version is intended to test, what remains unsafe or unresolved and which decision will follow.
“Release and learn” is not permission to expose clients to avoidable harm, insecure systems, inaccessible journeys or professionally unreliable output. The acceptable level of imperfection depends on the use, audience and consequence. A disposable internal prototype and a client-facing legal or financial service require different controls.
The useful response to mixed results is neither automatic defence nor automatic cancellation. Separate the evidence. A rise in enquiries alongside weaker engagement might reflect a new acquisition source, a measurement change or poorer relevance. Investigate before choosing the next action.
Govern outcomes and enabling work
Delivery dates, spend and completed features matter. They do not establish that the investment created value.
Connect outputs to a small number of outcomes with baselines, owners and review dates. Include harms and control outcomes where relevant. Ask what would need to be true for a delivered capability to create the expected result: adoption, content, process change, sales follow-up, data quality or staff capacity.
Outcome focus should not become a reason to ignore foundational work whose value arrives later. Architecture, research and control design may be essential. The team should explain which uncertainty or dependency the work resolves.
Make decisions with bounded consultation
Partnerships and regulated organisations need consultation. Programmes stall when the threshold for a decision remains undefined or every concern reopens settled work.
For each decision type, state:
- who decides;
- who must be consulted;
- what evidence is required;
- the deadline and consequence of delay;
- which risks require specialist or board authority; and
- what new information can legitimately reopen the choice.
Proceeding without unanimous support can be responsible when the mandate allows it and affected people have a meaningful route to contribute. It can also be reckless if leadership uses “pace” to bypass professional duties or material concerns. The governance design makes the difference.
Give teams authority that matches responsibility
“You own the project” means little if every material choice returns to the sponsor. Define budget tolerances, architectural and brand principles, risk thresholds and matters reserved for leadership. Let the accountable team decide within that space.
Escalation should be a service, not a test of loyalty. When a matter crosses a boundary, the sponsor needs to respond by the date the programme requires. Delegation without timely senior decisions turns team ownership into workload without power.
Four leadership patterns that create drag
Consensus without a decision rule
Discussion expands because nobody knows when consultation ends. The remedy is not less respect for partners. It is an agreed protocol and a named decision-maker.
Move detailed design choices to people with the relevant role. Keep the partnership informed through principles, outcomes and material exceptions rather than asking it to decide every implementation detail.
Risk treatment without proportionality
Leaders sometimes add reviews and approvals because a project is described as digital. Other times they minimise genuine risk because the initiative is small or fashionable.
Ask qualified specialists to identify the obligation, harm scenario, likelihood, impact and available controls. Match governance to the consequence. A status-only portal and a service containing sensitive client data should not inherit the same assurance merely because both are portals.
Responsibility with retained invisible vetoes
A project lead presents a recommendation and receives “let me think about it”. New concerns appear at each return. The sponsor may believe they are being careful; the team experiences an authority boundary that moves after every proposal.
Make the reservations explicit. Name the evidence needed and the date of the decision. If leadership is unwilling to delegate the choice, record it as a reserved matter and adjust the plan accordingly.
Sponsorship that fades after approval
The sponsor advocates for the programme, then becomes unavailable as client work and firm leadership compete for attention. That pressure is real. It means sponsorship capacity should be planned rather than assumed.
Appoint a deputy for defined decisions, protect review dates and establish an escalation route for urgent matters. If the sponsor cannot provide the authority the programme requires, leadership should change the role rather than let the team repeatedly wait.
Make leadership behaviour observable
“Mindset” can become a flattering abstraction. Review concrete evidence each quarter:
- decisions awaiting senior action and their age;
- risks raised early versus discovered late;
- outcomes reviewed and actions taken;
- changes made after user or client evidence;
- scope added or removed through explicit choice;
- time leaders and affected teams committed; and
- areas where delegated authority was overridden and why.
Do not turn these into league-table metrics. Use them to identify operating patterns. A long decision time may be appropriate for a material regulated issue. A minor content approval waiting a month may reveal a misplaced authority boundary.
How leaders describe the work also matters. “The digital team’s project” signals distance from a business investment. Overstating early success is equally damaging. Report what has changed, what remains uncertain and what leadership has decided.
Partnership governance needs bounded autonomy
An equity partnership cannot always operate like a single-owner company. Partners have legitimate interests in reputation, client service, risk and investment. Digital work also produces frequent choices that cannot all wait for broad agreement.
Create a mandate for a defined outcome, budget, period and accountable sponsor. Reserve the small set of decisions that genuinely belong to the partnership. Delegate the rest to named roles and review evidence at a predictable cadence.
This structure preserves collective authority at the right altitude. It also lets the programme respond between partnership meetings.
Distinction uses WHNN®, What and How, for the Now and the Next, as one quarterly structure for reviewing priorities and decisions. It is our framework and part of our commercial method. No framework can compensate for decisions that remain unmade.
For a related prioritisation method, see planning digital investment when budgets are constrained.
The sponsor’s self-assessment
The source article ended with the right question:
In the last digital initiative I sponsored, when did I last review the outcomes, and what did I do with what I found?
Answer with an example. Name the evidence, the decision and the consequence. Attending governance or expressing support is not the same as using outcome evidence.
If no example comes readily, review one active investment with the delivery and business owners. Ask which outcome leadership expects, what the current evidence shows, what remains outside the team’s authority and which decision now belongs to you.
The gap between approval and governance is filled by sustained, specific attention. That behaviour is learnable. It starts with taking responsibility for the decisions only leadership can make.
