Momentum help

Momentum · The workflow

How a conversation becomes shipped work.

Momentum models the work of an Innovation department as a single chain. Every shipped feature traces back, by record, to the discovery session that requested it.

Discovery to delivery, end-to-end

Discovery session

A scheduled conversation. Notes captured with slash menu + drag-handles. Pain points tagged inline.

Pain point

A specific friction named in a session. Severity 1–5, free-form tags, attached to a department.

Backlog item

A pain point promoted with a problem statement, priority, tags, and assignee. Source pain points stay linked.

Project

A coordinated bundle of backlog items. Status (Planning → In progress → Blocked → Shipped) plus health signal.

Shipped

Auto-publishes a changelog entry. Visible at /help/changelog with the source pain points still linked back.

What each step actually does

  1. 1

    Capture a discovery session

    Pick a template (Workflow shadowing · Stakeholder interview · Retrospective · Blank). Set scheduled time, duration, and department. Inside the session detail page the notes editor has slash commands, drag handles, and autosave. Tag pain points in the right rail as they come up.

    Get there:/discovery/new⌘K → New discovery session+ New → Discovery sessionc on /discovery
  2. 2

    Tag a pain point

    Each pain point lives under one discovery session. It carries a severity, optional tags, and a free-form description in the user’s vocabulary. Pain points are the bridge between conversation and decision — they're what makes “why did we build this?” answerable from inside the tool.

    Get there:Inside any discovery session detail pageSeverity slider 1–5Comma-separated tags
  3. 3

    Promote to backlog

    Promotion creates a backlog item with the pain-point text as its problem statement. The link table preserves which pain points (and which sessions) requested this work, so the source trace is permanent. On the backlog item detail page you can edit status, priority (P1–P5), assignee, and tags inline.

    Get there:Click the ↗ icon on any pain pointSource links carry forward automatically
  4. 4

    Bundle into a project

    Projects are collections of backlog items pursued together. Each carries a status (Planning → In progress → Blocked → Shipped), a health signal (on track / at risk / off track), and an optional target date. The lifecycle stepper on the detail page shows where the project is. The Next-steps panel surfaces gaps (no items linked, no target date, etc.).

    Get there:/projects/new+ New → ProjectLink existing backlog items from project detail
  5. 5

    Ship

    Shipped items publish to /help/changeloggrouped by month. Each entry retains the link back to its source pain points and discovery sessions. Cabinet question “why did we build this?” → answered with one click.

    Get there:Drag a backlog card to the Shipped columnOr set status = Shipped on detail

What runs in parallel

Departments

Each discovery session is attached to a department. The directory tracks engagement status (unengaged → scheduled → engaged → piloting → adopted) per department, with sessions and requested backlog items rolling up.

Audit log

Every mutation — create, transition, delete, promote, role change, feature flag toggle — writes to audit_log. Filterable from /admin/audit. FERPA-defensible record for everything that happened.

The user is the dataset

The seeded session in this app is Michelle’s feedback about Notion’s customization. The features you’re using were promoted from her pain points. The Notion-style block editor, the multi-view backlog, the Cmd+K palette — each maps back to a specific named pain point in her record. Open the Notion-style customization backlog item to see the trace for yourself.