When you're put on the spot and don't have an answer, say:

"I don't have a view on that yet. I'll come back to you by end of day."

Why it works: It's more credible than guessing, and it commits you to following up.

Use it: When you're asked something you haven't thought through.

Nodding is not the same as agreeing.

You've learned that the hard way, with one person on your team.

They nod in the meeting. They say, "got it." They ask a clarifying question or two, so it looks like buy-in.

Then they leave the room and do it their own way anyway.

The client contacted the wrong way.

The deadline treated as a rough guide.

The report built in the format you specifically said not to use.

You've raised it before. More than once.

Each time, calmly. Each time, reasonably.

Nothing changes.

They heard you the first time.

They heard you the second time too.

What they haven't experienced is a consequence.

Every time they've gone their own way and nothing happened, they've learned something.

They've learned your direction is a suggestion, not an instruction.

And they meant it when they nodded.

In the moment, agreeing feels easier than pushing back. It avoids friction in the room.

The problem shows up later, once they're back at their desk and the old habit takes over.

That's not defiance exactly. It's maths.

If ignoring you costs nothing, the choice makes itself.

Especially when doing it their way feels more familiar, more comfortable, or just quicker.

This is one of the most frustrating patterns in leadership.

Not because it's rare. Because it looks exactly like agreement, right up until it isn't.

You keep having the same conversation about the same incident, and it keeps not landing.

"You didn't follow the process on Tuesday" invites a defence about Tuesday.

"This keeps happening" leaves no room to argue.

One is a debate about a single event.

The other is a statement about what you've noticed.

Stop addressing each incident on its own.

If you raise the report on its own, then the deadline, then the client call, each one gets its own defence.

None of them add up to the pattern they actually are.

Name the pattern, once, and be specific about what happens next.

"I've been meaning to have this conversation for a while. It's not fair on either of us to keep letting it slide."

This tells them you've noticed more than the one thing that just happened.

It also tells them you're not springing this on them out of nowhere.

"This isn't the first time. The report went out in the wrong format last week. The client call went ahead without checking with me first. Now this. I'm not listing every example, I want it to stop from here."

Give them two or three concrete examples, not the full list.

Specifics tell them exactly what you mean. A running tally invites them to argue about which ones really count.

The point isn't proving the case. The point is what happens next.

"I shouldn't have to raise this twice. I'm trusting you to sort it out this week."

Notice what this does. It's not a threat.

It's an expectation, with a deadline attached.

"I want to check in on this next week, to see it's actually changed."

A deadline without a check-in is just a hope.

I've coached leaders who avoid this exact conversation because it feels like a bigger deal than the behaviour warrants.

It's not a bigger deal.

Letting it run for another month is.

You're not being difficult by naming this plainly.

You're doing the part of managing someone that most people skip, because it's uncomfortable, not because it's optional.

Nodding along was never the goal. Changed behaviour was.

Say it once, properly.

Then hold them to it.

That's not you being hard on them.

That's the job you're actually being paid to do.