Method Over Canon in Team Practice 2.2.4

What Canon Looks Like at the Team Level

Every successful team develops norms. Some are written — a process document, a decision framework, a meeting cadence. Most are unwritten — who speaks first, which objections are taken seriously, what kind of evidence counts. Over time, these norms become the team's operating culture. And operating culture, unchecked, becomes canon.

Canon, in this context, means the same thing it meant in the Objectivist schism that Phase 0 mapped (0.2.1): a body of conclusions treated as settled, defended by loyalty rather than by evidence, and resistant to revision regardless of changing conditions. The team that says "this is how we've always done it" is not citing evidence. It is citing precedent. And precedent, as Kelley argued about philosophical doctrine, earns its authority only through ongoing demonstration — not through historical endurance.

The core of Open Objectivism (OO) was the insistence that method takes precedence over canon — that how we know matters more than what has been declared. At the team level, this principle means that every practice, norm, and process must earn its place through ongoing evidence. A norm that once solved a real problem but no longer does is not a tradition worth preserving. It is a structure consuming resources for no return.

This is not a license to discard everything. It is a discipline for distinguishing what works from what merely persists.

The Practice Audit

The practice audit is the team-level tool for applying method-over-canon. It asks three questions of every standing team norm, practice, or process:

What problem does this solve? Every norm was created to address something — a communication gap, a coordination failure, a quality issue, a risk. Name it. If no one on the team can name the problem the norm was created to solve, the norm has already outlived its justification.

Is it still solving it? The problem may still exist, but the norm may have drifted from its original function. A weekly status meeting that was created to surface blockers may now be a performative ritual where people report what everyone already knows. The norm persists, but the problem it was built to solve is being addressed elsewhere — or not at all.

What evidence would tell us to change it? This is the fallibilist commitment applied to team norms. A norm without a revision trigger is a norm that has hardened into canon. Name the specific conditions under which the norm should be revisited: a change in team size, a shift in project type, a pattern of complaints, a measured decline in the output the norm was meant to protect.

Any norm that cannot answer all three questions is a candidate for retirement. Not immediate elimination — retirement, through the team's revision protocol (2.2.4-2).

The Canon Trap

The practice audit sounds straightforward. In practice, it runs into a specific form of resistance: the canon trap.

Teams that succeed early develop strong norms. Those norms are associated with the success — often correctly. The team's identity begins to incorporate the norms: "We're the team that does standups." "We're the team that reviews every PR." "We're the team that ships on Tuesdays." The norms become markers of team identity, not instruments of team function.

Once a norm has become identity, the practice audit's second question — Is it still solving the problem? — feels like a challenge to the team's self-concept, not a maintenance check on a process. The same identity adhesion that the individual-level sidebar (2.2.1-3) described for beliefs now operates at the collective level. The team defends the norm not because the evidence supports it, but because abandoning it feels like abandoning who they are.

The canon trap does not mean that long-standing norms are wrong. It means that long-standing norms are at higher risk of escaping evaluation — precisely because their longevity makes them feel earned when they may only be familiar. Method-over-canon does not mean abandoning successful practices. It means holding them to the same evidence standard as everything else.

Revision as Discipline

The practice audit detects norms that no longer serve their purpose. The revision protocol (2.2.4-2) provides the mechanism for changing them. Between detection and change, however, lies a space where most teams fail — the space of execution.

Revising a team norm requires four conditions. First, someone must propose the revision — and the team culture must make proposing revisions safe. If the person who suggests that a norm should change is treated as a troublemaker, the error-friendly retro (2.2.3-1) and the practice audit are both compromised. The individual disciplines of fallibilism (OO) and benevolence (OO) must be operating for the team-level disciplines to function.

Second, the team must evaluate the proposal against evidence — not against tradition, not against the preferences of the most senior member, not against the assumption that what worked before will work again. The steelman-first protocol applies here as well: the strongest version of both the existing norm and the proposed revision must be articulated before the team decides.

Third, the team must decide through a mechanism that is known in advance. Majority vote, consensus, delegated authority — the specific mechanism matters less than the fact that it exists and is understood. A team that discovers how it makes decisions only when a decision is contested is a team governed by power dynamics, not by method.

Fourth, the team must track the result. If the revision is implemented, the update ledger (2.2.3-2) records the change, the evidence that prompted it, and the review date. If the revision fails — if the updated norm produces worse outcomes than the original — the team has the data to revert, and the reversion is itself evidence of a healthy system, not a sign of failure.

The Handoff to Organization

Disagreement-as-data (2.2.3) detects when something is wrong. Method-over-canon (this unit) provides the mechanism to fix it. Together, they produce a team that can learn — not in the aspirational sense of "we're always growing," but in the auditable sense of "we changed this, for this reason, and here is the record."

That capacity is the foundation for the organizational units that follow. Institutional fallibilism (2.2.5) asks: can the organization revise its own rules? Protected dissent (2.2.6) asks: can the people who detect errors report them safely? Both questions assume that the revision mechanism exists. This unit builds it.