Operating Model
The cadence and the handoffs.
Where roadmap discipline decides what enters the plan and org design decides who owns what, the operating model decides the rhythm the plan runs at — and the specific interfaces between product, engineering, design, GTM, and support.
Most breakdowns at 100–400 people aren't about strategy. They're about a discovery loop that runs on ad-hoc Slack threads, a GTM handoff that happens the week of launch, and a planning cadence copied from a 20-person team that stopped scaling three quarters ago.
In short
Operating Model Design is a 6–8 week engagement for product organisations at 100–400 people where planning cadence, discovery, and PM–engineering–GTM handoffs no longer scale. We rewrite the cadence, redraw the interfaces between functions, then sit in on the first two planning cycles to adjust in real time. Output: a 10–15 page operating manual and two live cycles run under the new model.
- Duration
- 6–8 weeks
- Best fit
- Product orgs at 100–400 people
- Sponsor
- CPO, VP Product, or COO
What the redesign covers
- A planning cadence — quarterly bets, monthly checkpoints, weekly reviews — with named inputs and decisions at each step
- A discovery loop that produces evidence before commitment, not case studies after launch
- The PM–engineering interface: spec quality bar, when eng is looped in, who owns non-functional trade-offs
- The product–GTM interface: launch tiers, enablement lead time, and the feedback funnel back into the roadmap
- An escalation path so blockers surface in days rather than sprints
How the engagement runs
6–8 weeks, 3 phases, one handoff.
Weeks 1–2
Where it breaks
Trace the last three launches end-to-end. Interview PM, eng, design, GTM, and support on the same launches. Surface the specific interfaces that fail under load — not the ones people complain about most.
Weeks 3–5
Redesign
Rewrite the planning cadence, redraw the PM–eng and product–GTM handoffs, and produce a 10–15 page operating manual. Every interface has a named owner, an input contract, and an escalation route.
Weeks 6–8
Two cycles under the new model
We sit in on the next two planning cycles and the two launches inside them. Tune in real time when a ceremony doesn't produce the decision it was designed to produce.
Representative outcomes
What changes on the ground.
- → Launch cycles predictable — GTM enablement lands 2–3 weeks before ship, not on launch day.
- → Discovery loop produces one written finding per bet before engineering commitment.
- → Cross-functional blockers escalate in days, not sprints — escalation path is written down and used.
- → New PMs and engineers onboard against a manual, not tribal knowledge.
When to bring us in
Typical trigger: the product org has crossed 100 people and the cadence copied from the 30-person days is starting to leak. Or a merger has bolted two operating rhythms together without deciding which one wins. Or launches keep slipping and the postmortems all point at the same three interfaces.
Frequently asked
Product Operating Model Design — answered.
- Do you deliver a slide deck?
- No. The deliverable is a written 10–15 page operating manual, a live redesign of the next two planning cycles, and a two-week bedding-in period where we sit in on the new ceremonies and adjust. Slideware doesn't survive contact with a real launch.
- Is this an agile transformation?
- No. We don't take a side on agile, SAFe, or Shape Up. We start from your actual constraints and design the cadence that fits the size and stage of the org.
- Who needs to be in the room?
- The CPO or VP Product sponsors it. Engineering leadership, design leadership, and one GTM leader are in every workshop. Every interface we redesign needs both sides in the room when it's decided.
- How does this differ from roadmap discipline?
- Roadmap Discipline fixes what enters the plan. Operating Model Design fixes the rhythm the plan runs at and the handoffs between functions. Teams often need both, in that order.
Next step
Before committing capital, changing pricing, or restructuring product teams — let's talk.
We will be direct about whether an engagement is the right answer, and what scope would make it useful.