How the Truth Dashboard is introduced to the leadership team matters as much as the instrument itself. Unicorn Syndrome is most resistant to intervention when the leader does not yet experience the gap between what they say and what is true as a tension — it has become automatic. The opening framing has to locate that gap without triggering the defenses that make it invisible.

Before the session — context the facilitator needs

What to know before you introduce the Truth Dashboard to the team

Pre-session preparation Facilitator only

The chapter is precise: Unicorn Syndrome does not typically begin as a deliberate strategy. It begins with a single decision to present data in a favorable frame under conditions of genuine pressure. By the time the EQV engagement begins, the favorable framing has become automatic — the leader no longer experiences the gap as a tension because the framing has become genuinely internalized.

This means the opening framing cannot be adversarial. The leader who hears "you've been inflating your metrics" will defend, not engage. The framing that works is one that names the pressure that produced the behavior — because a trap that a leader understands as a rational response to genuine pressure is more workable than one they experience as an inexplicable personal failing.

Facilitator prep Three things to establish before you open

Know what the pressure was

Review the leader's Pre-Flight Diagnostic, particularly their Unicorn Syndrome cluster score and any intake notes. What was the specific context where favorable framing began — fundraising, board pressure, early-stage team motivation? The opening framing should acknowledge that specific pressure, not a generic one.

Identify the most consequential gap

Before the session, identify the metric where the gap between internally known reality and externally communicated narrative is widest. This is usually visible in the Pre-Flight data or the intake conversation. You will not name it immediately — but knowing it anchors the opening.

Check who is in the room

If the CFO, Head of Operations, or any senior leader who privately knows the gap is present, the leader may already feel exposed. Acknowledge this in private with the leader before the session begins — the opening framing should not surprise them.

→

Opening the session — facilitator language

Word-for-word framing for introducing the Truth Dashboard to the leadership team

Opening · 5–8 min Full leadership team

Use this language as a starting point, not a script to read verbatim. The principle behind each section matters more than the exact words.

Facilitator language Frame the trap without naming it as a flaw

Say something like:

Every leader in this room has been in a situation where the data didn't tell the story you needed it to tell — a fundraising conversation, a board update, a team all-hands at a fragile moment — and you made a decision about how to frame things. That decision was usually rational. It protected something that needed protecting at the time. The Truth Dashboard isn't about whether those decisions were right or wrong. It's about building a system where you don't have to keep making them under pressure, because the accurate version is already the default.

Facilitator language Name the actual cost — without accusation

Say something like:

The research on this is consistent. The original performance reality — the actual number, the actual miss — is almost always survivable. What is much harder to survive is when that number is discovered rather than disclosed. The cost of Unicorn Syndrome isn't the gap. It's the trust that evaporates when someone finds the gap themselves. The Truth Dashboard is how you stay on the right side of that distinction.

Facilitator language Set the purpose of the work today

Say something like:

What we're building today is not a liability document. It's not a record of what went wrong. It's a shared baseline — a single version of what is actually true that the whole leadership team reviews together before any external communication. The purpose is to make accurate self-assessment the starting point of every external conversation, rather than something that happens after the communication strategy is already set.

Coaching note (for EQV practitioners): If the leader visibly tenses during the opening framing, that tension is information. Don't smooth it over immediately. A brief pause — "I want to give that a moment to land before we move into the practical work" — is more useful than accelerating past it. The discomfort is the recognition that the gap is real. That recognition is the beginning of the escape.

Coaching note · EQV Framework

Resistance at the opening — what it looks like and how to respond

The most common forms of pushback when the Truth Dashboard is first introduced

→ "We already have dashboards. This is redundant."

Acknowledge the existing infrastructure, then locate the specific gap: "The question isn't whether the data exists — it's whether the leadership team reviews that data together, in its accurate form, before external communications are prepared. The Truth Dashboard is a process discipline, not a data system." If the leader has existing reporting that meets this standard, the work is simpler: establish the pre-brief protocol using what already exists rather than building from scratch.

→ "Our investors / board / stakeholders don't need this level of detail."

