Roadmapping

Splits an internal tools or platform team's capacity across requesting departments with a scored intake, a run-the-business share, a buffer and a published allocation others can challenge.

Audits feature and date promises found in contracts, sales emails and call notes into a register with source, wording strength, owner, risk and revenue at stake, and drafts honest follow-ups.

Prepares a roadmap briefing for a board, trustees or co-op committee covering the few bets that matter, cost, what was cut, risks and the decisions asked, plus answers to likely questions.

Builds a physical product roadmap with EVT, DVT and PVT gates, tooling and part lead times, certification, factory slots and retail deadlines, showing the latest safe date for each decision.

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.

Reviews an existing roadmap for overcommitment, features without outcomes, thin evidence, false date precision, hidden dependencies and no room for maintenance, with severity-rated fixes.

Writes a reply to a customer whose feature request will not be built that says no clearly, shows the need was understood, gives the honest reason and offers real alternatives.

Forecasts when roadmap items will land from the team's past throughput and remaining work, giving 50 and 85 percent dates instead of one date, with a plain message for stakeholders.

Acts as a product manager for internal tools who treats colleagues as customers, measures time saved and errors avoided, runs a transparent intake and plans change as carefully as the build.

Maps the dependencies across teams for an initiative into a register with owners, need-by dates, risks, the critical path and a coordination and escalation cadence.

Plans a public or charity service roadmap around policy deadlines, funding cycles, procurement, governance and legacy contracts, separating fixed dates from preferences and showing risks openly.

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.

Plans an early-stage startup roadmap backwards from cash runway and the milestones the next raise or break-even needs, with the few bets that move them, a cut list and checkpoints.

Builds a 12-month calendar for seasonal goods working back from selling windows to buyer deadlines, trade shows, samples, production and shipping, with the latest safe date per decision.

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.

Runs a turn-based game where you manage a product team's quarter at fixed capacity while events arrive, scoring trade-offs on outcomes, trust and team health, then debriefs your patterns.

Lets a product manager rehearse saying no or not yet to a senior stakeholder's request, with the assistant pushing back like an executive, then reviews their clarity, tone and trade-offs offered.

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.

Resets an overcommitted roadmap in gated steps - inventory every commitment and its source, compare with real capacity, re-prioritise, agree what stops and tell each stakeholder group.

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.

Plans a half-day cross-functional roadmap workshop with pre-reads, a timed agenda, capacity-limited voting, decision rules and the output, keeping the decision with a named owner.

Teaches roadmapping to a beginner or accidental product owner through short lessons on their own work, with an exercise after each and a first draft roadmap at the end.

Acts as a technical program manager who maps dependencies, surfaces risks early, keeps decisions moving and reports status plainly, without spin. For cross-team engineering and product initiatives.

Turns an internal roadmap into a public one with themes, now-next-later items in customer language, careful commitments, a holdback list and a way for customers to give feedback.

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.