Back to the Three Signal overview
Leadership Engineering
Working paper 03 The Three Signal Problem Series A/B
A diagnostic instrument · For founders, boards, and operating teams

The dashboards are green.

Something is wrong.

You cannot name it yet.

Three forces govern every scale-stage company. No dashboard plots them together. This page does.

Read time11 minutes
Fig. 01 · Capital × Execution phase space, Resonance overlaid
calm waters low pressure · clean delivery the forced march high pressure · still delivering quiet rot cash buys time · delivery slips signal collision pressure rising · delivery falling M+0 post-raise M+6 first slip M+12 today · collision Resonance integrity high degraded collapsed — ring size shows the strength of the leadership signal high low low high Execution velocity ↑ Capital pressure →
Capital pressure
How hard the financing structure is squeezing the company. Runway, board expectation, fundraise weight, valuation pressure.
Execution velocity
What the company is actually delivering in market. ARR, NRR, sales velocity, release cadence, hire stick rate.
Resonance integrity
How clearly the leadership signal travels through the organisation. Authority clarity, decision speed, coherence under pressure.

Two axes you already track. A third axis no dashboard captures.

Capital pressure and Execution velocity are the two numbers every Series A/B founder reads daily. The phase diagram plots them against each other and overlays the signal that almost no dashboard captures: Resonance integrity. It is shown here as the ring around each plot point. Bigger ring, cleaner signal.

The dashed line is the failure path most Series A/B companies actually walk. They start top-left after a successful raise — moderate pressure, healthy delivery, intact authority. Twelve months later they have drifted diagonally into the bottom-right, where pressure is high, delivery is slipping, and the ring has nearly disappeared. The board reads the slipping numbers and asks for more execution. The company no longer has the leadership signal to produce it.

Hover any quadrant
The four zones describe the kind of pain the company will produce next. Read them like weather, not verdicts.

Watch a real Series B for fifteen months. Each row is one event, read from three vantage points. The Board sees Capital. The COO sees Execution. The Founder sees Resonance. Each reading is correct. Each reading is one signal too small. The framework's job is to read the gap between them — because that gap is where the actual problem lives.

Case fileComposite Series B vertical SaaS, $40M raised
The board
Reads the metrics and the plan
via Capital signal
The COO
Reads the operating throughput
via Execution signal
Leadership
Reads the room and the room's silence
via Resonance signal
M+0
Series B closes. The room is loud.
"Plan signed: 3× ARR in 18 months. Fully funded path to Series C."
"Strong pipeline, NRR healthy, two enterprise logos closing this quarter."
"Energy is high. Story is coherent. People are bought in."
Reading
All three perspectives saying the same thing. This is what coherence sounds like. Mark it. The page returns to this baseline.
M+3
First scaling hires arrive.
"On plan. New senior team in place. Ahead on hiring milestones."
"VP Sales from a unicorn, two L7 engineers from FAANG. Onboarding well."
"Founder is delegating. Authority is becoming fuzzy in places it was clean."
Reading
Two perspectives celebrating, one perspective uneasy. The minority report is the one that matters. Authority blur this early in a senior-team build is the seed of every Resonance failure that follows.
M+6
First slip. Easy to dismiss.
"Quarter missed by 11%. Team explained it as deal timing. Watching."
"Two enterprise deals slid. New VP Sales playbook isn't landing on our ICP."
"Founder defers to VP Sales in front of the team. Old hands sense the shift."
Reading · the question
Three correct readings of the same miss. So which one is the cause? None of them — and all of them. Capital expectation is calling for delivery the playbook can't produce, and the founder's deference is degrading the authority needed to fix it. The signals are now in motion against each other.
M+9
Two more hires. One re-org.
"Burn accelerating. Runway 14 → 11 months. Need to see the plan tighten."
"Re-org announced to clean reporting lines. Should improve velocity by Q4."
"VP Product and VP Sales disagree publicly. Founder sides with neither. Middle managers stop bringing problems up."
Reading · callback
The authority blur from M+3 is no longer faint. Middle managers have stopped surfacing problems — the company has lost the ability to hear itself. Re-orgs require Resonance integrity to land. This one will accelerate the collapse it was meant to fix.
M+12
The collision becomes visible.
"Third miss. Bridge round on the table. Founder looks tired, defensive."
"Pipeline thin. Two senior hires on PIPs. Sales motion is broken."
"Co-founder tension surfacing. Best IC engineer resigned citing 'lack of clarity.' Founder isolated."
Reading
One problem. Three vocabularies. They are causing each other.
M+15
The wrong intervention.
"Hired a CRO. This is a go-to-market problem. Holding the bridge for now."
"CRO needs four months to learn the business. Numbers haven't moved."
"The actual fault is now invisible under three layers of hiring activity."
Reading · verdict
The board diagnosed the loudest signal and prescribed a fix at the wrong layer. From here, two more quarters burn before the right diagnosis is named — if it is named at all. The fault was visible at M+3. It was readable at M+6. It was undeniable by M+9. Nobody in the room could see it because nobody in the room was reading all three signals at once.
The point

