Why 'Living' Regulations Work, and Dead Ones Gather Dust on the Shelf
How to make regulations useful and used by the team.
A regulation lives when it helps work, not when it's "beautifully formatted." Dead documents are a graveyard of rules that no one believes in and that save no one. Living ones save time, reduce chaos, and make the team predictable.
Why Most Regulations Die
The reason is trivial: they are written not for work, but "to exist." Too detailed, too abstract, or too pompous—and the document turns into a museum exhibit.
A typical scenario: a team writes a huge document with dozens of points. A month later, no one can remember what's inside, and the regulation becomes "dead."
Principles of Living Regulations
1. One Regulation — One Situation
Format "just in case": What to do → when → who is responsible → what result.
Example of a living step: "If a client doesn't respond for 24 hours—write a follow-up using a template, mark in CRM, set a reminder for 2 days."
Such a point can be executed. It does not need to be interpreted.
2. Short, Specific, at the Action Level
No general phrases like "ensure quality interaction." A person in the moment needs a route, not philosophy.
If a step cannot be checked against a checklist—it is too vague.
3. Regulations are Integrated into Work Rituals
A regulation lives where it is regularly used:
- onboarding new employees;
- retrospectives ("where did we stumble again and what do we fix in the document?");
- error analysis ("what step was missing?").
Regulation = part of the work cycle, not a PDF on a disk.
4. There is a Document Owner
One person (not a group, not a committee) is responsible for relevance. Once a quarter, they review the document, delete outdated content, simplify, clarify.
If there's no owner—the regulation is guaranteed to turn into a mummification of processes.
Mini-Checklist for a Living Regulation
- [ ] One document → one situation.
- [ ] The text can be executed without clarification.
- [ ] Each step is checked by result.
- [ ] The regulation is included in onboarding and team rituals.
- [ ] There is an owner and a last updated date.
- [ ] The document is shorter than you would write "by habit."
How to Engage the Team (and not fall into bureaucracy)
A living regulation is not "an instruction from above." For the team to use it, they need to be co-authors.
Small tricks:
- collect pain points at retros: "where did we stumble again?";
- formulate steps together—this increases compliance;
- anchor updates in channels/confs: people see that the document is alive;
- don't be afraid to delete unnecessary things—minimalism makes the regulation applicable.
Comparison: Dead vs. Living Regulation
Dead:
- 12 pages of text
- general phrases
- no owner
- lies in a folder
- "seems to exist, but no one has seen it"
Living:
- 0.5–2 pages
- clear steps
- understandable results
- updated quarterly
- used in onboarding and retros
Conclusion
A living regulation is not a document, but part of the team's operational memory. It helps to act consistently, reduces errors, and simplifies task transfer.
Think: which work scenario in your team most often breaks? Start with it—write a short "on-demand" regulation and live with it for one cycle. If it gets easier—you've created a living document.