The board sees: 147 MQLs, $2.3M pipeline, 23% growth. The Head of Growth sees: outbound and content sharing zero data, 40% of pipeline untouched for 6 weeks, and a reporting dashboard that can’t trace a single lead from first signal to closed deal.
Both views are factually accurate. Only one of them tells you what is actually happening.
What Aggregate Metrics Hide
Board reporting is designed for altitude. MRR tells you the revenue trend. Pipeline value tells you near-term opportunity. CAC tells you whether acquisition economics are sustainable. These are the right metrics for a board that needs to assess company health in 45 minutes.
They cannot tell you whether your three growth motions are working together or running independently.
A $2.3M pipeline number aggregates across every deal in the CRM. It does not distinguish between deals that received outbound touches, content engagement, and paid retargeting in a coordinated sequence, and deals that entered through one channel and never received a follow-up from any other.
The aggregate looks the same. The conversion rate does not.
What the Operator Knows That the Board Does Not
The operator sitting in the growth team’s weekly sync knows things that do not appear in the board report:
The pipeline is inflated. Of the $2.3M shown, approximately 40% has had no substantive touch in the last 6 weeks. Those deals are not moving. They are occupying pipeline stages and making the aggregate look larger than the active opportunity actually is.
The motions are not connected. Outbound is running sequences that the content team has never seen. The content team is publishing assets that outbound does not know exist. Paid retargeting is targeting broad audiences because nobody handed them the content engagement data that would let them target warm prospects.
The reporting dashboard is a composite fiction. The “pipeline” in the CRM reflects what reps entered. The “MQLs” reflect what the marketing automation counted. Neither reflects the actual state of prospect engagement across all channels, because no single system has that view.
No report traces a full lead journey. From first signal to closed deal, the path crosses four systems that do not share data. You can see what happened in each system. You cannot see what happened between them.
Board metrics aggregate. Operating metrics decompose. The gap between them is where coordination debt hides.
Why the Board Report Stays Healthy While Execution Breaks
Coordination debt is slow-moving. It does not produce a dramatic quarter-over-quarter decline that triggers board-level alarm. It produces:
- Sales cycles that are 20-30% longer than they should be because buying signals are not reaching the right responders in time
- Conversion rates that are consistently below benchmark because prospects are not receiving coordinated follow-up across channels
- CAC that creeps up quarter by quarter because each growth motion is running its own acquisition strategy rather than reinforcing the others
Each individual metric stays within a tolerable range. None of them crosses the threshold that makes the board ask hard questions. But the cumulative effect of three motions running independently instead of as a system is a company growing at 60-70% of its potential.
The board sees 23% growth and calls it a good quarter. The operator knows that 23% with broken handoffs is 35-40% with connected ones.
The Metrics That Would Surface the Real Problem
The metrics that would reveal Coordination Debt are not in the standard board report:
Pipeline by last-touch age. What percentage of pipeline has had no outbound, content, or paid touch in the last 30/45/60 days? A deal sitting cold for 45 days is not pipeline. It is a future lost-deal entry.
Channel attribution by stage. Which growth motions touched each deal before it hit each pipeline stage? If 80% of closed-won deals have only one channel touch, you do not have a coordinated growth system. You have one channel that works and two that are overhead.
Cross-channel engagement rate. Of prospects who entered through content, what percentage received an outbound touch within 72 hours? Of prospects that outbound flagged as warm, what percentage entered a paid retargeting sequence? These rates measure whether the handoffs are functioning.
Signal-to-sequence latency. When a buying signal is detected — a prospect visits the pricing page, engages with a competitor comparison post, opens a sequence 3 times in one week — how long until a response reaches them? More than 24-48 hours, and the signal is cold.
None of these appear in a standard board report because building them requires integration across systems that are not currently connected. Monad’s more detailed analysis of how buying signals die between detection and the SDR queue breaks down exactly where this latency accumulates.
The Operator’s Position
The operator knows the report is incomplete. They know the $2.3M pipeline includes dead weight. They know the 23% growth came despite the coordination breaks, not because of a working system.
They also know that surfacing this to the board requires admitting that the growth infrastructure is more fragile than the aggregate metrics suggest. That is a hard conversation to initiate when the board is satisfied with what they see.
So the operator keeps executing inside broken handoffs, growing at 60% of potential, and hoping the coordination debt does not become a pipeline crisis before they have the resources to fix the underlying system.
This is the operational trap that Coordination Debt creates: invisible to leadership, expensive to the people executing, and self-perpetuating because fixing it requires acknowledging that the healthy-looking report is not the full story.
Making the Real Problem Visible
The Stack Audit creates the decomposed view that board reporting cannot. It traces where leads actually travel across systems, identifies which handoffs are breaking, and puts a number on the pipeline that is currently draining through coordination gaps.
It also gives the operator a board-safe framing: not “our motions are broken” but “here is the pipeline quality adjustment and here is the first investment that closes the gap.”
The conversation changes when you can show the board that the $2.3M pipeline includes $800K that has not been touched in 45 days, and that a specific operational change would recover 60% of that opportunity.
That is a conversation operators can have. It requires having the decomposed view first.
Request a Stack Audit to map this against your pipeline.
See also: more dashboards rarely fix execution and the $400K question: growth team vs growth infrastructure.
The board is not wrong about the numbers. They are reading the summary of a document the operator knows is missing three chapters.
Why don't operators surface coordination problems to the board? +
Because the board metrics look healthy. MRR is up. Pipeline grew. CAC is within range. Surfacing coordination problems requires admitting that the healthy-looking numbers are fragile — that the pipeline includes stale deals, that growth came despite broken handoffs, not because of a working system. That is a hard conversation to initiate when the aggregate looks fine.
Can better reporting tools fix this? +
Reporting tools show what is happening inside each system. They do not fix what happens between systems. A better dashboard does not route a content engager into the SDR queue. It does not push a buying signal into the right sequence. The coordination problem is operational, not informational. Fixing the dashboard does not fix the handoff.
What does a board-safe way to surface coordination debt look like? +
Frame it as pipeline quality, not coordination failure. Instead of 'our motions are not connected,' present: 'X% of our pipeline has had no touch in Y days, which means the real active pipeline is Z — here is what is blocking conversion.' That reframes the coordination problem as a pipeline efficiency question, which the board can act on.