Objective Change-Control Board¶
Governance body — instantiates Objective Boundary Governance
A standing forum that reviews each proposed addition against the admission rule, spends from a fixed exception budget, and enforces symmetric add/remove friction.
The Objective Change-Control Board is a standing decision forum — a group of people with authority, meeting on a cadence — that alone may admit, reject, defer, or require-a-swap for any proposed change to the objective boundary. Its defining trait is that it is the active gate: additions must be argued for in front of the whole trajectory rather than approved in a private side conversation with a single sponsor. Because the board sees every request in one place, it can do what no individual approver can — spend a fixed exception budget deliberately across competing asks, and insist that retiring an objective be exactly as easy as adding one. It is the enforcement muscle that turns admission criteria from a written aspiration into a place where "no" actually gets said.
Example¶
A satellite-hardware program runs a change-control board that meets every Thursday; no engineering change request that adds a requirement or feature can enter the baseline without passing through it. A team proposes adding a redundant star-tracker sensor "while the bus is open." The board runs it against the admission rule — fit, mass budget, schedule displacement — and then reaches for the two things a lone approver couldn't: the quarter's exception budget is nearly spent (two of three schedule-slipping exceptions already used), and the friction-symmetry rule requires the proposing team to nominate an existing requirement to retire in exchange.
The team can't find one they're willing to drop, so the sensor is deferred rather than admitted. Nothing about the sensor was unreasonable; what the board added was a forum where its cost competed openly with everything else, instead of being waved through because the person asking was senior and the meeting was short.
How it works¶
- Standing cadence, fixed membership, real authority — the board convenes regularly, and its verdict is binding, not advisory, or it will be routed around.
- Every request runs the admission rule live — fit, displacement, owner, measure, reversibility — argued in front of the board, not pre-approved.
- The exception budget depletes — a fixed number of envelope-breaking exceptions per period, so exceptions compete against each other rather than each looking free.
- Symmetric friction is enforced — retiring an objective uses the same fast path as adding one; the board can require a paired removal.
- Unresolved asks are deferred, not killed — sent to the parking lot with a revisit trigger.
Tuning parameters¶
- Membership breadth — wider boards see more angles but move slower and invite bikeshedding; narrow boards are fast but can miss displacement.
- Cadence and quorum — frequent meetings clear the queue but consume attention; infrequent ones let pressure build for side-door approvals.
- Exception-budget size — a tight budget forces hard prioritization; a loose one is decoration.
- Authority level — binding vs. advisory. Advisory boards get ignored; binding ones become bottlenecks if under-resourced.
- Default verdict — what happens on a tie or a stalled request (defer by default is safer than admit by default).
When it helps, and when it misleads¶
The board's strength is centralization: it is the one place the whole trajectory is visible, which is exactly what a diffuse set of local approvers cannot provide. It kills the side door through which "reasonable" additions slip.
Its failure modes are the standard pathologies of a committee. It can calcify into anti-learning bureaucracy, or fall into Parkinson's law of triviality[n1] — burning its meeting on the cheap, legible change while the consequential one passes with a nod. Or it degrades into a rubber stamp, approving everything so no one is offended, at which point the exception budget and symmetry check are theater. The guarding discipline is to keep the board scarce and consequential: protect its cadence, make it spend the exception budget visibly, and periodically check that people are still bringing changes to it rather than around it.
How it implements the components¶
sub_objective_admission_rule— the board is where the rule is applied to a live request by people with the authority to reject it.exception_budget— it holds and spends a fixed allowance of envelope-breaking exceptions, forcing them to compete rather than each appearing free.friction_symmetry_check— it enforces that retiring an objective uses the same path and effort as adding one, often by requiring a paired removal.
It does not implement charter_baseline — the reference state it judges against is the Objective Charter's — nor objective_boundary_ledger (the Sub-objective Decision Record, which logs the board's verdicts) or re_charter_gate (the Re-charter Workshop). The board makes the decision; the decision record is the trace it leaves behind.
Related¶
- Instantiates: Objective Boundary Governance — the board is the active gate where additions are admitted, priced against a budget, or swapped.
- Consumes: Objective Charter supplies the baseline and admission criteria the board applies.
- Sibling mechanisms: Objective Charter · Sub-objective Decision Record · Objective Drift Dashboard · Mission-Creep Audit · Opportunity-Cost Review · Plus/Minus Boundary Review · Re-charter Workshop · Deferred Objectives Backlog
Editorial Notes¶
Form Classification¶
Form family: Organization, Role & Governance
Rationale: The mechanism establishes a standing, authoritative forum with fixed membership, cadence, exception budget, and binding responsibility for objective changes.
Nearest alternative: Decision, Gate & Allocation — The board makes admission decisions, but those are operations of the durable governance body.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Program governance developed standing change-control boards that evaluate scope additions, exception budgets, authority, and symmetric removal obligations.
Related originating lineages:
- Engineering & Design — Configuration management contributed formal change requests, impact analysis, baselines, and controlled approval.
- Public Administration & Policy — Administrative governance contributes accountable exception budgets and reviewable authority.
Review resolution: Both independent reviews agree on primary origin organizational_management; reconciliation resolves alternate_origin_disagreement. Formative alternate lineages retained: engineering_design, public_administration_policy. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Parkinson's law of triviality (the "bikeshedding" effect) is C. Northcote Parkinson's observation that a committee will spend disproportionate time on trivial, easily-grasped items (the color of a bike shed) while nodding through consequential ones (a nuclear reactor) it feels less equipped to argue. A change-control board is especially prone to it, which is why keeping the board scarce and its agenda consequential is the core discipline. ↩