Partnerships can agree that a digital service is weak and still postpone every meaningful decision about it. Consensus on the problem conceals disagreement about priority, cost, risk, ownership and whose practice must change.
That is not necessarily obstruction. Equity partners have a legitimate interest in investment, and practice leaders see different client needs. The programme stalls when those differences remain implicit and the firm mistakes polite agreement for commitment.
Alignment means a decision people understand and can implement. It does not require universal enthusiasm.
Diagnose the decision, not the personalities
Before producing another business case, define the decision that is failing. “Approve digital transformation” is too broad. Partners may be reacting to different imagined scopes.
Write down:
- the client or business problem
- the decision required now
- options genuinely under consideration
- evidence available and missing
- who recommends, approves and is consulted
- how costs and benefits affect practices
- what will be decided later
- the deadline and consequence of no decision
This often reveals a governance problem. The firm may require broad consultation while lacking a clear decision owner. A meeting then becomes an attempt to discover requirements, settle strategy, allocate budget and approve delivery at once.
Separate those decisions and state the route for each one.
Surface conditional support
Ask each partner what would need to be true for them to support the next step. This is more useful than asking whether they support “digital”.
One partner may need evidence that clients use the website during selection. Another may accept the need yet dispute the timing. A practice leader may fear losing distinctive content or control. A finance partner may need a phased exposure. A risk owner may need clarity on data and accountability.
Record conditions and test them. Some are requirements; some are preferences; some are concerns that evidence can resolve. Do not label a colleague a blocker because they ask an awkward question. Equally, do not allow the same question to reopen after the agreed evidence has been provided without identifying what changed.
Private conversations can help people express concerns they will not raise in a large meeting. Summarise themes transparently and protect confidences. The aim is a more accurate shared picture, not a coalition built through side deals.
Use a diagnostic to buy evidence
A bounded diagnostic can be a sensible first commitment when the firm cannot responsibly approve a large programme. It should reduce specific uncertainties, rather than delay the real decision.
Define its questions in advance. These might concern client behaviour, platform support, content governance, accessibility, data integration, delivery options and total operating cost. Specify the evidence and the decision the diagnostic will inform.
The output should show findings, confidence, options and trade-offs. Avoid a maturity score that conveniently leads to a predetermined project. Partners need to see where observation ends and judgement begins.
Set the next decision date before the diagnostic starts. Otherwise, the firm may commission repeated discovery while the underlying service continues to deteriorate.
Benchmark without manufacturing urgency
External comparison can challenge insular assumptions. It can also mislead when a global competitor, an unverified result or an incompatible business model is used to provoke fear.
Choose relevant peers and inspect comparable client tasks. Record the source, method and date. Use external evidence to show what is possible or becoming expected, then return to the firm's strategy and clients.
The related article on how firms in your sector are investing in digital explains how to use benchmarks with their limitations attached.
A competitor's new portal is not a business case. Evidence that the firm's clients struggle with the same journey may be.
Design a shared foundation with meaningful variation
“My practice is different” may be true. Corporate transactions, private-client work and disputes can involve different audiences, evidence, journeys and duties.
The useful distinction is between shared capabilities and practice-specific expression. Identity, accessibility, security, analytics, content governance and core components may belong to a common foundation. Proposition, proof, terminology and some workflows may vary.
Show this through examples. Ask each practice to define priority audiences and tasks, then map where needs converge and differ. Make the costs of unnecessary variation visible: duplicated platforms, inconsistent records, fragmented support and slower change.
Standardisation should earn its place by improving the firm-wide service. It should not erase a practice's valid requirements for administrative neatness.
Match participation to accountability
A list of stakeholders is insufficient. People need to know what contribution is required, when and why.
Map partners and teams by decision role, affected work, knowledge and influence. Include operational colleagues who will run the service and clients or users who experience it. Identify who can make binding decisions on scope, content, risk and budget.
Ask for bounded participation: a decision in a named meeting, review of specific evidence, attendance at a user-research session or ownership of content approval by a date. General requests to “engage with the project” are easy to ignore.
When people cannot contribute, use the agreed escalation and delegation route. Do not allow calendar availability to become an accidental veto.
Phase delivery around learning
Phasing can reduce exposure and create evidence. It becomes political theatre when the first phase is selected solely for visibility or when later phases are assumed to be approved already.
Choose a coherent slice of service that tests important assumptions and can deliver value safely. Establish a baseline and success criteria. Include the operating changes required, not only the interface.
At the gate review, present results and failures against the criteria. The options should include continue, change, pause or stop. A weak result is useful if it prevents a larger mistake.
Early evidence can increase confidence, though it should not be overclaimed. A short pilot in one practice may not predict adoption, cost or integration across the firm.
Define alignment in observable terms
For a programme to proceed, the firm needs:
- an authorised decision and named sponsor
- understood scope and constraints
- owners for benefits, risks and service operation
- committed time from relevant practices
- an agreed route for resolving new disagreement
- measures and review dates
- no unresolved issue that makes delivery unsafe
People may still prefer another option. Record material dissent and the reason for the decision. This gives later reviews a fair account and prevents disagreement being rewritten as sabotage.
Commitment is visible in behaviour: decisions arrive, subject specialists participate, content owners meet obligations and leaders explain the programme consistently. A vote without those conditions is fragile.
Handle late challenges fairly
New evidence may justify reopening a decision. Define what counts: a material cost change, regulatory issue, client finding or technical constraint. A preference already considered does not automatically restart the process.
Use a change-control route with an impact assessment and accountable decision maker. This protects the programme from drift while allowing responsible correction.
The same discipline applies to scope requests from supportive partners. Enthusiasm can destabilise a programme as easily as scepticism.
A practical starting point
Take the next stalled initiative and prepare a one-page decision record. State the problem, immediate decision, options, evidence, roles and deadline. Speak to partners individually about their conditions for support, then publish the themes and what will be tested.
If evidence is inadequate, commission the smallest diagnostic that can close the important gaps. If decision rights are inadequate, resolve them before delivery. If practices differ, show which needs require variation and which foundations should be shared.
The stakeholder alignment planning template available below provides a structure for the map, decision conditions and phased evidence. Use it to make disagreement workable, rather than to categorise people as allies and opponents.
Partnership leadership is demonstrated by enabling a legitimate decision and carrying it through with accountability. The goal is neither permission from everyone nor compliance produced by force. It is enough shared understanding, evidence and commitment for the firm to move without pretending the differences have disappeared.
