If something went badly, you had to put it in the log…
““If something went badly, you had to put it in the log, characterize its severity, and make clear who was responsible for it. If a mistake happened and you logged it, you were okay. If you didn’t log it, you would be in deep trouble. This way managers had problems brought to them, which was worlds better than having to seek them out. The error log (which we now call the issue log) was our first management tool.””
About This Quote
This interpretation was drafted with AI assistance. It is one reading of the quote, not the author's own explanation.
The author explains that logging mistakes with severity and responsibility creates a transparent system, turning errors into management tools rather than hidden problems.
In simple terms: Record errors openly to improve management.
Key Takeaway
Use logs to surface and fix issues.
Themes
accountability
process improvement
transparency
Mood
pragmatic
instructive
Type
business
operational
When to use this quote
- project management
- team leadership
- quality control
Key Concepts
error tracking
organizational learning
Questions to Reflect On
- How can we keep error logging efficient?
- What prevents people from logging mistakes?
A Different Perspective
Too many logs can become bureaucratic overhead.