DailyWF / Projects
Projects
Lifecycle documents for starting, running, and closing projects.
Project use
Projects helps prevent project work from moving on assumption alone. Use it when a decision, boundary, dependency, or commitment must be visible before the next phase continues.
- Define the trigger that starts the workflow and the condition that ends it.
- Confirm the owner, participants, inputs, constraints, and expected output.
- Perform the steps in the order people will use during normal workload.
- Record evidence, exceptions, decisions, and unresolved follow-up.
- Review the workflow after repeated confusion, incidents, or ownership changes.
Expected output
A project record that clarifies scope, owner, dependency, decision, and next checkpoint.
Common failure mode
Treating agreement as obvious while scope, owner, or acceptance criteria remain implicit.
Use notes
| Best trigger | Use when the work repeats, affects others, creates risk, or needs a defensible handoff. |
|---|---|
| Evidence | Keep the shortest record that proves the decision, action, owner, and result. |
| Review point | Review after incidents, repeated confusion, tool changes, ownership changes, or missed expectations. |
Related pages
- Assumption LogTrack project assumptions before they become invisible sources of risk.
- Discovery BriefDocument early investigation before the project is formally approved.
- Implementation ChecklistPrepare controlled release or rollout work.
- Lessons LearnedCapture reusable learning from project execution.
- Milestone ReviewCheck whether a project should continue, adjust, pause, or close.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.