Articles · Leadership
Designing Work So Fewer People Need Exceptions
How better defaults reduce the need for one-off accommodations.
Shared Language editorial team
Published · Updated · 2 min read
Why this matters
If a system is clearer by default, fewer people need special exceptions.
Better defaults
Use supports that help many people.
- Written priorities
- Meeting agendas
- Clear deadlines
- Documented decisions
- Flexible communication
- Fewer unnecessary interruptions
Find a repeated request
If several people ask for meeting notes, a clearer deadline, or a link to the current file, treat that as information about the process. Choose one repeat problem and build the support into the default workflow. For example, a meeting owner can publish decisions in a shared note rather than sending a summary only when someone asks.
Make the default easy to maintain
Define a small responsibility: the task owner records the deadline, the requester names the audience, or the meeting host posts the next steps. Avoid adding a complex form that creates more work than it removes. Try the change with one team and ask whether it actually reduces searching, clarification, or repeated handoffs.
Leave room for individual needs
A clearer default does not remove the need for personal adjustments or a formal accommodation process. Invite people to say when the standard arrangement still does not work for them. The aim is fewer avoidable barriers, not fewer opportunities to ask for support. Keep both the common practice and the route for individual requests visible.
Try this next
Choose one recurring team friction point and redesign it as a default support.