Roadmapping

Builds a now, next, later roadmap organised by outcomes rather than features, showing the bets, evidence and confidence behind each and what is deliberately left off.

Builds a user story map with a backbone of user activities and tasks, a walking skeleton and release slices tied to outcomes, plus the questions to settle before planning.

Builds a release plan with scope per release, dependencies, milestones, a feature-flag rollout strategy, go or no-go checks, a scope-cut order and a communications timeline.

Maps stakeholders for a product initiative by influence and interest, with their concerns and decision roles, and builds a sequenced alignment plan with messages and meetings.

Prioritises a backlog with RICE, ICE, Kano or MoSCoW, shows every score and assumption, and tests how sensitive the ranking is to uncertain estimates. Use before roadmap planning.

Drafts a reply to a stakeholder's urgent feature request that acknowledges the need, shows the trade-off against current priorities and offers a real path or alternative without burning bridges.

Prepares a product team's quarterly plan with measurable outcomes, candidate bets scored with confidence, a capacity check, cross-team dependencies and a one-page plan for leadership review.

Writes a stakeholder update on roadmap changes that says what moved, why, what was traded off and what the readers need to do, tailored to the audience. Use after replanning.