This conflates the internal dashboard with the external communication — a conflation that is itself a signal. Clarify: "The Truth Dashboard is an internal document. It's reviewed internally before any external communication is prepared. What goes externally is still the leader's decision — the dashboard just ensures that decision is made from an accurate baseline rather than a favorable-framing baseline."

→ "I'm worried about creating a document that could be discoverable in due diligence."

This is the most important resistance to handle carefully — it often signals that the leader already knows the gap and is genuinely anxious about it. Do not dismiss the concern. Acknowledge it: "That's a legitimate operational question, and one to raise with counsel. The document itself doesn't create liability — the gap between what's in the document and what's been communicated externally is the liability. What the dashboard does is reduce that gap, not increase it." If this concern is acute, involve legal counsel in Step 1 before metric definitions are formalized.

→ "This feels like you're saying we've been lying."

Return to the opening framing directly: "I'm not. The chapter is precise about this — Unicorn Syndrome is not fraud. It is the normalized, socially accepted practice of framing data in the most favorable possible terms. Most of the leaders I work with have done it under genuine pressure and with genuinely good intentions. The question isn't whether it happened. The question is whether continuing it serves the organization at this stage — and the answer is almost always no, because the cost has changed."

Step 1 is where the real work begins — and where the most resistance concentrates. Getting a leadership team to agree on a single written definition for every metric used in external communication, and to commit that no external label may deviate from that definition for audience, is often where Unicorn Syndrome is most visibly operational. The team that cannot agree on what "users" means is showing you the gap.

Canonical metric definition session

Establishing written definitions for every externally-used metric — the standard the dashboard enforces

90–120 min · single session Full leadership team High resistance risk

The session produces one output: a written register of canonical metric definitions, signed off by the leadership team, that becomes the governing document for all external communications. Every metric label the organization uses externally must have a matching entry in this register. The test the EQV Framework applies is simple: is the metric definition the same in the internal dashboard as in the board presentation? If no, the gap is the trap operating.

Facilitator language Open the definition session

Say something like:

We're going to build a register of canonical metric definitions. For each metric the organization uses in external communications — with investors, the board, partners, the press — we're going to write down exactly what it means. Not what we'd like it to mean, not what sounds strongest. What it actually measures. The rule is simple: any label we use externally has to match this definition without modification for audience. If we use a different label or different scope for a different audience, that's the gap we're trying to close.

Facilitator language Surface the first metric — use a diagnostic question

Say something like:

Let's start with the metric you use most prominently in external communications. What is the single number you lead with when describing organizational performance? Now — without looking at any presentation material — can everyone in this room give me the same definition of what that number actually counts?

Facilitator note: The inability to give a consistent definition around the room is the most common and most useful signal in Step 1. Do not move past it quickly. This is the moment where the team sees the gap for themselves. Let it sit for a beat before moving to definition work.

Facilitator language Run each metric through the canonical definition test

For each metric, work through these four questions with the team. Do not move to the next metric until all four are answered and written down.

What does this metric actually count?

The exact events, transactions, or states that qualify for inclusion. No favorable language — the operational definition only.

What explicitly does not count?

The exclusions are as important as the inclusions. "Users" that includes sign-ups who never activated. "Revenue" that includes contracted but not invoiced amounts. These need to be written down explicitly.

Is the label we use externally an accurate description of this definition?

If the team uses "users" externally but the definition counts sign-ups, the label is wrong. The canonical definition governs — the label must change, not the definition.

Who owns this definition?

Name the person responsible for maintaining this definition and flagging if the external label or scope begins to drift from it. This is usually the CFO or Head of Data, but must be explicit.

→ "Different audiences need different framings — that's just communication."

This is the most common and most important resistance in Step 1 — it is the Extraction Mindset in metric form. Respond directly: "Framing how you contextualize a number is communication. Using a different definition of the number for different audiences is Unicorn Syndrome. The canonical metric test is simple: is the underlying count the same in the board presentation as in the internal dashboard? If yes, you have communication. If no, you have a gap."

