Workflows Directory

Find your team’s next superpower.

Results

6 workflow templates

  • Acceptance criteria sheet

    Hand a developer or agency a story with its definition of done written down: testable expected behaviours, error cases and edge cases, each traced to a rule or design state, with the unclear terms and open questions listed for the product owner.

    Starts it
    Product owner
    Brings
    notes
    Gets
    5 outputs
  • Assumption map

    For a product owner whose plan rests on beliefs nobody has tested: each belief is written down, set against the evidence you hold, ranked by what it would do to the plan, and given a cheap test to choose from. You decide what to test; no evidence is invented.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    6 outputs
    • Product management (filtered by)
    • Hardware and physical technology (filtered by)
    • Consumer brands
  • Product sample feedback revision list

    After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.

    Starts it
    Product lead
    Brings
    export, notes, document
    Gets
    7 outputs
    • Product management (filtered by)
    • Hardware and physical technology (filtered by)
    • Consumer brands
  • Release notes draft

    The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 outputs
    • Product management (filtered by)
    • Hardware and physical technology (filtered by)
    • Consumer brands
  • Roadmap tradeoff review

    When a new priority arrives, the product owner sees what the roadmap would have to give up to hold it: the capacity gap by team, the work that could move, the commitments and dependencies that move with it, and the questions still open. The owner decides.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 outputs
    • Product management (filtered by)
    • Hardware and physical technology (filtered by)
    • Consumer brands
  • Technical demo plan

    Before a technical discovery or demo meeting, the account executive and solutions engineer get an attendee brief, a demo sequence built around the buyer's stated workflow from approved scenarios, and open questions. Requests nobody has verified stay questions.

    Starts it
    Account executive
    Brings
    export, notes, pasted text
    Gets
    7 outputs
    • Sales
    • Product management (filtered by)
    • Hardware and physical technology (filtered by)