Question
What is right level of detail?
Quick Answer
Too detailed is as unhelpful as too abstract — match the level to your current need.
Example: A senior engineer is debugging a production outage. She does not need the system architecture diagram that shows twelve microservices and their relationships — that is too abstract. She does not need the raw assembly instructions executing on the server CPU — that is too detailed. She needs the application logs from the specific service that is failing, the recent deployment diff, and the error stack trace. Her purpose — diagnosing a specific failure — determines the exact level of detail that will be useful. An hour later, when she writes the post-mortem for leadership, she shifts to the architecture diagram because her purpose has changed. Same system, same person, different purpose, different level.
This concept is part of Hierarchy and Nesting in the How to Think curriculum.
Learn more in these lessons
Go beyond the answer
This topic is part of The Staff Engineer’s Thinking Infrastructure — a guided sequence of 20 lessons.
After completing this path you will be able to consciously choose your level of abstraction, build shared mental models across teams through ADRs and RFCs, make architecture decisions that persist beyond your involvement, structure your own time in an undefined role, and manage the invisible emotional load of technical leadership.
Start the path →