Talk it through with Aurelius
When you're always the last one to leave
You're reflexively the last one to leave — staying late by default, long after the work that needed doing is done, sometimes with nothing left to do but be there. It's not the workload; it's a compulsion. Leaving on time feels like slacking, even when everyone else already went home.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
Mostly inner — what the staying performs or avoids, and the permission to leave (guidance). A little practical reframe of presence vs output.
How the two dials adapt to you →What’s really going on
Staying late by reflex isn't dedication — it's usually about being seen as dedicated, a discomfort with leaving before some invisible bar is met, or a life outside work you're quietly avoiding. The hours past the point of usefulness aren't producing anything; they're performing something, or escaping something. We look at what the staying is really for, and build the permission to leave when the work is done.
🔒 What you’ll build togetherUnlock by starting
KnowledgeWhy you can't be the one who leaves first
KnowledgePresence isn't productivity
KnowledgeWhat the late hours are really for
KnowledgeLeaving when the work is done
A moveName what you're afraid of if you're the first to leave — and whether it's real.
A moveLeave on time once this week, work finished, and notice what the discomfort is about.
PractiseLeave first · a Pod of 4 · 25 min
What changes unlock by starting
- You leave when the work is actually done.
- You stop confusing presence with productivity.
- You reclaim the hours you were performing away.
- Leaving on time stops feeling like slacking.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.