This newsletter post is part of my 45 days series. Everyday for the next 45 days I will send an email to you. Helping you transform your work environment, get you more visible and promoted asap!

"No budget this year" is an opening position, not a verdict.

"There's no budget this year."

Having said that sentence from the approving side of the desk many times, let me translate it: "you haven't given me enough ammunition to win the fight above me, and I'd rather not have a fight I'll lose." There is almost always money. Retention cases, off-cycle adjustments, the quiet pot that appears when someone resigns. What there isn't, is appetite for a weak case.

Most people hear the sentence as a verdict and go quiet for a year. The protocol below converts it into a contract instead. Four steps.

Step one: accept nothing, contest nothing

Arguing with a budget "no" fails, because you're arguing with a policy while the real objection is the case. Accepting it fails differently: silence reads as closure. The move is a third thing, one question, twelve words:

"Understood. What would need to be true for it to happen in January?"

The question doesn't challenge the no. It converts the conversation from whether to when, and it hands your manager homework: they now have to name actual conditions. A target, a scope, a sign-off. If they can't or won't name conditions, that's diagnostic too, and you've learnt something important about this manager a year earlier than you otherwise would have.

Step two: write the conditions down

Within 24 hours, the summary email: "As discussed: if X and Y land by December, we revisit in the January cycle." The mechanism here is well documented in behavioural research: explicit, recorded commitments get honoured at far higher rates than vague spoken intentions. A verbal maybe evaporates. A written one accrues obligation. Nobody replies to that email with "actually, let's not commit to that", because doing so would require them to articulate why.

Step three: deliver against the conditions, visibly

The conditions now function as a private promotion case with a deadline. Log the progress in the evidence file (day 2), reinforce monthly (same protocol), and make sure the delivery is witnessed by the people the money-fight will involve (day 3). You are arming your manager for a battle they now have contractual reasons to fight.

Step four: book the follow-up yourself

In the original meeting, before leaving: "Shall we put thirty minutes in for the second week of January?" Diarise it there and then. This is not optional. The other party to this contract has no calendar incentive to enforce it, and the forgetting curve works on managers' promises exactly as fast as everything else. The person who books the follow-up owns the timeline.

Why this compounds

Run once, this protocol converts one no into one rise at decent odds. Run as a standing habit, it changes something larger: you become someone whose requests always come with conditions, evidence and dates attached. Approvers learn this. Cases from people like that get pre-approved in anticipation of the fight, which is how the second and third rises get quicker. Vague askers train the system to defer them. Precise askers train it to budget for them.

Your assignment

If you're currently sitting on a soft no about pay, or a title, or a role change, send the January question this week, adapted to your cycle. If you're not, file the twelve words. The sentence gets said to everyone eventually.

Talk soon, Yasar

P.S. There are 558 scripts like this in the Ultimate Script Book, and the searchable version lives inside the OVD Lab, which comes with the cohort: https://ovdlab.com/for​