Workflows Directory

Find your team’s next superpower.

Results

37 workflow templates, showing 25 to 37

  • Presentation outline and talk track

    Anyone presenting to a board, a client or a conference gets a storyboard built on one message, then a spoken script for every slide, timed to the slot and true to their own speaker notes. Every fact comes from what the presenter supplied, and the presenter approves the message and the words.

    Starts it
    Presenter
    Brings
    notes, pasted text
    Gets
    4 outputs
  • Program outcome map

    Before an evaluation, the program and evaluation leads get one map linking each activity to the outcome it is meant to serve, with proposed measures, data sources, assumptions and the questions the evidence cannot yet answer. It claims no impact.

    Starts it
    Program lead
    Brings
    export, notes
    Gets
    8 outputs
  • Project handover readiness check

    When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    6 outputs
    • Project and delivery (filtered by)
    • Software technology (filtered by)
    • Construction
  • Project intake and capacity review

    When a new initiative is proposed, the portfolio owner sees it scored on the business's own criteria beside the projects already committed, the delivery days it would use month by month, and what it would crowd out or push later. The owner accepts, defers or rejects it.

    Starts it
    Portfolio owner
    Brings
    export, notes, document
    Gets
    6 outputs
  • Project lessons review

    When a phase or a project ends, the project manager gets one blameless review: whether it achieved what it was for, how scope, schedule and budget moved and why, whether the success measures were the right ones, and practice changes for the team to choose, each with an owner and a follow-up date.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    8 outputs
    • Project and delivery (filtered by)
    • Software technology (filtered by)
    • Construction
  • Project scope baseline

    A project manager turns an approved brief into a draft scope baseline: the deliverables, what is excluded, the acceptance criteria for each deliverable, the constraints and the open questions for the sponsor. Nothing implied counts as scope until the sponsor says so.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    7 outputs
    • Project and delivery (filtered by)
    • Software technology (filtered by)
    • Construction
  • 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
  • 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
  • Reviewer comments into one resolution list

    The owner of a document that came back from several reviewers gets one checklist: every proposed edit and comment, grouped by section, with clashes between reviewers set side by side. Every item stays open until the owner decides it, and the document itself is never touched.

    Starts it
    Document owner
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
  • Service visit work packet

    Before a planned visit to a turbine, inverter or terminal asset, the maintenance supervisor gets one packet built from the logs and approved scope supplied: reported symptoms, previous visits, open parts requests and access questions. It judges no condition and sends nothing.

    Starts it
    Maintenance supervisor
    Brings
    export, notes
    Gets
    7 outputs
  • Stakeholder and decision rights map

    Before kickoff, the project manager holds one map of everyone the project touches: each group placed by influence and interest, every key decision with exactly one accountable owner, the decision makers still missing, and who hears what, when and from whom. The sponsor confirms every decision right.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    6 outputs
    • Project and delivery (filtered by)
    • Manufacturing (filtered by)
    • Construction
  • Thirteen-week cash flow forecast

    The owner sees cash week by week for the next thirteen weeks: what comes in, what goes out, the lowest point and every week below the floor they set, with each assumption written on the page. The forecast informs the decision; the owner makes it, and nothing is paid or moved.

    Starts it
    Bookkeeper
    Brings
    export, notes
    Gets
    7 outputs
  • Workflow fit check: is this piece of work ready for AI?

    Before you build anything, run one piece of work through six checks and get a straight answer on one short page: build it, build one part, do something simpler first, not yet, or leave it with your people. The owner decides what gets built first, with the reasons in front of them.

    Starts it
    Owner
    Brings
    notes, pasted text
    Gets
    6 outputs