I picked a conversation I'd been circling for weeks, raising a scope issue with a colleague I was fairly sure would …

Read more

You already know exactly how the familiar version hurts. You know what Tuesday looks like afterward. The unfamiliar better thing comes with no such guarantee, so it gets treated as the riskier choice, even when every visible sign points the other way.

This shows up in people who can name, with real precision, exactly what’s wrong with a job, a routine, or a way of working, and who still find themselves circling the alternative. Not because the insight is missing. The insight is usually excellent. Something else may be keeping the current option in place.

Decision research documents two related tendencies: we often give extra weight to the option already in place, and we can prefer known risks to ambiguous ones. Neither means the present option is better. It means the present comes with a known map, even a miserable one, while the alternative asks us to estimate costs we cannot yet see.

Read more

There’s a specific kind of dread that shows up the moment your name gets said out loud in a meeting. Not the whole-body panic of danger, smaller than that. A tightening. A sudden awareness of your own face.

I used to think this meant I didn’t like being visible. That I was, underneath it, someone who preferred to hide.

That’s not quite it.

Two weeks ago I gave a talk to a room of maybe forty people. Terrifying, on paper. But it wasn’t. What was terrifying happened the week before, in a Slack thread where someone quoted three words I’d written, out of order, and asked if I “really meant that.” Forty strangers, fine. Three words, misread, in front of six colleagues, not fine.

The difference isn’t audience size. It’s not even about strangers versus people who know me. The difference is what the visibility is actually doing.

Being seen is being taken in, understood in context, with room for the version of you that’s still figuring things out. Being watched is being observed for a verdict. Someone is deciding something about you, and you don’t get to be in the room while they decide it.

Both feel like attention. Only one of them is actually frightening.

This distinction explains a pattern that shows up constantly in this audience: people who say they want more visibility, a bigger platform, more reach, more recognition, while their body does everything it can to avoid the small, ordinary version of it that’s already available to them. Speaking up in the team meeting. Posting the thing. Sending the message without three qualifiers stapled to the front.

It’s not a contradiction. It’s two different things wearing the same word.

Psychologists sometimes call part of this social-evaluative threat: the possibility that something important about you will be negatively judged by other people. The response can intensify when the situation also feels outside your control. A Slack thread is not physical danger, and I don’t want to pretend it is. But judgement, uncertainty, and the feeling that your meaning has left your hands, can still produce a very real tightening.

That was the difference between the room and the thread. The forty strangers heard the thought in sequence, in my voice. If they looked confused, I could explain. The six colleagues saw a fragment, already framed as suspect. Being seen wasn’t about being known. It was about being encountered with enough context, and enough room to respond, to remain a participant in what my words meant.

Scale isn’t automatically the enemy. Contextless scale is. A hundred more people can mean a hundred more chances for a fragment to travel without you. It can also create resonance, if the work carries enough context and gives people some route back.

Reach and resonance are different things. The algorithm can count the first. It can’t tell you whether the second is happening.

Before I make myself more visible now, I run a two-part check, not to make the fear disappear, but to decide what the moment actually needs.

Read more

Last week I wrote a message to someone I work with. The first sentence was an apology.

Not for anything I’d done. For what I was about to ask. “Sorry, I know you’re busy, this’ll only take a second” — a full sentence of pre-emptive smoothing before I’d said a single word about what I actually needed. I read it back before hitting send and stopped. There was nothing to apologise for. I hadn’t even made the request yet.

I deleted the apology. Sent the rest. It took eleven seconds and felt like removing a layer of clothing in public.

Nobody taught me to do this, not in any lesson I could point to. It arrived the way these things arrive: early, quietly, through a thousand small penalties for other people’s mild discomfort. Ask for something and watch a face tighten, even slightly, and you learn. Take up space and feel the room’s temperature drop a degree, and you learn faster than any lecture could teach you. By the time I was running my own business, I wasn’t following a rule I remembered choosing. I was following one I had absorbed before I had the vocabulary to question it.

Stay quiet. Stay grateful. Never be the reason someone else has a worse day.

It gets mislabelled, and the mislabelling is most of the problem. People call it easy-going. Low-maintenance. Considerate. I believed the considerate one for years — that this was just who I was, someone who didn’t need much. But consideration is a choice you make freely, for people you’re glad to make it for. This isn’t that. This runs whether or not the situation calls for it, whether or not the person on the other end would even notice if I skipped the apology entirely. It runs with people who’ve told me, more than once, that I don’t need to brace like this.

The tell is proportion. Watch what happens next time you need something small — five more minutes, a straight answer, someone to just say what they think. If the apology arrives before the request, sized for something far larger than what you’re actually asking, that’s not manners. Manners are proportionate. This isn’t. It’s an old rule, still running, long after the room that made it necessary stopped being the room I’m in.

Here’s the part that took me the longest to accept: the rule made sense once. Somewhere, being quiet and grateful and easy to accommodate kept me safe, kept things calm, kept me liked in a situation where being liked genuinely mattered. It wasn’t a flaw that put it there. It was a reasonable response to a real set of conditions. The problem isn’t that I built it. The problem is nobody told me it came with an expiry date, and habits don’t announce when they’ve gone past use the way instructions do.

Recognising the rule helped me understand it. It didn’t stop me obeying it. What finally helped was a two-question check I now use before sending an ordinary request — plus one sentence that keeps the warmth without the apology.

Read more

I still over-explain in emails to people who have never once questioned me.

Three sentences of context before I get to the ask. A pre-emptive answer to an objection nobody has raised. A closing line that leaves the other person an easy exit, so that if they say no, I can tell myself I’d made it easy for them.

Nobody I currently work with has ever given me a reason to write like this. I know that. I do it anyway.

I noticed it properly a few months ago, rereading something before sending, and caught myself adding a fourth sentence of justification to a message that could have been one line. I sat there for a moment genuinely puzzled by myself. Then I remembered where I learned it.

There was a stretch of my working life where being wrong in front of the wrong person was expensive. Not catastrophic. Just expensive enough that I developed a habit of never being wrong out loud without having already accounted for it. The over-explaining wasn’t anxiety. It was infrastructure. It worked.

And then that job ended, and the people changed, and the risk went away. The habit stayed exactly where it was, running at full strength, in an environment that had stopped requiring it years earlier.

That’s the thing nobody warns you about. Protections don’t come with a review date. There’s no notice period, no retirement, no moment where your nervous system checks back in and asks whether the original problem still exists. They just keep running, quietly, in rooms that no longer need them.

And because they still look like competence from the outside — careful, thorough, easy to work with — nobody thinks to question them.

Including you.

Share Imperfect Club

Here’s the part I keep coming back to: an expired protection almost never announces itself as fear.

It arrives dressed as a personality trait.

Read more

There’s a message on my phone from a friend I like very much. It has been sitting there for eleven days.

Nothing happened between us. No argument, no falling-out, no slow cooling I could point to. I read it, I meant to reply, and then I put the phone down and the day did what days do.

By day four it had become its own small problem. By day eight the reply I owed had grown a preamble — an explanation, an apology, some account of myself. By day eleven the message was heavier than the friendship.

Here’s what took me an embarrassingly long time to notice.

I have a whole vocabulary for protecting my time at work. I can say I’m at capacity. I can say this week is full. I can say let’s push it to next month, and nobody takes it personally, because everyone accepts that a calendar is a finite object with edges.

I have almost nothing for friendship.

