Retrospective
A structured review after a project or sprint, where the team reflects on what went well, what did not, and what to improve next time.
For example, after a launch the team runs a 30-minute retrospective: the design handoff was smooth, but scope crept in week three, so next time they will tighten the change-order habit. The lessons feed straight into the next project.
Why it matters to your firm: retrospectives are how an agency compounds its delivery skill instead of repeating the same mistakes. Capturing what to keep and what to fix - and actually changing the process or SOPs - is what turns experience into a real, durable advantage.
Retrospective agenda
- What went well
- What did not
- What surprised us
- Actions to change next time
- An owner for each action
Common mistakes
- Skipping it when the project went fine.
- Blaming people instead of fixing the process.
- Capturing no actions, so nothing changes.