Conference Planning Lessons Learned
This is a practical guide to building a lessons learned for a conference planning project — what went well and badly, captured to improve future projects, adapted to the realities of organising a conference.
What a Lessons Learned is
A lessons learned is what went well and badly, captured to improve future projects. For the full concept and how it works in general, see Lessons Learned. On a conference planning project it plays the same role, tuned to this kind of work.
Why it matters for a Conference Planning project
Conference Planning projects live or die on organising a conference. A well-built lessons learned gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how conference planning projects drift into avoidable delay and cost.
What to include
- What happened
- Impact
- Root cause
- Recommendation
Conference Planning-specific considerations
Tailor the lessons learned to the risks that most often derail conference planning projects:
- Speaker and agenda logistics
- Registration and venue
- Budget control
Example
On a real conference planning project, the lessons learned would be shaped by organising a conference. In particular, it should explicitly account for the project’s biggest risks — speaker and agenda logistics, registration and venue, budget control — rather than treating them as afterthoughts.