The words on offer are all relational. I’ve been distant. I’ve been a bad friend. I’ve not been making the effort. Every one of them describes how I feel about the person. None of them describes what actually ran out.

That’s the gap. When the only language you have for pulling back is language about affection, then pulling back has to mean something about affection. So you don’t pull back. You keep showing up at half strength, slightly resentful, until the friendship costs more than it gives — and then you disappear anyway, but badly, and with far more damage than one honest sentence would have done.

I’ve been on both sides of that. The disappearing, and the disappeared-on.

What follows is the vocabulary I’ve been building for myself. It isn’t a script. It’s closer to a set of distinctions — the ones that let you protect your energy inside a friendship without either of you having to conclude that the friendship is the problem.

Read more

By April she called me almost embarrassed. Nothing had gone wrong. That was the problem. She’d done all the right things, applied to the right places, had the right conversations, and the result was: nothing yet. No rejections to learn from. No offers to weigh up. Just weeks stacking up with no visible movement in any direction.

“I think I’ve made a mistake,” she said.

She hadn’t. She was in the waiting room, and nobody had told her it existed.

Subscribe now

The gap nobody plans for

Most of us plan for the decision. Some of us plan for the work after the decision. Almost nobody plans for the stretch in between — the part where you’ve done everything you know how to do and the world hasn’t responded yet.

That stretch is longer than people expect. Not sometimes. Usually.

And because nobody names it in advance, it arrives feeling like evidence. Evidence that you chose wrong, moved too early, overestimated yourself. The silence gets read as a verdict.

It almost never is.

Two things people do in the waiting room, both of which make it worse

The first is to fill it. If nothing is happening, the reasoning goes, then I should do more — more applications, more outreach, more content, more of whatever the activity was. This feels productive and occasionally is. But past a certain point it stops being work and starts being a way of not sitting still. You can spot the tipping point easily enough: it’s when you’re doing things you can’t explain the purpose of, only the anxiety behind.

The second is to renegotiate the decision. Every week without a result becomes an argument for reversing it. Maybe I should go back. Maybe the old thing wasn’t so bad. Maybe I misjudged all of it. This is the more expensive mistake, because decisions made from inside the waiting room are almost always made in the wrong emotional state — tired, unwitnessed, slightly humiliated by the silence. That’s not the version of you who should be running a review.

Both mistakes come from the same misreading: treating the gap as dead time. Something to be got through, endured, or shortened by force.

What the gap is actually doing

Here’s what I’ve come to think, having been in a few of these myself and watched more of them from the outside.

The waiting period is when the decision stops being an idea and starts being your actual life. That’s not a metaphor — it’s the practical reality. In January my colleague had made a choice. By April she was living inside it: adjusting to less income, explaining herself at dinner parties, discovering which parts of her identity had been load-bearing and which hadn’t. None of that produced a visible result. All of it was necessary before any visible result could hold.

This isn’t the waiting I wrote about a few weeks back, where the thing you’re waiting for is a better version of yourself that never actually turns up. This is different, and in some ways harder. You’ve already acted. The waiting isn’t avoidance — it’s the lag between cause and effect, and the lag is real. Seeds don’t come up faster because you’re watching.

The honest bit I have to include here, since I write about rest and also post something most days: I’m not immune to any of this. I check numbers more often than is useful. I have absolutely done the “maybe I should do more” thing at 11pm, and called it strategy.

What actually helps

Three things, none of them dramatic.

Name the phase out loud. Just saying “I’m in the waiting part, this is a known thing, it’s not a verdict” removes a surprising amount of weight. Most of the pain in the waiting room isn’t the waiting. It’s the private interpretation that the waiting means something bad about you.

Set a review date, and refuse to review before it. Pick a date far enough out to be fair — three months, six, whatever suits the thing. Write it down. Then treat every mid-week wobble as noise rather than data. You are allowed to reassess. You are not allowed to reassess on a Tuesday night because nobody emailed back.

Find the part that isn’t waiting. There’s usually something inside the gap that’s genuinely moving, just not the thing you’re measuring. Skills sharpening. Relationships forming. Your own tolerance for uncertainty quietly going up. Those aren’t consolation prizes. They’re often what makes the eventual result survivable when it arrives.

The reframe worth keeping

Waiting isn’t the delay before the work. Some weeks, it is the work — the unglamorous, unwitnessed part where the decision gets absorbed into a life rather than just made.

My colleague found something in June. Not from the shortlist, not from the plan, from a conversation that only happened because she’d had five months of other conversations that went nowhere. She described those months as wasted right up until the point they obviously weren’t.

If you’re in one of those stretches now: it’s probably longer than you were told, it’s probably not a verdict, and the day it ends will likely make the whole shape of it look different in hindsight.

That’s not much comfort on a Tuesday night. But it’s true, which is the more useful of the two.

Leave a comment

Download the Calm Kit

A woman I used to work with left her role of nine years to “reinvent herself.” She spent four months building a business plan, taking courses, going to networking events three nights a week. She told me it was the most energised she’d felt in years.

Eight months later, she was back working for someone else. Not because the plan failed. She collapsed halfway through executing it, and only then admitted she’d been running on empty since before she’d even started.

Reinvention gets planned before recovery happens

There’s a version of career change that looks like momentum but is actually a way of avoiding rest. New plan, new possibility, new identity to try on, all of it feels like progress, because it’s active. Recovery, by comparison, looks like nothing is happening, which is exactly why so many people skip it.

Usually the actual issue was never the wanting. It was building the something-different on top of a person who was already running low before the idea ever showed up.

Subscribe now

What restoration actually looks like, and why it gets skipped

Restoration is unremarkable. It rarely produces a story worth telling at a dinner party. Nobody posts about the week they did nothing but notice how tired they actually were. That unremarkable week, though, is the difference between a reinvention that holds and one that collapses eighteen months in, wearing a different job title but running the exact same depleted operating system underneath.

Someone who disappears for a while during a hard stretch usually hasn’t gone anywhere. They’ve gone still, and stillness gets misread as absence, sometimes as being stuck. Most of the time the work is still happening. It’s just not the kind anyone can see from outside.

The order is the intervention

Restore first. Redesign after. Almost nobody does it in that sequence, because restoring feels like standing still and redesigning feels like doing something. Skip the restoring, though, and the redesign rebuilds the same unsustainable structure, just with a new name on the door and a fresher story attached to it.

Sequencing, not ambition, is what this essay is actually about.

The capacity has to come back before the new plan gets built on top of it, or the new plan inherits every crack the old one had.

A place to start, if you want one

One thing worth trying this week: before you plan the next chapter, spend a few days just noticing your actual energy levels. Not planning around them. Just noticing. What time of day are you actually capable of clear thinking? What’s been running you down that has nothing to do with your job title?

If restoring capacity, not just planning the next role, is the part you keep skipping, the Calm Under Pressure professional well being collection was built around exactly that sequencing question, composure and capacity before the next move, not instead of it.

Explore Calm Under Pressure professional well being collection:

• Breaking Free from Burnout: Sustainable Performance Habits

• Finding Your Way Through Burnout

• Gentle Focus - Working Without Overwhelm

• The Gentle Guide to Good Stress

• The Gentle Art of Work-Life Balance

The reinvention you’re planning might be entirely real and right. It might also be a genuinely convincing way of avoiding the slower, less photogenic work of coming back to yourself first. Only you know which one this actually is.

Read more

