The end-to-end walkthrough

Product Workspace

From a fresh idea to a shipped feature, walked step by step. 28 steps across six stages — every one backed by a page in the Product Workspace.

Running agents instead of sprints? The AI Delivery Lifecycle is the Studio equivalent of this walkthrough.

🔭

Strategy

Set the destination. What does this product exist to do, who is it for, and what outcomes will tell us we got there?

  1. 1
    🔭

    Product Vision

    The mission, the 3–5 year vision and the strategic goals.

    What happens
    Capture mission, vision statement, audience and a small number of strategic goals. Reviewed annually.
    Who leads
    Product Manager / Owner with executive sponsor
    Output
    A single Vision record per workspace.
    Open Product Vision
  2. 2
    🎯

    Outcomes

    Measurable results that move the strategy forward.

    What happens
    Define outcomes with key results (baseline, target, current). Each outcome has a target quarter and an owner.
    Who leads
    Product Manager
    Output
    Outcomes with key results.
    Open Outcomes
  3. 3
    🏔️

    Epics

    Large bodies of work that move outcomes.

    What happens
    Decompose outcomes into epics. Each epic gets an owner, target quarter and (when ready) a full design.
    Who leads
    Product Owner
    Output
    Epics linked to outcomes.
    Open Epics
🧭

Discovery

Understand the problem, the people and the flow before committing to build. New work also enters here through the Inbox.

  1. 1
    🧩

    Product Catalogue

    What we build, with lifecycle and migration paths.

    What happens
    Maintain platforms, domains, products, sub-products and components with purpose, audience, principles and an 8-phase lifecycle.
    Who leads
    Product Manager
    Output
    Product hierarchy with lifecycle state.
    Open Product Catalogue
  2. 2
    🗺️

    User Journeys

    How customers actually experience us, end to end.

    What happens
    Map top-level journeys and nested sub-journeys with purpose, desired outcome and linked work.
    Who leads
    UX Designer / BA
    Output
    Journey tree with personas.
    Open User Journeys
  3. 3
    👤

    Personas

    The people inside each journey.

    What happens
    Build persona canvases (goals, frustrations, motivations, channels) and map them onto journeys with role, involvement and emotional state.
    Who leads
    UX Designer
    Output
    Personas + journey mappings.
    Open Personas
  4. 4
    📊

    Value Stream Mapping

    Find the waste, design a better flow.

    What happens
    Three-step canvas — current state, target state, transition plan with improvements, risks and success metrics. Improvements can be promoted directly into Features or Stories with a bidirectional link back to the VSM.
    Who leads
    Scrum Master / Tech Lead
    Output
    VSM linked to a journey.
    Open Value Stream Mapping
  5. 5
    📥

    Inbox (Work Intake)

    A single front door for new requests.

    What happens
    Anyone submits requests, feedback, support issues or big-ticket ideas. Each captures problem, AC, impact of inaction, value and timescale.
    Who leads
    Anyone (triaged by Product Owner)
    Output
    Work Intake items.
    Open Inbox (Work Intake)
  6. 6
    🗳️

    Triage Sessions

    Time-boxed group decisions on incoming work.

    What happens
    Bundle Inbox items into a scheduled session with per-item timers. Each item is actioned, monitored or rejected — with a reason.
    Who leads
    Product Owner
    Output
    Triage decisions; actioned items become Features / Stories / Tasks / Bugs / Tech Debt.
    Open Triage Sessions
✏️

Shaping

Turn an epic or a triage decision into a feature with enough rigour to estimate, prioritise and plan.

  1. 1
    🧩

    Features

    Coherent slices of capability.

    What happens
    Create features with five lifecycle sections — Scoping, Assessment, Design, Development, Completion. Section dots show progress at a glance.
    Who leads
    Product Owner
    Output
    Features linked to epics.
    Open Features
  2. 2
    🧭

    Feature Designer

    Assisted breakdown of a feature into draft stories.

    What happens
    Walk problem, scope, MoSCoW requirements, risks and a phased delivery plan with draft stories / spikes / tasks. Promote drafts to real stories when ready.
    Who leads
    Product Owner + Tech Lead
    Output
    Feature design document; drafts ready to promote.
    Open Feature Designer
  3. 3
    📐

    T-Shirt Sizing

    A coarse complexity estimate per feature.

    What happens
    Compare candidate features to references the team has already shipped; pick a size XS–XXL. Minutes per feature.
    Who leads
    Tech Lead / team
    Output
    Each feature has a size.
    Open T-Shirt Sizing
  4. 4
    🎯

    Prioritisation (WSJF)

    Objective ranking by cost of delay over job size.

    What happens
    Score business value, time criticality, risk reduction and job size. The page computes WSJF and ranks the backlog.
    Who leads
    Product Owner with team
    Output
    A defensible feature ranking.
    Open Prioritisation (WSJF)
  5. 5
    🧩

    Scheduling Assistant

    Tetris-fit the prioritised list onto real capacity and constraints.

    What happens
    Each feature is placed as a block (width = assigned people, height = SP ÷ (people × velocity)) onto a 26-week canvas. Constraint conflicts (specific people or limited roles) push features later and surface a reshuffle indicator.
    Who leads
    Product Owner + Delivery Manager
    Output
    Realistic start / end dates per feature and an early signal for capacity bottlenecks.
    Open Scheduling Assistant
  6. 6
    🗺️

    Roadmap

    Features mapped to quarters.

    What happens
    Assign features to target quarters; the page warns when a quarter exceeds historical throughput.
    Who leads
    Product Owner
    Output
    Quarterly view that the team and stakeholders share.
    Open Roadmap