→ "Our metrics are genuinely complex — this level of definition isn't practical."

Acknowledge the complexity, then distinguish it from what is being asked: "Complexity in what you measure is real. The register doesn't require simple metrics — it requires that whatever you measure, you measure it the same way every time, and that what you say externally is what you measure internally. If the metric is genuinely complex, that complexity goes in the definition. What can't go in the definition is a different version for a more favorable impression."

→ "Our investors know the industry and understand favorable framing. This is standard practice."

This is the normalization argument — the most culturally embedded resistance. Name it: "Favorable framing being standard practice is exactly the problem the EQV Framework addresses. The fact that everyone does it doesn't reduce the trust cost when a sophisticated investor finds the gap during diligence. The discovery of a gap between presented and actual performance during diligence is frequently terminal for the transaction. The leader who disclosed the gap proactively — even the same gap — has a fundamentally different conversation."

What a successful Step 1 session produces

A written canonical metric register with a definition entry for every metric used in external communications — including what counts, what does not count, and who owns the definition
Agreement that any external label must match the internal definition without modification for audience — and a named owner responsible for flagging drift
At least one metric where the team identified that the external label or scope did not match the internal definition — this is the session's most important output because it makes the gap visible before it reaches an external communication context
A completed Step 1 section of the Truth Dashboard, ready for the actuals-versus-plan tracking in Step 2

Session notes — metric gaps identified Canonical register location / owner

Step 2 is the operational core of the Truth Dashboard — the gap between planned and actual for each canonical metric, displayed prominently and reviewed on the same cadence as external communications. The facilitation challenge here is different from Step 1: less about resistance and more about normalizing the visibility of gaps before they reach external contexts.

Establishing the actuals-versus-plan review

Cadence, display standards, and the culture of gap visibility this step is designed to build

Ongoing · same cadence as external comms Leadership team + data owner

The chapter is specific about the display standard: the gap is displayed prominently, not buried. This is not a design preference — it is the mechanism that prevents Unicorn Syndrome from operating within the internal review itself. A gap that is buried in an internal report is already being managed. A gap that is displayed prominently becomes the normal input to communication decisions.

Facilitator language Introduce the display standard — why prominence matters

Say something like:

The dashboard tracks planned versus actual for each canonical metric. The gap column is the most important column — it gets the most space, and it doesn't come with context or mitigation attached. Context and mitigation are legitimate in external communications once you've acknowledged the gap accurately. But internally, the gap needs to be visible on its own first, before the narrative around it is constructed. That's the sequence that changes the behavior.

Facilitator language Set the review cadence

Say something like:

The Truth Dashboard is updated on the same cadence as external communications — not quarterly when it's convenient, but whenever a board presentation, investor update, or major stakeholder communication is being prepared. The review happens before the communication strategy is discussed, not after. If the dashboard review happens after the presentation narrative is already set, it becomes a compliance exercise rather than an input. The sequence is: review the accurate baseline first — then discuss how to communicate it.

Coaching note: Watch for the dashboard being maintained by a single person without team review — this is often where the gap re-emerges. The data owner updates the numbers, but the leadership team doesn't review them together before external communications are prepared. The pre-brief in Step 3 is the mechanism that prevents this. Step 2 is only effective when it feeds directly into Step 3.

Coaching note · EQV Framework

→ "Showing gaps prominently will demoralize the team."

Distinguish between the internal review and what gets communicated externally or to the broader team: "The dashboard is a leadership team document. It is not an all-hands tool. The question of what gets communicated to the broader team — and how — is a separate communication decision that the leadership team makes after reviewing the dashboard together. Prominent gap visibility in the leadership review is what enables the team to make that communication decision well, rather than defending a favorable narrative that the leadership team already knows is incomplete."

→ "We already know what the gaps are. We don't need to write them down."

This is often true — and is not an objection to the dashboard. Respond: "If you know what the gaps are, the dashboard takes fifteen minutes to maintain. The value isn't in discovering gaps you don't know about. It's in the discipline of having the whole leadership team look at them together, explicitly, before any external communication — rather than each person carrying their own version of what the gaps are and constructing external narratives accordingly."