A few years ago I watched a colleague field a question in a meeting that should have rattled her. It didn’t. Someone challenged her numbers, in front of her boss, in the tone people use when they already think they’ve caught you out. She paused for exactly as long as it takes to breathe once, then answered clearly, without any of the defensiveness the moment was built to provoke.

Afterwards I told her she was lucky to be so unflappable. She looked at me like I’d complimented the wrong thing.

“I’m not unflappable,” she said. “I rehearsed this exact scenario in my car this morning.”

I didn’t believe her at first. Not because it seemed unlikely she’d prepared, but because “rehearsed” felt like the wrong word for what I’d just watched. Rehearsal is for actors. What she’d done looked like personality.

It wasn’t. It was a rep.

A rep, in the gym sense — one repetition, the unglamorous unit calm turns out to be made of.

The trait story is easier to tell than the practice story

We have a strange habit of sorting people into calm and not-calm as though it’s a fixed setting, like handedness. Some people just have it. The rest of us are working with what we were given.

I understand why the story persists. It’s simpler than the alternative, and it lets everyone off the hook in a specific way: if composure is temperament, then panicking under pressure isn’t something you did wrong, it’s just who you are. That’s oddly comforting. It’s also, as far as I can tell, mostly untrue.

What actually separates the person who stays steady from the person who doesn’t is whether they’ve already been through some smaller version of this exact pressure before. Not pressure in general. This pressure, specifically, or something close enough to it that the nervous system doesn’t register it as new.

That’s a practice gap, not a character gap. And practice gaps are a genuinely different, more solvable problem than character gaps.

Read more

There’s a version of you that’s more settled than this one.

More confident. Less reactive. The one who’s finally figured it out. You’ve been getting ready for that person for a while now — clearing space, building conditions, waiting for the moment they arrive so you can finally start living the way they would.

They’re not coming.

Not because you’ve failed to become them. Because they were never a destination. They’re a story you tell the current version of yourself about why it’s reasonable to keep waiting.

The shape of the deferral

It rarely looks like avoidance. It looks like responsibility.

“Once I get through this period.” “When I’ve finished this project.” “After the next promotion.” Each one sounds like patience. Like knowing your moment hasn’t come yet. What it actually is: a small, constant postponement of permission — to rest, to speak up, to take the thing seriously, to let this version of you count.

The future self who gets to do those things is always more ready than you are right now. That’s not a coincidence. You built them that way. You needed someone to blame for the waiting, and inventing a more deserving version of yourself was easier than asking whether the waiting was necessary at all.

Subscribe now

What the future self is actually made of

Notice how you describe them. Rarely in specific skills. Mostly in negatives: less anxious, less uncertain, less prone to the thing that currently embarrasses you.

That’s worth sitting with. You’re not picturing someone more capable. You’re picturing someone relieved of what’s currently inconvenient about being you. That’s not a goal. It’s a fantasy with a deadline nobody’s written down.

Read more

There is a conversation you have been meaning to have for a while now.

You know what it is. You might even know roughly what you would say. The other person is not a stranger — they are someone you work with, or have worked with, or are in some kind of ongoing relationship with that requires this conversation to happen at some point.

And still it keeps not happening.

Not because you are conflict-averse. Not because you are unkind or unclear on what needs to be said. Because the moment never quite arrives. There is always a reason for this week to not be the week. A deadline, a mood, a sense that now is not quite right. Next week will be better. After the project wraps. When things settle.

The things do not settle. The week never becomes the week. And the conversation that should take eleven minutes has now been sitting for six months.

This essay is about that.

What the not-having costs

The cost of an unresolved conversation is rarely dramatic. It does not show up as a single large deduction. It shows up as small, steady withdrawals from every interaction that touches the thing you are not saying.

The slightly adjusted tone when that person’s name appears in your inbox. The small detour you take in meetings to avoid the topic. The care you spend managing around the edges of something you could simply address directly. The half-second pause before you say something, checking whether it is safe to say.

None of this is catastrophic. All of it is expensive.

The research on this is fairly consistent: people dramatically overestimate the emotional cost of having a difficult conversation and significantly underestimate the cost of not having one. The anticipatory dread is almost always more unpleasant than the conversation itself. The dread accumulates. The conversation, once had, tends to take a fraction of the time the dread spent building.

But this is not quite the right frame either. Because the problem is not only that you are carrying something uncomfortable. The problem is that the conversation is happening anyway — just without you in it.

The gap that fills itself

When you do not say what you mean to say, the other person’s imagination fills the silence. They do not know what you would say if you said it. They know only that you have not said it, and they construct their own version of why.

Their version is almost never accurate. And it is almost never more generous than your actual message.

The professional who owes their colleague a difficult conversation about workload has been calculating how hard that conversation will be. Their colleague has been calculating something else: what the silence means. Whether they have done something wrong. Whether something is about to change. Whether they are valued in the way they thought they were.

The gap between what you would actually say and what the other person is currently imagining grows a little every week you do not say it. You are not avoiding a conversation. You are allowing a conversation to happen in your absence, in someone else’s mind, with outcomes you cannot correct.

Why the moment never arrives

The moment never quite arrives because arriving is a decision, not a circumstance.

Read more

There is a thought that has probably ended more than one of your weekends before it started.

I haven’t quite done enough today.

Not a dramatic thought. Not a verdict. Just a low, persistent feeling that you haven’t crossed the threshold yet. That rest — real rest, the kind where you’re not monitoring what you’re not doing — is something you haven’t quite earned.

You’re not lazy. You’re not avoiding anything. You finished things today. You’re tired in the way that is beyond tired. And still, something in you insists: not yet.

This essay is about that insistence. Where it comes from. What it costs. And why the threshold it keeps pointing toward does not actually exist.

The texture of the belief

Earned rest is a concept that sounds fair.

You work; you rest. You output; you recover. You give the day what it needs; you give yourself what you need. The logic is clean. The problem is that it never functions that way.

Because what “earned rest” actually means, in practice, is rest that is conditional on completion. And completion, in modern knowledge work, is not a state you reach. It is a state you perpetually approach and never quite arrive at.

The inbox regenerates. The list grows faster than it clears. Every task completed opens two more. Every meeting generates action items that generate meetings. This is not a design flaw. This is the architecture of most professional roles — generative by nature, designed to exceed the hours available.

Inside that architecture, “earned” rest is a concept with no referent. You cannot earn something that has no defined earning condition. And the belief that you haven’t done enough to stop is not information about your output. It is information about a standard that has been quietly calibrated to stay just out of reach.

Where the belief comes from

The idea that rest must be earned is not a personal failure. It is a cultural inheritance.

Modern professional culture has, over several decades, fused two things that should have stayed separate: human worth and productive output. The person who rests without having worked for it is indulgent. The person who stops before finishing is falling behind. The person who cannot account for their time is failing some implicit audit of their adequacy.

Inside this framework, rest is not a biological necessity. It is a reward. It must be deserved. And to deserve it, you must first have produced enough — a threshold that the culture around you sets and revises upward whenever you approach it.

Yesterday’s ambitious list is today’s baseline. Today’s completed project is tomorrow’s minimum. The goalposts do not stay still. They are designed not to.

The impossibility of “enough”

Here is the specific cruelty of the earned rest model: it contains no mechanism for satisfaction.

The threshold is always calibrated to your current capacity. If you worked hard today, the threshold knows. If you cleared the list, the list grows. If you stayed late, staying late becomes the new normal. Whatever you offer, the belief adjusts to require slightly more before it will release you.

