Governance systems do not start bloated. They accumulate. A committee is formed to address a specific concern; the concern resolves, but the committee continues meeting. An approval requirement is added after a near-miss; the context changes, but the approval requirement remains. A reporting format is inherited from a predecessor board; no one remembers why it was designed that way, but changing it feels like a larger project than anyone wants to take on. Over years and decades, the average board's governance structure becomes a sedimentary record of past anxieties — processes layered on processes, most of which were never evaluated against the outcomes they were meant to serve.
The result is governance that is busy without being effective. Boards that spend hours reviewing reports that do not contain outcome data. Committees that produce minutes nobody reads and recommendations nobody acts on. Approval workflows that consume executive time without adding oversight value. Meeting agendas filled with items that feel important because they are familiar, not because they are governing.
The Traceability Test
There is a simple diagnostic for any governance process: can the board complete this sentence? "We do this because it helps us [set direction / monitor results / maintain accountability] for [specific outcome]."
If the board can complete that sentence clearly and specifically, the process is earning its place. If the best available answer is "we've always done it this way" or "it keeps everyone informed" or "the bylaws require it," the process is clutter. That does not necessarily mean it should be eliminated — bylaws exist for legal reasons, information-sharing has value — but it means the board has not yet established that the process is doing governance work.
The three functions in that sentence matter. Setting direction means the process helps the board decide what outcomes to pursue and what success looks like. Monitoring results means it gives the board reliable information about whether those outcomes are being achieved. Maintaining accountability means it creates a mechanism for the board to respond when results are off track. Every governance process should do at least one of these things, for a specific outcome. If it is not doing any of them, it is not governing.
"The board's time is the scarcest resource in any governance system. Every hour spent on a process that cannot be traced to an outcome is an hour not spent on one that can."
What a Process Audit Looks Like
Auditing existing governance processes does not require a governance consultant or a multi-month review. It requires a board willing to ask the traceability question about every standing item on its agenda and every committee in its structure. The audit can be done in a single board session, with a simple framework: list every recurring governance activity, apply the traceability test to each, and sort the results into three categories — traceable (keep), potentially traceable (clarify or modify), and untraceable (eliminate or pause).
The most common findings in a process audit: committee structures that duplicate each other's scope, or that address operational questions the board has no business deciding. Consent agenda items that are not truly routine and should be discussed, mixed with genuinely routine items that belong on the consent agenda but aren't there. CEO reports formatted around activities and inputs rather than outcomes and results. Board self-evaluation processes that measure attendance and meeting quality rather than whether the board's governance work produced anything.
The audit should also surface what is missing. Most boards discover that they have extensive processes for approving things — budgets, policies, contracts — and very few processes for monitoring whether outcomes are improving. The approval infrastructure is robust; the accountability infrastructure is thin. This imbalance is the single most reliable indicator of a board that is busy but not governing.
The Standard for Adding New Processes
Governance systems grow in one direction: toward more process, more structure, more requirements. The gravitational pull of institutional caution always favors addition over subtraction. Applying the traceability test to new processes before they are adopted is the most effective way to prevent accumulation from recurring after an audit cleans things up.
When a board member proposes a new committee, a new reporting requirement, or a new approval workflow, the proposal should answer the traceability question before it is adopted. What outcome does this serve? Which governance function — direction-setting, monitoring, or accountability — does it perform? What currently happens to that function that makes a new process necessary? If those questions cannot be answered clearly, the proposal should be set aside until they can.
This is not a counsel of minimalism for its own sake. Some governance systems are genuinely under-structured — too few monitoring processes, too little accountability infrastructure, too little written clarity about outcome goals. The goal is not fewer processes; it is better-justified ones. A governance structure where every process can be traced to an outcome it serves is not a lean governance structure — it is a functioning one.