The Board, the COO, and the Founder are not wrong. They are each reading one signal accurately, and missing the other two. The CRO hire makes sense from inside the Capital perspective. The re-org makes sense from inside the Execution perspective. The founder's withdrawal makes sense from inside the Resonance perspective.

The framework's diagnostic power is not that it produces a fourth opinion. It is that it reads the gap between the three opinions — and that gap is where the real problem has been living, in plain sight, since month three.

The forensic above showed all three signals failing together. That is the late stage. The diagnostic value of the framework is at the early stage — when only one signal has degraded and the other two are masking it. Each column below is what the company actually looks like, day to day, when that one signal is the one quietly failing. If a column reads as your company, you have found the diagnosis.

When Capital fails alone

The story breaks before the company does

Execution is real. Resonance is intact. The team is shipping and the leadership signal is clean. But the financing structure no longer matches the reality — the plan the board signed is not the plan the company is now living.

What it looks like
  • Two sets of forecasts: the board version and the real version
  • Founder dreads board prep more than board meetings
  • Quiet conversations about a "smaller raise" or a bridge
  • Strong product, strong team, weakening valuation case
  • Investor calls trend from extension to interrogation
The fix is a re-base, not a recovery. The longer the gap between the two forecasts is held, the more it costs to close.
When Execution fails alone

Everyone is busy. Nothing is moving.

Capital is patient and the leadership signal is clean. Decisions land. People know what to do. But the company is not converting motion into outcomes — sprints close, hires onboard, releases ship, and the metrics that matter do not respond.

What it looks like
  • Pipeline coverage is healthy; close rate is not
  • Roadmap delivery is on time; customer outcomes are flat
  • New hires perform their role; the system does not improve
  • Quarterly reviews surface explanations, not patterns
  • Founder feels the company is "running in mud"
The fix is operational, not structural. Look for the broken transmission between activity and outcome — usually one or two unowned interfaces.
When Resonance fails alone

The numbers look fine. The room does not.

Capital is patient. Execution is delivering. The dashboards are green. But something in the room has changed — A-players are leaving with reasons that do not quite name themselves, decisions take longer to land, and meetings end without anyone being sure what was decided.

What it looks like
  • Quiet attrition of people you did not expect to lose
  • Senior hires "not quite landing" three months in
  • Disagreements at the top resolved by founder fiat, then re-litigated
  • Middle managers stop bringing problems up the chain
  • What people say when the founder leaves the room is no longer what they said in it
The most dangerous of the three. Capital and Execution will read green for two more quarters before the collapse becomes visible — by which time the rebuild is twelve months long.
When two signals fail together, the third one lies. A Capital + Execution failure with healthy Resonance presents as a coherent story about a hard quarter. A Capital + Resonance failure with healthy Execution presents as "we just need to ship faster." A Resonance + Execution failure with healthy Capital presents as "we have runway, we'll figure it out." The healthy signal becomes the alibi. That is the framework's hardest read, and the one most worth running.
§ IV  ·  The instrument, in your hand

Eight questions. Structural readout.

Answer for the organisation as it is today. This is not a personality test and not a confidence exercise. It is a fast structural reading of how capital, execution, and resonance are interacting underneath the visible story.
Question 01 · Capital
When you next report upward, how confident are you that the numbers will hold without heroic explanation?
FoggyCredible
Question 02 · Capital
How closely does the plan you present upward match the plan you would write privately for the next twelve months?
Two different documentsSame document
Question 03 · Execution
If priorities changed this week, how quickly would the organisation reorient and move without creating fresh confusion?
Weeks of confusionDays, without churn
Question 04 · Execution
How often do material delivery problems reach you late rather than early?
Routinely lateSurfaced early
Question 05 · Resonance
When two senior leaders disagree, do the people one layer down still know what to do next?
They wait, or guessThey move, with reason
Question 06 · Resonance
How consistent is the understanding of priorities below the top layer?
FragmentedCoherent
Question 07 · Resonance
In the last quarter, have you lost anyone important for reasons that did not quite name themselves?
Yes, more than onceNo, departures were clean
Question 08 · Cross-signal
How different is the version of reality presented upward from the one your team would describe privately?
Two different storiesSame story
Live readout
Capital
Execution
Resonance
Answer all eight to reveal the dominant distortion in the system: where the company is carrying more story than truth, more effort than coherence, or more alignment than belief.
On the framework

The Three Signal Problem

A working diagnostic for the structure underneath Series A and Series B failure. Built from twenty-five years inside investment banks, consultancies, and operating teams. Refined through founder engagements where the surface diagnosis kept producing the wrong intervention.

Where the instrument is used

In the room, before the fire

Pre-board diagnostics. Founder counsel during the quiet drift between quarters. Executive team interventions where the surface label has already failed twice. Investor advisory when the dashboard reads green and the company does not.

Navigation

Return to the Three Signal overview

Go back to the main page.

Return to overview