Overview
End-to-end strategic paths addressing specific organizational questions
A Pipeline is an end-to-end strategic path. Each pipeline answers one specific strategic question and composes 2–4 techniques in sequence. Think of pipelines as the journeys of the methodology — choose the one that matches your current question, and the techniques inside are the legs of that journey.
The pipelines fall into two thematic lines. The first is about what to build — the platform/product strategy arc (the classic "macro-problems"). The second is about how to organize to build and operate it — the platform-organization (3EO) arc. Restructuring the Portfolio is the bridge between them.
Platform & Product Strategy
The linear arc of a new platform engagement: from understanding the ecosystem to engineering sustainable growth.
Understanding the Ecosystem
Landscape the territory, profile entities, articulate value propositions, validate assumptions — before committing to platform design.
Designing the Platform Experience
From a validated ecosystem to a designed platform — relationships, flywheels, transaction engine, learning engine.
Bringing the Platform to Market
Frame the Platform Strategy Model, solve the chicken-and-egg liquidity problem, choose the launch tactics.
Engineering Sustainable Growth
After liquidity: growth loops, cohort metrics, the quantitative growth model.
Organizational Design
How the organization is structured and operated as a platform — the 3EO arc. Restructuring the Portfolio is the junction with the strategy line.
Restructuring the Portfolio
Map customer needs, offerings, GTM and capabilities in one picture; realign the portfolio and the operating model. The bridge between strategy and org design.
Adopting Distributed P&L
Move an internal unit from centralized budget to financial autonomy through three layers: catalog visibility, virtual economics, real P&L.
Launching Initiatives in a Distributed Organization
Launch by composing existing internal capabilities — treating the launch as the formation of a temporary, outcome-anchored ecosystem of contributors.
Picking a pipeline
| Your question right now | Pipeline to start with |
|---|---|
| "We need to understand who's in our ecosystem and where we fit." | Understanding the Ecosystem |
| "We have an ecosystem map — now how do we design the platform experience?" | Designing the Platform Experience |
| "How do we launch the platform and reach the liquidity tipping point?" | Bringing the Platform to Market |
| "We're past liquidity — how do we keep growing without burning cash?" | Engineering Sustainable Growth |
| "We have overlapping products and an unclear org structure — how do we restructure?" | Restructuring the Portfolio |
| "Our internal services feel like cost centers — how do we give them P&L autonomy?" | Adopting Distributed P&L |
| "We need to launch something new on top of our internal capabilities — how?" | Launching Initiatives in a Distributed Organization |
How they chain
The pipelines can run independently or compose. The natural sequence for a new platform engagement runs down the strategy line:
The organizational-design line is entered when growth or structure surfaces tensions about how the organization itself is built:
Restructuring the Portfolio is the junction: it can run independently, often kicked off by a strategic question about the organization itself, but it benefits from outputs of Understanding the Ecosystem (the customer ecosystem layer is partially populated by ecosystem scans). Adopting Distributed P&L is a prerequisite for the platform operating model — its financial visibility is what makes the multi-party contracts in Launching Initiatives executable. All pipelines are circular: expect to revisit them as later work surfaces gaps.