How to use a decision journal before asking for a raise

Write down the specific case for the number, what you will do if the answer is no, and the honest reason you are asking this month rather than three months ago — before the conversation, not while you are replaying it afterward. Asking for a raise is a clean decision-journal case: something real is at stake, you genuinely do not know how it will go, and you usually find out inside a single meeting instead of waiting months. The entry does not need to make the case sound stronger than it is. It needs to exist before you ask, so that later you can tell whether the case was solid or the timing was doing all the work.

The conversation is decided twice

Once in the room, and once earlier, in whatever made you pick this particular week to bring it up. Most people only prepare for the first part — the talking points, the number, the answer to "why do you deserve this." The second part usually goes unexamined, and it is often the part that determines whether the case sounds solid or defensive. A request built on six months of a genuinely expanded role sounds different from one built on a bad Tuesday, even if the words in the room end up nearly identical. Writing down why now, honestly, before you ask, is what lets you tell the two apart later — and it costs nothing if the reason turns out to be a good one.

The distortion runs in two directions

Seeing a coworker's number, reading a job posting with a higher range attached, or a specific expense landing at home can make asking feel urgent immediately — sometimes before you have actually named what has changed about your work, which is the part a manager can act on. Comparison and money pressure are real, but neither one is a case; they are a reason to go build one. In the other direction, a specific fear — sounding pushy, being told the budget is not there, or the vague sense that a raise should just arrive if you are doing good work — can keep someone quiet for a year or two past the point the case was obviously sitting there. That second direction is the one that goes unnoticed longest, because not asking never feels like a decision. It is one, and it is worth writing down just as much as asking is.

What to write before you ask

Three lines, before the conversation, whichever direction you are leaning.

• The case, in terms someone else could check. Not "I work hard," which nobody can verify or deny. What specifically changed since the last raise or review — a project you now own that used to need someone more senior, a scope that grew without the title catching up, a number you can point to. If the only thing you can name is time passed, write that down honestly too; it changes what kind of conversation this actually is.
• What I will do with a no. Decide this before you are sitting across from the answer, not in the middle of it. Ask again on a set date, start looking at what the role is worth elsewhere, or accept the timing was wrong and pick a real date to revisit it. Naming this in advance means the plan does not get written in the emotional minute right after you hear no.
• The honest reason it's now. A comparison, an anniversary, a specific accomplishment, a bill. It does not need to be a noble reason, only a true one — it is the line that later tells you whether the timing was carrying the case, or whether the case would have held up any month you asked.

Name what would count as a real no

A no is not one piece of information; it can mean the case did not land, the money genuinely is not there this cycle, or the person across from you does not have the authority to say yes regardless of the case. Before you ask, write down what response you would treat as a real no — clear, with a reason that would not shift if you asked again next quarter — versus a soft one worth revisiting, something tied to a specific future date or a specific target you would need to hit. Without that line written ahead of time, it is easy to spend a year quietly re-litigating an answer that was actually "yes, later," or to keep asking against a no that was never going to move.

Read it back against what was actually said

If the answer is yes, check it against the case you wrote, not just the outcome. Did the specific thing you named carry it, or did something else do the work — a competing offer, a budget cycle that happened to open up, a manager who advocated harder than expected? Knowing which one it was tells you what to build next time. If the answer is no, reread the entry against the actual reasoning you were given, not your mood in the days after. A no that matches a gap you already suspected is useful information about the case. A no that cites something you never wrote down — a reason unrelated to your work at all — is worth noticing precisely because it means the case was never really the variable.

When it stops being about the case

If the case keeps being solid across two or three cycles and the answer stays no for reasons that never connect back to anything you named, that pattern has stopped being about how you ask. It is information about the job, not about your negotiating, and it deserves to be written down as its own line rather than folded into another hopeful entry that this time will be different.

None of this needs an app to work — the three lines fit in a notes app as easily as anywhere else. CreedOS's daily check-in has a short note field for exactly this kind of entry, and it sits squarely in the money category among its six template areas, though the timing and the aftermath of a raise conversation often touch the emotion and social ones as well. If the same pattern keeps showing up across review cycles, an AI coach can help think through what a standing standard for it would look like once you have named it. It is free, with no in-app purchases.