By Low Friction Lab ·
Capacity conversations often begin with calendars, staffing, or workload. Those matter. But a quieter drain on capacity is ambiguity.
When a team is unsure who owns a decision, where the current document lives, or what “done” means, people spend time rebuilding context. They send another message, attend another meeting, or create a parallel tool just to feel certain.
Look for repeated reconstruction
Listen for questions that surface again and again:
- Which version should I use?
- Is this required or recommended?
- Who makes the final call?
- What happens after I submit this?
- When should I expect a response?
Repeated questions are not evidence that people failed to listen. They are evidence that the system is asking them to reconstruct information.
Put clarity at the point of need
A clear system answers the next likely question before the person must pause to ask it. That might mean adding a response-time expectation to a form, naming a decision owner in the meeting agenda, or removing two outdated links from a shared page.
The improvement can be small. The capacity it returns accumulates every time the work repeats.
Treat clarity as infrastructure
Clarity is not extra communication layered on top of the work. It is part of the work’s infrastructure. When teams can see the path, they can direct more attention toward students, judgment, and collaboration.