In short
- Five partners with five plans give a steering committee five versions of the truth.
- Make planning and reporting inside your own system a condition of every contract.
- Partners rotate; the plan, the decisions and the know-how should stay with you.
The steering committee pack has five sections, one per partner. The strategy firm reports on the roadmap. The system integrator reports on the build. The technology vendor reports on its platform. A specialist firm reports on cyber security. An interim leader reports on the operating model. Each section is well made, and each uses its own plan, its own status scale and its own dates.
The integration slips. The integrator's report says it is waiting for the vendor's interface. The vendor's report says it is waiting for the client's data. The roadmap assumed both would be on time. Nobody is wrong, and nobody owns the slip.
The client's transformation office spends the next fortnight reconciling five versions of the truth so that the committee can decide anything at all.
What goes wrong
Most organisations now deliver transformation with several partners at once. That is sensible: no single firm has every skill. The trouble is in how the partners are contracted and joined up.
Each partner brings its own plan. The partner's plan is part of its method, and often part of its contract. So the client ends up with several plans that overlap at the edges and disagree on the dates where they meet. The joins, which are where transformations fail, appear in nobody's plan.
Each partner reports its own version. Status scales, definitions of done and reporting dates differ. Leaders wait for the reports to be reconciled before they decide, so decisions are taken on information that is weeks old.
Accountability falls between contracts. When something slips, every contract points somewhere else. Each partner can show that it met its own obligations, and the outcome the client paid for belongs to none of them.
Knowledge walks out with each firm. The analysis, the decisions and the reasons behind them sit in the partner's files. When the engagement ends, the next partner starts again, and the client pays twice to learn the same thing.
The client is left stitching by hand. The transformation office becomes a reconciliation team: copying dates between plans, translating status scales and chasing each firm for its update. That is the opposite of the orchestration it was set up to do.
What good looks like
The fix is not fewer partners. It is a different relationship between the partners and the client's own model. Five steps, which I suggest buyers write into the way they contract.
Start from the need, not the firm
Begin with the gap the programme has: an integration that keeps slipping, a cyber exposure, a capability the organisation lacks. Then decide what kind of expertise closes it. Buying a firm first and working out its scope second is how overlapping plans begin.
Buy expertise for a defined piece
Contract for a stated outcome and a stated period: a sprint, a phase, a specific deliverable. A large team on day rates for an open-ended period is expensive, and it makes the partner the de facto owner of the plan.
Put every partner inside your model
Make it a condition of the contract that the partner plans and reports in the client's own system, with the same data, the same rights model and the same audit trail as the client's own teams. Their milestones sit in the client's plan, their dependencies on other partners are recorded as links between projects, and their status uses the client's scale. One plan, one set of dates, one record.
This does not mean a partner has to give up its own working tools. Its engineers can keep their task boards and its analysts their models. What matters is that the commitments the client steers by, the milestones, dates, status, risks and decisions, live in the client's model and are updated there. The partner's internal method is its business; the client's plan is the client's.
Govern delivery through your own approvals
A partner's change to a date, a scope or a budget should travel the same approval route as one raised by the client's own staff. The client approves; the partner delivers against the client's gates. That one rule keeps accountability with the organisation that pays for the outcome.
Keep the know-how when partners rotate
Because the plan, the decisions and the reasons for them live in the client's system, a partner's departure takes nothing with it that the client needs. The next partner starts from the record, not from zero. What should be left behind at the end of an engagement is covered in what a transformation partner should leave behind, and the wider shift to an owned office in the next-generation transformation office.
In Lodestar, a partner's people can be granted access project by project, under a role that sets what they may do, and the changes they raise follow the same approval routes as everyone else's. The resource view separates internal and external people and flags critical-path work assigned to an external person as a delivery risk. A partner's update is entered once, in the client's plan, and rolls up from there to every level that reads it, from the project team to the steering committee, without being re-keyed into anyone's report.
Questions for your next review
- How many separate plans do our partners keep, and who reconciles the dates where they meet?
- Do our contracts require partners to plan and report in our own system?
- When a partner raises a change, does it go through our approval route or theirs?
- If our largest partner left next month, what would we lose that we cannot find in our own record?
A transformation with many partners needs one place where their work meets. When that place belongs to the client, the client orchestrates; when it does not, the client stitches.