What a successful Step 2 setup produces

A named data owner and an explicit update cadence tied to external communication cycles
A display format where the gap column is prominent — not buried after context and mitigation columns
Agreement that the dashboard is reviewed by the full leadership team before any external presentation strategy is discussed — not after
A completed actuals-versus-plan section of the Truth Dashboard, populated with current data

Data owner and update cadence Current gaps requiring attention before next external communication

The pre-brief is the most operationally critical step — and the one most likely to drift. Its purpose is to create a shared accurate baseline before any external presentation strategy is discussed. The failure mode is specific: the pre-brief becomes a presentation strategy session rather than an accuracy session. The facilitator's job is to maintain the sequence and name the drift when it happens.

Pre-brief facilitation protocol

Running the leadership team review before any external communication is prepared

30–45 min · before each external communication Full leadership team High drift risk

Facilitator language Open the pre-brief — establish the sequence explicitly

Say something like:

Before we discuss how we're going to present to [board / investors / stakeholders], we're going to spend thirty minutes on the dashboard together. The rule is: we look at what is actually true first, before anyone proposes how to frame it. Framing happens in the second half of this meeting. The first half is accuracy only. If someone starts talking about how to present a number before we've agreed on what the number is, I'm going to name it and bring us back.

Facilitator note: State this rule explicitly at the opening of every pre-brief, not just the first one. The drift toward presentation strategy is so natural — and so culturally rewarded — that the rule needs to be active in the room at the start of each session, not assumed to be operating from prior sessions.

Facilitator language Walk through each metric — accuracy questions only

For each canonical metric on the dashboard, ask only accuracy questions in the first half of the session. These are the only questions permitted before the shared baseline is established:

→

"Is this number accurate?"

Does everyone in the room agree this is the correct figure using the canonical definition? If there is disagreement, resolve it before proceeding.

→

"Is the gap displayed here accurate?"

Does everyone agree on the gap between plan and actual? Not whether the gap is acceptable, not how to explain it — whether it is correctly stated.

→

"Is there anything in this report that overstates performance relative to what we know internally?"

This question is asked of the group, not the leader. It creates shared accountability for the accuracy of the baseline rather than placing it entirely on one person.

Drift signal When the pre-brief starts becoming a presentation strategy session

These are the specific language signals that indicate the session has drifted from accuracy to communication strategy. When you hear them in the first half of the session, name it and return.

Framing language

"The way we'll want to position this is…" / "Investors will understand that…" / "We can contextualize this by saying…"

Mitigation-first language

"Yes, but if we explain [X], then [Y] looks reasonable…" / "The gap is there but the trajectory is…"

Audience management language

"[Name] won't push on this if we lead with [Z]…" / "They care more about [A] than [B], so…"

Label substitution

"Can we call this [alternative term] in the deck?" / "If we use [X metric] instead of [Y metric], the picture is stronger."

Recovery language — when drift is named

That's exactly the conversation I want us to have — in the second half of this session. Right now we're in the accuracy half. Let's finish establishing what is actually true before we discuss how to communicate it. What I heard you start to say about [metric] — is that the accurate number using our canonical definition?

Facilitator language Transition to the communication strategy half

Say something like:

We now have a shared baseline. Everyone in this room has seen the same accurate picture. Now we can talk about how to communicate it — and that conversation is legitimate and important. The question we're asking in the second half is not "how do we make this look better than it is." It is "how do we communicate what is actually true in a way that is useful to our stakeholders and honest about where we are." Those are different questions, and we're only qualified to ask the second one because we just did the first.

→ "This is slowing us down — we know the numbers, let's just prepare the presentation."

This resistance is highest in the first few pre-briefs and typically decreases as the team experiences that the accuracy-first sequence actually makes the communication strategy conversation faster. Respond: "The thirty minutes we spend on the accuracy half now is what prevents us from having a much longer conversation later — either when the presentation strategy falls apart because someone finds the gap, or when a board member asks a question the presentation wasn't designed to answer. The investment is front-loaded. It pays for itself in the first board meeting where you don't have to improvise around a number you didn't acknowledge."

