Interim and fractional CPTO in short
An interim or fractional CPTO holds product and technology as one seat: what to build, how to build it and which teams deliver it, decided by one executive. The interim keeps the roadmap and the architecture moving together through the transition, so trade-offs are settled once, until a permanent CPTO takes the seat.
Make product ambition and engineering capacity meet.
The roadmap and the technology organisation are changing at the same time. Product priorities cannot be set independently of architecture, capacity and the cost of delivery.
The interim CPTO leads both functions. The role makes the trade-offs across what to build, how to build it and which teams can deliver it, keeping product direction and technology execution connected through the transition.
When to bring in an interim CPTO
- Product and engineering pull in opposite directions: the roadmap promises what the architecture cannot carry, and no single executive can settle the conflict between them.
- The platform has to be re-architected while the roadmap keeps shipping to customers, and nobody owns the trade-off between the two.
- The business is entering a regulated market, and product scope, architecture and evidence of compliance now have to be decided together.
- The product and technology leader has left, and decisions on scope, architecture and team capacity have stalled at once.
When it is the wrong answer
- Product already has a leader, and what lacks an owner is architecture, engineering and delivery. The CTO seat holds technology on its own.
- Technology has its own executive, and the gap is in product choices: value, priority and the portfolio. The CPO seat leads product on its own.
- Product and technology agree on where to go, and what is missing is the capacity to get there. An Expertise adds that capacity without taking the seat.
What the CPTO holds
- The roadmap: what gets built, in which order, and what is dropped when capacity runs short.
- Architecture: the target design, and which parts of the platform change while the roadmap keeps running on them.
- The cost of delivery: product ambition priced in engineering effort before it is promised to the business.
- Team shape: product, design and engineering organised around shared goals, with one line of accountability.
- Regulatory requirements, whenever the business enters a regulated market: what product scope and architecture must meet, decided before the build rather than after it.
The first 90 days
Days 1 to 30
- Agree the starting terms of the mandate: the product and technology decisions the seat owns, what success will be measured on, who the CPTO answers to and how the seat is passed on.
- Put the roadmap and the architecture side by side, and list where one promises what the other cannot deliver.
Days 31 to 60
- Reset the roadmap against real engineering capacity, and decide which re-architecture work runs alongside it.
- Organise product, design and engineering into teams that share goals rather than hand work to each other.
Days 61 to 90
- Run planning as one forum where product scope and technical cost are decided together.
- Identify who will lead product and technology next, and pass them the trade-offs the interim has been making.
What you keep
- One roadmap that engineering has costed and product has prioritised.
- A target architecture tied to that roadmap, with the order in which the platform changes.
- Teams organised around shared product goals, each with a named lead.
- A planning forum that weighs every promise against its engineering effort.
- For a regulated market, the requirements written into product scope and architecture, each with an owner.
We leave when the function can run without us: an identified permanent owner, a roadmap they hold, and a team that no longer routes through the interim.
Questions
- What does an interim CPTO do?
- An interim CPTO leads product and technology as one function while it has no permanent leader. The interim decides what to build, how to build it and which teams can deliver it, keeps product direction and technology execution connected, and answers for both in the client's executive forum, so trade-offs stop travelling between two leaders.
- When is an interim CPTO the wrong answer?
- When only one half of the role lacks a leader: if technology is the gap, the CTO seat fits; if product choices are, the CPO seat fits. When product and technology agree on where to go and only capacity is missing, an Expertise adds it. Combining the two only helps when their decisions cannot be taken apart.
- What does the CPTO hand over at the end?
- A roadmap engineering has costed, a target architecture tied to it, teams organised around shared product goals, and a planning forum that weighs scope against engineering effort. The permanent CPTO receives a product and technology organisation that already arbitrates its own trade-offs instead of escalating them to two different executives.
- When is a CPTO the right role?
- When the roadmap and the technology organisation change at the same time, and product priorities cannot be set apart from architecture, capacity and the cost of delivery. A re-architecture under a live roadmap, or entry into a regulated market, are typical cases: one executive has to weigh product scope and technical consequences together.
- CPTO or CPO?
- If technology already has its own executive, a CPO leads the product decisions: value, priority and the portfolio. A CPTO leads both functions in one role, and fits when product choices keep running into architecture, capacity or regulation, so that splitting the seat would send every important decision back and forth.