Back to ideas
Solution EngineeringPractice reflection2 min read

What is worth keeping after a project?

Beyond the report: reasons for choices, mistakes, and enough instructions for the next person to start.

Leading consulting work made a recurring problem visible: even after a similar project, the next request could begin with searching for material and asking experienced colleagues.

The final report rarely explains all the reasons for a method or the approaches that did not work.

A few more records help

I keep how the question was defined, constraints that shaped the study, execution problems, and which steps can be reused under which conditions. These are easier to apply correctly than a template detached from its context.

Responsibilities matter too: who handles the client, equipment, execution, analysis, and report? Having all the material does not guarantee someone owns the next step.

The next project is the check

Do colleagues use the records? Do they still need someone to explain them again? Which instructions cause confusion? New problems should update the material.

Templates and knowledge collections need maintenance. I want colleagues to start with prior experience while seeing which conditions are different this time.