Write down the worst case, the most likely outcome, and what you'd do if each happened.

Why it works: The worst case gets all your attention until you've written it down next to the others. Having a plan for it takes most of the worry away.

Use it: When your mind has already played out the conversation badly.

You led it.

You made the call to change supplier.

You rewrote the plan when the first version stalled.

You had the conversation nobody else wanted to have.

Then your CEO asks how the project went.

And you say: "The team did a brilliant job."

That's true. It's also not the whole story.

I'm not criticising the instinct. Crediting your team is a good habit.

But when you describe every result as a team effort, nobody asks for your view on the next big decision.

The people deciding who gets the bigger remit hear "the team".

They don't hear the judgement behind it.

And you walk out irritated with yourself, because you know exactly what you did.

Saying "the team" is the safe option.

It sounds generous. It sounds modest. Nobody will ever call you arrogant for it.

Your brain is protecting you from being judged as self-promoting.

So it picks the answer with no risk in the moment.

The cost arrives later.

When you don't describe your part, other people fill in the gap.

Usually with a version where you coordinated, supported or kept things moving.

Not the version where you made the decision.

I think this is one of the most common reasons capable leaders get overlooked.

It isn't their results.

It's that nobody can see how they got them.

You've probably also watched someone else take the credit and decided you never want to be that person.

But the opposite of that isn't saying nothing, you've merged two separate things.

Giving credit and owning your contribution feel like opposites.

They aren't. You can do both in one sentence.

Sharing credit is generous.

Always hiding your part isn't humility. It's editing yourself out of your own work.

Stop describing effort. Start naming decisions.

"I worked incredibly hard on this" sounds like boasting.

"I decided X because of Y" sounds like information.

Use this order: your decision, your reason, then credit.

Before: "The team pulled together and we got it over the line."

After: "I made the call to change supplier in week three. The team made it work."

The reason is what shows your judgement.

"I decided to pause the launch because the data wasn't strong enough. Priya and her team rebuilt the forecast in a week."

Notice the credit is specific.

That makes it land harder, not softer.

"It went well. I'm pleased with the call on the supplier, and how the team delivered it."

"Thanks. That decision to delay the launch was a tough one to make."

Say it flatly. Then stop.

Don't add "but really it was the team" afterwards. That's softening, and it undoes the sentence you just said.

"I decided to..."

"My part in this was the decision to..."

"The call I made was..."

If you've got a review coming up, try this:

"I'd like to talk through three decisions I made this year, and what came from each."

That puts your judgement on the table, which is what they're really assessing.

Why this works: facts don't sound boastful. Adjectives do.

"I decided" is a fact.

Use "I" for decisions and "we" for delivery.

Do it when your team is in the room too.

It shows them how to describe their own work.

You'll survive saying "I decided" out loud. I promise.

This week, pick one update you're already due to give.

Before you give it, write down the one decision that was yours.

Then say it. First person. No apology.

Your team won't think less of you. They know who made the call.

The people above you don't, unless you tell them.