apply-transparent-rules

name	apply-transparent-rules
description	Use when designing governance, organizational policy, or team operating standards — to publish rules explicitly, permanently, and publicly before situations arise, so that enforcement is predictable and independent of the enforcer's discretion

Apply Transparent Rules

Publish rules explicitly, permanently, and publicly before situations arise — because without codification, enforcement power naturally accumulates with whoever interprets rules in real time, and predictability collapses.

Why This Is Best Practice

In 536 BC, Zichan (子产) of Zheng cast the state's criminal code onto bronze cauldrons and displayed them publicly — the first act of public legal codification in Chinese history. Shu Xiang of Jin objected in a famous letter: "When the people know what the laws are, they will lose their awe of those above them and will begin to argue and appeal. When they find the exact word that fits their case, they will be able to demand their rights on the basis of mere text." Zichan replied: "I am not doing this to win fame for future generations. I do it because a single generation of the people must be saved." Confucius later praised the act. 左传 records that Zheng's governance stabilized. The bronze cauldrons transferred authority from person to rule — enforcement became predictable, discretionary power shrank.

Adopted by: Every functioning modern legal system on earth. Codification of law — the replacement of discretionary aristocratic judgment with published, stable, publicly accessible rules — is the foundational transition in governance history. Modern organizational equivalents:

• Amazon Leadership Principles (14 principles, published publicly): All hiring decisions, promotion decisions, and performance actions reference these explicitly. The rules exist before any specific employee situation. Jeff Bezos insisted that they be written, published, and stable — not subject to managerial reinterpretation in the moment.
• Netflix Culture Deck (published 2009, 20M+ views): Reed Hastings published explicit behavior standards, performance expectations, and consequences before any individual situation arose. The deck was designed specifically so that managers couldn't invoke discretion — employees could reference the published rule themselves.
• Google Engineering Culture: ADR (Architecture Decision Records) and internal design docs make decisions written, published, and accessible. Engineers appeal to the rule, not the person.
• Procedural justice research (Leventhal 1980; Tyler & Lind 1992; meta-analysis by Colquitt 2001): The most replicated finding in organizational psychology — employee compliance and trust are most strongly predicted by whether rules were known in advance and applied consistently. Organizations with published, pre-stated norms have higher compliance rates, lower grievance rates, and faster conflict resolution than those relying on discretionary judgment.

Impact: The most replicated finding in organizational psychology (Colquitt 2001 meta-analysis) is that advance publication and consistent application of rules is the strongest predictor of employee compliance and institutional trust — outperforming outcome favorability; Netflix's published Culture Deck (20M+ views) enabled explicit, manager-independent performance standards that scaled across rapid headcount growth; 左传 records that Zheng's governance stabilized after Zichan's bronze codification, and Confucius praised the act — the bronze cauldrons transferred authority from person to rule, shrinking discretionary power and making enforcement predictable for an entire state.

Why best: Arbitrary discretion, even when exercised wisely in individual cases, produces two structural failures: (1) unpredictability — people cannot plan behavior when outcomes depend on the enforcer's judgment rather than the rule; (2) accumulation — discretion concentrates power with whoever makes real-time decisions, creating a single point of failure and a corruption target. Published rules are a forcing function: you must decide the standard before you face the case, which eliminates motivated reasoning and reveals whether the stated standard is actually enforceable.

Distinct from apply-institutional-integrity: apply-institutional-integrity addresses enforcement-under-pressure — honoring an existing rule when tempted to deviate (e.g., Zhuge Liang executing Ma Su despite personal loyalty). apply-transparent-rules addresses the prior step: creating and publishing rules before situations arise, so enforcement is unambiguous when it occurs. You cannot apply institutional integrity until transparent rules exist.

Distinct from apply-credibility-demonstration: apply-credibility-demonstration makes a visible costly action to establish trust before a major announcement. apply-transparent-rules is structural, not demonstrative — it creates a permanent reference that governs all future enforcement without requiring repeated demonstrations.

Steps

1. Identify where discretion currently lives. Map every point where an individual (manager, enforcer, executive) currently makes judgment calls without reference to a written standard. Ask: "If this person acted differently tomorrow, would anyone have grounds to object?" If no — the rule is implicit and the power is personal.

2. Draft the rule before the specific case arrives. Write the standard while no particular case is pending. Rules drafted in response to specific situations are reverse-engineered to produce a predetermined outcome — which is still discretion wearing a procedural costume. If a case is already pending, recuse the rule from that case and apply prospectively.

