Question 1

What does the platform actually do?

Accepted Answer

It runs The Frustration Question — a single open-text prompt and an optional Likert reading — anonymously across one or more teams, then helps the facilitator cluster what repeats into the five Frustration Architectures, walk each cluster through one of the Three Doors (Remove, Defer, Accept), and tell the room exactly what changed. It is the operating companion to Dr. Tim Hough's book; every concept name on screen comes from the published work.

Question 2

Who is it for?

Accepted Answer

Leaders accountable for a team or a portfolio of teams: founders, COOs and operating partners, family-business principals, and the HR or people-ops partners who support them. It is built for the person who has to make the decision, not for a research department.

Question 3

How is this different from an engagement survey?

Accepted Answer

Surveys ask everyone the same questions on a calendar. The Frustration Question is a single prompt people answer when something actually obstructs their work. There is no sentiment dashboard, no 83-slide read-out, and no leaderboard — only recurring frustrations clustered by the structural shape they take.

Question 4

What are the five Frustration Architectures?

Accepted Answer

Approval Audit, Priority Forcing, Outcome Ownership, Three Columns, and Four Names — the five recurring shapes the book identifies, named not by what they look like but by what they do to the work. Each one has its own page in the app and its own entry in the Field Guide.

Question 5

What are the Three Doors?

Accepted Answer

For each cluster of frustrations, the facilitator commits to exactly one decision on the record: Remove the obstruction, Defer it with an owner and a date, or Accept it with the reason. No silent backlog and no diffused responsibility — and the room is told which door was chosen.

Question 6

What is the Constraint Register?

Accepted Answer

Every Three Doors decision and every Cross-Functional Listen commitment is written to a single workspace-scoped register, so a facilitator can show — at any time — what was decided, by whom, on what date, and what the team was told.

Question 7

How do I join my team?

Accepted Answer

Your facilitator shares a short join code (or a link that contains one). Open it, confirm you are joining the right team, and you are in. There is no account creation, no password, and no email required to participate.

Question 8

Are my answers anonymous?

Accepted Answer

Yes. Open-text answers and Likert readings are stored against your team, not against you. Facilitators see what the team is saying, not who said it. The platform is designed to be anonymous to the room and on the record only for the leader's decision.

Question 9

What is the one question I am being asked?

Accepted Answer

The Frustration Question — the same single, open-text prompt used in the book's research. You answer it when something actually obstructs your work, in your own words, in as much or as little detail as you want.

Question 10

Can I edit or delete what I wrote?

Accepted Answer

You can revise your most recent entry from your team's home page. Each entry shows when it was last edited so the facilitator knows the room is responding to current conditions.

Question 11

What is The Mirror?

Accepted Answer

The facilitator dashboard. It shows the Withdrawal Arc for each team, the patterns that keep repeating across the workspace, the Echoes chart of clusters that keep coming back, and any open Three Doors decisions that still need to be made.

Question 12

What is the Withdrawal Arc and what triggers an alert?

Accepted Answer

The Arc is a longitudinal trend line that captures whether a team is moving toward effort or toward withdrawal. The platform watches for sustained downward shifts and emails the facilitator when a team's Arc crosses an alert threshold, so withdrawal is caught while it is still reversible.

Question 13

What is the weekly digest?

Accepted Answer

An optional Monday morning email that summarises overdue Deferred decisions, the patterns that intensified during the week, and any Arc alerts that fired. Facilitators can opt out of the digest from their profile at any time, and the workspace shows whether other facilitators have opted out as well.

Question 14

What is the Cross-Functional Listen?

Accepted Answer

A 30-minute structured practice where a leader from one function listens to another function describe what is obstructing their work — using a printed visitor's script. It is included on every plan; the Team plan adds workspace-wide scheduling.

Question 15

What are peer-leader scripts?

Accepted Answer

