Workflows Directory
Find your team’s next superpower.
- Function: Project and delivery
- Industry: Hospitality
- Industry: Manufacturing
- Industry: Software technology
- Clear all filters
Results
12 workflow templates
Implementation blocker brief
When a customer's setup milestone slips, the implementation lead gets one brief: the missing inputs, the unresolved access and data questions and the dependencies behind the delay, each with its source and an owner, plus points to raise with the customer.
- Starts it
- Implementation lead
- Brings
- export, notes
- Gets
- 6 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
Meeting agenda, notes and follow-ups
Whoever runs the meeting walks in with an agenda where every topic has an outcome and a time, and walks out with a one-page record: what was decided, who owns each action and by when, and what is still open. Nothing reaches anyone until that person has read it and sends it.
- Starts it
- Team lead
- Brings
- notes
- Gets
- 4 outputs
Missed milestone client reply
When a client challenges a delay, a deliverable or an earlier commitment, the account director gets a draft reply and an internal action note that keep confirmed facts apart from proposed recovery steps and the decisions still needed. Nothing is sent.
- Starts it
- Account director
- Brings
- export, notes, document, pasted text
- Gets
- 2 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
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
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 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 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
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