Your governance framework was built for a different organizationToday’s Executive Briefing: What Makes Governance Architecture Sustainable In Kern v. Arlington Ridge Pathology, bylaws sat in the company record for years while the organization operated around them. When the dispute reached court, the written governance was treated as functionally abandoned. The documents existed. The governance they described was gone. That is the danger in "governance drift". The architecture can lose force without repeal or announcement. The organization makes decisions another way for long enough that the written system becomes a record of what used to govern. (Kern v. Arlington Ridge Pathology, 2008) Larry Greiner named the broader pattern in his growth-stage model. The practices that solve one stage of growth become the constraints of the next. Founder control creates speed until the organization needs authority beyond the founder. Functional hierarchy creates order until complexity requires faster distributed judgment. The old solution becomes the new problem. (Greiner, 1972/1998) Governance follows the same pattern. A governance framework can be accurate when it is written and obsolete by the time the organization needs it most. The document may still be good. The operating condition has changed. Corporate law guidance recommends reviewing bylaws every three to five years, and sooner when actual governance practices diverge from the literal terms of the bylaws. Investors and acquirers look for those gaps during diligence because the gap between written authority and actual authority can delay a transaction or reduce valuation. (SJKP LLP, 2026) The diligence question is simple. Does this governance still govern? That question gets sharper in founder-led companies. Cambridge Family Enterprise Group describes the founder-stage organization as a hub-and-spokes model. One person can decide quickly, resolve ambiguity, and keep the system moving. That model can work for years. It can also keep governance inside the founder’s judgment instead of inside the organization. When succession, scale, risk, or transfer enters the room, the model has to change. (Cambridge Family Enterprise Group, 2017) Governance that lives in one person’s head can be effective. It is rarely transferable. In my diagnostic work, I name three governance conditions: No Architecture, Aspirational Architecture, and Inadequate Architecture. No Architecture means governance was never formally built. Decisions happen case by case. Authority moves through proximity, personality, urgency, tenure, or whoever is willing to carry the work. Aspirational Architecture means governance is documented but not operational. The organization has the language, the committee, the policy, the decision map, or the strategic framework. The work moves around it. Inadequate Architecture means governance is real and operating, but it was built for an earlier condition. The system once worked. It may still work in places. It no longer carries the scale, complexity, risk, ownership structure, or ambition now sitting on top of it. From the outside, all three can look like governance failure. Inside the organization, each one requires different work. No Architecture needs construction. Aspirational Architecture needs installation. Inadequate Architecture needs reauthoring. Most organizations skip that read. They update the policy, redraw the decision rights, add a committee, or clarify the escalation path before naming the condition. Those moves help when the condition calls for them. They waste money when the condition is different. The AI governance data shows the same pattern on a newer surface. BSI’s 2025 global research found that only 24% of businesses have a formal AI governance program. Fewer than half say AI use is controlled by formal processes. Only 28% of leaders know what data sources their business uses to train or deploy AI tools. (BSI, 2025) The signal is a governance condition. The organization adopted a new operating surface faster than it built authority around it. Governance Architecture Condition ReadThe read is small enough to do thoroughly. Choose one governance domain: strategy decisions, AI use, spending authority, hiring approval, board escalation, succession, or major customer risk. Ask three questions.
If no, you are looking at No Architecture.
If it is documented but decisions move another way, you are looking at Aspirational Architecture.
If the system operates but cannot carry current scale, ownership, complexity, or risk, you are looking at Inadequate Architecture. Write the honest answer on one page. Then write the cost of misnaming it. © 2026 Lauren Carter. This instrument is proprietary. For individual diagnostic use only. Reproduction, adaptation, or redistribution in any form requires prior written permission from Lauren Carter. If your organization’s governance architecture had to be named today, which condition would be honest? What would that answer change about the next investment you make?
— Lauren If this is the conversation someone in your network has been needing, forward it. They'll know. |
A twice-weekly diagnostic on the structural conditions underneath how organizations actually perform. Each issue names a mechanism most strategy conversations skip, then gives you a tool to test it in your own operation. Built for executives, founders, and operators who already suspect the problem is architectural.