What a successful pre-brief produces

A shared, explicit baseline that every member of the leadership team has seen and agreed is accurate — before the presentation strategy conversation begins
Any gaps that exceed the materiality threshold identified and flagged for proactive disclosure (see Step 4)
A communication strategy conversation that is grounded in the accurate baseline rather than constructed around a favorable framing objective
A completed pre-brief section of the Truth Dashboard, with the date, the metrics reviewed, and any disclosure decisions recorded

Pre-brief date and upcoming communication Metrics reviewed — any accuracy disputes or corrections? Disclosure decisions from this pre-brief

The materiality threshold is the most technically demanding facilitation moment. Without explicit guidance, teams set it too high (nothing triggers disclosure) or too low (the standard becomes unworkable). The threshold has to be set before a gap exists — not in response to a specific gap that is already creating pressure to manage rather than disclose.

Materiality threshold-setting session

Establishing the disclosure standard before a gap exists — the rule the team will hold itself to

60–90 min · one-time setup + annual review Set before any current gap creates pressure

Critical timing note: The materiality threshold must be set when no specific gap is currently creating pressure to manage rather than disclose. If the session is triggered by an existing gap, the threshold will be set to exclude that gap. Schedule the threshold-setting session before the next external communication cycle — not in response to one.

EQV Framework · Timing requirement

Facilitator language Introduce the materiality concept — and why it must be set in advance

Say something like:

The materiality threshold is the rule we set now, before any specific gap is on the table, that determines what gets disclosed proactively in the next scheduled stakeholder communication rather than held until asked. We're setting this rule now — not in six weeks when a specific number is creating pressure — because if we set it then, we'll set it to exclude the number that's creating the pressure. That's not a disclosure standard. That's Unicorn Syndrome with a procedure attached to it.

Facilitator language Walk through the three threshold dimensions

The threshold is set across three dimensions. Work through each one with the team and write the agreed standard into the dashboard.

Magnitude threshold — how large does a gap need to be?

Express as a percentage variance from plan for each metric category (e.g. "any metric more than 15% below plan"). Different thresholds may apply to different metric categories — revenue and retention typically warrant lower thresholds than pipeline.

Duration threshold — how long must a gap persist?

A single-period miss is different from a sustained gap. The threshold should specify whether a gap triggers disclosure immediately or after a defined number of periods (e.g. "two consecutive periods below plan threshold"). Single-period misses with a credible corrective plan may not require proactive disclosure; sustained gaps always do.

Audience threshold — who needs to know?

Not every gap requires disclosure to every audience. The standard should specify: which gaps go to the board, which go to investors, which go to the broader team, and in what format. The chapter's language is precise: "the leader identifies who needs to know, in what format, and by when."

⊙

Reference thresholds — starting points, not prescriptions

Common threshold ranges observed across EQV engagements — adapt to organizational context

Metric category	Typical magnitude threshold	Duration before disclosure	Risk level if unaddressed
Annual gross revenue retention	>5% below plan	Single period	High
Monthly recurring revenue	>10% below plan	Single period	High
Pipeline / sales forecast	>20% below plan	Two consecutive periods	Medium
New logo / customer acquisition	>25% below plan	Two consecutive periods	Medium
Burn rate / runway	Any change >15% from stated figure	Single period	High
Headcount / team changes	Any material change not previously communicated	Immediate	Medium
Product / roadmap milestones	Any slip of >1 quarter	Single period	Low–Medium

→ "If we set the threshold this low, we'll be in constant disclosure mode."

This objection often signals that current performance is already below where the threshold would sit. Respond carefully: "If performance is consistently below a 15% threshold, the disclosure practice is the right response — but it also tells us something about the plan. A plan that consistently produces 20–30% misses is not a credible plan, and sophisticated stakeholders know it. Proactive disclosure of a realistic trajectory is almost always received better than the discovery of a gap during diligence. The threshold doesn't create more disclosure — it creates earlier disclosure, which has a fundamentally different trust impact."