This is not a system that can ever pay out.

The professionals who understand this earliest — not as philosophy but as practical reality — are the ones who stop trying to satisfy the threshold and start working around it. They do not rest because they have finished. They rest because they have decided that the work that remains can wait until tomorrow, and tomorrow they will do what they can.

Not because they do not care. Because they understand that a depleted person working on residual energy is not serving the work or themselves. Rest is not what you do instead of the work. It is what makes continued work possible.

The difference between being tired and having permission

This is the thing that catches most people off guard: you can be completely exhausted and still not feel that you have earned rest.

Tiredness is a physical state. Permission is a psychological one. They are not the same thing, and solving one does not touch the other.

You can sleep eight hours and wake up feeling like you still owe the day something. You can take a week off and spend it cataloguing everything you are not doing. You can sit in a garden on a warm evening and feel guilty for not being at a desk.

The permission deficit is not solved by rest. It is solved by the decision to give yourself permission — before you have finished, before the list is clear, before the day has delivered the feeling of enough that you have been waiting for.

That feeling is not coming from the day. The day is not designed to produce it. The day is designed to produce more day.

The permission was always yours to give.

What rest actually requires

Not completion. Not a cleared inbox. Not having handled everything that arrived since the last time you stopped.

A decision.

Made before you are done. Made in the knowledge that done is not a state you are going to reach today. Made in the understanding that the work that remains will still be there tomorrow, and that the version of you who rested will do it better than the version of you who didn’t.

This is not lowering your standards. This is understanding what your standards are actually for.

You set them because you care about the quality of your work. Depleting yourself in service of a threshold that was never going to be satisfied is not in service of that quality. It is in service of a belief that your worth is contingent on your output — a belief that, if you look at it directly, you probably do not actually hold.

The rest you haven’t earned yet is waiting for you to stop waiting to deserve it.

Before you go: what would you do this weekend if rest wasn’t something you had to earn first? Not what you should do. What you would actually do. Reply to this. I read everything.

Leave a comment

Ricky

Read more

There is a specific kind of disappointment that nobody warns you about.

You finish something you have been working toward for a long time. A project. A deadline. A period of sustained effort that required more of you than felt reasonable. And then it is done.

You expect relief. Or at least something legible — some clear signal from your body that the thing you worked for was worth it.

What you get instead is a quiet flatness. A sense of arriving somewhere that looks exactly like the place you left. The inbox already has new things in it. The next deadline has moved into view. The list that was supposed to shrink is already growing again.

This is what “caught up” actually feels like. And if you have felt it — if you have crossed a finish line and found almost nothing waiting there — this essay is for you.

The anatomy of the anticlimax

We talk about burnout. We talk about overwhelm. We talk about the exhaustion of carrying too much for too long.

We almost never talk about this: the specific deflation of arriving at the place you were working toward and finding that the reward is not there.

Part of what makes it so disorienting is that it looks like ingratitude. You achieved the thing. You should be grateful. You should feel accomplished. Instead you feel — strange. A little hollow. Already looking at what comes next, as if your nervous system never received the message that something finished.

The first thing most people conclude is that they chose wrong. The goal was not the right one. The work was not meaningful enough. They must not really want what they thought they wanted, otherwise arriving would feel like more.

This conclusion is almost always wrong.

What the flatness is actually telling you

The flatness is not a verdict on your choices. It is information about the structure of the reward you were pursuing.

Here is what I mean.

When you chase “caught up” — when you work toward the end of the list, the cleared inbox, the finished project, the moment when you can finally rest — you are not just working toward a task completion. You are working toward a feeling. Specifically, the feeling of being enough. Of having done enough. Of being, for a moment at least, adequate.

That feeling is real. It exists. But it was never attached to the task.

The feeling of “enough” is not a reward that the work delivers when you complete it. It is a state you can access independent of the list. And because we have spent so long treating it as a reward — as something that must be earned before it can be experienced — we are perpetually one task away from a feeling that keeps receding.

We keep moving the finish line and calling the restlessness ambition.

The reward structure that does not pay out

This is not a flaw in your motivation or your character. It is a feature of the system most of us work inside.

Modern professional life is, almost by design, generative. Every task completed surfaces two more. Every email answered creates a reply. Every goal achieved reveals a larger goal behind it. This is not because you are doing it wrong. It is because the work is designed to exceed the hours available and the energy you bring to it. That is what it means to operate in a connected, fast-moving environment.

Inside that system, “caught up” is not a destination. It is a horizon. The closer you walk toward it, the further it moves.

But here is what nobody tells you: the way we have learned to motivate ourselves for this kind of work involves treating “caught up” as if it were a destination. We tell ourselves — explicitly or quietly — that if we work hard enough, push through enough, sacrifice enough of the present moment, we will eventually arrive somewhere that feels like rest. Like completion. Like finally, briefly, being enough.

The system takes the payment but never delivers the goods.

What changes when you stop expecting the feeling to come from the task

Nothing about the work changes. The list is still there. The deadlines still exist. The inbox still fills.

What changes is the question you are trying to answer.

The old question is: Have I done enough yet?

That question has no satisfying answer inside a generative system. There is always more. There will always be more. Every answer to have I done enough yet is an invitation to find one more thing that is not done.

The new question is: What would “enough for today” look like if I decided rather than discovered it?

This is a meaningful shift. “Discovered” means waiting for the system to tell you when you are done. The system will not tell you. It is not designed to. “Decided” means naming, before you begin, what done looks like — and then treating the completion of that thing as done, even when more exists.

Not because there is not more. There is always more.

Because the capacity to stop is not something the list will grant you. It is something you have to take.

The thing the flatness is pointing toward

If you have ever finished something big and felt nothing — or felt it for about an hour before the next thing arrived — you are not broken. You did not pick the wrong goal. You have not failed to want the right things.

You have been chasing a reward that the system was never going to pay out.

The flatness is the system showing you its structure. It is information. This is how this works, it is telling you. The feeling you are looking for is not here. It was never going to be here. It lives somewhere else.

Where it lives is in the deciding. In the naming. In the act of saying — before you begin, not after you collapse — this is what done looks like today, and when I reach it, I am going to stop.

Not because you cannot do more. You probably can.

Because doing more was never the thing that was going to deliver the feeling. And continuing to believe that it might is the most expensive error most high-functioning people make.

One question before you go

What would “enough for today” look like if you decided it right now — before you open the next thing, before you check what is waiting, before the list tells you what you still owe?

Not a vague answer. A specific one.

Name it. And when you reach it today, notice what it feels like to stop on purpose rather than waiting to be given permission.

That noticing is the beginning of a different relationship with the work.

Before you go: what is a finish line you crossed that felt strangely empty? What were you actually waiting to feel? Reply to this. I read everything.

Leave a comment

Ricky

Read more

I want to describe a specific professional experience that is almost universal and almost never named clearly.

You end the day having done a lot. You answered the emails that needed answering, attended the meetings, made the decisions, completed the work that was in front of you. By any reasonable measure, it was a productive day.

And yet you close the laptop with the distinct feeling that you are behind.

Not failed. Not lazy. Not unproductive. Just — behind. The list is longer than it was this morning. There are things you didn’t get to. There are things that will be waiting tomorrow that weren’t waiting yesterday. There is a persistent, low-level sense that you are not quite catching up.

