Skip to content
← Product management

PLAN / ROADMAPS & CAPACITY

Plan what’s next.
Keep the why.

Connect priorities, dependencies and recorded capacity. Give the team a roadmap it can explain—and a way to challenge the plan.

A complete Product workspace. Connect the wider work when useful.
Roadmaps & capacity workflowSequence the work. Expose the dependencies.. An authored illustration with fictional planning examples. NowNextLater FOUNDATIONAccess rulesOwner review PROPOSED WORKExternal reviewDepends on access rules DRAFTReview remindersMore evidence needed PEOPLE CAPACITYSet availability before committing the planNot recorded
Sequence the work. Expose the dependencies.
Product workflow illustration · Fictional planning examples
01Now, Next & Later
02Dependencies & risks
03Capacity & scenarios

SEE THE WORK / MAKE A CHOICE

Choose the horizon.
Keep the reasoning.

Place a request in Next or Later, then revisit the assumptions behind its priority. Keep the reason for the timing attached.

Working demo screens · Fictional examples

PRODUCT / INSIDE THE DEMO

Give proposed work a place.

Place external-review sharing in Next or leave it in Later. Make the planning status explicit before moving into scope.

The demo illustrates the horizon decision. Capacity and dependency analysis are explained in the sections below.

Try a roadmap decisionInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Place external-review sharing in Next or leave it in Later. Make the planning status explicit before moving into scope.

PRODUCT / INSIDE THE DEMO

A bigger estimate changes the choice.

Move external review from an eight-day to a sixteen-day effort assumption. See the same demand produce a different ranking.

Keep demand fixed and change the effort estimate to see how the trade-off moves.

Try changing the estimateInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Move external review from an eight-day to a sixteen-day effort assumption. See the same demand produce a different ranking.
01

EXPLAIN THE PLAN

Give each piece of work a place.

Use Now, Next, Later and Done to show what is active, what may follow and what is finished, then switch to a timeline, presentation or export when the conversation needs it. Release milestones connect product intent to the stages of delivery.

Start with
Prioritized work, its state and the relevant release milestones.
Work toward
A roadmap that explains the order and horizon of planned work.
Detail of the Product demo with fictional example data
ProcessScout / Producta target window, not a promised date · fictional data
02

UNDERSTAND THE SEQUENCE

Find the work that must come first.

The dependency projection shows confirmed ordering, unreleased predecessors and cycles, with recorded risks beside them. A clear priority can still wait on other work, and the view names the condition that needs attention first.

Start with
Confirmed dependency links, predecessor release state and recorded risks.
Work toward
A view of ordering constraints and conditions that deserve review.
Detail of the Product demo with fictional example data
ProcessScout / Productan open question the work waits on · fictional data

HARBOR / THE WORKED EXAMPLE

A high priority can still have a predecessor.

In the fictional Harbor plan, external-review sharing sits in Next. The team examines whether a permission change must come first and records the dependency if confirmed. The resulting sequence remains separate from any forecast window or delivery commitment.

Walk through this example

NEXT, WITH ITS PREDECESSOR NAMED.

  1. HorizonExternal review sharing in Next
    RQ-184
  2. DependencyAccess rules settled first
    POL-03
  3. EffortEight days, an assumption
    ESTIMATE
  4. Release windowAfter a pilot review
    NO DATE
Fictional planning example · No result is claimed
03

CHECK THE DEMAND

Compare the plan with the capacity you have recorded.

Capacity compares Now and Next charter demand with credits, execution slots and recorded people availability, kept as separate kinds of supply. People estimates need linked process estimates and directory availability; incomplete inputs stay visible as gaps.

Start with
Now and Next demand, configured execution supply and recorded availability.
Work toward
A capacity comparison with visible constraints and missing inputs.

Demand against the supply you recorded

  1. Charter demandNow and Next
  2. Build supplyCredits and slots
  3. People capacityRecorded availability
Illustration · fictional example

THE PRACTICAL DETAILS

Reading the
roadmap.

Talk through your workflow
Can we present a roadmap without committing to dates?

Yes. Now, Next and Later communicate horizons and ordering. Timeline views add a timing perspective when the available evidence supports it.

Why might there be no forecast range?

Forecasts depend on sufficient history. When that basis is missing, the product leaves the range unavailable instead of inventing a delivery window.

Does capacity replace our staffing or sprint planner?

The implemented capacity view compares charter demand with recorded execution and people capacity. It is not a general workforce or sprint scheduling system, and incomplete estimates remain visible.

YOUR NEXT PRODUCT DECISION

Place the next piece of work.
Show what it depends on.

Try a fictional example, or bring one question from your product.

Product view

ProcessScout interactive demo · Fictional Harbor data