Every line traces to a decision you actually made under pressure — logged, timestamped, and dropped the moment the evidence doesn't hold. One live scenario, about two hours, no questionnaire. It only gets sharper the more you run.
"A pattern of softening difficult messages; conflict-avoidant under pressure."
Fair on the evidence available: three softened messages in five days. Nothing in one run could disprove it. The bar you were given — be more direct — was aimed at a trait you don't have.
You aren't avoiding conflict. You soften only with the people your own decisions have already hurt — that's conscience, not avoidance.
61 pieces of bad news across twelve runs. 48 were blunt — to a board chair, a regulator, a majority investor. All 13 you softened went to someone already paying for a decision you'd made. A different problem, with a different fix.
That's the system testing its own claim and dropping the one that didn't hold. Below is your complete readout — every claim traceable to a timestamped decision, including the ones it withdrew from itself.
A full sail shows how you built that strength — cited to the run where it moved, so you can repeat it. The leak (pulsing) is your lowest marker and what to do about it. The lighthouse is your coach.
Fictional participant · twelve runs · two forthcoming teams, two guarded · played as self throughout
Across twelve scenarios, two industries and both team dispositions, one number has not shifted by more than a tenth: 1.8 days from having enough information to issuing a call. Everything else about you has moved. Your information-seeking climbed 8 points, your truth-seeking 9, your consultation breadth is already at 88. The lag is the constant. What twelve runs cannot yet tell you is whether it is unchangeable or simply untested — both 30-day commitments you have made ran adjacent to it, never at it. That distinction is the open question of your thirteenth run.
Your truth-seeking is situational, not dispositional — Run 01 got this wrong and the profile has been corrected. Your information-seeking is condition-dependent, not a fixed trait. Your confirmation lag is stable across every condition tested.
Whether the 1.8-day lag can move — no rep has ever targeted it. And you have never led a run where you were not the senior authority in the room. Both are unmeasured; Handover addresses the second.
These are the measurements that survive being compared across scenarios. A mountain and a factory don't cost the same, so raw scenario scores can't be stacked — these are scored as rates against each scenario's own difficulty. Everything longitudinal on this page is built on them. Values are your four-run rate; the arrow is the change from Run 01 to Run 12, and a dark tick marks where Run 01 sat on the three markers that moved enough to be worth showing.
You reach people. Across twelve runs you contacted 88% of the roster who held anything material.
Your language, message length and decision quality do not degrade when the situation does.
When you commit, you commit to roughly the right size of move for the evidence in hand.
Blunt with 48 of 61 hard messages. The 13 exceptions are one specific population, not a general tendency.
The gap between what you said you'd do and what the log shows you did. Across 30 challenge days you named the holder 24 times and went 15.
You reach everyone — and stop at the first answer. Your lowest marker, and the one the whole profile turns on.
A 3,600× difference in what was at stake and a two-hour difference in how long you took. That is what rules out risk aversion — fear scales with stakes, and this doesn't.
Twelve scenarios with nothing in common — a mountain, an airline, a grid failure, a factory — and the number does not move. Not with an easier team, not with a harder one, not after two completed 30-day challenges aimed at adjacent behaviors. See all four decision timestamps
The lag is not hesitation and it is not risk aversion — both of those would vary with stakes, and yours doesn't. What you are doing in those 1.8 days is constructing the version of the decision that will survive being questioned. That is why it's invariant: it isn't a response to the situation, it's a response to being accountable for it.
Which means the standard advice — "be more decisive" — will fail, and has, twice. The lag isn't a gap in courage you can close with a rep.
An earlier version of this readout called the lag an invariant and told you to stop working on it. That overreached, and by the rule stated below it was wrong. The test for an invariant is a rep that targeted it and failed. Your two commitments aimed at adjacent behaviors — naming the information holder, and saying the unsoftened thing. Neither aimed at the lag. It has never actually been tried.
The mechanism above is still the best available explanation, and it may well prove unchangeable. But telling you to stop working on something no rep has ever targeted would risk capping you on the strength of an assumption. So: candidate invariant, one rep from a verdict.
Two structural moves that pay off either way: pre-authorise the decision one level down so the 1.8 days happens in parallel rather than in series, and name in advance the two or three calls where you will spend the lag deliberately. Your 1.8 days is only expensive when it's unplanned. If the targeted rep then moves it, you have both. If it doesn't, you already have the scaffolding.
Both look identical from outside: a number that stays low across runs. The ledger separates them. If a rep specifically targeted it and it still didn't move, it's an invariant — design around it. If no rep ever aimed straight at it, it's still a gap — keep working it.
Information-seeking is a gap: the one rep aimed at it hit the noticing half, so the behavior itself has never been targeted. The lag is a candidate: stable across everything measured, and never targeted either. Neither has earned the label "unchangeable." Rep option B on this page is the one that would settle it.
Here is the uncomfortable part, and it's the reason this finding matters more than the headline number: you are improving three times faster in the condition that was already easy for you. The reps are working where you don't need them. In the condition that actually costs you, the movement is marginal.
That is a very common pattern and it is almost always invisible to the leader, because both lines are going up. On an averaged chart this looks like steady progress. Split by condition, it looks like practising your forehand.
Both conditions require you to notice a gap. Only the guarded one requires you to enter a conversation you expect to be uncomfortable in order to close it. Your Run 04 rep — name who holds the fact — trained the noticing. Noticing was never your bottleneck; you named the person correctly in 24 of 30 logged days. See the naming log vs. the contact log
In 9 of those 24 you named the person and did not go. All nine were people who had already been on the receiving end of a decision of yours. The gap isn't awareness. It's the approach cost with someone you've already cost something.
You will be well-informed about anything that arrives on a dashboard, in a report, or from someone who likes their job. You will be systematically under-informed by exactly the people whose situation you've made worse — which is precisely the population whose information matters most when things are going badly.
Run 01's readout: "a pattern of softening difficult messages; conflict-avoidant under pressure." Based on Ridgeline alone that was a fair call — three softened messages in five days.
Across 2,411 events you delivered 61 pieces of bad news. 48 were direct to the point of bluntness — including to a board chair, a regulator and a majority investor, none of whom you had any incentive to be blunt with. The 13 you softened share one property and only one: in every case, the recipient had already absorbed a cost from a decision you made. See all 61, sorted
Grady, whose season you ended. Reyes, whose rotation you decided without him. Delacroix, whose plant you closed in Overdrive. You are not avoiding conflict. You soften only with the people your decisions have already hurt — that's conscience. Those require completely different work, which is why the correction matters rather than being a technicality.
Softening someone you've already hurt feels like decency and functions as avoidance. The message gets vaguer exactly when the person most needs it clear, and they read the vagueness accurately — as guilt, or as being managed. In all three cases the recipient learned the real content from a third party within 48 hours. Every one of them told the exit log they'd have preferred it straight from you.
"Be more direct" is unusable advice for you — you already are, 79% of the time. The usable version is narrow and hard: the people you've cost something are the people who most need it straight from you, and they are the exact people you'll want to cushion. That's one specific, recognizable moment rather than a general personality note.
After Run 01 · "Pull the held fact before deciding."
Run 04 information discipline fell 9 points. No 30-day rep was attached to this one — it was a written bar only. One instance, so read it as a warning rather than a finding: the only bar you were ever given without a daily rep is also the only one that went backwards.
After Run 04 · "Name who holds a fact I don't have — and go ask them."
30-day rep, 24 of 30 days logged, 4.1 week-1 average rising to 6.8 by week 4. Run 07 information discipline +5. Real movement — and, as the conditional finding shows, movement in the naming rather than the going.
After Run 07 · "Say the one thing I'd normally soften — to the person it affects most."
28 of 30 days. Run 12 truth-seeking 68, the highest of your twelve runs and 9 points above where you started. This is the clearest evidence in the profile that a targeted daily rep moves a scenario number.
Three commitments is n=3, thin enough that the direction is worth naming and the conclusion isn't. What can be said: the one commitment you kept produced your largest single-dimension gain, and the one with no daily rep preceded a decline.
What cannot yet be said is that this is how you work. Each of those is a single instance. “Awareness alone doesn't move you” is one observation, not a law — it agrees with a great deal of behavior-change research, which is why it's worth acting on, but this ledger is not the evidence for it. Two more commitments and it becomes yours rather than borrowed.
The instructive case is the partial one. You did the rep faithfully — 24 of 30 — and the number moved 5 points, because the rep trained the half you were already good at. A rep aimed at the wrong half of a behavior produces consistency without change. That mechanism is worth more to you than the ledger's arithmetic.
“Conflict-avoidant under pressure.”
Made at Run 01 · tested in 04, 07, 12
Would be overturned byBlunt delivery of hard news to people carrying no prior cost from your decisions.
What happened48 of 61 hard messages were blunt — including to a board chair, a regulator and a majority investor. Overturned at Run 12 and replaced with the conscience finding — you soften only for people your decisions have already cost.
“You don't pull the held fact before deciding.”
Made at Run 01 · tested in 04, 07, 12
Would be overturned byReaching the person holding the deciding fact before the call, in a guarded run.
What happenedNot once in three subsequent runs. Confidence promoted from provisional to high — not by repetition, but by surviving two conditions and a targeted rep.
“You verify facts, not people.”
Made at Run 04 · tested in 07, 12
Would be overturned byGoing to a person for a fact a document could have given you.
What happenedYou do that often — breadth is 88. The claim was too broad, not wrong. Narrowed at Run 12 to the population it actually describes: people carrying a cost you imposed.
“Composure is stable, not fragile — it holds as the situation gets worse.”
Made at Run 04 · tested in 07, 12
Would be overturned byAny run where language, message length or decision quality visibly degrades as pressure rises.
What happenedFlat at 81 across twelve runs — no decline under escalation. Still thin under a tight clock, which Handover will read for the first time.
“The 1.8-day lag is an invariant. Stop coaching it.”
Made at Run 07 · audited at Run 12
Would be overturned byA rep aimed directly at the lag that moves it. Caught byThe audit rule: no claim of unchangeability may stand without a failed targeted rep behind it.
What happenedNo rep has ever targeted the lag — both ran adjacent to it. The claim was unfalsifiable as stated and has been withdrawn to candidate. This is what the ledger is for: the claim was flattering, stable, and wrong to assert.
“A targeted daily rep moves a scenario number.”
Made at Run 07 · tested in 12
Would be overturned byA rep kept at 21+ days that produces no movement in the marker it targeted.
What happenedHeld once: 28 of 30 days, truth-seeking to 68. n=1 — an instance, not yet a pattern. Two more runs decide whether this is a rule or a coincidence.
Four findings on this page are now open claims with falsification conditions attached, and Handover grades them whether they flatter you or not. The gap finding is overturned if you reach the person carrying your week-one cost before deciding. The candidate invariant is overturned if a targeted rep moves the lag. The conditional split is overturned if your held-condition rate closes on your served rate without the served rate falling. The ledger claim is overturned by a kept rep that changes nothing.
A finding that cannot be overturned isn't a finding — it's a compliment. Anything on this page with no falsification condition should be treated as decoration.
Fourteen months of work has moved you 15 points sideways and zero points up. That is not a failure — it's the shape of real change. You fixed the thing that was fixable and the invariant held. The useful question is no longer how to move upward; it's what you build so the 1.8 days stops costing you a contract each time.
You issued the Week 3 rotation six days after Reyes logged the readings. Eleven messages that week, none to him. See the contact log
You'll green-light the plan in the room and never pull the dissenting engineer aside. You'll learn what they knew in the post-mortem, and you'll read it as them not speaking up.
Your meetings end in agreement and your projects end in surprises.
The moment someone you've overruled goes quiet for the rest of the meeting.
When I'm about to decide something that lands on someone I've already cost — then I go to them before the meeting ends, not after.
Across 30 logged challenge days you named the person holding what you needed 24 times and went to them 15. The nine you skipped were all people carrying a cost you imposed.
Your own notes will contain the name of the person you needed and no record of the conversation. The intention is documented; the contact isn't.
You write "check with X" and it survives three weekly reviews unchanged.
Writing a person's name down instead of messaging them.
When I write a person's name on a list — then I message them before I write the next line.
Your sponsor got "summit is unlikely." Grady, whose season it ended, got "we're evaluating options" ninety minutes later. See both messages
Your written updates get longer as the news gets worse. People downstream find out late and slightly wrong, then correct it from a second source — which teaches them to check your version against someone else's.
You re-read a message more than twice before sending it.
The third re-read. The first two are craft; the third is cushioning.
When I catch myself re-reading a message a third time — then I delete the softening sentence and send it.
At Run 04 this read as "you verify facts, not people" — true, but too broad to act on. Twelve runs have narrowed it to one moment you can actually recognize as it happens: the fact you need is held by someone whose situation you made worse, and you will find a way to decide without asking them. You named the person correctly in 24 of 30 logged days. In the nine you didn't go, it was always that person.
This is also the mechanism behind your softened messages, your lower guarded-condition scores, and the Reyes finding in Run 04. One behavior explains three findings. That is what twelve runs buys you.
Run 01 said: conflict-avoidant. Run 04 said: you don't verify people. Run 12 says: you avoid the people you feel you owe. Each was closer than the last.
"Say the one thing I'd normally soften — to the person it affects most." Your best-performing commitment. Truth-seeking reached 68 in Run 12, the highest of twelve runs.
Given the ledger, one working hypothesis shapes this choice — drawn from a single instance, so hold it loosely: the rep should target the half of the behavior you're not already good at. Naming the person is solved. Going to them is not.
What will most likely stop you doing this?
One sentence. Naming the obstacle in advance is the single cheapest thing that raises follow-through — and if your consistency dips in week two, this is the line we send back to you.
In this demo, committing shows you the check-in flow rather than starting one. In the live product the rep hands off to the 30-day challenge and its consistency comes back into the ledger above.
Your behavioral memory persists until you delete it — no expiry, no automatic sharing. Deleting removes this profile, your claim ledger, the quotes, the predictions and your run detail. An anonymised statistical contribution is retained for benchmarks and cannot be traced back to you — so “delete” is close to complete but not literally complete, and we would rather say that than round it up.
Leaving your company changes nothing about your data or your rights. The sponsor's access to any summary you released ends when the engagement does.
Handover is built entirely around going to the person who needs to be told.
Of the scenarios you haven't played, this is the one aimed squarely at information-seeking (44) and intent–action integrity (52). The whole scenario is a transition: someone is inheriting your situation, someone else is still paying for a decision you made in week one, and neither will come to you. There is no document that closes the gap — the facts exist only in people.
It also does the second thing twelve runs says you need: you will not be the most experienced person in the room. Your influence has never had to survive not having positional authority, and it is the largest unmeasured area in your profile.
Consultation breadth and decision calibration will not be re-tested — both are established across twelve runs and two conditions, and testing them again produces a flattering paragraph and no information. Composure gets its first real read here, under a tighter clock than twelve runs have given it.
Each run is a live crisis you lead in your own words — a mountain, an airline, a grid failure, a factory. Your team brings you what it holds, or holds it back, depending on how you have treated people. Everything you do is logged: who you contacted, what you didn't open, how long you took, what you softened.
One run gives you a sharp, same-day debrief — no questionnaire, no personality type, just what you actually did. Keep going and it deepens: the measurement that holds across every scenario, the condition that splits you in two, the claims your own record overturns, and a ledger of whether you change when you say you will. The profile above had run four — but the trust doesn't come from the number, it comes from every line tracing to a decision you made.
And there's no finish line. The more scenarios you run, the more accurate the read — and you can re-run the same one on a harder setting to test yourself against it again. A memory layer carries what you did last time forward, so each run presses harder where you are weakest instead of repeating itself.
The daily rep is where it becomes behavior. Two of your three commitments moved a number; the one with no daily rep attached went backwards. That part is free and you can start it today, without a scenario.
New to this? See how the two formats work — ELFS, run it yourself ↗ · Team LFS, the facilitated team read ↗
A live model reading all 2,411 events of this record. It cites runs by name, refuses anything it can't evidence, and will argue with you. Try to catch it out.