The job of this console
Write what to repeat or avoid, tag the project, link RCA after failures, keep sensitive detail out of search snippets.
Projects · Knowledge
Lessons Learned
Institutional memory from delivery — stored as lessons on projects, with masked summaries if they touch people-sensitive topics.
Scroll to Flowcharts. Scenario: Capture a lesson after a milestone.
What we keep
Lessons on the project, not a blame wiki
Lessons learned store reusable delivery knowledge on Project. They are not the issue register and not a place for unmasked people files.
Projects → Lessons learned
Route
/project/lessons-learned
Org flag lessonsLearnedEnabled
Manager · Project Manager · Executive · Admin
Seat at the table
PMs, executives, admins. Team members may contribute if allowed.
The working rhythm
After a milestone or incident, write, link, publish. Search before repeating a known miss.
Moments that bring you here
Retro. Post-incident. New PM on an old account. Before a similar bid.
ⓘ
Masked knowledge
AI and Work Graph must store summaries/references, not raw performance or medical text.
Flowcharts
1 — Write a lesson
Capture what to repeat or avoid, link RCA when needed.
flowchart TD
A[Open Lessons] --> B[Pick project]
B --> C[Write lesson]
C --> D{Failure?}
D -->|Yes| E[Link RCA]
D -->|No| F[Publish for reuse]
- 1OpenProjects → Lessons learned.
- 2WriteOn the project.
- 3LinkRCA when it was a failure.
- 4ReuseSearch later; masked snippets.
Overview
Lessons are knowledge records. RCA is structured cause analysis. AI knowledge reads these with masking.
How to use
1. No raw HR data
Performance and medical stay out.
2. Project tagged
Orphans are hard to find.
3. Action still on issues
A lesson is not a substitute for an open action.