He asked for the raise on day four

$ eldr --debrief 5TQ1

POSITION     MOVE
CONFIDENCE   8/10
WINDOW       10d
OUTCOME      acted
LOGGED       day 12
SATISFACTION 5/5
SOURCE       constructed file

This is a constructed worked example, not a customer. Nobody has run a read here yet: the product has not launched and the decision log is empty. The situation and the numbers are written to show how the instrument reads a file of this shape. Real debriefs replace it when there are any.

Nine months of rehearsing a conversation, then eleven minutes of having it. That ratio is the ordinary shape of a money file and it is worth sitting with before the details.

The decision

Ask for a raise, or wait for the annual cycle in five months. He had taken over a second team in November without a compensation change, had the retention argument on his side, and had written, in the free-text input: "I know I should just ask. I have known for months."

That sentence is doing a lot of work. When a man states the answer in the intake and then asks for a position anyway, what he is looking for is not information. It is a forced move, and the instrument is allowed to provide one — that is precisely the mechanism the coin-toss study measured.

The read

MOVE at 8/10, window 10 days. High confidence, and it is worth being explicit about why, since 8 is rare in this log. Three inputs aligned with no contradiction: a documented scope increase, a stated lean that matched the described behavior of someone already preparing, and a decision drag of 270 days with no external date attached — no deadline means no decay excuse, which removes the only respectable reason to wait.

The window was not tied to any external event. It was set to 10 days because that is a length of time in which a conversation can actually be booked and because a longer window on a decision this unblocked would have been a courtesy, not an instrument.

The counter-case, verbatim

The five-month cycle exists and your manager will use it. Asking now converts a raise you were probably going to get anyway into a negotiation you may lose, and it spends the retention argument at the worst possible moment — you have no outside offer and no stated intention to leave, which means the only pressure in the room is your discomfort. Consider that the annual cycle is not avoidance for you; it is the mechanism working as designed.

What happened

He asked on day 4. He requested a 22% increase against a market number he had actually sourced from three recruiter conversations, and he got 9% immediately plus a written commitment to revisit at the cycle with the second team formally in his title.

Satisfaction 5 out of 5, on less than half of the increase he asked for. That combination is the whole reason this example is here: the number was not the thing being bought.

Where the read was wrong

The counter-case predicted the cost — spending the retention argument with no outside offer — and it was right about the mechanism and wrong about the magnitude. He got 9% now rather than a possible larger number later, and a strict money-maximizer would argue the counter-case won on the arithmetic.

What neither the position nor the counter-case priced was the nine months. The value he logged came almost entirely from closing a loop that had been consuming attention since the previous autumn, and no part of the read measured that. The instrument has an input for the cost of waiting, he had filled it in as "moderate", and the outcome note makes clear it was not moderate at all. The most consequential number in this file was the one he guessed at.

That is a known weakness, stated here rather than in a footnote: the wait cost is self-reported, men systematically under-report it, and every read that depends on it inherits that error.

Why 8/10 is rare, and what it is not

A word on the number, because men read a high confidence figure as a strong forecast and it is not one. The 8 here was an audit result: fourteen answers with no internal contradictions, a decision that was one decision rather than two, a window he could actually execute inside, and a counter-case that named a real cost rather than a possibility. That combination is rare, and an 8 should be read as rare rather than as a forecast. It says the argument is coherent. It says nothing whatsoever about whether his manager would say yes, because nothing in the intake had access to his manager.

The reason to publish the number at all is comparative. He ran an earlier read in the winter on the same question and it came back at 5/10 — same job, same scope argument, but at that point he had not sourced a market figure and had rated his conviction at 4. Between the two reads he did one piece of homework and the number moved three points. That is what the figure is for: watching your own file get stronger or weaker as you do or do not gather what the counter-case asked for.

The transferable part

Two things, both cheap.

• Source the market number before the conversation, not during it. Three calls. He did this and it is the reason a 22% ask was not dismissed as a mood.
• If you already wrote the answer in your own notes, ask for a date, not a position. Nine months of certainty plus no date is not deliberation. It is a conversation you are afraid of, and the instrument's job in that file is to put a number of days on it.

For entertainment and reflective purposes only. Not a substitute for professional financial, legal, medical or mental-health advice.