Understanding yourself

Why do I feel like I can never fully switch off?

If rest never quite feels like rest — if there's always a background hum of things unfinished, things that could be better, things you should be doing — there's a specific reason for that.

You're on holiday. Or it's Saturday afternoon. Or it's ten o'clock in the evening and there is genuinely nothing that needs doing right now. And yet — there's something. Not a specific task, not an urgent problem, but a kind of background running that doesn't pause just because you've stopped. Your mind is still processing. Still returning to unfinished things. Still aware, at a low level, of everything that isn't quite done yet.

The people around you seem to rest more completely. They watch something without checking their phone. They sit without an agenda. They appear to occupy the present moment without being accompanied by the persistent low hum of things that need attention. You've tried to do the same. Sometimes it works for a while. But fully switching off — really arriving in the rest, without the background process still running — happens less often than you'd like.

This isn't anxiety in the clinical sense, though it can overlap with it. It's something more specific — a relationship with completeness, with standards, with the gap between where things are and where they could be, that doesn't have an off switch. Understanding where it comes from changes what you can do about it.

What the background process is actually doing

The hum isn't random. It tends to orbit specific things — the task that isn't quite finished, the conversation that didn't land right, the project that's good but could be better, the decision that's been made but hasn't been fully integrated yet. It's a monitoring process, checking in on open loops, maintaining awareness of things that haven't been resolved or completed or brought to the standard they should be at.

For some people, open loops close easily. They finish work, put it down, and the mental file genuinely closes. For others the file stays open — not because they're choosing to keep it open, but because their processing system treats incompleteness as a persistent signal that requires continued monitoring until resolved. The hum is that monitoring. It's not worry. It's attention that doesn't know it's allowed to stop.

The exhausting part is that the monitoring runs regardless of whether you can actually do anything about what it's monitoring. It runs at ten o'clock at night when the office is closed. It runs on holiday when the project is three thousand miles away. It doesn't coordinate with your schedule. It just runs, because it's a process that responds to incompleteness rather than to opportunity — and incompleteness is always present.

The different versions of this experience

Not being able to switch off takes different forms depending on what's driving it.

For some people it's standard-driven — the awareness of gaps between where something is and where it should be. The work is done but it could be better. The conversation happened but something wasn't quite right about how it went. The project is complete but there's a version of it that would be more accurate, more thorough, more defensible. The monitoring is quality-focused. It's looking for the gap.

For others it's task-driven — the awareness of things that haven't been done. A to-do list that never reaches zero. The inbox that fills faster than it empties. The sense that being productive enough would eventually produce the peace of a fully cleared plate — except the plate never stays clear long enough to produce it. The monitoring is list-focused. It's tracking what's outstanding.

For others still it's relational — a low-level checking in on the people around them. Did that person seem okay? Was there something in how they responded that needs following up? Is someone expecting something I haven't provided yet? This version of the hum is less about tasks and more about connections — a monitoring of the relational landscape for things that might need attention.

There's a name for how you're wired

The DISC personality framework identifies four core behavioural traits — Dominance, Influence, Steadiness and Conscientiousness. People who struggle most to fully switch off tend to score highly in Conscientiousness — the C trait — sometimes alongside Dominance — the D trait.

C types have a fundamental orientation toward accuracy and quality. Their internal standard for what constitutes a properly completed thing is high — and the monitoring system that checks against that standard doesn't have a scheduled off time. It runs continuously, which means it runs during rest. The C type who can't switch off isn't a workaholic. They're a person whose quality-consciousness doesn't pause just because the working day has ended. The same precision that makes their work excellent makes their rest incomplete.

D types bring a different version. They're driven by results and momentum — and the absence of forward movement, even during legitimate rest, can feel uncomfortably like stalling. The monitoring in a D type is less about quality and more about progress. Is the thing moving? Is anything being produced? Is the time being spent in a way that moves something forward? Rest that doesn't produce anything struggles to satisfy the D type's orientation toward outcomes.

DC types carry both simultaneously. The C's quality-consciousness and the D's results-orientation combine into a system that struggles to rest because rest is both unproductive (D) and incomplete (C). These are the people for whom the working day genuinely never ends — not because they're workaholics but because their natural operating mode doesn't distinguish between work time and rest time in the way that most people's does.

What it costs you that you might not be tracking

The obvious cost is the quality of the rest itself — which isn't as restorative as it should be because it isn't complete. Rest that's accompanied by a background process running is lighter than rest without it. The recovery is partial. Over time the partial recovery compounds into a tiredness that isn't addressed by the holidays or the weekends because the holidays and the weekends aren't fully reaching the thing that needs replenishing.

There's also a creativity cost. The connections between ideas that produce insight, the unexpected thinking that happens when the mind is genuinely unoccupied, the capacity to arrive at something new — these tend to come from properly idle states. The mind that's always monitoring doesn't have the genuine downtime in which the more lateral, more surprising thinking happens. You may be producing work that's technically excellent while closing off the conditions for it to be genuinely novel.

And there's a relationship cost. The person who can't switch off tends to be partly somewhere else even when they're present. Not obviously — they're there, they're engaged, they're responsive. But something is split. The partner who has learned that their person is never quite fully in the room has usually stopped mentioning it. That gap, unaddressed, widens slowly.

What to do with this

Create a deliberate closing ritual. Not a wind-down routine — a specific act of completion that signals to the monitoring system that the day is done. Writing down everything that's open, in one place, so that the mind doesn't have to hold it. A short review of what was done today rather than what remains. Something that closes the day rather than just stops it. The ritual doesn't resolve the open loops — but it tells the system that they're accounted for and don't need active monitoring until tomorrow.

Distinguish between productive monitoring and unproductive monitoring. Some of what the background process is doing is useful — genuinely keeping track of things that need attention. Some of it is running loops on things that can't be acted on right now and where the monitoring isn't adding anything. Getting better at identifying the second category — and explicitly giving yourself permission to stop monitoring it — develops with practice.

And reframe rest as an input rather than an absence of output. The C type and D type in you may only be able to justify rest if it serves something. Let it serve something. Rest produces better work. Rest produces clearer thinking. Rest produces the physical and mental substrate that the quality and results you care about actually run on. You're not stopping. You're investing in the conditions for what comes next.