Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

71 workflow templates, showing 49 to 71

  • Quality management review pack

    Before the periodic quality review, the quality lead gets one brief for senior leaders: where each measure stands, complaints and defects, audit findings, action status, and the decisions still open. The leaders decide; the brief claims no compliance with any standard.

    Starts it
    Quality lead
    Brings
    export, notes
    Gets
    8 outputs

  • Range margin by channel review

    When a wholesale offer or a promotion changes the economics of a range, the finance lead gets a margin worksheet for every product in every channel, showing which cost layers are in each figure and which gaps are still open. It invents no cost and changes no price.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    5 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

  • Repeat incident pattern review

    A safety lead with a year of incident records and earlier actions gets them compared in groups: confirmed causes, what was done before, and where incidents recur, with questions for the team. A competent person judges what the pattern means.

    Starts it
    Investigation lead
    Brings
    export, notes
    Gets
    6 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

  • RFI review package

    The project engineer gets one packet for each request for information: the register entry, the question word for word, the drawing revisions and specification extracts it touches, earlier responses, and a numbered list of what is unresolved. No answer is proposed.

    Starts it
    Project engineer
    Brings
    export, notes, pasted text
    Gets
    8 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

  • Sales pipeline review

    Each week your sales lead sees the whole open pipeline on one page: value and age by stage, what moved since last week, the deals at risk and coverage against your target. Every figure traces to your export, and the forecast number is left for a person to commit.

    Starts it
    Sales lead
    Brings
    export, notes
    Gets
    9 outputs

  • Shipment documentation check

    When a job finishes, the shipping or quality lead gets one index comparing the order, the inspection records, the required certificates and the packing details, with each missing record and each quantity that does not agree set out. Nothing is certified or released.

    Starts it
    Shipping lead
    Brings
    export, notes
    Gets
    6 outputs

  • Site observation follow-up

    After a site visit, the visiting engineer and the project manager get one observation report: each field note beside its location, source photograph, drawing revision and any earlier register entry, a proposed follow-up owner, and the questions still open. It assesses no condition.

    Starts it
    Visiting engineer
    Brings
    export, notes
    Gets
    5 outputs

  • Slow-moving stock and markdown plan

    Before a seasonal reset, the merchandiser or store owner gets one plan from the sales and stock exports: each item's sell-through and weeks of cover, the cash tied up in dead and slow stock, and a markdown plan in dated steps with the margin each leaves and a date to stop. The owner decides every price.

    Starts it
    Merchandiser
    Brings
    export, notes
    Gets
    5 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

  • SOP exception capture

    Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.

    Starts it
    Operations lead
    Brings
    notes, document
    Gets
    2 outputs

  • Spreadsheet check before sharing

    Before a model or schedule goes to a client, a lender or a board, the sender gets one report on it: every error value, short total, buried assumption and hidden row pinned to its cell, each with a fix or a question, and a plain list of what was not checked. Nothing in the workbook is changed.

    Starts it
    Finance manager
    Brings
    export, notes
    Gets
    5 outputs

  • Submittal register review

    The project engineer gets one register of every required submittal: what has arrived, the review status as recorded, the documents still missing and the long-lead items at risk against the date each order must be placed. Nothing is routed, accepted or ordered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 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

  • 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

  • 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

  • Website findability audit

    An owner or marketer asking why the website is not found gets a plain report from saved copies of their own pages: what stops each page being reached, read or understood, the fixes in order, and the checks only a live look can settle. No ranking is promised.

    Starts it
    Owner
    Brings
    notes, document
    Gets
    7 outputs

  • Win-loss review

    Once a quarter your sales lead sees, from the deals you closed, where the losses ended, which kinds of deal you win and lose, what the largest deals show, and which findings rest on enough deals to act on. Actions are proposed in proportion to the evidence, and nothing in your sales system is changed.

    Starts it
    Sales lead
    Brings
    export, notes, document, pasted text
    Gets
    8 outputs

  • Write an SOP from how the work is done

    Turn a walkthrough of how one piece of work is really done into a written procedure anyone on the team can follow: who does each step, how they know it is done, what to do when it goes wrong and when to stop and ask. The owner approves it before anyone relies on it.

    Starts it
    Operations lead
    Brings
    notes, document, pasted text
    Gets
    2 outputs