→ "This removes our discretion about when and how to communicate bad news."

Name the distinction between timing and content: "The threshold governs whether to disclose proactively — not exactly what to say or how. You still have full discretion over framing, context, and the narrative around the gap. What the threshold removes is the discretion to not disclose at all when a material gap exists. The chapter is direct: the leader who discloses bad news early and proactively builds a trust premium that no amount of favorable framing produces. The threshold is how you systematize that behavior so it happens before the pressure to manage rather than disclose takes over."

What a successful Step 4 session produces

A written materiality threshold for each metric category — magnitude, duration, and audience — recorded in the Truth Dashboard
Agreement that the threshold was set before any specific current gap created pressure to exclude it
A named owner responsible for applying the threshold and initiating disclosure when a gap crosses it
A scheduled annual review of the threshold — to adjust for organizational maturity and stakeholder relationship development, not to exclude current gaps

Agreed thresholds — by metric category Threshold owner and next scheduled review date

The closing protocol serves two functions: it anchors what the session produced in concrete, written commitments that the team can be held to, and it gives the leader a moment to name — privately or with the group — what the work actually cost them. The behavioral escape from Unicorn Syndrome is gradual and often uncomfortable. The closing is where that experience gets acknowledged.

✓

Session close — what the facilitator confirms before the room leaves

The checklist that turns session outputs into accountable commitments

10–15 min · end of any Truth Dashboard session

Work through this checklist with the group before closing any Truth Dashboard session. Each item should be confirmed verbally and recorded — not assumed.

Canonical metric register is written down and accessible. Not in someone's head, not in a presentation — in a document that the team can refer to before the next external communication.

A named owner is responsible for maintaining the register and flagging any drift between the internal definition and an external label before the communication is finalized.

The dashboard update cadence is agreed and tied explicitly to the external communication schedule — not to a separate internal reporting cycle that may not align.

The pre-brief protocol is scheduled for the next upcoming external communication — date, time, attendees, and the explicit rule that accuracy precedes communication strategy in the session.

The materiality threshold is written and agreed — by metric category, with magnitude, duration, and audience specifications. If not yet set, the threshold-setting session is scheduled before the next external communication.

Any gaps identified in this session that meet the materiality threshold have a named disclosure decision: who is told, in what format, and by when.

The leader has named at least one metric where the external label or framing will change as a result of this work. This is the behavioral evidence that the escape has begun — not just the creation of a document.

Coaching language Close with the leader privately — after the team has left

Say something like:

I want to check in before you head back into the day. What we did in there — looking at those numbers accurately, out loud, with your team — is not a small thing. Most leaders at your stage haven't done it. It's uncomfortable, and that discomfort is information: it tells you the gap was real. The question for you now is not whether to continue doing this. It's what the first external communication looks like where you lead with the accurate number rather than the favorable framing. That's the moment the escape becomes concrete. What's coming up next that we should use?

Coaching language If the leader is resistant at the close — the harder version

Say something like:

I noticed some resistance today, and I want to name it directly before we finish. The resistance isn't a problem — it's expected. But I want to ask you one question and have you sit with it: if a sophisticated investor reviewed everything you've communicated about organizational performance in the past twelve months against what we looked at today — would they find a material gap? If the honest answer is yes, the question is not whether to close that gap. It's whether you close it on your terms or theirs.

The behavioral escape from Unicorn Syndrome does not happen in a single session. The Truth Dashboard is a system that makes accurate self-assessment the default input to external communication — gradually, consistently, and irreversibly. The closing protocol is where the leader commits to the next concrete action: the first external communication where the accurate number is disclosed rather than managed. That commitment — specific, named, and dated — is what converts the session from a development exercise into the beginning of the escape.

EQV Framework · Ch. 9 · Escape Strategies · Unicorn Syndrome

First proactive disclosure commitment — what, to whom, by when Next session / check-in date Session notes for the practitioner record