This is one of the most common experiences I hear described by capable professionals. And almost nobody has named it accurately yet.

The structural reality

Modern knowledge work is generative.

Every email answered produces a reply. Every decision made generates a follow-up. Every task completed surfaces two more. Every meeting creates action items that will, themselves, create meetings. The work does not decrease as you address it. It regenerates.

This is not a flaw in your system. It is not a problem to be solved with better tools or more disciplined habits. It is the inherent nature of most professional roles in the knowledge economy.

The inbox is not a problem to solve. It is a condition to manage.

A river is not broken because it keeps flowing after you’ve swum across it. The work is not broken because it keeps arriving after you’ve processed a portion of it. Both are simply behaving according to their nature.

Why catching up is the wrong frame

The goal of getting on top of it assumes there is a top. A fixed endpoint. A state of completion that exists and is reachable if only you work hard enough, get organised enough, find the right productivity system.

For most knowledge workers, that state does not exist.

The work is not designed to fit into the hours available. It is designed to exceed them — not through malice or poor planning, but because the nature of the role is to respond to an environment that generates more demands than any one person can address. That is what it means to be a professional in a connected, fast-moving organisation.

So the people who suffer most from the always-behind feeling are not the least organised or least disciplined. They are often the most conscientious — the ones who take the volume of unfinished work as personal information about their adequacy. Who treat a structural condition as a character flaw.

It is not.

The guilt mechanism

The always-behind feeling is not information about your performance.

It is information about the gap between the volume of incoming work and the hours available to process it. That gap is structural. It is built into the design of the role. And it will not be closed by working harder, staying later, or finding a better system for managing your inbox.

What the feeling is actually telling you — if you listen to it accurately rather than personally — is this: the work generates more than one person can finish. That is a fact about the job. Not about you.

The professionals who carry this most heavily are the ones who haven’t made this distinction. Who experience the natural overflow of a generative workflow as evidence that they are somehow falling short. Who spend their energy trying to prove, to themselves and others, that they can actually finish — when finishing was never on offer.

You are not behind. You are in a job that produces more work than one person can finish. Those are not the same thing.

What changes when you stop trying to finish

When you release the goal of getting on top of it, a different question becomes available.

Not: what’s left? But: what matters?

These produce very different days.

The first question has no satisfying answer. There is always something left. The inbox always has something in it. The list never fully clears. Every answer to what’s left is another invitation to feel behind.

The second question has a real answer. Every day. It requires judgment — the specifically human kind, the kind that knows the difference between what is urgent and what is important, between what needs to happen today and what only feels like it does. But it is answerable. And the day that ends with I did the things that mattered most today feels categorically different from the day that ends with I did a lot and I’m still behind.

Triage is not a crisis response. It is a discipline.

In medicine, triage doesn’t mean fixing everything. It means deciding in advance what undone looks like when you stop — and making that decision calmly, before the pressure of the moment forces it. The same discipline applies to professional work. Deciding what can safely remain undone today is not laziness. It is the practice of someone who understands the nature of the work they are doing.

One honest question to close with

What is the thing on your list that has been there the longest?

Not the hardest thing. Not the most urgent. The one that keeps getting moved to tomorrow. The one that has been on the list so long it has stopped feeling like something you will actually do and started feeling like a verdict on you.

Sit with that for a moment.

It is probably not there because you are lazy or disorganised. It is probably there because it is either genuinely not important enough to prioritise over the things that keep arriving — in which case the honest answer is to take it off the list entirely, not move it again — or because it requires something that the daily flow of generative work never quite allows: uninterrupted time, a different kind of attention, the absence of the always-arriving present tense.

Naming it honestly is the first step. Not scheduling it. Not committing to it. Just naming what it actually is and why it is actually still there.

That distinction — between I haven’t done this because I’m behind and I haven’t done this because this is what it actually requires — is where the work of getting out of the always-behind mindset begins.

Before you go: what is the thing on your list that has been there longest? Reply to this. I read everything.

Leave a comment

Ricky

Read more

I want to describe a specific kind of professional.

They are the first to offer. The last to ask. They give help fluently, proactively, often before the other person has found the words to say what they need. They read the room, anticipate the difficulty, step in.

And then someone tries to help them. And something shifts.

They over-explain why they need it. They minimise what they actually need. They thank the person more than the gesture warrants. And within moments of the help being offered, they are already calculating what they can do in return.

None of this looks like a problem. From the outside it looks like consideration, gratitude, relational intelligence. But underneath it, something is working quite hard to make sure the help doesn’t fully land.

It is not pride

Pride would be obvious. You would feel it — the sting of being seen as someone who needs something, the resistance of the ego.

This is quieter than that. It doesn’t feel like pride. It feels like being practical, being efficient, being someone who doesn’t make unnecessary demands on other people.

But it is a belief. And the belief runs something like this: I am the kind of person who handles things. Needing help is a departure from that. And departures from that feel, if not dangerous, then at least like information I would rather not transmit.

The belief is rarely conscious. It has usually been operating for long enough that it simply feels like character. I’m independent. I prefer to do things myself. I don’t like asking. These feel like facts about personality. But they are conclusions drawn from a particular kind of environment, reinforced over time.

Where it comes from

High-achievement environments reward self-sufficiency.

The person who figures it out alone. Who doesn’t need their hand held. Who handles the problem without escalating it. Who delivers without needing much from anyone.

Over years, this shapes what feels safe. Needing help doesn’t just become uncomfortable — it becomes associated with a version of yourself you are trying not to be. Less capable. Less reliable. More burden than asset.

And so the reflex forms: handle it. Work it out. Don’t ask.

The reflex is fast. It fires before the conscious mind catches it. By the time you’re aware you’re minimising someone’s offer of help, the deflection is already happening.

The cost that goes unnamed

The obvious cost is exhaustion. Carrying more than you need to carry, for longer than necessary, because you made it difficult for anyone to actually share the load. That is real and it compounds.

But there is a quieter cost that takes longer to name.

The professional who cannot receive help cannot fully connect.

Connection requires showing where you are not whole. It requires the kind of vulnerability that comes from actually needing, and actually being given to, without immediately balancing the ledger. The person who is always the one who handles things, always the one who gives and rarely the one who receives — they are kept at a specific kind of distance from the people around them. Not because anyone chose that distance. Because the system they built to manage their own discomfort with need has that distance as its natural output.

The relationships stay warm. The care is genuine on both sides. But something stays at the surface. The people who want to help them sense, without quite knowing how to name it, that there is a door that doesn’t open. And eventually most people stop knocking.

Three signals that this is happening

These are not diagnoses. They are moments worth pausing at.

You over-thank when someone helps you. Not because you don’t mean it — you do — but the thank you is doing extra work. It is managing the imbalance, signalling that you are aware of the debt, trying to reduce it through the currency of expressed gratitude.

You preface any request with excessive justification. Before you even get to what you need, you have explained why you need it, acknowledged that it is an imposition, noted that you understand if it isn’t possible, and provided three alternative options. The request is surrounded by so much scaffolding that by the time it arrives, it barely resembles a request.

You think about what you can do in return before the help has actually landed. The offer is made. And your immediate internal response is not relief or gratitude but calculation. What does this create? What do I now owe? How do I make this even?

None of these are failures. They are patterns. And patterns, once named, can be worked with.

What actually helps

Not asking for help more. That is often where this conversation goes, and it misses the point.

The difficulty is not in asking. It is in receiving — in letting the help actually arrive, without managing it away. The ask might happen. And then the help is offered. And everything that follows is a set of reflexes designed to ensure that the help doesn’t create an imbalance, doesn’t mark you as someone who needs things, doesn’t change how you see yourself or how you imagine others see you.

The practice is in the receiving, not the asking. It is in noticing the moment the reflex fires — the over-thank, the calculation, the minimising — and choosing, on that occasion, not to act on it. To let the help land. To let it matter. To let the person who offered it feel that they actually reached you.

This is harder than it sounds because the reflex is fast and the discomfort is real. But the discomfort is not a signal that something is wrong. It is the unfamiliarity of a different position. The position of being, for a moment, the one who needed.

There is nothing wrong with that position. You have been the other one for a long time. It might be worth trying this one.

Before you go — one question: what is the last time someone offered to help you and you said no, when actually you could have used it? Reply to this email. I read everything.

Leave a comment

Ricky

Read more

I want to describe someone who has been meaning to rest for about six months.

The holiday got planned. Then rescheduled. The long weekend had good intentions until Friday afternoon, when one thing led to another and the weekend filled itself before it had properly started. There’s a phrase that recurs in the background of most weeks, attached reliably to a different completion point each time: once this is done.

Once this project wraps up. Once this quarter settles. Once things calm down at work. Once the children are back at school. Once I’ve dealt with the thing I’ve been putting off dealing with.

The phrase never resolves. It reschedules.

The completion myth

The structure of modern professional life means that completion is always partial.

Projects end and are replaced by projects. Inboxes empty and refill within hours. The deliverable gets finished and the next one is already waiting. The calendar clears for a week and then fills again. There is no natural stopping point. There is no moment when the work is genuinely, finally done.

This means that if rest must wait for completion, it waits indefinitely. Not because you are lazy or undisciplined or bad at time management. Because the condition you’ve attached to rest — completion — is structurally unavailable in the kind of work most capable professionals do.

The finish line was never fixed. It moves.

Where the belief comes from

High-achievement environments are built around output. The things that get noticed, rewarded, and praised are the things that get produced. Rest, in this framing, is the absence of production — the gap between productive periods, the space where nothing is being generated.

Over years, the brain files this away. Rest is what you get when you’ve done enough. Rest is the reward at the end. And the corollary, unspoken but deeply present: resting before you’ve done enough is a kind of failure. A premature exit. A withdrawal of effort before the work has justified it.

The problem is that enough was never defined.

You absorbed the structure — work first, then rest — without ever being given a clear account of what would constitute sufficient work. And so the threshold moved with you. As you got better, more was expected. As more was expected, the standard of done enough rose accordingly. The rest receded at roughly the same rate as your competence advanced.

This is not a coincidence. It is how the belief sustains itself.

The guilt mechanism

For many capable professionals, resting when things are unfinished produces a specific discomfort that doesn’t feel like preference — it feels like irresponsibility.

Not laziness. Not indulgence. A specific, physical-register discomfort that reads as: I shouldn’t be doing this. There is something I should be doing instead.

This discomfort is the belief in operation. It is not a signal that rest is genuinely wrong or harmful. It is the learned response of a nervous system that has been trained to treat stillness as risk. A system that equates activity with safety and rest with exposure.

The discomfort feels like information. It isn’t. It’s a reflex. A well-established, thoroughly reinforced reflex — but a reflex nonetheless.

The physiological argument

Here is what the research actually says, separate from any belief system.

The prefrontal cortex — the part of the brain responsible for judgment, creativity, decision-making, and sustained attention — degrades under sustained cognitive load. It does not degrade slowly and then recover when you eventually stop. It degrades continuously and recovers with genuine rest.

This means that the professional who works through the evening, the weekend, the holiday, and the quiet moments that other people use for recovery is not accumulating an advantage. They are eroding the very capacities they are working to apply. The judgment gets worse. The decisions become less good. The attention narrows. The creativity flatlines.

You are not choosing between productivity and rest. You are choosing between sustainable productivity and its gradual, largely invisible erosion.

Rest is not the reward at the end of productivity. It is a condition for productivity. Treating it as a reward is how you accidentally make it unavailable.

What rest actually requires

Not completion. The work will not be done. There will always be something outstanding.

Not permission from your workload. Your workload will never tell you it is time. There is always one more thing.

Not a clear conscience in the terms your achievement-environment defined. That standard was never reached by anyone who held it. It was designed to be unreachable.

What rest actually requires is a decision.

The only thing standing between you and rest, in most cases, is a belief — the belief that you haven’t yet done enough to deserve it. That belief feels like a fact. It is not a fact. It is a conclusion you drew from a particular kind of environment, and it has been running in the background ever since.

Decisions can be made before beliefs are fully resolved. You do not have to stop believing that rest must be earned in order to rest. You just have to act ahead of the belief, rather than waiting for the belief to change first.

The belief changes after the decision. Not before.

One honest question to close with

Not: have you done enough to deserve rest this week?

That question has no satisfying answer. You already know this.

Instead: what would you need to believe to give yourself permission to rest this week — without finishing everything first?

That question points at the belief directly. And the answer, when you sit with it honestly, is usually some version of: I would need to believe that nothing catastrophic will happen if I stop. That the work will still be there. That I am not abandoning anything by being a person who also rests.

Which is, it turns out, true.

Before you go: what’s the thing you’re waiting to finish before you let yourself rest? Reply to this. I read everything.

Leave a comment

Ricky

Read more

I want to describe a specific kind of professional experience that rarely gets named directly.

Not burnout. Burnout is about depletion — running on empty after running too long.

Not imposter syndrome. That’s about doubting whether you deserve to be here.

Not a career crisis. That implies something dramatic, a breaking point, a moment of collapse.

This is quieter than any of those. It’s the experience of being genuinely good at something that has quietly stopped fitting the person you’ve become.

You’re competent. You know you’re competent. The evidence is consistent and visible. And somewhere between the last performance review and this morning, the work stopped generating the feeling you thought competence was supposed to generate.

Three versions of the same experience

Because this shows up in different forms, and the version you’re in determines what actually helps.

The promoted ceiling.

You worked towards a role for years. The progression was deliberate and earned. And then you got there — and discovered that the role is a completely different kind of work from the job you loved.

The job you loved was the doing. The craft, the making, the solving. The role is the managing. The reporting. The performance of leadership that comes with the title.

You’re good at the role. You’ve developed the skills. But the thing that used to energise you — the actual work, the hands-on version — is now something you supervise rather than do.

This isn’t failure. It’s a structural consequence of progression in most organisations. The people who are best at doing get promoted into not doing. And almost nobody warns you that this might not be what you wanted.

The competence trap.

You got very good at something. Better than most people around you. And then you stayed.

Not because you love it. Because leaving felt wasteful. Because the competence is real and starting again feels like choosing to lose something you earned. Because the identity you’ve built over years is tied to this particular skill, and releasing the skill means releasing the identity.

So you keep doing the thing.

And the thing keeps not being quite right.

The competence trap is particularly common in high-achievers because high-achievers are, by definition, people who became very good at things. The same quality that made them effective is the quality that holds them in place.

The quiet drift.

This is the most common version and the least dramatic. Nothing changed. There was no promotion, no moment of realisation, no obvious turning point.

The work just gradually stopped generating what it used to generate. You used to leave energised. Now you leave fine. The work is adequate. The income is reasonable. The colleagues are decent. There’s nothing obviously wrong.

Fine is not the same as good. But fine is easy to miss. And by the time you notice the drift, you’re usually quite far from where you started.

Why this is hard to name

The reason this experience rarely gets spoken out loud is that it sounds, from the outside, like ingratitude.

You have a good job. You’re good at it. You’re paid reasonably. What exactly is the problem?

The problem is that ‘the problem’ is the wrong frame. This isn’t about problems. It’s about fit. And fit, unlike problems, doesn’t have a straightforward solution.

Fit is the relationship between the work and the person doing it. A job that fits perfectly at thirty might not fit at forty. Not because the job changed. Because you did. You developed, expanded, shifted in emphasis. The work stayed the same. The misalignment emerged slowly, without announcement.

Naming this isn’t ingratitude. It’s accuracy.

What actually helps — three honest questions

These aren’t designed to push you towards any particular outcome. They’re designed to help you see more clearly what’s actually happening, which is the only honest starting point.

If you could stop doing this tomorrow with no consequences — financial, relational, identity-related — would you?

Not: should you. Not: is it realistic. Just: would you?

Most people who answer yes have been answering yes for longer than they’ve admitted. The question doesn’t require action. It requires honesty. And honesty about where you are is necessary before you can think clearly about where you might go.

What were you hoping the work would give you that it isn’t giving you now?

Energy. Meaning. The feeling of using the part of yourself that most wants to be used. A sense of growth. The specific satisfaction of doing something that feels like it’s yours.

Naming what’s missing is different from deciding to leave. It’s just naming what’s missing. That clarity is useful regardless of what you do next.

What are you still getting from this work that you’d have to deliberately replace?

This question matters because the answer is often more than just salary. Security, structure, identity, community, status, a sense of competence that’s hard to rebuild elsewhere.

These are real things. Acknowledging them isn’t a reason to stay in something that no longer fits. It’s a reason to be honest about the full picture when you’re deciding what to do with it.

What you’re not being asked to do

This isn’t a call to quit. It isn’t a suggestion that you’re in the wrong career. It isn’t advice.

It’s an invitation to look clearly at something that most professionals spend considerable energy not looking at.

You can be excellent at something and no longer be the person that work was built for. That’s not a failure of the work and it’s not a failure of you. It’s what happens when people grow and circumstances don’t always grow with them.

What you do with that knowledge is yours to decide. But you can only decide it honestly if you’ve first allowed yourself to see it clearly.

Is there something you’re very good at that you’d stop doing if you could? What would it take to name that honestly?

Before you go — one question: what’s the work you do well that quietly costs you? Reply to this email. I read everything and it shapes what I write next.

Leave a comment

Ricky

Read more

I want to describe a specific kind of exhaustion.

Not the tiredness that comes from a heavy workload. Not the depletion of a difficult week. Something more particular than that — the kind that arrives before anyone has said anything, before anyone has asked anything of you, before the day has technically made any demands at all.

You walk into a room and you feel the mood before it’s been named. You notice a colleague’s tension in the set of their shoulders before they’ve spoken. You sense that something is wrong at home before anyone has mentioned it.

And then, without making any conscious decision, you start managing it.

It’s not care. It’s something else.

Care is a choice. You see something, you decide to help, you act. There’s a moment of agency in the middle of it — the decision point where you could have said no.

What I’m describing has no decision point. The worry arrives and you hold it before you’ve made any choice at all. It’s automatic. It’s reflexive. It bypasses the part of you that could have said: this isn’t mine to carry.

This matters because care and absorption look identical from the outside. Both involve attention, effort, and emotional investment. Both leave you tired. But care is sustainable. It’s bounded by the choice that initiated it. Absorption has no natural boundary. It expands to fill whatever space your capability creates.

Why this clusters around capable people

The professionals who absorb the most are usually the most perceptive.

They’re the ones who read a room accurately. Who anticipate problems before they fully form. Who notice what others miss and act before they’re asked. These are professional strengths. They’re the reason you’re good at what you do.

But the same skill that makes you effective at work operates continuously. It doesn’t stop when you leave the office, when you sit down at dinner, when you’re trying to rest. The brain that’s trained to detect problems keeps detecting them. The person who absorbs other people’s worry isn’t doing something wrong. They’re doing something they’ve been rewarded for doing, in a context where it isn’t serving them.

There’s also a specific variant of this that’s worth naming: the anticipatory worrier. Not just someone who absorbs existing anxiety, but someone who worries in advance on behalf of people who aren’t worried yet. They imagine what the other person might worry about if they were paying attention — and then they do the worrying for them, pre-emptively, so no one else has to.

This is not a character flaw. It is a very efficient way to be exhausted.

The weight of absorbed worry

Here’s what makes absorbed worry particularly hard to identify: it feels like yours.

By the time you’re carrying it, you’ve already integrated it. It sits alongside your own legitimate concerns, mixed in with your actual responsibilities, indistinguishable in texture from the things that genuinely belong to you. It feels urgent. It feels important. It feels like something you need to address.

One useful test is to check whether the worry is proportionate to the actual risk — but with absorbed worry, the more useful test is simply: is the person whose worry this is actually worried?

If they’re not worried and you are, you haven’t identified a risk they’ve missed. You’ve taken on something that isn’t yours to hold. You’re not being more careful than them. You’re doing their worrying for them, and they didn’t ask you to, and they don’t know you are, and it’s costing you in a way that has no obvious source when you try to trace it back.

Three questions that help sort it

These aren’t designed to make you stop caring. They’re designed to help you notice what you’re actually holding — and whether you chose to hold it.

Did someone explicitly ask me to carry this? Or did I pick it up because it was there and I was capable of holding it?

The fact that you can hold something doesn’t mean it belongs to you. Capability isn’t consent. Being perceptive enough to notice a problem doesn’t automatically make that problem yours to solve.

Is the person whose worry this is — actually worried?

If the answer is no, you’re not helping them by absorbing their anxiety. You’re just distributing it differently, from them to you. They’re fine. You’re carrying something they’ve already put down.

If I put this down for 24 hours, would something actually break?

Not: would I feel anxious? Would I feel guilty? Would I feel irresponsible? Those feelings are real and they don’t mean the answer is yes. The question is whether something would objectively worsen if you stopped holding it. Most absorbed worry fails this test. The thinking doesn’t prevent the problem. It just keeps you company while the problem resolves or doesn’t resolve entirely on its own terms.

What you’re not giving up

The goal here is not to become less caring. It’s to distinguish care from absorption — because they are different things, and conflating them is expensive.

You are not a more caring person because you carry worry that isn’t yours. You are just a more exhausted one. The people you care about are not better served by your depletion. They are better served by you noticing what you’ve agreed to hold, and what you’ve simply accumulated.

Putting down absorbed worry isn’t abandonment. It isn’t selfishness. It’s accuracy. It’s being honest about what was ever actually yours to carry — and returning the rest, gently, to where it belongs.

Before you go — one question: whose worry are you carrying right now that isn’t technically yours to hold? Reply to this email. I read everything and it shapes what I write next.

Leave a comment

Ricky

Read more

I want to describe someone you might recognise.

They close the laptop at the end of the day. They go home. They sit at dinner with people they love. They are physically present and mentally still at their desk.

The food goes cold. The conversation happens around them. Somewhere in the background, a problem they left unresolved is still running. A decision not yet made. A conversation they’re mentally rehearsing for tomorrow.