📋

Planning

From refined backlog to a committed sprint, with capacity that reflects reality.

  1. 1
    📋

    Work Items

    The smallest committed unit of work.

    What happens
    Break features down into work items — stories, tasks, bugs, tech-debt and spikes. Each has acceptance criteria, tags, severity (bugs) or effort (tech-debt).
    Who leads
    Product Owner + Engineers
    Output
    A backlog of work items per feature.
    Open Work Items
  2. 2
    🔎

    Story Refinement

    Continuous backlog grooming.

    What happens
    The Refinement page surfaces stories missing AC, points or a feature link. Inline edit; queue for the next pointing session.
    Who leads
    Product Owner
    Output
    Two sprints of refined work ahead of the current sprint.
    Open Story Refinement
  3. 3
    🔧

    Tech Debt Register

    Make compromises visible and unavoidable.

    What happens
    Every story typed as tech-debt aggregates into a register with status, effort and a debt ratio across the backlog.
    Who leads
    Tech Lead
    Output
    Debt ratio metric and prioritised remediation list.
    Open Tech Debt Register
  4. 4
    🃏

    Story Pointing

    Relative complexity, set by the team.

    What happens
    Open a session, vote privately, reveal, discuss outliers, agree the value. Custom or Fibonacci scales.
    Who leads
    Scrum Master
    Output
    Each ready story has agreed points.
    Open Story Pointing
  5. 5
    👥

    Teams & Capacity

    Who is available and how much.

    What happens
    Define teams, allocate members with split percentages, set per-team unplanned reserves, account for absences.
    Who leads
    Delivery Manager
    Output
    Per-sprint capacity that reflects reality.
    Open Teams & Capacity
  6. 6
    🏃

    Sprint Planning

    Commit to a sprint goal and a story set.

    What happens
    Set the sprint window, write the goal, drag refined stories into the sprint until allocated points equal target capacity.
    Who leads
    Product Owner with team
    Output
    A committed sprint with goal and stories.
    Open Sprint Planning
🔨

Execution

Run the sprint — keep the team aligned day by day, watch the trend, finish what was started.

  1. 1
    📌

    Sprint Board

    Where work flows.

    What happens
    Kanban across To Do → In Progress → Review → Done. Drag-and-drop or status dropdown updates and audits the change.
    Who leads
    Whole team
    Output
    Live state of the sprint.
    Open Sprint Board
  2. 2
    🌅

    Daily Standup

    15 minutes, structured.

    What happens
    Per-person digest of yesterday / today / blockers, derived from the audit log and current story states.
    Who leads
    Scrum Master
    Output
    Aligned team, surfaced blockers.
    Open Daily Standup
  3. 3
    📉

    Burndown

    Are we on track?

    What happens
    Ideal vs actual remaining points across working days. Scope creep is highlighted, not hidden.
    Who leads
    Scrum Master
    Output
    A trend the team reads at standup.
    Open Burndown
🔍

Review & Learn

Confirm what shipped, share it, improve how the team works.

  1. 1
    🎬

    Sprint Review

    What got done, was the goal met?

    What happens
    Polished summary for stakeholders — completed stories grouped by feature, carry-over, unplanned consumed, velocity vs rolling average.
    Who leads
    Product Owner
    Output
    A confirmed sprint outcome.
    Open Sprint Review
  2. 2
    🔄

    Retrospective

    What to stop, start, continue.

    What happens
    Sticky-note canvas: gather, group, vote, discuss, action. Each action has an owner and a due date and rolls up to the Retro Actions Board.
    Who leads
    Scrum Master
    Output
    Concrete, owned actions across sprints.
    Open Retrospective
  3. 3
    📝

    Release Notes

    Stakeholder-friendly summary, generated.

    What happens
    Pick a window (sprint, quarter, custom). Notes are produced from completed features and stories — accurate by construction.
    Who leads
    Product Owner
    Output
    Markdown / HTML release notes.
    Open Release Notes
  4. 4
    📊

    Reports

    Each report answers one question.

    What happens
    Planning, Productivity, Efficiency, Health, Vision Achievement, Strategic Alignment, Capacity, Voting, User Journey, Work Intake, Product Map, Team Reports.
    Who leads
    Product Manager / Delivery Manager
    Output
    Insight that drives the next planning cycle.
    Open Reports

Ready to walk this with your own team?

Spin up a workspace, choose your hierarchy depth and follow the same path with your own data. Every page in this walkthrough is one click away inside the workbench.

Create Free AccountSee Pricing