3. State the rule with enough specificity to be falsifiable. A rule that cannot be violated cannot be enforced. "We treat people with respect" is not a rule — it's an aspiration. "Performance reviews are completed within 30 days of the review period" is a rule. For each standard, identify: what specific action or outcome does it require or prohibit? What constitutes a violation?

4. Publish in a form that is permanent and accessible to those governed. Bronze cauldrons were permanent (hard to alter) and public (displayed at the city gate). The modern equivalent: written policy in a location where the governed population can find and reference it independently. Accessibility matters — a rule buried in a legal document no one reads is discretion with paperwork.

5. Apply the rule consistently to the first cases that test it. The first enforcement event establishes whether the rule is real. If the first violation is excused for relational or political reasons, the rule has been revealed as advisory rather than binding — and the population now knows that rule-exception decisions depend on relationship, not rule. Apply uniformly to early cases, especially when uniform application is costly.

6. Create a stable revision process for the rules themselves. Published rules are not immutable — they should be updated when conditions change. But revision must be prospective (announced before taking effect), deliberate (not in response to a pending case), and itself governed by a published process. Arbitrary revision of published rules is equivalent to having no rules.

7. Eliminate parallel informal norms. If the published rule says one thing and the informal norm (what managers actually do) says another, the informal norm is the real rule — and it has all the problems of discretion. Either revise the published rule to match practice, or eliminate the informal norm through enforcement.

Rules

• Never draft a rule in response to a specific pending case. Prospective rules only — if a case is already live, defer the rule to future situations.
• Publication to those who enforce is not the same as publication to those governed. The rule must be accessible to the people whose behavior it regulates, not only to the team enforcing it.
• Consistent first-case enforcement is not negotiable. Discretion in the first enforcement event permanently signals that rule-exception decisions are relational. There are no "soft" first cases.
• Rules with undefined violation conditions are guidelines, not rules. If a rule cannot be violated, it cannot be enforced — and it provides no predictability benefit.

Examples

Performance management: Instead of managers informally deciding what constitutes unsatisfactory performance, HR publishes a policy: "Employees rated 'below expectations' for two consecutive review cycles are placed on a performance improvement plan with specific milestones. Failure to meet milestones in 90 days results in separation." This rule exists before any specific employee's case. When a manager makes an exception for a high-performing colleague, they face a documented violation — not a judgment call.

Engineering team norms: Engineering lead publishes: "All architectural changes affecting two or more services require an ADR approved by two senior engineers before implementation. Hotfixes under 50 lines that revert a recent change are exempt." The rule exists before the next architectural disagreement. Engineers can self-assess compliance without asking permission.

Startup equity: Founders publish a vesting schedule, cliff terms, and acceleration conditions before the first employee signs. An employee who later receives a verbal promise of "accelerated vesting if we sell" can reference the published terms. When the acquisition happens, enforcement is unambiguous — or the deviation from the published rule is visible as a deliberate decision, not an interpretive judgment.

Governance: A city council passes an ordinance defining the conditions under which public permits are granted or denied, including a maximum processing time and an appeal right. Citizens denied permits can verify whether the denial complied with the published standard and appeal to the standard — not to the official's personal interpretation. Processing times fall; corruption reports fall; permit grant rates stabilize.

Common Mistakes

• Publishing rules after cases arise: Retroactively applying a rule to a case that was already live is enforcement by reverse-engineered justification. The rule provides no predictability benefit and damages trust more than discretion alone.
• Making the rules too abstract to be violated: "We value integrity" is not a rule. It cannot be violated and therefore cannot be enforced. Rules must specify observable behavior or outcomes — "Conflicts of interest must be disclosed to the compliance team before participating in any decision involving the conflicting party."
• Publishing but not enforcing: A published rule that is not enforced is worse than no rule — it signals that the publication process is theater, that the actual standard is still whoever holds power, and that the published document cannot be relied upon. Unenforced rules erode trust in all published rules.
• Allowing informal norms to persist alongside published rules: If the informal practice diverges from the published rule, the informal practice is the real governance system. Close the gap by either enforcing the published rule or updating it to match practice.
• Treating rules as immutable: Published rules should be updated when conditions change — but prospectively and through a deliberate, published process. Organizations that treat rule revision as failure avoid necessary updates and accumulate rules that no longer reflect practice.