DailyWF / Projects
Lessons Learned
Capture reusable learning from project execution.
Project use
Use this soon after project completion while context is still available and before the team normalizes friction.
- Capture what worked, what failed, and what surprised the team.
- Separate individual mistakes from system, process, or assumption failures.
- Identify reusable changes to templates, reviews, checklists, or estimates.
- Assign only the few follow-up actions likely to be completed.
- Link learning back to future intake, planning, or rollout pages.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Producing a retrospective note that never changes future work.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Project IntakeCapture a proposed project before committing time or budget.
- Assumption LogTrack project assumptions before they become invisible sources of risk.
- Discovery BriefDocument early investigation before the project is formally approved.
- Milestone ReviewCheck whether a project should continue, adjust, pause, or close.
- Project Change RequestEvaluate requested changes to scope, budget, schedule, or acceptance criteria.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.