People respond to confusion by explaining more.
We add context, expand on details, and try to walk others through our thinking step by step. The intent is right, but the result is the opposite. The more we explain, the harder it becomes for others to follow.
The problem is not a lack of explanation.
It is the lack of structure.
⸻
Why explanation fails
Explanation assumes the listener can organise information as it is being delivered.
In reality, people cannot do this while keeping pace with incoming information.
When information arrives without a clear frame, the listener has to do two things at once: understand the content and figure out how it fits together. This increases cognitive load and reduces clarity.
Over time, conversations become longer, documents become heavier, and alignment remains fragile.
What looks like a communication issue is often a design issue.
⸻
What structure does
Structure reduces the effort required to understand.
When information is organised, the listener does not have to search for meaning. They know where the conversation is going, what matters, and how each part connects to the whole.
A simple example is leading with the answer and then supporting it. This was the topic of the earlier blog post this week. This is the core idea behind the Minto Pyramid Principle.
You start with the conclusion, then group supporting points underneath. The listener gets direction first, and detail second.
The same principle applies beyond communication. Clear ownership, defined interfaces, and explicit decision rights are all forms of structure. They reduce the need for repeated explanation because the system itself provides clarity.
⸻
Why people default to explanation
Explanation feels productive.
It gives the sense that more effort is being applied to solve the problem. It is easier to add more words than to rethink how information is organised.
Structure, on the other hand, requires constraint. It forces you to decide what matters, what can be removed, and how ideas relate to each other. This takes more effort upfront, but reduces effort for everyone else.
⸻
A better approach
Instead of asking how to explain something better, start by asking how it can be structured better.
Define the main point first. Group related ideas together. Remove anything that does not directly support the outcome. Make the flow visible so the listener does not have to infer it.
In many cases, once the structure is clear, the need for explanation reduces.
⸻
Practical shift
If you find yourself repeating the same explanation multiple times, pause and look at the structure.
It is likely that the system is unclear, not the people.
Fix the structure, and the explanation will become unnecessary.
⸻
Closing thought
Explanation is a patch.
Structure is a solution.
The more you rely on explanation, the more effort the system demands. The better you design structure, the less you need to explain.