For CEOs
A read on the system. Not the score.
Your engagement survey is a lagging indicator. By the time the score drops, the structural causes have already spent months teaching your best people what effort is worth in this system. The Frustration Condition Tracker is the structural read that precedes the score.
It does not replace the survey. It explains it — and it does so in a form a CEO can actually act on between board cycles: five named structural patterns, each with a recorded Three Doors decision, an owner, and a date.
The problem with engagement scores for a CEO
Engagement scores are measured annually or semi-annually, at best. They aggregate across populations in ways that obscure where the structural damage is happening. They produce a number and, typically, an 83-slide deck of driver items — most of which describe the same underlying structural friction from different angles. And they arrive after the fact.
Capable people do not disengage in the quarter the survey runs. They disengage over months of accumulating evidence that effort in this system does not convert to progress. By the time the score moves, the structural training has already completed — and the people most likely to have options have already started exercising them.
The CEO's problem is not the score. It is the mechanism that produces the score and the fact that the mechanism is not visible until after it has already taught its lesson.
What the Frustration Condition gives a CEO
The platform surfaces the structural mechanism as five named Architectures: Decision Bottlenecks, Approval Loops, Priority Churn, Role Ambiguity, and Unspoken Constraints. These are not survey categories or engagement drivers. They are structural patterns — each one a specific way the system breaks the link between effort and progress.
A quarterly Cross-Functional Listen — 30 minutes, open-text, anonymous to the room — produces a named picture of which Architectures are dominant in a given team or function. The platform clusters the responses and tracks the pattern across sessions.
What a CEO sees is not a sentiment trend. It is a set of named structural patterns, the verbatim language the team used to describe each one, a frequency count, and — critically — the Three Doors decision that leadership committed to in the debrief.
What leadership sees after a session
- →The dominant Architecture for the session — the structural pattern that produced the most responses.
- →The verbatim language the team used to describe each cluster, without attribution.
- →A frequency arc across sessions — whether the same Architecture keeps re-surfacing.
- →The Three Doors decision logged against each cluster: Remove, Defer With Clarity, or Accept.
- →Whether prior Defer commitments have been honored, surfaced automatically in the next session.
The Three Doors and why they matter to a CEO
The discipline that separates the Frustration Condition Tracker from a listening session or a qualitative survey is the forced decision. For every cluster surfaced, leadership must choose one of three doors: Remove the structural cause, Defer With Clarity (named reason, named date), or Accept it explicitly on the record.
For a CEO, the Accept door is as important as Remove. When a structural pattern exists for real business reasons — a governance requirement, a regulatory constraint, a trade-off the business has decided is worth making — naming it explicitly on the record changes the signal the team receives. It tells them that the pattern is heard, that it is not invisible, and that leadership chose it deliberately rather than inherited it by default.
The record is visible to the leadership team in subsequent sessions. If a Remove decision was made in Q1 and the cluster re-surfaces in Q2, the platform flags the re-emergence. If a Defer With Clarity commitment passed its named date without action, the platform surfaces the broken commitment. The CEO can see the pattern of follow-through without chasing it.
What the cadence looks like in practice
Most CEOs start with their own leadership team: a Cross-Functional Listen that the executive team itself participates in, surfacing the structural patterns the leadership layer works around. This is often the most diagnostic session the platform produces, and it grounds the CEO's understanding of the framework before it expands to business unit or function-level sessions.
From there, the cadence is quarterly. The facilitator runs each session; the CEO's role is the debrief and the recorded Three Doors decision. The platform carries the longitudinal read — which Architectures are trending, which decisions were honored, which commitments slipped — so the CEO sees the arc without reconstructing it from memory each cycle.
By the third or fourth quarter, the platform produces something no engagement survey can: a visible decision record that the team can see, and a structural pattern history that shows whether leadership acts on what the room says.
Covered in the book
The full treatment — why engagement programs consistently produce the wrong leadership response, the operating mechanics of the Three Doors, and the CEO's specific role in the debrief — is in Why Your Best People Stop Trying by Dr. Tim Hough.
Frequently asked
CEO questions about the platform.
- How much time does this require from the CEO?
- Approximately two hours per quarter: one 30-minute Cross-Functional Listen session, a 45-minute leadership debrief on the resulting clusters, and a brief review of the Three Doors decisions in the platform. The facilitator runs the session; the CEO's role is the debrief and the recorded decision.
- What is the difference between this and an engagement survey?
- An engagement survey measures a state — a score at a point in time. The Frustration Condition Tracker names the structural patterns producing that state and forces a recorded decision on each one. The survey tells you how engaged your people are; this tells you which specific structural causes are doing the disengaging and what your leadership team is doing about them.
- Does the CEO see individual responses?
- No. Responses are grouped into the five Architectures — named structural clusters — not attributed to individuals. The CEO sees the pattern, the frequency, and the underlying verbatim language that produced it, without attribution to any person.
- What does a Three Doors decision look like in practice?
- For each cluster surfaced in the session, the leadership team commits to one of three doors: Remove (the structural cause is eliminated, with a named owner and date), Defer With Clarity (removal is deferred with a named reason and a named date), or Accept (the pattern is real, will not be removed, and leadership names this explicitly). The decision is logged in the platform and visible in subsequent sessions.
- Can this be run with just one team or does it require the whole company?
- It starts with one team. Most CEOs begin with the leadership team's own Cross-Functional Listen — the structural patterns that the executive team itself works around — before expanding to business unit or function-level sessions. The platform supports multiple concurrent workspaces.