Risk, Decisions, Governance
Key Takeaways
How to capture and categorise lessons learned on projects, programs, and portfolios in GreenVee.
A Key Takeaway is a lesson learned or important insight captured on a project, program, or portfolio. It is the structured way to record what worked, what did not, and what future teams should know.
Key Takeaways turn experience into institutional knowledge. Without them, the same mistakes recur and the same discoveries get made twice.
Fields
Section titled “Fields”| Field | What it means |
|---|---|
| Title | A short, clear headline for the takeaway |
| Context | Background — where did this learning come from? What was the situation? |
| Takeaway Text | The actual lesson — what should future teams know or do differently? |
Categorisation
Section titled “Categorisation”Every Key Takeaway is classified along two dimensions:
| What it is | |
|---|---|
| Takeaway Category | The top-level grouping (e.g. Procurement, Team, Technical, Schedule, Stakeholders) |
| Takeaway Type | A sub-type within the category (e.g. within “Procurement”: Vendor selection, Contract terms, Supplier communication) |
This two-level structure makes it possible to search and filter takeaways across many projects — finding all procurement lessons across the portfolio, for instance, or all technical lessons from infrastructure projects.
Where Key Takeaways live
Section titled “Where Key Takeaways live”Key Takeaways can be attached to any of three levels:
| Level | Use it for |
|---|---|
| Project | Lessons from a specific project — most common |
| Program | Lessons that apply across a group of related projects |
| Portfolio | Strategic lessons about how the portfolio operates |
Writing a good takeaway
Section titled “Writing a good takeaway”A useful takeaway is specific and actionable. Compare:
| Weak | Strong |
|---|---|
| “Procurement was hard” | “Vendor onboarding took 6 weeks instead of 2. Build 4 extra weeks into schedule estimates for any project requiring a new supplier.” |
| “Communication could be better” | “Weekly stakeholder updates prevented escalations in Phase 2. Introduce weekly updates from day one on projects with more than 3 stakeholder groups.” |
The Context field carries the story. The Takeaway Text carries the rule.