Decide faster which method fits right now.
288 Methods20 Categories12 Method forms
Favorites
Favorites are stored locally in the browser and appear through the favorites filter in the catalog.
288 Methods20 Categories12 Method forms
Favorites are stored locally in the browser and appear through the favorites filter in the catalog.
Turns scope, ordering, and flow into a tangible result by collecting items, assigning must/should/could/won't categories, and finalizing the release set.
Core question: Which items must be included in the release, which are negotiable, and how much scope remains for stakeholder negotiation?
Turns scope, sequencing, and delivery flow into a tangible result by listing stakeholders and audiences, clarifying information needs, and planning review and adaptation.
Core question: Which message reaches which audience through which channel in which cadence so the initiative is understood, accepted, and supported as planned?
Moves scope, sequence, and delivery flow toward a concrete result through "create a table for Risks, Assumptions, Issues, and Dependencies", "carry over initial entries from discovery and kickoff", and "archive resolved items instead of deleting them".
Core question: Which risks, assumptions, issues and dependencies are currently open, who takes care of them, and which ones need movement or escalation now?
Turns scope, sequence, and delivery flow into a tangible result through selecting a value stream, mapping current state, and designing a future state.
Core question: Where do waiting time, rework, and waste emerge between trigger and delivery, and which two or three interventions improve lead time most?
Moves scope, order, and delivery flow toward a concrete result through "adopt the initiative list", "clarify value types for each initiative, such as revenue, efficiency, or risk", and "derive a sorted sequence".
Core question: How much does each week cost us when this initiative is not delivered, and in which order should we maximize avoided loss?
Moves scope, sequence, and delivery flow toward a concrete result through "formulate the forecast question", "choose historical flow data", and "update the forecast regularly".
Core question: With what probability will the desired scope be finished by the target date (or how much scope can we complete by then), and which assumptions drive the distribution?
Structures product work around shaped pitches, bets, fixed cycles, hill charts, and scope hammering.
Core question: Which shaped pitches do we bet on for the next 6-week cycle, and how does the team deliver them autonomously in fixed time with negotiable scope?