Office Relocation Lessons Learned
This is a practical guide to building a lessons learned for an office relocation project — what went well and badly, captured to improve future projects, adapted to the realities of moving an office to new premises.
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 an office relocation project it plays the same role, tuned to this kind of work.
Why it matters for an Office Relocation project
Office Relocation projects live or die on moving an office to new premises. 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 office relocation projects drift into avoidable delay and cost.
What to include
- What happened
- Impact
- Root cause
- Recommendation
Office Relocation-specific considerations
Tailor the lessons learned to the risks that most often derail office relocation projects:
- Minimising downtime
- IT and telephony cutover
- Staff communication
Example
On a real office relocation project, the lessons learned would be shaped by moving an office to new premises. In particular, it should explicitly account for the project’s biggest risks — minimising downtime, IT and telephony cutover, staff communication — rather than treating them as afterthoughts.