Workflows Directory

Find your team’s next superpower.

Results

12 workflow templates

  • App data requirements

    When the requirements for an internal app leave fields or actions unclear, the business systems analyst gets one data specification: entities, fields, who reads and writes each, and every unresolved name as a question. Nothing is built or changed.

    Starts it
    Business systems analyst
    Brings
    export, notes, document
    Gets
    9 outputs
  • Cloud spend variance bridge

    When cloud or tooling costs move away from budget, the finance lead and the engineering manager get a bridge from budget to actual by service and cost owner, with usage beside each large move, the unallocated and shared costs, and the questions each side must answer.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    6 outputs
  • Employee offboarding and handover checklist

    When someone leaves, your HR lead and their manager share one checklist: every piece of their work handed to a named colleague before the last day, every system on your access register removed by its owner at a set time, and every item of equipment back. Nothing is removed or sent without a person.

    Starts it
    People lead
    Brings
    export, notes
    Gets
    7 outputs
    • People and HR
    • IT and systems (filtered by)
    • Software technology (filtered by)
  • Engineering change affected records index

    When an engineering change request enters review, the document controller gets one index: the assemblies, revisions, stock and open purchase orders the change reaches in the exports supplied, and a question for each owner wherever the records are unclear.

    Starts it
    Document controller
    Brings
    export, notes
    Gets
    3 outputs
  • Goal alignment review

    Before next period's goals are set, the chief executive sees every team goal mapped to the company priority it serves: goals with no company parent, goals that pull against each other, priorities nobody owns, and the questions for each owner. It judges goals, never people.

    Starts it
    Chief of staff
    Brings
    export, notes
    Gets
    5 outputs
    • Leadership
    • Operations and process improvement (filtered by)
    • Software technology (filtered by)
  • Lone work arrangements review

    For each task someone does alone, the manager gets the check-in method, the places where nobody could be reached, who responds when a check-in is missed and how soon, and alternatives. A competent person decides what is acceptable.

    Starts it
    Operations manager
    Brings
    export, notes
    Gets
    6 outputs
  • Pilot acceptance-test preparation

    Go into every AI pilot with the test already written: the cases that matter, what good looks like for each and the rule your owner will use to decide.

    Starts it
    Pilot owner
    Brings
    notes, document
    Gets
    4 outputs
    • Operations and process improvement (filtered by)
    • IT and systems (filtered by)
    • Software technology (filtered by)
  • 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
    • Operations and process improvement (filtered by)
    • Software technology (filtered by)
  • 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 and delivery
    • Operations and process improvement (filtered by)
    • Software technology (filtered by)
  • 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
    • Operations and process improvement (filtered by)
    • Software technology (filtered by)
  • 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
  • Temporary change register

    For a site or operations manager with temporary changes to equipment, layout or process still in place: a register of every change with its expiry date, the checks still outstanding and the procedures and training it touches, ready for the competent person who decides what happens next.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    7 outputs