A transformation office should be designed around the work the organisation needs help to do.

Establishing a transformation office is an organisational design decision. It changes how information moves, where problems are resolved and which roles coordinate work across established boundaries. Its structure should follow a clear account of what the organisation needs from it.

Without that account, the office can acquire responsibilities by default. It chases updates, resolves gaps between teams and becomes the place where difficult questions accumulate. Leaders may then struggle to distinguish a capacity problem from an unclear mandate.

The Project Routemap governance module highlights defined authority, escalation routes and terms of reference. These are useful design considerations for a transformation office; the model proposed below should be adapted to the organisation's context. Project Routemap: Governance.

Define the problem the office will solve

Begin with specific delivery difficulties. Are programmes competing for the same resources? Are cross-functional dependencies unresolved? Do leaders lack a reliable view of progress? Are teams missing the capability to structure and manage complex change?

Different problems call for different services. An office created to coordinate enterprise dependencies needs different capabilities from one established to coach inexperienced programme teams. Trying to provide every possible service from the outset makes priorities harder to sustain.

Write a short purpose statement connecting the office to the decisions and work it will improve. Test it with executive sponsors, operational leaders and programme managers. Each should be able to explain why the office exists and when they would use it.

Specify the services and their users

Describe what the office will provide, who will use it and what each service requires from other teams. Possible services include portfolio coordination, delivery planning, decision preparation, capability development and the consolidation of reliable management information.

Define the output in practical terms. “Support governance” could mean preparing a decision schedule, checking that papers contain viable options or tracking agreed actions. These are different activities with different effort requirements.

Set boundaries for each service. If the office assembles a portfolio view, project owners still need to provide accurate information and explain changes. If it facilitates planning, the delivery leads remain responsible for the commitments they make. Make these relationships explicit before introducing new templates.

Match authority to the expected intervention

Clarify which matters the office can resolve itself, which it can recommend and which it must escalate. The answer may differ across priorities, resources, scope, standards and timing.

Avoid expecting the office to secure changes that only an executive sponsor can authorise. Give it a direct route to the right decision-maker, with clear criteria for escalation and a reasonable response expectation.

In a hypothetical organisation, two programmes might disagree about the sequence of a shared system change. The office could assemble the evidence and broker an option. If the choice changes an approved service commitment, the designated executive should make the decision. Recording this boundary prevents coordination from becoming unacknowledged approval authority.

Establish a working agreement with the business

Agree how the office and operational teams will work together. Identify the information required, the support available and the points at which the office should become involved.

Use existing management routines where they serve the purpose. A new reporting cycle should earn its place by supporting a decision or reducing a material information gap. Repeatedly asking for the same data in different formats consumes the capacity the office is meant to help organise.

Create a route for teams to challenge requirements that add effort without a clear use. Treat those challenges as design feedback. The office's credibility should come partly from improving the working arrangements around delivery.

Staff for the mandate and the stage of change

Translate the service commitments into capabilities and workload. Coordination, analysis, change management, planning and executive communication are related skills, but they are not interchangeable.

Decide which capabilities belong in the central office and which should remain close to programmes or operations. A small central team may maintain common methods while specialists support particular initiatives. Another organisation may need temporary hands-on delivery support while internal capability develops.

Make temporary responsibilities visible. If the office takes on work because a business role is vacant or underdeveloped, specify the receiving owner and a route to transfer it. Otherwise, an interim arrangement can become an enduring dependency without a conscious decision.

Protect the quality of challenge

An office deeply involved in delivery can provide valuable context, but its involvement should be considered when designing assurance. Leaders need to know whether a view is management's assessment or an independent review.

Separate those purposes proportionately. The office may maintain evidence, identify inconsistencies and coordinate responses, while appropriately independent people examine the areas requiring impartial challenge.

Allow concerns to reach the accountable sponsor without being softened to preserve an attractive portfolio picture. Reporting standards should make uncertainty and disagreement understandable. They should also make it possible to acknowledge progress when evidence supports it.

Measure usefulness and plan the next form of the office

Review whether the office is solving the problems in its mandate. Examine unresolved dependencies, the quality of decisions, the reliability of commitments and the ability of teams to manage change. Use feedback from the people receiving its services alongside the operating evidence.

Activity measures can help explain workload, but a count of reports or meetings does not establish value. Investigate whether recurring issues are being resolved and whether teams can act on the information provided.

Set a review point for the office's future. Some functions may become permanent portfolio management capabilities; others may transfer into operations or close when the transformation ends. Agree the evidence for that decision early, then revisit it as the organisation's needs change.

Executive questions

  • Which specific delivery problems justify this office?
  • What services will it provide, and who remains accountable for the underlying work?
  • Can its authority support the interventions we expect from it?
  • Where would independent challenge add value?
  • Which capabilities should the organisation retain when the temporary mandate ends?

JP Associates helps organisations define transformation mandates, clarify working relationships and design practical operating arrangements that strengthen delivery capability.