Pre-written, in-voice prompts a facilitator can email to another leader who is about to host a Listen, so the visiting leader knows exactly what to say, what to ask, and what not to do. The platform tracks delivery and tells the facilitator if a script email bounces.

Question 16

Can I export or print what the platform produces?

Accepted Answer

Yes. Every team has a printable one-pager and a printable poster, every architecture cluster has a shareable summary, and the Constraint Register exports as CSV. The one-pager and poster work without signing in via a share link.

Question 17

How is data encrypted?

Accepted Answer

All sensitive text and JSON fields — including open-text answers, Likert responses, and facilitator notes — are encrypted at rest using AES-256-GCM. Filterable encrypted fields are queried via separate HMAC-SHA256 hash columns so the platform never has to decrypt to look something up.

Question 18

How is anonymity preserved?

Accepted Answer

Participants do not create accounts. Open-text answers and Likert readings are stored against the team, not the person. Facilitators only see aggregated and clustered output; the platform is built so that even a workspace admin cannot map an answer back to an individual.

Question 19

Is there an audit log?

Accepted Answer

Yes. Every mutating action — by a facilitator, an admin, or a platform admin — is written to an audit log with the actor, the action, the target, and the timestamp. Platform-level actions are logged with a null tenant id and are visible only to platform admins.

Question 20

What cookies does the site use?

Accepted Answer

Only essential cookies needed to keep you signed in and to remember your cookie-consent choice. There are no analytics, marketing, or third-party tracking cookies on the public site or inside a workspace.

Question 21

Where is the data stored?

Accepted Answer

In a single multi-tenant PostgreSQL database hosted on the same infrastructure as the application. Every domain table carries a tenant id and the platform enforces default-deny tenant isolation at the API layer.

Question 22

What does the Solo plan include?

Accepted Answer

One team, The Question, The Mirror, the Three Doors, pattern clustering, the Withdrawal Arc, the Starter Kit, and the Field Guide. It is free forever for one facilitator with one team — no card required.

Question 23

What does the Team plan add?

Accepted Answer

Unlimited teams in the workspace, Cross-Functional Listen scheduling, workspace branding and accent colour, and the weekly facilitator digest. It is priced per workspace, not per seat — facilitator seats are unlimited on every paid plan.

Question 24

What does the Enterprise plan add?

Accepted Answer

Multi-workspace rollout support for PE portfolios and family-owned groups, custom retention and audit configuration, SSO, named onboarding, and a quarterly read-out using the author's framework. Pricing is by annual agreement.

Question 25

What happens if I cancel?

Accepted Answer

Your workspace stays on the Solo plan with one team. Existing data is never deleted; teams beyond the Solo limit are archived and can be restored if you upgrade again.

Question 26

Can the platform admin help with templates?

Accepted Answer

Yes. Platform admins maintain shared dimension templates and survey templates that any tenant admin can apply to their workspace, so a new facilitator can stand up a workspace with a sensible default configuration in a few clicks.

Question 27

How do I start a workspace?

Accepted Answer

Sign up, name your workspace, and you become its first facilitator. The Starter Kit walks you through standing up your first team, sharing a join code, and committing to your first Three Doors decision — the smallest viable leadership commitment.

Question 28

How do I invite my team?

Accepted Answer

Generate a join code from your team's page and share it however you would normally reach the team — email, chat, or printed. The recent invites list shows who you have invited, who has joined, and whether any invite emails have bounced.

Question 29

Do participants need an account?

Accepted Answer

No. Participants join with a code and answer The Question in their browser. There is no password, no profile, and no email collected by default.

Question 30

Where do I learn the framework?

Accepted Answer

Read the book, then walk the Field Guide — seven domains that turn the five Architectures and the two practices into work the team can actually do this week. The Companion page maps every Part and Appendix of the book to the surface in the app that operationalises it.

Answers about the platform, the practice, and the data.

Where to go next.

Still the smallest viable leadership commitment.