A portfolio company is underperforming. The market is there. The technology works. The team is talented. Something is broken and nobody can name it. Board discussions circle the same issues — “execution needs to improve,” “we need stronger commercial leadership,” “the team isn’t aligned.” These are descriptions, not diagnoses. The structural reality is that the organization itself is generating the underperformance. The system — how decisions get made, how information flows, how roles interact, how resources are allocated — is producing the outcomes you’re seeing. Different people in the same structure would produce the same results. An external structural diagnosis reveals what board observation can’t: the specific organizational mechanics that are converting talent and market opportunity into disappointing outcomes.
Why board observation isn’t sufficient
The board sees the company through a specific lens: curated updates, compressed narratives, and metrics designed for investor communication. This isn’t deception — it’s structural. The reporting cadence and format filter out the operational texture where organizational dysfunction lives. A board member sees that sales missed target. They don’t see that sales missed target because product prioritization is driven by engineering preferences, which means the features that customers need don’t ship on time, which means the sales team is selling a product that’s perpetually six months behind market demand. That causal chain is invisible from the board seat because it requires mapping the actual decision flow inside the organization, not reviewing the metrics that result from it. Board observation tells you what happened. Structural diagnosis tells you why it keeps happening.
What structural diagnosis maps
A structural diagnosis examines the organization as a system producing outcomes. The diagnostic process maps four patterns that generate underperformance. Decision bottlenecks — where decisions stall, who actually holds authority versus who’s supposed to, and where the gap between formal and informal decision-making creates latency. Role confusion — where competing mandates, unclear ownership, and misaligned incentives make it structurally impossible for individuals to succeed regardless of their capability. Strategy-execution gaps — where the strategic intent articulated at the board level loses coherence as it moves through the organization, producing work that’s locally rational but strategically misaligned. And adaptation traps — where accumulated workarounds have become invisible process, making the organization heavier and slower than the business requires.
What it reveals
The diagnosis produces a structural map — not an opinion about the team, but a mechanical explanation of how the organization converts inputs into outputs. This map typically reveals that the underperformance has a specific structural source, not a general capability deficit. The company doesn’t have an “execution problem.” It has a decision architecture that routes every product decision through the CTO, creating a bottleneck that delays releases by six to eight weeks. The company doesn’t have a “culture problem.” It has three teams with conflicting mandates that produce interpersonal friction regardless of who fills the roles. The company doesn’t need “stronger leadership.” It needs an organizational design that distributes authority and information so that the leadership it already has can actually operate. These are specific, fixable structural problems — but they’re invisible without a diagnostic methodology designed to find them.
What I see
The first thing I look for in a portfolio diagnosis is the gap between the narrative and the operating reality. The board deck tells me the story. The actual decision flow tells me the truth. In every structural assessment I’ve run, there’s a moment when the pattern becomes visible — usually within the first few interviews — and it’s almost never what the board expected. The board sees a leadership problem. The diagnosis reveals a decision architecture problem. The board sees a culture issue. The diagnosis reveals three teams with conflicting mandates. The board sees an execution deficit. The diagnosis reveals that the strategy-to-operations translation layer was never built. The structural cause is always more specific and more fixable than the symptom suggests — which is why it’s worth finding.
How it differs from consulting
Management consulting typically starts with the strategy and works down: is the strategy right, and is the organization aligned to it? Structural diagnosis starts with the organization and works up: what is this system actually producing, and why? The difference matters because the strategy is usually fine. Climate tech founders with deep domain expertise rarely have a strategy problem — they understand their market, their technology, and their competitive position. What they have is an organizational design that can’t operationalize the strategy. Consulting engagements that begin with strategy review and end with a reorganization recommendation miss the point: the problem isn’t the org chart. It’s the decision mechanics, information flows, and role interactions that exist independent of any org chart. Structural diagnosis finds these patterns because it examines the operating system, not the operating plan.
What changes after diagnosis
The diagnostic output is specific and actionable: these are the structural patterns generating underperformance, these are the mechanisms that sustain them, and these are the design changes that would address them. Not “improve communication” — redesign the information architecture so that the product team has access to customer data without routing through sales leadership. Not “empower middle management” — redistribute decision rights so that specific decisions are made by specific people with specific information, at a cadence that matches the business need. The investor’s role shifts from giving advice the founder can’t act on to creating the conditions for structural intervention — providing the external perspective, the board support, and sometimes the capitalization required for the founder to make changes that are difficult from inside the system.
The structural cause is always more specific and more fixable than the symptom suggests. Reach out.