Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

15 workflow templates

  • 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

  • Batch distribution trace

    When the quality lead needs to know where one production batch went, they get a map from the batch record to every recorded shipment: quantities, transfers and repacking links, with each gap in the trace written as a question. It decides no hold and contacts nobody.

    Starts it
    Quality lead
    Brings
    export, notes
    Gets
    6 outputs

  • Business model assumptions review

    Before you commit money to a new or revised business model, see it block by block with every claim marked evidenced or assumed, the riskiest assumptions ranked, and the cheapest test for each. You choose what to test; no projection or valuation is made.

    Starts it
    Founder
    Brings
    export, notes
    Gets
    7 outputs
    • Leadership
    • Product management (filtered by)
    • Consumer brands (filtered by)

  • Customer feedback themes

    Each month your support lead sees what customers keep telling you: tickets, disputes, reviews and survey comments grouped into themes with counts and quotations, the three issues most worth fixing with a proposed fix and owner, and a note for customers once a fix ships. A person decides every fix.

    Starts it
    Support lead
    Brings
    export, notes, document
    Gets
    5 outputs

  • Customer interview synthesis

    Turn a stack of customer call notes into the answer to one question, in your customers’ own words. Every quotation is cited to the note it came from, every theme shows its confidence and the evidence against it, and nothing is claimed that the notes do not say.

    Starts it
    Founder
    Brings
    notes
    Gets
    5 outputs

  • Packaging artwork handoff check

    Before packaging artwork goes to print, the packaging owner gets a checklist that matches each file to the approved product facts, pack sizes, variants and printer specifications, with version conflicts, missing files and missing approvals listed. It writes and judges no label claim.

    Starts it
    Packaging owner
    Brings
    export
    Gets
    5 outputs

  • Pilot build readiness brief

    Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.

    Starts it
    Build lead
    Brings
    export, notes, document
    Gets
    7 outputs

  • Product pricing options

    A product owner weighing how to price or package a product gets one options brief: what each customer group uses, the willingness-to-pay evidence held with stated kept apart from observed, what each option would bill every account, the uncertainties and the tests. It recommends no price.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    6 outputs

  • Product recall customer contact plan

    Once your business has issued a recall, the customer care lead gets the contact plan: affected customers from the order export, the approved notice word for word, drafts that offer only the remedies you run, and a tracker that counts a customer done only when the item is back or repaired.

    Starts it
    Customer care lead
    Brings
    export, notes, document
    Gets
    6 outputs

  • 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

  • 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

  • Returned unit review brief

    When a failed-unit report or return request arrives, the service coordinator gets one brief tying the customer's report to each unit's shipment record, serial and recorded configuration, with unmatched serials and missing evidence listed. It names no cause.

    Starts it
    Service coordinator
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs

  • 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

  • Smallest useful release scope

    A product owner or founder with more features than capacity gets one page: what is in the first release and what is deferred, all tied to one user outcome, with the reason for each cut. The owner decides the scope; no effort is estimated beyond what is supplied.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    7 outputs

  • Supplier quality response check

    A quality or purchasing person who has raised a defect with a supplier gets the supplier's reply set against the finding: what is answered, what is not, the evidence still to ask for, the actions proposed and what has yet to be verified. The person decides whether the answer is accepted.

    Starts it
    Supplier-quality owner
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs