The Attorney Who Got Her Evenings Back
Thirty years of practice. Fifteen meetings a day. And the discovery, at midnight, that the thing she needed from a colleague was due in nine hours.
A real story, shared with care. Identifying details disguised.
A Second Brain
This is what I build for you: a second brain. Notes that keep themselves, a calendar that tells the truth, delegation that happens at first touch, and a private system that feeds your work tools only what's cleared to enter them.
For people who carry too much in their heads and pay for it at midnight — including regulated environments where the usual AI tools are off the table.
Talk to me about a Second BrainShe found out at midnight.
A filing she owed the next morning depended on a piece a colleague hadn't finished, and she discovered it the way she discovered most things about her own workload: too late to do anything graceful about it. So she did what she always did. She stayed up. She patched it. She made the deadline, because she has made every deadline for thirty years.
That's the thing about the most capable person in the building. The building never finds out what it's costing her.
Fifteen meetings and a legal pad
She's a senior attorney in a heavily regulated corner of the law — the kind of world where the rules are real, the stakes are people's lives, and anything written down can end up on the record. Some days run fifteen meetings. And here's the twist that made her situation genuinely hard: because of strict records-disclosure rules, most of the AI tools the rest of us lean on were off the table. The transcription apps, the meeting notetakers, the chat assistants — anything that touched her organization's systems could become part of the record. Her compliance environment didn't just fail to help her. It actively forbade the helpers.
So the action items lived in three places: her head, a legal pad, and a trail of emails. The master to-do list — she calls it her matter tracker — existed mostly as a feeling. Delegation happened at the last minute, which is to say it barely happened at all, because by the time a task surfaced, the only person with enough context to do it fast was her. At midnight.
Her work-life split, when we measured it honestly, was running 20/80. And the 20 wasn't the work.
The turn
She didn't need more discipline. She had thirty years of discipline. She needed architecture.
We didn't start with an app. We started with the shape of her days — where information entered, where it stalled, and where it ambushed her. Then we rebuilt the system around the rules instead of against them:
- Notes that keep themselves — compliantly. A note-capture routine designed for her records-disclosure reality: what gets written, what gets cleaned, and clear guardrails on what enters the official systems. The technology bent to the compliance, not the other way around.
- A calendar that tells the truth. Her real commitments, work and life, mirrored into one honest view — so a 7 a.m. glance shows the whole day, including the collisions, before they happen.
- Delegation that happens early. Tasks with dependencies got first-touch checkpoints. The handoff happens when the task is born, not the night before it's due. Midnight discoveries became Tuesday-morning conversations.
- A private second brain. Her own system, on her own device, for the thinking, planning, and tracking that belongs to her — feeding the work systems only what's cleared to enter them.
The number we're chasing
The target is 40/60. Not perfection, not balance-influencer nonsense — just a life where the split doesn't quietly consume the person holding it. The evenings came back first. The matter tracker moved out of her head and into a system that doesn't sleep, which means she finally can.
None of it required a single rule to be broken, and none of it required her to work less hard. It required the thing high performers are never offered: an operating model designed for how their day actually runs.
If your action items live in your head, your legal pad, and your inbox, that's not a discipline problem. It's an architecture problem. The pattern that worked here works in any constrained environment: capture compliantly, mirror the calendar, delegate at first touch, and keep a private second brain. If your rules are strict and your days are fifteen meetings deep, this is exactly the kind of system I build with clients.
Book a conversation