For consultants
A framework that survives the handoff.
The chronic problem in engagement and culture consulting is the handoff. The engagement produces a diagnosis, a vocabulary, and a set of recommendations that live in a slide deck — and the structural discipline that produced the insight walks out the door when the consultant does.
The Frustration Condition framework is designed to be handoff-ready. The vocabulary is concrete (five named Architectures, not six culture pillars). The practice is runnable by a trained internal facilitator. The platform carries the decision record and the longitudinal pattern history so the structural discipline survives after the engagement ends.
A shared vocabulary for the structural causes
Most engagement and culture work lacks a precise vocabulary for the structural causes of the patterns it diagnoses. "Lack of psychological safety" describes a state. "An Approval Loop in which feedback from overlapping authorities contradicts earlier guidance and the work does not converge" describes the structural mechanism producing the state — and it names something a leader can actually act on.
The five Frustration Architectures give consultants and clients a shared, concrete vocabulary for the structural patterns behind engagement friction. The vocabulary is precise enough to route to a specific leadership decision, and simple enough — five named patterns — that line managers can use it without a consultant facilitating every conversation.
The five Architectures as a consulting vocabulary
- 1.Decision Bottlenecks — A category of decisions cannot move without a specific person or forum. Names the structural cause more precisely than 'slow decision-making.'
- 2.Approval Loops — Finished work circulates through overlapping authorities without converging. Names the structural cause more precisely than 'unclear governance.'
- 3.Priority Churn — The top-priority list changes faster than the team can deliver. Names the structural cause more precisely than 'lack of strategic focus.'
- 4.Role Ambiguity — More than one person reasonably believes they own the same decision. Names the structural cause more precisely than 'accountability gaps.'
- 5.Unspoken Constraints — A real binding constraint is known to leadership but not surfaced to the team. Names the structural cause more precisely than 'lack of transparency.'
The Cross-Functional Listen as a diagnostic tool
The Cross-Functional Listen is a 30-minute structured session that produces the Architecture picture. Participants type open-text responses to a single prompt — "What in our day-to-day work is most frustrating right now?" — anonymously to the room. The platform clusters responses into the five Architectures in real time.
For consultants, the Listen has two uses. In the diagnostic phase, it produces a named structural picture of the client's operating patterns in a single session — data that would otherwise require multiple stakeholder interviews and weeks of synthesis. In the implementation phase, it provides the recurring structural accountability mechanism that keeps the engagement's recommendations from degrading back to the status quo.
The session is anonymous to the room, which means that people can be candid about the structural patterns they work around without social risk. This routinely produces more honest data in 30 minutes than a stakeholder interview series produces in two weeks — because the structural candor that is available in an anonymous prompt is not available in a named interview.
The Three Doors as a client accountability discipline
The Three Doors decision discipline is the mechanism that separates structural diagnostic work from structural change. For every cluster the session surfaces, the leadership team must commit to Remove, Defer With Clarity, or Accept — on the record, before the session closes. There is no fourth door.
For consultants, the Three Doors record does two things. First, it forces the decision that engagement work typically defers — the specific structural commitment from a named leader, in the session, not in a follow-up action plan. Second, it creates the accountability artifact that the consultant can review in the next session: which decisions were honored, which Defer commitments were kept, whether Remove decisions actually removed the pattern.
The record is in the platform. It is not in a slide deck that someone else owns. This is what changes the handoff dynamic: when the consultant exits, the client retains the decision record, the Architecture history, and a facilitated practice that a trained internal person can run without external support.
Designing for the handoff from day one
The Frustration Condition framework is designed to transfer. The five Architectures are simple enough to memorise. The Cross-Functional Listen protocol is teachable to an internal facilitator in a half-day training. The Three Doors decision is concrete enough that a line manager can name it without a consultant present to validate the language.
This means that consultants can design a client engagement that includes a formal handoff moment: a session in which the client's internal facilitator runs the Listen with the consultant observing, followed by a debrief in which the facilitator makes the Three Doors decision without consultant prompting. By the time the engagement ends, the client has a running practice — not a documented methodology that will accumulate dust in the shared drive.
Consultants who train and certify client-side facilitators report that the practice continues independently for twelve months or more after the engagement closes — which changes the nature of the client relationship and the evidence the consultant can point to when discussing sustained impact.
Covered in the book
The full treatment of the framework — the five Architectures in depth, the facilitation protocol, the Three Doors mechanics, and the operating moves that follow from each door — is in Why Your Best People Stop Trying by Dr. Tim Hough.
Frequently asked
Consultant questions about the framework.
- Is the framework co-brandable inside a client engagement?
- Yes. Consultants can run the Cross-Functional Listen and deliver the Architecture clustering and Three Doors debrief under their own methodology brand. The framework, vocabulary, and platform are the operating infrastructure; the engagement and facilitation are the consultant's.
- What does a facilitator certification look like?
- Certification covers the five Architectures, the Cross-Functional Listen facilitation protocol, and the Three Doors debrief mechanics. Certified facilitators can run sessions independently, train client-side facilitators, and access the platform's full diagnostic history for the workspaces they manage. Contact us for the current cohort schedule.
- Can the client continue running sessions without the consultant?
- Yes — and by design. The framework is concrete enough that a trained internal facilitator can run subsequent sessions without a consultant in the room. The platform carries the Architecture history and Three Doors record, so the diagnostic continuity survives the handoff.
- How does this sit alongside a culture or operating-model engagement?
- The Cross-Functional Listen provides the structural diagnostic layer that culture and operating-model engagements typically lack: specific named patterns, a frequency read, and a leadership decision record. It is not a replacement for a culture diagnostic or a org-design engagement — it is the recurring structural accountability mechanism that runs alongside the engagement and survives after it ends.
- What is the minimum viable use inside a short engagement?
- A single Cross-Functional Listen session — 30 minutes of open-text response, 45 minutes of leadership debrief — produces a named Architecture picture and a Three Doors decision record that the client can act on immediately. Even in a two-week diagnostic engagement, one session gives the client team a structural vocabulary and a decision record they can carry forward.