Maintaining a practice of documenting shifts over time can help teams better understand how their approach is changing and provide a context for addressing new challenges.
An engineering leader recently discussed his company’s practice of recording 'reference feature types' for the past eight years, which has helped them better understand lead times as well as how team members’ perceptions of development have changed.
Another example of maintaining documentation over time is an athlete keeping track of hills climbed, speed and other metrics along with a training journal.
For teams, documentation can provide a time capsule that shows how their work and priorities have changed over time as well as a starting point for assessing what causes shifts.
Recording what steps a team took to achieve a challenging goal, for example, can highlight the extra hoops that are now taken for granted, as well as identify changes to resources and processes that may contribute to changes over time.
According to the article, humans are not very good at remembering things, especially things that caused dissonance or that were not prioritized.
Recommendations for not forgetting include actively deep-documenting how goals were achieved, and perhaps creating a time capsule of perspectives.
For teams, documentation can provide a context for understanding why a once-easy task became challenging and help them plan and work more efficiently going forward.
Overall, healthy teams cultivate the practice of documenting changes over time and using that documentation to continually improve their methods and processes.
Maintaining a practice of steady documentation over time can also more easily help diagnose problems and prevent overtraining, overworking the team, and other issues.