This isn’t workaholism. The workaholic chooses work over everything else. What I’m describing is different. This person isn’t choosing to keep working. They just can’t stop. The work follows them. The thinking never fully pauses.

It’s not a discipline problem

The first thing to understand is what this isn’t.

It isn’t about weak willpower or poor boundaries. It isn’t about being bad at rest or not valuing your personal life. The professionals I see struggling most with this are often the ones who are most aware of how much they need to switch off — who know, rationally, that they should be present — and still can’t get there.

Classic workaholism is about choosing work. You know you could stop. You don’t want to.

What I’m describing is closer to the opposite. You want to stop. You just can’t find the door.

Why this clusters around capable people

Here’s the structural reason, and it matters.

The more competent you are at your job, the more your brain has been rewarded for staying engaged. At some point — probably many points — staying mentally present prevented something from going wrong. You spotted the mistake. You anticipated the problem. You remembered the thing everyone else forgot.

Vigilance has a track record.

So your brain files this under: useful behaviour. Keep doing this. Don’t switch off.

This is not a conscious decision. It’s a pattern that gets reinforced over years of being reliably good at your job. The brain learns that switching off is risky. And so it stops offering the option.

The professionals who struggle most with this are often the ones with the longest track record of competence. Not because something is wrong with them. Because something went right, repeatedly, for a long time — and the nervous system drew the wrong conclusion.

The anxiety underneath

There’s a belief underneath all of this, usually operating below the level of conscious thought.

It goes something like: if I stop watching, something will go wrong.

Not because there is a specific thing likely to go wrong. But because staying mentally present feels protective. Like watching a flame — if you look away, it might spread.

You are not, rationally, keeping anything safe by lying awake at 11pm replaying a conversation that went fine. You know this. But the anxiety doesn’t care about rational assessment. It cares about reducing threat.

And so the thinking continues. Not because it’s useful. Because it creates the feeling of being in control of something that is, in reality, already out of your hands.

Three things that actually help

These are not quick fixes. But they are the things that address the actual problem rather than the surface symptom.

1. Scheduled incompleteness

This sounds counterintuitive. Don’t end the day at a clean stopping point. End at a point where something is obviously unfinished — but clearly resumable.

Leave a note: Tomorrow, start here.

The brain relaxes when it has a specific re-entry point. It doesn’t need to hold the work open all evening if it knows exactly where to come back to. The mental file stays closed because you’ve told it exactly how to reopen it.

Clean stopping points, ironically, leave the brain searching for what it might have missed. Deliberate incompleteness tells it: we’re done for today. There’s a door. Here’s the handle.

2. A transition ritual

This doesn’t need to be significant. It needs to be repeatable.

A specific walk. A particular playlist. A cup of tea made with attention, not with half your mind still on the day.

The purpose of a transition ritual isn’t relaxation — though that’s a useful side effect. The purpose is training the nervous system to recognise a signal: this moment means it’s safe to stop.

Not one session. Not ten. Over time, with repetition, the signal starts to work. The nervous system is slow to learn. But it does learn.

3. One question

Is there anything that will actually be worse tomorrow if I don’t think about it for the next two hours?

Almost always, the answer is no.

The thinking doesn’t prevent the problem. It creates the illusion of control without the substance of it. You are not keeping something safe by thinking about it. You are keeping yourself anxious.

This question doesn’t eliminate the anxiety. But it exposes the mechanism. And once you can see the mechanism clearly, it has slightly less power.

What switching off actually requires

It’s not discipline. It’s not willpower. It’s not a better productivity system.

It’s the slow accumulation of evidence that nothing catastrophic happens when you stop watching.

That takes time. It takes repeated small experiments in letting go. It takes noticing, over and over, that the world didn’t fall apart while you were at dinner — and letting that evidence land, rather than discounting it.

This is slower than any tip. It is also the only thing that actually works.

What does switching off actually feel like for you? Is it something you can access — or does it feel like it requires permission you haven’t given yourself?

Leave a comment

Ricky

Read more

I want to describe someone you might recognise.

They’re capable. Thoughtful. They do good work when they start.

But they don’t start very often.

Not because they’re lazy — they’re visibly not lazy. They’re always doing something: researching, planning, refining, preparing. The folder on their desktop is meticulously organised. The notes app is full. The idea has been thought about from every angle.

And yet the thing itself — the project, the conversation, the piece of work that matters — remains unstarted.

This is one of the most common patterns I see in overwhelmed professionals. And it’s almost always misdiagnosed.

It’s not procrastination

Procrastination, in its classic form, is avoidance. You know what needs doing, you don’t want to do it, you find other things to do instead.

What I’m describing is different. The person isn’t avoiding work. They’re doing work — just the preparatory version of it, indefinitely.

The distinction matters because the solutions are different.

For procrastination, the intervention is usually about motivation, accountability, or breaking the task into smaller pieces.

For chronic preparation, the intervention is about something harder to name: the relationship between readiness and safety.

The confusion between readiness and safety

Readiness is a genuine state. It means you have what you need — the skills, the information, the plan — to make a reasonable start. Readiness improves with preparation, up to a point.

Safety is different. Safety is the feeling that nothing can go wrong. That you won’t be embarrassed, won’t fail publicly, won’t produce something that falls short.

For the chronic preparer, readiness and safety have become confused. They’re not preparing until they’re ready. They’re preparing until they feel safe.

And safety, in that sense, is never fully achievable. Because the only thing that would make the work feel safe is the work being done — which requires starting.

This is the trap: preparation is the thing that’s supposed to reduce the risk of starting. But when it becomes a proxy for safety, more preparation doesn’t reduce the anxiety. It delays it.

Why this happens to capable people specifically

Chronic preparation tends to cluster around people who are good at what they do.

Here’s why: when you’re capable, the gap between what you can envision and what you can currently execute is wider. You can see clearly how good it could be. That visibility is a gift when you’re doing the work. It’s a liability when you’re trying to start.

You’re not avoiding starting because you don’t care. You’re avoiding starting because you care a great deal — and starting means producing something that might not match the vision.

The preparatory phase is safe. The actual work is exposed.

The question that breaks the loop

When I work with someone stuck in chronic preparation, I ask one question:

What would a good enough version of this look like — not a perfect version, a good enough one?

Not: what would the best possible version look like? Not: what would impress people?

What would be good enough? Sufficient. Worthy of existing.

Then: can you produce that version in less time than you’ve been preparing?

Almost always, the answer is yes.

The preparatory work has usually exceeded what’s needed for a good enough start. The information is there. The plan is there. What’s missing isn’t readiness.

What’s missing is the decision to accept that the work will be imperfect when it starts — and that imperfect and started is worth more than perfect and unrealised.

One thing that actually helps

Set a start date, not a ready date.

Not: I’ll start when I’ve finished the research. Not: I’ll start when I feel more confident.

A specific date. A specific time. A first action that is small enough to be genuinely hard to avoid.

Not finish the thing. Not even make significant progress. Just: the first action. The one that means it’s started.

Readiness is a feeling. And feelings follow action, not the other way around. You cannot think your way to feeling ready. You can only act your way there — and the act has to be small enough to actually happen.

This week’s Calm Kit — The One Small Start — is a one-page tool for the moment before beginning. It helps you identify the single smallest action that counts as starting, and what’s actually stopping you. Attached below for Founding Members.

Read more