Workflows Directory

Find your team’s next superpower.

Results

18 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
  • Brand strategy workshop

    Give your company one answer to why it exists, who it is for and how it sounds. Over about three hours (a planning figure, not yet timed), the owner makes the six choices that define the brand from options an AI assistant drafts, signs off the rest, and leaves with the tests that check it with real buyers.

    Starts it
    Founder
    Brings
    notes, document, pasted text
    Gets
    3 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
    • Professional services (filtered by)
    • Software technology (filtered by)
  • Channel partner fit review

    When a referral, reseller or alliance partner approaches, the founder or head of partnerships gets one review: evidence the partner brings customers of its own, the type that evidence supports, a ninety-day plan with signs to go on or stop, and the commission range that still beats selling direct. A person decides.

    Starts it
    Founder
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
    • Sales
    • Professional services (filtered by)
    • Software technology (filtered by)
  • 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
  • Invention disclosure brief for patent counsel

    Before the first call with patent counsel, the founder or engineering lead has one factual brief: the invention in the inventor's words, who contributed what and when, every outside demonstration, sale, talk or publication with its date and audience, and the records still missing. Counsel decides.

    Starts it
    Founder
    Brings
    export, notes, document
    Gets
    7 outputs

    Prepares work for a lawyer. Not legal advice.

  • Journey accessibility findings

    When a user journey is ready for accessibility review, the reviewer gets a finding list: each finding with its task impact and evidence, the manual checks still required and the limits of the review. The reviewer verifies every finding and agrees fixes with the design owner.

    Starts it
    Accessibility reviewer
    Brings
    export, notes
    Gets
    5 outputs
  • Launch checklist

    Whoever owns a launch date gets one dated checklist for the weeks before, the day itself and the weeks after, with an owner on every line. Each announcement is written out so the approver sees exactly what goes out, to whom and from where before saying go. Nothing is announced by the assistant.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    6 outputs
  • Offer review

    Before you sell a packaged service, see it the way a buyer will: what they get and what is left out, what answers each doubt they raise, what protects them, and whether there is an honest reason to decide now. The weakest point is named and one change drafted, from your facts only.

    Starts it
    Owner
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs
  • Premortem before a decision

    Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.

    Starts it
    Owner
    Brings
    notes
    Gets
    4 outputs
  • Press pitch preparation

    An owner or marketer with one story to offer gets the outlets and writers it genuinely fits, each backed by a piece they recently published, and a short pitch draft for each. Every claim in a draft comes from facts you supply. Drafts only: a person decides and sends.

    Starts it
    Owner
    Brings
    notes, pasted text
    Gets
    5 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
  • Research summary brief

    An executive handed a pile of reports, articles or papers gets one brief: what each source found, where the sources agree and disagree, the limits of each, and exact quotations cited to the page. Built only from the documents supplied. What it means for the business stays the reader's call.

    Starts it
    Analyst
    Brings
    notes, document
    Gets
    7 outputs
  • Sales proposal preparation

    Your account executive answers an RFP in minutes, not weeks, with a proposal draft where every claim traces to approved company information and every gap is already a question for the right person.

    Starts it
    Account executive
    Brings
    document
    Gets
    4 outputs
    • Sales
    • Engineering firms (filtered by)
    • Professional services (filtered by)
  • 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
  • Tracking event plan

    Before analytics goes onto a website or app, the founder or product owner gets one plan: the events and properties worth collecting, when each fires, where it goes, what it is called and who owns it, each tied to a question the business needs answered. The owner approves what is collected.

    Starts it
    Founder
    Brings
    export, notes
    Gets
    5 outputs
  • Usability test session plan

    Before a prototype or a confusing flow goes in front of users, the research lead and product owner hold one plan: who to recruit, the tasks in plain words, the neutral prompts, a blank note sheet and how success is counted. Recording and data handling are listed as decisions.

    Starts it
    Product owner
    Brings
    notes, document
    Gets
    9 outputs
  • User research plan

    When a design decision needs user evidence, the research lead gets one study plan: what the team needs to know, what evidence already exists, method options with their hours, participant criteria, permissions needed, how answers will be read and what the study cannot establish.

    Starts it
    Research lead
    Brings
    export, notes
    Gets
    9 outputs