5 Survival Lessons When The Pressure Never Stops

What Silicon Valley's top performers do to keep their role from swallowing them

It’s Sunday evening. A founder is finishing a board deck when a customer escalation pings her phone. Two engineers are messaging about a production issue that may or may not be serious. Her partner appears in the doorway to ask what time dinner is. She holds three conversations at once, half-finishes the deck, and tells herself she’ll deal with the escalation properly in the morning, knowing she won’t, because the morning has its own version of all this waiting.

This isn’t a bad week. It isn’t a crunch before a launch, nor the fallout from a missed quarter. It’s the ordinary texture of the job.

The pressure in Silicon Valley, where Nicole Ohebshalom, PhD is a therapist to CEOs, founders, engineers and their families, has some defining features:

• Teams are distributed across time zones, so the inbox never sleeps; by the time you’ve cleared London, San Francisco is waking up.

• Capital cycles force constant narrative-building, so even a company that’s doing well is forever fundraising, forecasting and explaining itself.

• Talent markets are tight enough that every retention conversation feels existential. The engineer you lose today is the one a competitor has been courting for six months.

A similar texture shows up well beyond tech. For example, the world of consulting runs on many of the same features: continuous client demands, distributed teams, the expectation of constant availability and a sense that the workload will never cool down. That’s the world that I (Andrea) work in.

Why standard advice on how to cope falls flat

Most of the advice aimed at people in these situations is about prioritisation. Time-blocking, the Eisenhower matrix, ruthless calendar audits, the two-minute rule, the weekly review. These tools are useful, and almost everyone reading this will already have tried several of them.

Yet, this type of advice assumes boundary conditions that don’t apply in environments operating at high pace. Every one of these techniques treats the load as finite and the main problem as sequencing: you have a fixed pile of work, and the skill is putting it in the right order so that the important things get done and the rest waits for its turn. That model works perfectly when there is, somewhere on the other side of the effort, a cleared queue and a quiet afternoon.

At this intensity, however, the load is effectively infinite and the rhythm is continuous, so sequencing alone doesn’t cut it. You can order the work perfectly and still find that finishing the top item simply reveals three more beneath it. And that the restful break you were sequencing towards never actually materialises.

This means that a different approach is needed. In cases where the pressure is relentless, the job is to keep operating at altitude and at pace for years without burning out the engine. The people who manage that have stopped expecting to be on top of their work. They have built a way of working that survives the unique features of their environment and enables them to stay Above the line.

Here is what they actually do.

If you want to go straight to our practical guidance, check out our playbook for the price of a coffee! Or get it for free as a paid subscriber to The Art of Asking Questions - check the Members Area.

Lesson one: Manage your energy instead of your time

Most time-management thinking treats the day as a container of hours and the job as fitting tasks into it. But the founders and executives who last think in cognitive and emotional bandwidth instead, and they make trade-offs against that. They know that there is no point in fighting against the clock.

The clinical reality is that decision quality, emotional regulation and the ability to deal with complexity are not constant across a day. They draw down, and we’re sure you have experienced this directly regardless of what you do: two hours in the morning and two hours at 6pm are not the same two hours, and this even varies by person. You need to identify when you are most energised and productive, and cluster your high-intensity tasks around that time of day. In practice, people who do this well protect the windows where their judgment is sharp and spend the depleted windows on things that don’t need that judgment quite as much.

One executive that Nicole works with refuses every meeting before 10am. This isn’t because mornings are sacred in some abstract, wellness-poster way but because the first three hours determine the quality of her decisions that day. Those hours are when she does her major thinking.

The hard part isn’t recognising that bandwidth is finite, but following through on this concept: guarding your best hours means declining things that look perfectly reasonable on the calendar and doing it consistently enough that people stop expecting otherwise.

Manage your energy like an asset. Everything else is downstream of it.

Lesson two: Drop the ball deliberately, out loud

Time management advice is built to help you do everything. At this level of intensity that’s the wrong goal, because everything was never going to fit anyway.

The people who last do something that looks almost cold from the outside. They decide, deliberately and ahead of time, what they are going to be bad at in a given period of time. We are not talking about prioritisation here, but things that they actively choose to let slide, with full knowledge of the cost. And then they say it out loud, both to their team and to the people at home, so that the gap is expected.

The difference is between dropped balls that are visible and chosen and dropped balls that are hidden and accidental. The first kind is a decision you can defend and that others can plan around. The second kind affects trust, because it looks like unreliability. On top of that, it costs you twice: once in the thing that didn’t happen, and again in the scramble when someone finds out it didn’t.

Note that this doesn’t have to be dramatic. While this technique could be applied to an entire month or quarter, it can be very effectively scaled down to the level of a day. For example, something I do on occasion is tell colleagues that on a certain day I will not be responsive on email or Teams, and that in that window things will either need to be parked or escalated through other colleagues. This could read as a leader stepping back, but the reality is that people can adapt quickly and learn to see this as a stated operating constraint rather than an unexplained failure to reply.

The thing that makes this approach work isn’t the boundary itself but the fact that it’s discussed explicitly.

If you need focused time, claim it and acknowledge the trade-offs openly.

Lesson three: Build recovery into the rhythm, not after it

Most people treat rest as the reward waiting at the finish line: get through this stretch, ship this thing, survive this quarter, and then you’ll recover. It’s a reasonable instinct, and at normal intensity it works, because the finish line does exist. But if the sprint never ends, the reward after the finish line never arrives.

So the operators who last do something counterintuitive. They treat recovery as an input, scheduled into the rhythm of the work the way a serious athlete treats sleep. In practice, recovery and rest are a condition of performing at all. The recovery comes first, or at least reliably, and is not treated as the thing that gets sacrificed the moment the week gets heavy.

