Navigate
The sample report, in full
⚠ Fictional sample
“Relay” and “Meridian Analytics” do not exist. This report was produced by running the full diagnostic method on synthetic evidence, to show you exactly what you receive. No real client data appears here — we say so because we'd rather show you a labeled sample than an invented case study.
Team Conditions Report
Relay · Meridian Analytics
Engagement: four weeks · Prepared by Alex · FourFlowOS
What we found, what it's costing, and the first thing worth changing.
Section 1
The Read
The whole diagnosis on one page. Everything after this is the evidence.
The bottleneck — Feedback Systems, i.e., signal loops
Relay ships real work into silence. Features release and no adoption signal returns to the team; decisions leave the weekly meeting without an owner or a date and resurface weeks later as open questions. The team is talented, engaged, and likes its tools — and it is flying without instruments.
What it's costing
In one observed planning meeting, five decisions were raised and one closed. The team's strongest engineers spend roughly a day a month hand-building private usage reports the system should be producing. The same questions recur across meetings — “third week running,” in the team's own words. Effort that should compound is being spent on compensating.
The first intervention — the closing loop
Two habits, ~10 minutes a week, starting Monday: every decision in the weekly leaves with an owner and a date, in the meeting; every shipped feature gets one adoption number, reviewed the following week — starting from the tracking sheet one of your engineers already built.
The 30-day indicator
Decisions leaving the weekly with an owner and a date: from the observed baseline of 1 in 5 to 4 in 5. Countable from your own meeting notes. No tooling required.
And honestly
Eleven other conditions were read. Three are genuinely strong — this team is not broken, it is blocked, and the fix builds on what already works.
Section 2
What We Looked At
| Evidence stream | Volume |
|---|---|
| Confidential interviews | 4 × 30 min |
| Meeting transcripts (recorded with consent, announced in advance) | 3 meetings — planning, standup, retro |
| Team questionnaire | 11 of 11 respondents + team lead (same instrument) |
| Leader intake | 1 |
| Work artifacts | not collected this engagement |
All quotes are non-attributed and edited to remove identifying phrasing. No individual was scored. Six conditions produced too little evidence to read in this engagement — they're marked not read below rather than guessed at, with what would light them up.
Section 3
The Twelve Conditions
The full read — strengths get real ink; thin evidence gets named, not stretched.
Tuned Emotions — i.e., emotional bandwidth · Working · Confirmed
Disagreement on this team surfaces and resolves without residue. Two technical disputes in one meeting ended in evidence, not politics — and the lead named it: “I like hearing people actually fight about something technical instead of just agreeing to be polite.” This is load-bearing: the intervention below assumes a team that can hear a bad number without flinching. Yours can.
Focused Body — i.e., energy, recovery, sustained focus · Not read
No signal in any collected stream. Not “fine” — unread. One interview probe (“what does the week look like by Thursday?”) would light it up next time.
Open Mind — i.e., cognitive load, mental flexibility · Not read
Recurring topics in meetings looked adjacent to this, but the evidence pattern belongs to the loop failure below; we didn't stretch it.
Intentional Space — i.e., focus protection · Not read
One thin positive mention; too little to read either way.
Optimized Tools — i.e., tool fit & friction · Working · Confirmed
The day-to-day stack fits. Questionnaire item 5 is among your three strongest, and two respondents volunteered, unprompted, that the tools are genuinely fine. Whatever is wrong here, it is not the tools — which matters, because the tempting fix (a new platform) would treat the one thing that isn't broken.
Feedback Systems — i.e., signal loops · Blocked · Confirmed — the bottleneck
Argued in full in Section 4.
Generative Story — i.e., the team narrative · Strained · Indicated
A mild “nothing we ship seems to matter” note runs through the retro and one interview — though not uniformly (one member explicitly rejects the decline framing: growth outpacing infrastructure, not decay). We read this as downstream of the bottleneck: a team that cannot see what its shipments do will eventually narrate that they do nothing.
Clear Mission — i.e., mission clarity · Strained · Indicated
The Northwind-vs-V2 ranking stalls in planning, and a March “no” has decayed into ambiguity. Also read as downstream: you can't rank what you can't score. Re-read at day 30 before treating separately.
Empowered Role — i.e., role ownership · Not read
One ambiguous moment (a decision nobody owned) reads as a loop symptom, not an authority problem — we'll check that reading with you directly at the debrief.
Grounding Values — i.e., values congruence · Not read
Ignited Curiosity — i.e., real engagement · Working · Confirmed
Your highest questionnaire score of all twelve, visible live in the transcripts: an engineer's unprompted weekend spike met with “send me what you've got, I want to poke holes in it.” The engagement your survey measured was real. It just isn't the problem — which is why the survey couldn't find the problem.
Visualized Vision — i.e., shared vision · Not read
Section 4
The Bottleneck
Feedback Systems — i.e., signal loops · the argument, stream by stream
The evidence converges from every stream collected. Behaviorally: 1 of 5 decisions closed in the observed planning meeting; V2 shipped three weeks prior and its PM had no adoption number (“I mean. Good question.”); the team's own dashboard dismissed in a breath — “Nobody opens Pulse” — by the people it was built for; an item marked “let's not let this one drift” still not live two quarters later. In interviews, 4 of 4 described the same gap; the sharpest, from an engineer: “The thing that actually eats time isn't building it, it's not knowing if I need to keep touching it.” On the questionnaire, the lowest team mean of all twelve items (1.82 of 4) — and even the most positive respondent never rated it above “Sometimes.”
How the team is compensating — the strongest proof. Two engineers run private adoption-tracking sheets off hand-written queries. Status moves by direct-message chase. The same questions recur week over week — recurrence is what an open loop looks like from inside a calendar. A team that lacked the capability wouldn't have built the workarounds; the workarounds are the diagnosis, and their cost is your original complaint.
The perception gap. The widest leader-team divergence in the data sits on this exact condition: the lead rated it 4 of 4; the team mean is 1.82. The lead's own note explains it better than we could: “we do have dashboards, so I landed on ‘almost always.’ Rating it made me realize I'm not sure the last time I actually used one myself to check something.” The rating measured the system's existence; the team lives its use. That gap is itself a signal-loop finding.
What it explains. Capable team, flat output: effort without return signal can't compound. Survey up, work unchanged: the survey measured sentiment — and sentiment here is genuinely good — while the block was structural. The strain on mission and narrative: downstream, both.
The case against, taken seriously. “This is really a prioritization problem.” The stall is real — but the March decision was made and then decayed because nothing tracked it: a closure failure wearing a strategy costume. And your own team's “change one thing” answers asked for decision-closure and an adoption number — not for strategy. We diagnose the condition that's Confirmed in four streams before the one that's Indicated in two.
Section 5
What To Do First
The closing loop — two habits, one named owner, 30 days
1 · Decisions close in the room. Every decision raised in the weekly leaves with an owner and a date, written where the team already takes notes. When it can't close, that's said explicitly — “parked” is a decision too.
2 · Every shipment gets one number. One adoption metric per shipped feature, reviewed for two minutes the following week. Start from the tracking sheet that already exists on this team — make it shared, not private. Do not build anything new to do this.
Week-by-week, working looks like: week 1, awkward and slow; week 2, the number gets asked for before it's offered; week 4, the baseline has visibly moved. What it needs from the lead specifically: ask for the number, never shoot the messenger of a bad one, and let the owner own it.
What NOT to do first. A new analytics platform — your tools scored among your best conditions; the last dashboard didn't fail for lack of features. And another survey or engagement initiative — sentiment here is strong and already measured. In your own team's words, from the questionnaire: “Please don't recommend another survey. We just did that.”
Section 6
The 30-Day Indicator
One observable signal — not a score
Decisions leaving the weekly with an owner and a date: from 1 in 5 (observed baseline) to 4 in 5. Counted by the loop owner from the team's own notes; reviewed together at the day-30 call (booked at the debrief). Secondary check: an adoption number reviewed for every feature shipped in the window.
Section 7
Where This Goes
Day 30, one of three honest recommendations: done — the indicator moved and the team runs with it (a real outcome; we'll say it plainly); adjust — right condition, wrong-sized habit; or next layer — the loop now produces signal, and ranking Northwind-vs-V2 with real numbers becomes the natural follow-on. If the team wants the individual-level picture behind the team-level fix, the Flow Map Session gives each person their own map in one session. No pressure attaches to any of these.
Appendix A
About the Method
The twelve conditions this report reads are the twelve Keys of the FourFlow framework — four dimensions of the conditions under which good work happens (appearing in this report as People, Tools & Systems, Direction, Values), three Keys each — built and practiced at fourflowos.com. The diagnostic stance: the blocker is always a condition, never a character flaw; diagnosis precedes intervention; evidence precedes verdict. AI was used to read the evidence base at depth — every transcript, interview, and response, against all twelve conditions — and the diagnosis, the argument, and every sentence of this report are the practitioner's.
Appendix B
Evidence Index
Per-finding pointers to stream and volume (never raw transcripts) available on request. Interviews confidential and non-attributed; recordings announced in advance; no individual scored. All engagement data is deleted 30 days after the follow-through call; deletion confirmed in writing.
The one-page companion artifact
Team Conditions Map
People
how the humans are doing
Tools & Systems
what the work runs on
Direction
where the work is pointed
Values
what's underneath
Full evidence in the Team Conditions Report · 4 streams · non-attributed · no individual scored
This is the deliverable — with your team's name on it instead, and real evidence behind every line.