A retrospective is a deliberate look back at recent work to decide what to improve. An engineering manager can use one with a cross-functional team, after a project, or alone at the end of a transition into management. The focus changes with the setting: collaboration, delivery, or personal growth. section 2.4.2 section 9.2.5 section 10.3
Choose questions that fit what you are reviewing:
- With cross-functional partners, periodically discuss successes, areas for improvement, and actionable next steps. Keep gathering feedback between sessions through one-on-ones and other channels. section 9.2.5
- After a project, make the retrospective part of postexecution work alongside reviewing success metrics, operational maintenance, and technical debt. section 10.3
- After a move into management, ask what was frustrating or satisfying, how team morale changed, what feedback you handled well, and what gaps need attention. Seek perspective from peers and mentors. section 2.4.2
Reviewing where your time went
To examine your work habits, review time spent in the four Eisenhower Matrix quadrants. You can estimate each day’s allocation quickly, or record tasks at 30-minute intervals for a more precise picture. Look for trends over a few weeks, then consider whether planning, delegation, or dropping low-value tasks would improve the balance. section 14.3.3 section 14.5
