Start with the outcome
Select a cycle for the current initiative instead of treating every station as a mandatory maturity ladder.
Connected journeys
One method. Multiple cycles.
API and integration products do not move through a single funnel. Choose the cycle that matches the outcome in front of you, then cross into another journey when the work changes.
Explore the complete method mapMethod structure
Journeys overlap where the work overlaps
Cycles supply goal-oriented sequences, while metro lines connect related practices across those sequences. Shared stations make handoffs explicit rather than duplicating guidance.
Keep canonical order
Each cycle provides a deliberate station sequence, giving teams a coherent path while leaving room to enter where their work actually begins.
Cross cycle boundaries
Metro lines reveal the same practice in different journeys, making it easy to continue a concern such as design, governance, or operations.
Reuse shared stations
A station can participate in multiple cycles. Its decisions and resources stay consistent while the surrounding journey context changes.
Four connected cycles
Choose the journey that fits the work
Every cycle offers its own ordered route through shared method stations. The metro lines below are the cross-cutting practices that connect them.
01Capability ProductizationTurn a business capability into a reusable digital capability before choosing its implementation style.02API ProductizationProductize, design, deliver, publish, and continuously improve an API.03Integration ProductizationShape reusable integration capabilities before selecting how they will be implemented.04AutomationIdentify, design, deliver, enable, and improve automation opportunities.
Put it to work
Choose your current journey
Open a cycle to follow its ordered journey, or choose a metro line to trace one practice across cycle boundaries.
Explore the complete method map