I’m done performing.
Not done working. Not done caring. Done with the particular exhaustion of operating inside a game where everyone knows the rules are fake and nobody says it.
The Game Everyone Plays
You know the game. The org chart that describes a company nobody actually works in. The meeting where three people give three different revenue numbers and everyone nods. The process the team follows on paper and the process they actually follow, which are not the same process and have not been for a while. The high performer who’s killing it — who is also, quietly, the reason the thing that should be a system is not collapsing.
Everyone sees this. Almost nobody says it out loud.
I spent years being called difficult for saying it out loud.
The Real Work of Detection
I have ADHD. I have PTSD. I manage both — today, now, alongside client work and family and everything else a functioning human being is supposed to keep aloft simultaneously. I am not telling you this as backstory. I am telling you this because it is currently true and I am done treating it as something to manage quietly.
I found out at 41, in a clinician’s office. But the conditions didn’t stop there. They came to work with me the next day, and the day after that.
A coworker found me hyperventilating in a parking lot once. I was mortified. I finished my workday anyway.
I’ve been mortified about that for years. I’m done being mortified.
The ADHD pattern recognition doesn’t stop at the edge of a job description. The hypervigilance — the kind that develops when your nervous system learns early that missing a signal has consequences — turns out to be excellent preparation for walking into a business and immediately knowing something is wrong.
I was not being difficult. I was detecting. And I was doing it while managing a nervous system that sometimes required a parking lot break.
Two Companies Running Simultaneously
What I kept detecting — in every organization, at every stage of growth, across every industry I ever worked in — was the same thing. Two companies running simultaneously. One of them on paper, confident and clean. One of them in reality, held together by people and workarounds and the kind of invisible labor that doesn’t appear on any report.
I eventually found the name for what I’d been doing.
Revenue Architecture. It’s a field. It existed before I found it. When I discovered it I had the quiet recognition of finally finding language for something you’ve known your whole career but couldn’t explain in a board meeting.
I built the most rigorous methodology I could find for practicing it. I started doing this work formally. And then I started writing, because someone needed to say what this work keeps finding.
Every time. In every organization.
Why This Exists
This is not a how-to. It’s not a sales pitch. It’s not a personal brand play. I’m not trying to position myself as a thought leader, which is a phrase I will never use again in any context, amen.
This is the thing I wish someone had written ten years ago. The argument that the way we’ve built business — for an idealized, frictionless, always-rational human who does not exist and has never worked for you — is costing us in ways most organizations have never bothered to calculate.
I wrote it because I got tired of watching people get blamed for system failures.
I wrote it because founders deserve to know what’s actually happening inside their companies, not just the version the org chart shows.
I wrote it for the ops leader who kept raising her hand and kept being told it wasn’t a priority.
I wrote it for the team that built the spreadsheet — not to undermine the CRM, but because the work still needed to happen.
I wrote it for the person who got called difficult.
Follow along or don’t. But this is real.