I catch myself reading meaning into the punctuation in my boss’s Slack replies. A short “sounds good” used to mean exactly that. In a new role, the missing exclamation point can start to look like a verdict.
They regret promoting me.
A delayed reply becomes evidence. A rescheduled one-on-one becomes avoidance. You are no longer responding to the message in front of you. You are building a story about what your boss thinks of you.
Sometimes the story is wrong. Sometimes the concern is grounded in something real. The problem is that guessing does not help you tell the difference.
Consider Rowan, newly promoted to senior manager. The transition is rough. Two direct reports used to be peers, and now their updates feel guarded. A cross-functional project is behind schedule. Rowan is working long days and quietly taking on individual-contributor work because delegating feels risky.
Then Rowan’s boss reschedules their one-on-one again.
The message says there is an urgent client issue and they will meet next week. Rowan reads something else: She sees the project slipping. She knows she picked the wrong person.
That interpretation might be right. But the message alone cannot tell Rowan. What it can do is trigger the familiar urge to prove worth through more hours—or to ask for reassurance in a way that never gets near the actual work.
Mind-reading can feel safer than asking for specifics. If you keep guessing, you do not have to hear feedback you might not like. You can keep working harder and hope the anxiety eventually quiets down.
Usually, it just finds new evidence.
Rowan starts to write: “No worries about the meeting. Just checking that we’re still good and that I’m meeting expectations.” It is an understandable question. But it asks the boss to settle a feeling, while leaving the project, team dynamics, and expectations mostly unnamed.
Rowan revises it:
“Understood on the reschedule. Before we meet next week, I want to make sure my priorities match yours. The Q3 project is tracking behind, and I’m spending a lot of time navigating the team transition. Can we use part of our next one-on-one to discuss what success looks like right now, where you think I should focus, and what needs to change?”
The difference is not that one message is professional and the other is not. Wanting reassurance is human. The difference is that the revised message gives both people something concrete to discuss.
It names the work that is not going well. It makes the new team dynamic visible. And it asks for direction rather than asking the boss to read Rowan’s mind in return.
That conversation may clarify expectations. It may surface a real concern about the project, the role, or Rowan’s approach. It cannot guarantee reassurance, and it cannot prove what the boss privately thinks.
That uncertainty matters. If your boss repeatedly cancels check-ins, withdraws support, or avoids giving clear feedback, do not explain away a pattern as anxiety. A calibration conversation cannot fix every management problem or establish that a promotion was the right fit. But it can move the discussion from imagined motives to observable work.
Ask what matters most now. What should you stop doing? Where are you spending time that belongs with someone else? What would your boss like to see change, and by when? Bring your own read of the situation, too. The project is behind. The team is adjusting. Here is what you have tried, and here is where you need a decision or support.
Then listen to the answer. Not for a guarantee that you are valued. For information you can use.
A promotion can make ordinary ambiguity feel personal. You may find yourself treating every pause as a judgment because you want the new title to prove you belong. But your boss cannot clarify expectations you never bring into the conversation, and you cannot manage a role by decoding punctuation.
Make the work visible. Ask for the calibration. The answer may be uncomfortable. At least it will be about something you can address, not a verdict you wrote for someone else.
