hermes
55 entries · 52 prompts, 2 personas, 1 workflows

Roadmapping

Roadmaps, release plans and communicating them to stakeholders.

Start here 1

The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.

Search and filter in Roadmapping
  • Build an outcome roadmap

    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.

Specific 49

One situation, audience, tool or format inside the category. Example: Plan a road trip with children.

  • Decline a feature request

    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.

  • Plan a release

    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.

  • Plan stakeholder alignment

    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.

  • Prioritize features

    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.

  • Prepare quarterly planning

    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.

  • Technical program manager

    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.

  • Teach me roadmapping basics

    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.

  • Write a roadmap update

    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.

  • Build a user story map

    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.

  • Answer a customer's roadmap question

    Writes a reply to a customer asking when a feature will ship that is honest about status and certainty, avoids promises the team cannot keep, and gives what they can plan around today.

  • Critique a roadmap

    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.

  • Map cross-team dependencies

    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.

  • Play a roadmap trade-off game

    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.

  • Push back on a roadmap request

    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.

  • Allocate capacity across departments

    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.

  • Choose a roadmap tool

    Compares roadmap tools against the team's size, planning process, audiences and integrations, recommends one with a trial plan, and says when a spreadsheet or the tracker already in use is enough.

  • Design a roadmap visual

    Chooses how to show a roadmap to a given audience - format, level of detail, dates or horizons, labels and what to leave out - and drafts the slide or board layout ready to build.

  • Internal tools product manager

    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.

  • Plan cross-platform feature parity

    Sets the rules for shipping features across web, iOS, Android and desktop - which platform leads, which gaps are acceptable, parity targets per feature type and how parity debt is tracked.

  • Reset an overloaded roadmap
    WorkflowRoadmapping

    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.

  • Run a betting table

    Prepares and runs a Shape Up style betting table for the next cycle - checks each pitch is ready, sizes appetite against team slots, frames the bets and records what was not bet on and why.

  • Run a roadmap retrospective

    Compares last period's roadmap with what actually shipped and what it achieved, measures predictability, finds why plans slipped and turns the causes into changes for next planning.

  • Run a roadmap workshop

    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.

  • Set roadmap change rules

    Writes the rules for changing a committed roadmap mid-period - what counts as a change, who can approve it, the swap rule, an emergency lane and how changes are logged and announced.

  • Write a public roadmap

    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.

  • Align a roadmap to OKRs

    Maps each roadmap item to the objective or key result it should move, flags orphan items and key results with no work behind them, and proposes what to add, cut or reword.

  • Audit roadmap promises made to customers
    PromptRoadmappingLegal · safety checks

    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.

  • Build an annual product roadmap

    Builds a yearly product roadmap from strategy with themes, quarter placement, an investment split, capacity check and confidence that drops the further out an item sits.

  • Build a hardware product roadmap

    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.

  • Plan discovery and delivery tracks

    Plans a dual-track roadmap showing discovery items with learning goals next to delivery items, with capacity for each and the evidence an idea needs to move into delivery.

  • Plan a public service roadmap

    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.

  • Plan a roadmap around platform deadlines

    Builds a yearly calendar of platform-driven work - mobile OS releases, store policy changes, browser changes, vendor API deprecations - and fits it into the roadmap with owners and buffers.

  • Plan a roadmap against runway
    PromptRoadmappingMoney · safety checks

    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.

  • Plan a seasonal product calendar

    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.

  • Run a mid-quarter roadmap check

    Runs a mid-quarter roadmap check that marks each item on track, at risk or off track with evidence and causes, and sets out the decisions needed now while there is still time to act.

  • Set the roadmap investment mix

    Sets how team capacity splits between new features, improvements, tech debt and bugs, with guardrails, how the mix shifts by product stage, and how to track it against reality.

  • Set up a roadmap cadence

    Sets up how a roadmap is kept and shared - one source of truth, item fields, status and confidence labels, views per audience, update rhythm and owners - so it stays current without heroics.

  • Take over an inherited roadmap

    Helps a product manager who has inherited a roadmap find what is really committed, who promised what, what is stale or unfunded, and plan the first 30 days before changing anything.

  • Write a cross-team roadmap request

    Writes a request asking another team to put your dependency on their roadmap, with the specific ask, why it matters, the cost of a no, the date needed and options that make yes easier.

  • Write an open-source project roadmap

    Writes a public roadmap for an open-source project that respects volunteer capacity, separates maintainer plans from help-wanted work, links proposals and states what the project will not take.

  • Fit a regulatory deadline into the roadmap

    Plans product work for a fixed legal or regulatory deadline - confirmed obligations, scope to meet them, a backward schedule with buffers, what it displaces and the open questions for legal.

  • Map the roadmap against the customer journey

    Overlays a roadmap on the customer journey to show which stages get investment and which are neglected, weighs that against where customers struggle, and suggests rebalancing.

  • Plan a roadmap around a fixed event

    Plans product work backwards from a fixed conference, keynote or trade show date, with scope tiers, a cut-line, decision dates and a fallback story if the cut-line is reached.

  • Brief a board on the roadmap

    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.

  • Forecast roadmap dates with ranges

    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.

  • Practise pushing back on a stakeholder

    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.

  • Write the roadmap for investors

    Writes the roadmap section of an investor pitch or data room that ties product milestones to use of funds, proof points and the next round, without overpromising.

  • Write a roadmap guide for sales

    Writes a guide telling sales and account teams what they may say about the roadmap - item by item certainty, approved phrasing, what never to promise, and how to request a commitment.

  • Plan a roadmap with a hiring ramp

    Plans roadmap capacity while a team is growing, counting time to hire, onboarding ramp and the drag on existing staff, so the plan does not assume new people are productive on day one.

Advanced 5

Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.

  • Compare roadmap scenarios

    Lays out two or three alternative roadmaps under different budgets, headcount or priorities side by side, with what each delivers, gives up and risks, for a leadership decision.

  • Consolidate team roadmaps

    Combines several teams' roadmaps into one portfolio view, linking items to shared goals and exposing duplicates, conflicts, gaps and overloaded dependencies for leadership to decide.

  • Estimate cost of delay

    Estimates the cost of delay for roadmap items, gives each an urgency profile, and sequences them by cost of delay divided by duration, with every assumption shown.

  • Resolve conflicting stakeholder priorities

    Prepares a decision paper when two leaders want conflicting roadmap priorities, framing the options, trade-offs and evidence fairly, with a recommendation and the decision to escalate.

  • Plan a customer migration program

    Plans moving all customers from a legacy product, platform or version to a new one in waves, with cohort rules, readiness gates, support capacity, communications and rollback rules.