Nobody in your organization knows who can say yes. Decisions get escalated, deferred, or made by whoever cares most and pushes hardest. The org chart says one thing. The actual decision flow says another. There’s a shadow hierarchy — an informal power structure that determines what actually gets decided and by whom — and it’s invisible from the outside and exhausting from the inside. The conventional fix is “empower people to make decisions.” But empowerment without architecture is chaos. The problem isn’t that people lack permission to decide. It’s that the decision rights, the information needed to decide well, and the accountability for outcomes aren’t in the same place. The architecture is broken. Telling people to “be more decisive” inside a broken architecture just produces faster bad decisions.
What it looks like
A product decision that should take a day takes three weeks. Not because it’s complex — because nobody is sure who owns it. An engineering lead makes a technical choice, then gets overruled by the CTO in a hallway conversation. A sales director commits to a customer timeline without checking with delivery, because there’s no mechanism that requires it. Meetings end without decisions. Or they end with decisions that get relitigated in the next meeting because someone with informal authority wasn’t in the room. Teams escalate everything to the founder — not because they can’t decide, but because deciding and then being overridden is worse than waiting. The organization has learned that the safest move is to defer. So everything moves slowly, and the few things that move fast are driven by whoever has the social capital to push them through the informal system. That’s not a decision architecture. That’s organizational natural selection.
The mechanism
Decision architecture has three components that have to be co-located: the right to decide, the information to decide well, and the accountability for the outcome. In most growing startups, these three things are in different places. The right to decide is formally distributed (the org chart says the VP of Product owns product decisions) but informally concentrated (the founder overrides when they disagree). The information to decide well is scattered across teams, tools, and people’s heads — nobody has the full picture without assembling it from multiple sources. The accountability for outcomes is assigned after the fact, usually to whoever is most visible when things go wrong. When these three things aren’t co-located, decisions either don’t get made (because the decider lacks information or confidence), get made badly (because the decider lacks information), or get overridden (because the person with informal authority disagrees). The result is a decision system that produces high latency, low quality, and zero accountability.
Why it persists
The shadow hierarchy serves the people who hold power within it. The founder who overrides decisions isn’t doing it maliciously — they have better context, better judgment, and the outcome matters to them. The problem is that their informal authority destroys the formal system without providing a scalable alternative. But giving up that informal authority feels like accepting worse decisions, which feels irresponsible. Meanwhile, the people who’ve learned to navigate the shadow hierarchy have an advantage over those who haven’t. They know who really decides. They know which meetings matter and which are theater. This navigational knowledge is a form of organizational capital that they don’t want to lose. So both the people with informal power and the people who know how to access it have incentives to maintain the current system. The people who suffer are the ones who take the org chart at face value — often the newest hires and the most capable senior leaders, who expect the formal authority they were given to actually mean something.
What changes
Decision architecture has to be designed explicitly, not inherited from the org chart. For every major decision type — product priorities, hiring, pricing, resource allocation, customer commitments — the architecture needs to specify three things: who decides (one person, clearly identified), what information they need (and where it comes from), and who is accountable for the outcome (which should be the same person who decides, or the system is broken). This sounds bureaucratic. It isn’t. The most effective decision architectures I’ve seen are simple — a one-page document that maps the top twenty decision types to specific roles, with clear escalation triggers. The key is making the informal formal. If the founder is going to override product decisions when technical architecture is at stake, build that into the architecture explicitly. Don’t pretend the VP of Product has authority they don’t have. A decision architecture that reflects reality — including the founder’s involvement — is infinitely better than one that pretends the org chart governs decisions when it clearly doesn’t.
What I see
The decision architecture failures I diagnose in climate tech almost always have the same root: the founder has legitimate technical judgment that the formal system doesn’t account for. The founder overrides decisions — not out of ego, but because they’re often right. The team learns that formal authority is provisional. Senior hires with real decision-making experience discover their authority is cosmetic, and they leave. The board calls it a hiring problem. It’s a design problem: the founder’s involvement isn’t the issue — the lack of architecture around that involvement is. When I map the actual decision flow in a company versus the org chart, the gap tells me everything about where the slowdown lives and why talented people keep leaving the same roles.
Where this shows up
Decision architecture failure is amplified in climate tech by the number of competing decision domains. Earth observation companies need to make decisions across satellite operations, analytics product, commercial sales, and government contracts — and the authority rarely matches the expertise. Defense & dual-use companies layer classified program decisions on top of commercial product decisions, creating a parallel decision architecture that nobody designed deliberately. Energy markets companies face regulatory decisions, technical decisions, and commercial decisions that interact in ways the org chart doesn’t reflect. Carbon capture companies split between R&D decisions and deployment decisions with different time horizons and different risk profiles. For investors, decision architecture is one of the most diagnostic elements of organizational due diligence — and the hardest to assess from the board seat. A portfolio diagnosis that maps the actual decision flow almost always reveals why execution feels slow.
A decision architecture that reflects reality — including the founder’s involvement — is infinitely better than one that pretends the org chart governs decisions when it clearly doesn’t. Reach out.