Handling Pressure and Setbacks

As a senior leader working remotely, pressure rarely arrives as a single dramatic moment. It accumulates quietly: a project slipping past a date you committed t

Level: Senior leader
Setting: Remote
Core skill: Steady through difficulty
Common pitfall: Hiding the struggle
Practice to try: A name-it-and-ask habit

What this looks like in real work

As a senior leader working remotely, pressure rarely arrives as a single dramatic moment. It accumulates quietly: a project slipping past a date you committed to, a key person going silent for days, a decision you made last quarter now looking shaky, a stream of messages that all seem to need an answer you do not yet have. Because you are not in a room with people, none of this is visible in the usual way. There is no hallway where someone reads your face, no shared kitchen where a colleague notices you are unusually quiet. You are a set of messages and calls, and you can choose exactly how much of the strain to show.

Setbacks in remote leadership also tend to be lonelier. When something goes wrong, the instinct is to absorb it privately, fix it quietly, and present a calm surface at the next meeting. That instinct is understandable and often well intentioned. You do not want to alarm people, and you do not want to look like you are struggling. But the effect over time is that the team sees only outcomes, never the reasoning or the difficulty behind them. They learn that problems appear solved, as if by magic, and they never see how a steady leader actually moves through a hard stretch.

Steadiness through difficulty does not mean feeling nothing. It means being the person whose presence lowers the temperature in the room, even when the news is bad. In a remote setting, that steadiness has to be communicated deliberately, because nothing communicates itself.

Why it trips people up

The main reason senior leaders hide the struggle is that they have been rewarded for it. Earlier in a career, composure under pressure gets noticed. You are the one who does not panic, who delivers, who keeps the mood up. By the time you are leading leaders, that habit is deeply grooved. Admitting that a setback is affecting you can feel like undoing years of built credibility. So you say things are fine, you keep the update crisp, and you carry the weight alone.

Remote work makes this easier to do and harder to notice. There is no accidental exposure. You can mute yourself, turn off the camera, delay a reply, and compose a perfectly even message while your actual state is anything but even. Nobody bumps into you and asks a simple question. The distance that protects your privacy also protects the hiding.

There is also a status dimension. Senior leaders often believe that naming difficulty will cause the team to lose confidence, or that peers will read it as a lack of control. In practice, the opposite is usually true. People lose confidence when they sense something is wrong and nobody will say what it is. The silence is more unsettling than the truth. The trip-up is not the pressure itself; it is the assumption that showing any of it would be a failure of leadership.

The mistake that quietly hurts

The mistake is not having a hard time. The mistake is letting the team infer the hard time from your behaviour while you deny it in words. When you go quiet, shorten your messages, cancel a recurring check-in, or become unusually terse, people notice. They fill the gap with their own explanations, and those explanations are usually worse than reality. A delayed reply becomes a sign that something is badly wrong. A cancelled meeting becomes evidence that leadership is scrambling. You have not protected anyone; you have handed them a mystery.

This quiet hurt compounds. If you never name difficulty, your team never learns how you handle it, so they have no model to follow when they face their own setbacks. They may conclude that struggle is something to conceal, and the same pattern spreads. Over time, the organisation becomes very good at presenting calm surfaces and very bad at surfacing problems early, which is exactly backwards for a remote team that depends on written clarity.

There is a personal cost too. Carrying every setback alone is exhausting, and exhaustion eventually shows up as impatience, avoidance, or decisions made too quickly. The people around you then experience the strain anyway, just without the context. Hiding does not remove the difficulty from the system. It only removes the explanation.

A practice you can repeat

Try a name-it-and-ask habit. It has two parts and takes about a minute. First, name the situation plainly, without drama and without spin. Second, ask for one specific thing you need. The naming keeps people oriented; the asking keeps you from carrying it alone. The habit is small enough to repeat often, which is what makes it work. One grand confession is not the goal. A steady rhythm of small, honest statements is.

Here is how it might sound in a weekly written update: "The migration is behind where I wanted it to be. I am not yet sure whether the delay is a capacity issue or a design issue. I will know more by Thursday." That is naming. Then the ask: "If you have seen this pattern before, I would value fifteen minutes of your thinking this week." You have not asked anyone to solve it. You have asked for a specific, bounded contribution.

Make the habit concrete by attaching it to something you already do. For example, at the end of each week, write three lines: what is hard right now, what I am doing about it, and what I need from whom. Send the relevant line to the relevant person. Keep a private version for yourself so you can see patterns over a month. The point is not to broadcast every worry. The point is to stop the default of silence and replace it with a short, repeatable act of clarity.

What to say and do

The wording matters less than the consistency. Aim for plain, specific, and free of either self-pity or false cheer. Name the situation, say what you are doing, and make one clear request. Avoid vague reassurances like "everything is under control" when it plainly is not, because people hear the gap between the words and the tone. A short, honest sentence does more for confidence than a polished non-answer.

Some phrases that work well: "This is harder than I expected, and here is what I am doing about it." "I do not have an answer yet. I will have one by Friday, and I will tell you either way." "I am carrying this one, but I could use a second pair of eyes on the plan." Each of these names reality, signals forward motion, and invites a specific kind of help without handing over the whole burden.

What to do alongside the words matters too. Follow through on the small commitments you make in these moments, because that is what turns honesty into trust. Keep your camera on when you can, so people can see a human face rather than a blank tile. Protect a short, regular check-in where difficulty can be raised before it becomes a crisis. And when someone brings you a problem, resist the urge to immediately solve it; ask what they need first. You are modelling the very habit you are asking of them.

When the stakes get higher

When the setback is large, the pressure to hide grows with it. A major delay, a lost opportunity, a decision that clearly did not work. The instinct is to retreat, get the facts straight, and only reappear once there is a clean story. That instinct is dangerous at exactly the moment it feels safest. In a remote setting, your absence is loud. People will read the silence as chaos, and some will start making their own plans.

At higher stakes, increase the frequency of contact rather than reducing it, even when you have little new to say. A brief note that says "I am working on this, here is what I know, here is when I will update you again" does more than a perfect briefing delivered late. Give people the shape of the problem, not every detail. You are not obligated to share everything you are feeling, but you are responsible for the story people are telling themselves about what is happening.

Also widen the circle of honesty slightly. Tell a peer or a trusted colleague what is actually going on, not just your team. Senior leaders under pressure often isolate most from the people best placed to help. Steadiness at high stakes is not the same as solitude. It is the ability to stay connected, keep communicating, and let others carry part of the weight while you keep the direction clear.

Questions new leaders ask

"Won't admitting difficulty make my team doubt me?" Usually the opposite. Teams doubt leaders who go quiet and leave them guessing. Naming a problem clearly, along with what you are doing about it, reads as competence, not weakness. What damages confidence is the mismatch between a calm surface and visible strain.

"How much should I share when I am not sure of the facts?" Share what you know, what you do not know, and when you will know more. You do not need conclusions to be honest. "I do not have the full picture yet, and I will update you Thursday" is a complete, trustworthy message. Withholding everything until you have a tidy answer is what creates anxiety.

"What if I name a problem and nobody helps?" Then you have still gained something: you have stopped pretending, and you have learned where the real support is. Keep the ask specific and small, and repeat it. Over time, the habit builds a team that surfaces problems early instead of hiding them, which is the whole point of staying steady through difficulty.