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!

Ambiguity gets read as a no. Say the sentence.

I asked my daughter for wise words before a big meeting once. She said: "Just say what you want. Then they know." Then she went back to her drawing.

That's the whole protocol, and almost nobody runs it. Today: why hinting fails structurally, and the format for declaring intent so it actually lands.

Why hinting fails

From the decision-maker's chair, hinting looks like nothing. Literally nothing. I sat in years of talent reviews where a name came up and the room genuinely didn't know what the person wanted. "Is she interested in managing?" "Would he relocate?" Nobody knew, so the room guessed, and rooms guess conservative. Ambiguity gets read as a no, because assuming interest that turns out not to exist is embarrassing for the assumer, and rooms avoid embarrassment above almost everything.

Meanwhile, the people who had declared, out loud, to the right person, got remembered at exactly the right moments. Not because declaring obligated anyone. Because when an opening appeared, their name arrived pre-attached to it. Openings are allocated in minutes (day 1), from whatever the room already knows. Declared intent is the cheapest possible way to be in the room's working memory at that moment.

The format

"I want [specific thing], and I'd like to know what it would take."

"I want the Head of role when Sarah moves on. What would it take?" "I want to be in the room for Q4 planning." "I want an international assignment inside two years."

The second clause matters as much as the first. It converts a declaration into a request for conditions (day 5's mechanism, applied to advancement), which gives the other person something concrete to do with your statement. Without it, a declaration is a mood. With it, it's an open workstream with an owner.

The delivery rules

Rule one: a 1:1, not a corridor, and not appended to another agenda. Intent declared in passing gets processed in passing.

Rule two: no preamble and no apology. The declaration loses most of its force wrapped in "I know this might sound ambitious, and obviously whatever's best for the team...". Say the sentence, then stop talking. The silence after it is the other person's turn.

Rule three: repeat quarterly. Declared ambitions decay on the forgetting curve like everything else (day 2). A quarterly refresh ("still very much aiming at the Head of role; here's what I've done about the conditions") keeps the intent current without becoming a nag, because each repeat arrives with new evidence attached.

The objection you're feeling

"Shouldn't my work make this obvious?" No, and the belief that it should is the single most expensive assumption ambitious people carry (day 17 dismantles it fully). Your work demonstrates capability. It cannot demonstrate desire, because desire isn't visible in output. Two people producing identical work can want completely different futures, and the room knows it, which is why the room waits to be told.

Why this compounds

Declared intent doesn't just position you for the opening you named. It reclassifies you generally: you become someone with a known direction, and people with known directions get brought opportunities adjacent to them ("it's not the Head role, but it's a step towards it, and I thought of you"). The undeclared get considered for nothing because they're a guess in every direction.

Your assignment

Write your sentence, both clauses. Book the 1:1 where you'll say it. Both halves this week; the sentence without the booking is journalling.

Talk soon, Yasar

P.S. Nothing to buy today. Say your sentence, then reply and tell me you said it. Those are my favourite replies.