Let’s be precise about why, because this is an operational argument and not a wellness one. The case for recovery isn’t that “you deserve it” or that balance is nice. It’s that decision quality degrades without it, measurably and fairly quickly, and that a depleted leader making a string of slightly-off calls does more damage in a week than a rested one would undo in a month. You protect recovery for the same reason you protect a production system: because the cost of it failing is higher than the cost of maintaining it.

The Art of Asking Questions is a reader-supported publication. To support my work, please consider becoming a paid subscriber. And check out my Perks page!

As in the previous lesson, you can start small. For example, you can make physical exercise a non-negotiable part of your routine. I personally insist on doing my daily working hours at a high pace and intensity, then break for a gym session (which includes a bike ride to the gym and some Italian music). Then, I feel like I can pick up any work left over from the day.

You can scale this up or down based on your circumstances: a software engineering leader Nicole knows has a habit of booking a full day off every third Friday and holding it regardless of what’s on fire that week. They arrived at the rule through experimentation, by noticing that pushing through those Fridays reliably cost them more the following week in poor calls and slow thinking, as well as small things they would normally have caught.

Protect recovery time the way you protect a production system. This is not indulgence, but basic maintenance.

Lesson four: Find one or two people you can be honest with

The performance demands of these roles mean that most of the conversations are filtered. The board gets the confident version, and the team gets the calm version, because if the team feels the leaders panic they’ll carry it into everything they touch that week. The person at home often gets a version designed not to worry them. This is a way to balance feelings and vibes around you.

But as you become better at managing expectations and emotions, you will also notice that it’s lonely at the top. You will end up surrounded by people all day and not actually known by any of them. Since every version of the truth is shaped for someone else (to steady them, to reassure them, to protect them), there’s no one left who simply gets you, the unedited person underneath all the managed ones. These gaps often go unattended for a very long time.

What sustains the people who last is at least one relationship that sits outside all of these balancing acts. A peer founder in the same weather. An old colleague with nothing at stake in your company. A coach, a therapist, a sibling. It is one place where the unfiltered version can go and where you don’t have to manage the impact of what you say before you say it.

The cost of not having this is concrete. If the pressure has nowhere to leave the system, it quite simply doesn’t leave: it piles up internally and comes out sideways in the form of sleepless nights, or a flatness where your energy used to be.

The people most at risk are rarely the ones you’d expect. They are usually the most capable, so fluent at being what everyone needs that they have disappeared as someone with needs of their own. When they finally have somewhere to set the real version down, the relief tends to surprise them.

Everyone needs one room where they don’t have to be the leader.

Lesson five: Separate the role from the self

Pressure becomes genuinely unsurvivable when you take every business setback personally and start reading it as a verdict on you as a person. For example, you might feel that a churned customer means you’re not good enough, or that the missed quarter means you were always going to be found out.

It’s worth reflecting on how those fusions form. For example, taking the company personally is usually what powered the early years of one’s career. The difficulty is that the same wiring doesn’t work when the company evolves and the stakes rise. The thing that drove you at the start is the same thing that, later, leaves you with no protection when the work goes badly. And, at some point, it will.

The people who last find their way to something different. They still care enormously about the outcomes, more than most. That intensity is usually the very reason why they’re doing that job. But they can hold the company in real trouble and still find a self that exists separately from how the quarter is going. That bit of separation is what lets them make a clear decision in a crisis.

It can be harder than it sounds, and it is usually learned painfully. One founder that Nicole worked with got there after her company failed. The thing she’d spent years worrying about just happened, and what surprised her after was that she was still here. She was grieving and she felt smaller for a while, but she was still herself. The company going under hadn’t taken her with it, which it would have, if the two had really been the same thing. She came out of this situation able to take risks again, because failing at something didn’t feel like she’d failed as a person.

That’s why the separation is what makes it possible to keep caring this much, for this long, without the caring slowly consuming the person doing it.

The role can collapse without taking you with it, but only if there was a you standing somewhere outside it.

What this changes

Taken together, these five lessons mark a shift in the question being asked. The instinctive question, the one all the productivity tools are built to answer, is “how do I get on top of everything?”

The question these leaders have learned to ask instead is “how do I keep functioning well inside something I will never be on top of?”

This question is uncomfortable, because answering it means giving up the fantasy that if you just found the right system or worked the right number of hours, the load would finally resolve and you could relax. Letting go of that is a genuine loss, and it’s why many of us resist the reframe for as long as we can.

But that reframe is also where the real work starts. Once you stop waiting for the queue to clear and accept that the job is to operate well at altitude for years, the questions turn concrete: which hours you guard, what you allow to drop, how you build recovery in, who you tell the truth to, and how you keep the role from swallowing the self.

None of it makes the pressure stop. But it makes you someone who can keep doing the work for years without it hollowing you out.

Do you want to actually install this operating system?
The five lessons above are the principles. When the Pressure Never Stops - A Playbook for Operating at Altitude turns them into practice with a diagnostic to find your weakest joint, the scripts for guarding your hours and declaring your drops, a one-page survival template, and a structure for the first week of the ‘new you.’

If you are a paid subscriber of the Art of Asking Questions, this playbook is free. Check out the Members Area for this and a lot more!

About Nicole Ohebshalom, PhD: Therapist to Silicon Valley’s CEOs, founders, and engineers. And their families. Founder of the Coherence Approach, a practice built on one premise: it begins with you. Relational intelligence — with yourself, at home, at work. Meditator.

---

Enjoyed this piece? Become a paid member and get my Consulting with AI prompt library, the full Asking Questions Like a Pro course ($199 standalone), practical templates from a decade of fieldwork, and discounts on many other resources. 🔗 See everything included in the paid tier.