A team should not have to renegotiate itself every day.
A charter is one team’s editable account of its purpose, work, measures, authority, roles, and guidelines. Guidelines are short rules for situations the team encounters again and again.
Write down the rules people already rely on. New colleagues and agents can use them without waiting for an experienced person to explain what usually happens here.
Every team has rules. Most of them are stored in people.
You have seen one experienced person keep a team moving because they know which stakeholders matter and remember what happened last time. The team writes documents a certain way, reviews work in a certain order, escalates one class of problem, and handles another locally. Those repeated choices are already guidelines; writing them down makes access fairer.
When the rules stay in people’s heads, new members learn through correction. Remote colleagues miss the hallway explanation. A manager becomes the interpreter of every ambiguous situation. The people who have been around longest appear unusually capable because they carry a private copy of the operating system.
The usual alternatives both fail. A values slide is too thin to guide a Tuesday afternoon. A policy library is too distant and exhaustive to use in motion. Guidelines occupy the useful middle: local enough to describe real behavior, short enough to remember, and revisable enough to improve.
Values name what matters. Guidelines say what to do.
Transparency becomes useful when a product team knows when to share incomplete work. Ownership becomes practical when a role holder knows which choices they can make alone. Customer focus changes behavior when the team names the evidence required before a change. A guideline writes down those consequences while leaving room for judgment.
Situation
Name when the rule applies: a reversible decision, an active customer harm, or a change to a shared standard.
Action
Use an observable verb. Write the decision, consult the affected team, name a steward, or escalate the risk.
Boundary
Say when the rule stops. Default to asynchronous review, except when the choice is urgent or emotionally consequential.
Intent
Write down why, so people can improvise when the next case is different.
Write the behavior. Preserve the judgment.
Begin with a repeated negotiation
The best source is a question the team keeps answering: when does this need a meeting, how long do we wait for consultation, what evidence is enough, or which problems must be escalated? A one-off question may need a decision. A recurring question may need a guideline.
Start with the real friction, not a list of admirable traits. The useful guideline removes a predictable round of negotiation while leaving room for the facts of the case.
Use a verb and show the boundary
Prefer “Write the decision before calling the meeting” to “Be collaborative.” Prefer “Consult affected teams for 48 hours before changing a shared standard” to “Communicate transparently.” The first version changes what someone does next.
Rules become dangerous when their limits remain implicit. A default to written review may yield during an incident, difficult performance conversation, or decision that expires in two hours. Write the exception where people can see it.
Keep the set small and revisable
A team should be able to scan its guidelines and recognize itself. Detailed procedures, company policies, legal requirements, and technical standards can stay in their own systems. The charter carries the few local rules that organize recurring judgment.
When people repeatedly work around a guideline, investigate. The team may be ignoring a good rule, the environment may have changed, or the exception may have become normal. The answer is a review with evidence, not automatic enforcement.
A guideline with its reason, scope, and history
Particulars keeps each rule beside the team it governs. Editors can revise the language while the version record preserves what changed and who changed it.
Connected evidence can reveal a divergence. The software proposes a specific repair and cites what it observed; a person decides whether the rule or the work should change.
Use the least irreversible intervention that stops the harm.
Temporary uncertainty was repeatedly converted into permanent account action.
Incident response · Account restrictions · Risk recommendations
Turn local wisdom into a system the organization can learn from.
Once guidelines are structured and versioned, teams can compare how similar work is governed without forcing every team into one policy. A guideline can reveal where a company value has a practical consequence and where it remains only a slogan.
Visible rules let you see where consistency matters, where local judgment is better, and where an agent still needs a clearer boundary before it can contribute safely.
- Notice rules that repeatedly generate exceptions.
- Separate a working guideline from an absent decision right.
- Give new people and software contributors the same current operating context.
“Culture is partly what people do when the handbook runs out. A good guideline gives that judgment a form without pretending judgment has ended.”
— The Particulars thesis