Management by Implication

A client described a meeting with their boss last week. Nothing dramatic. Routine catch-up about workload and upcoming deadlines. Then the boss said something like: the team sometimes needs to put in extra time on weekends and during holidays "when needed."

Just a phrase. Slipped in. Casual. Not a demand. Not a request. Nothing written down, nothing agreed to.

My client caught it immediately and has been sitting with it ever since. They never agreed to work weekends, much less holidays. It was never part of the conversation when they joined. But now "when needed" is floating in the air between them, and neither person has defined what it means. My client doesn't want to push back on something that wasn't technically said. The boss doesn't have to own something they never technically asked for.

That's not communication. That is management through implication. And it's one of the more subtle forms of bad leadership I hear about regularly in sessions.

So we went back to basics. What is he actually doing this job for, and why?

It's not to impress the boss. Not to become CEO. Not to prove something. He's been in the industry long enough, worked hard enough, and sacrificed enough that he has a clear and specific goal: financial freedom. A defined number. A defined point at which he can stop trading his time for someone else's agenda and start living by his own. He went into that role knowing exactly what he needed from it.

That kind of clarity changes everything.

Once you know what you're actually there for, you can run every decision through that filter. When to boss says, working weekends and holidays "when needed." Does that get him closer to financial freedom? No. Does it cost him something he won't get back? Yes. Does his boss's implicit expectation have anything to do with the reason he took the job? No.

This is when it is good practice to know your values (and your boundaries). A values assessment is a tool to help. Not a theoretical exercise about what matters to you in the abstract. A concrete grounding in what you're actually trading your time for, and whether any given demand on that time serves it or erodes it.

When you're clear on your values, someone else's expectations stop having the same grip on you. They become something you can assess against your own standard rather than something you absorb and feel guilty about not meeting.

The boundary becomes obvious once the values are clear. He's not working weekends because working weekends doesn't serve what he's there for. That's not a negotiation. That's alignment.

And that is something bad leadership consistently tries to disrupt: your connection to the reason you showed up in the first place. The boss who implies rather than asks is counting on you not having a clear enough answer to "why am I here?" to push back.

I've talked about the psychology of work pressure in more depth in In The Rooms. Three complaints show up in almost every corporate counselling session, and they all connect to the same root. Worth watching if any of this is familiar.

“

At some point, that corporate ladder you're climbing stops being ambition and becomes a trap, because you're always looking for the next thing.

William Ferrell, M.Couns.

Watch Video3:47

Why This Is Harder Than It Looks

Most people don't push back on management by implication because they don't feel like they have the standing to. Nothing was formally agreed, so there's nothing formal to contest. The phrase sits in the room and does its work quietly: it makes you feel guilty for not working weekends before anyone has even asked you to.

That guilt is the mechanism. It works because a lot of people in high-pressure roles have tied their identity closely enough to the job that their employer's expectations feel like a measure of their own adequacy. If the boss expects it, maybe it's what a serious professional would just do. Maybe everyone else is already doing it and not saying so.

This is worth separating out clearly. Why setting boundaries is so hard is the companion piece to this one: understanding why it's so hard to say no even when you know you should.

That's not a personality trait. It's a skill. And it starts with getting clear, not on how to say no, but on what you're saying yes to.

What "When Needed" Is Actually Telling You

My client isn't in his job to be its most devoted employee. He's not there to climb to a title that impresses people at dinner parties. He's there to hit a number that gives him the freedom to live on his own terms. That's his value system, and it's a completely legitimate one.

When he's clear on that, "when needed" becomes information about the boss's expectations, not an instruction he's obligated to absorb. The boss's implicit expectation has nothing to do with the reason he took the job. So it doesn't get to rewrite the terms of it.

That's what being true to yourself actually looks like in a work context. Not performance. Not a statement. Just a clear internal map that tells you which demands are worth meeting and which ones belong to someone else's agenda.

The boundary isn't the end of the story. It's the result of the clarity that came before it.

If the psychological side of high-pressure work is something you're dealing with - the guilt, the identity, the sense that you've lost track of what you're actually there for - men's therapy is a good place to look at it properly.

If you've lost track of what you're actually doing the job for, that's worth looking at. Book a session.