What your boss is carrying

Every boss I've worked for was carrying a short list. Two things, sometimes three, that were genuinely costing them sleep.

None of them ever announced it. It wasn't in the all-hands, it wasn't in the goals doc, and in a couple of cases it directly contradicted what the goals doc said mattered. Meanwhile I was doing good work aimed somewhere else entirely and wondering why it never quite landed.

You can just ask.

Ask, then stop talking

The question I'd use: what's worrying you most right now, and what would you want to have known a month earlier. Ask it in a one-to-one, on a day when nothing is on fire.

Then shut up.

The first answer is the official one, the version they'd give an investor, and it's usually about the quarter. The real one turns up maybe forty seconds later, if you leave the silence alone and don't fill it with your own theory about what's wrong. Most people can't manage the forty seconds. I couldn't for years, and what I was filling it with was my own need to look useful, which is a poor trade for hearing what's actually going on. The other half of the discipline is not solving it in the room. Nothing kills the second disclosure faster than watching the first one turn into an action item, and after that you get the investor answer forever.

If the relationship is new enough that the direct question feels strange, there's a softer version. What would make this a good quarter for you personally. Personally is the word doing the work.

Pressure arrives as behaviour

Most of the time nobody tells you anything. You get shown, and the showing usually looks like your boss being irritating.

They reopen a decision that was settled. They start asking for detail they never wanted before, or they go quiet on something they used to care about, or they turn up in a channel they've never once posted in. Your one-to-one gets moved twice and then gets shorter.

Take it less personally than it feels.

Pressure lands on them from above or from beside, and it comes out sideways, at you. Someone asked them a question they couldn't answer, so now they want the detail. A board member said something in passing that they can't unhear. Their own boss went cold on a project and nobody explained why, and the not knowing is worse than the news would have been. Curiosity works better than defence in all of these, and it costs you nothing to try it first.

So ask what changed, plainly and without an edge. "You've been in the delivery detail more than usual, has something shifted upstream?" Half the time you get the real answer, and it turns out to be a fear you can retire with one number.

Solve one, visibly

Knowing gets you nothing on its own. Aim something at it.

One item off the list per quarter, with real weight behind it. An actual change with an outcome they can see, not a slide about the change. If the worry is runway, that's a cost line that goes down and a short note explaining what you did to it. If it's one large customer going quiet, that's their reliability numbers, their open bugs, and you offering to join the next call. If it's whether the leadership team is good enough for what's coming, that's you visibly growing someone, and saying out loud that's what you're doing.

Then say it's done. Once, in a sentence, and no campaign about it.

Latitude is what this buys you. Not thanks, and not a warm feeling. The leader who has taken something real off their boss's plate gets the benefit of the doubt on the next thing, gets a faster yes on headcount, and hears about problems earlier. It compounds, and it's remarkably cheap to acquire, which is the odd part. Hardly anyone tries.

The list has a shelf life

Re-ask quarterly.

It turns over faster than you'd think, and solving the top item usually just promotes the second one rather than emptying anything. A raise, a big customer, one bad month, and it's rewritten. A new boss resets it completely, and everything you learned about the last one is now trivia, so ask again in the first month, before you've assembled a picture out of what other people tell you about them. Worth knowing your boss's boss's list too, roughly. Your manager's worries are usually a translation of somebody else's, and reading the original makes their behaviour legible in a way that guessing never will.

Where this stops

There's a version of this that turns you into an instrument of somebody's anxiety, and the difference matters.

Sometimes the fear is simply wrong. The thing they're worried about isn't what's going to hurt the company, and then what you owe them is evidence. Bring the number, say plainly that you think the risk sits elsewhere, name what you'd watch instead. That's the job. Agreeing would be the easy version and it's worth considerably less to them, whatever their face does in the moment.

Sometimes the fear is real and the ask that falls out of it is destructive. A date that breaks the team, a shortcut you'll be paying for all year. Serve the fear, refuse the ask: "I understand what you're protecting, here's a way to protect it that doesn't cost us the quarter after."

And if the whole list turns out to be about their own position, with the work as raw material for it, that's information about the job you've taken. Worth knowing early, whatever you decide to do with it.