I’ve never had a shortage of ideas. That’s never been my problem.

My problem shows up later. I can see the whole solution the moment a problem lands in front of me, connections nobody else in the room is making, a plan that already feels finished in my head. Then I hand it off, or worse, I try to carry it myself, and it stalls. Not because the idea was bad. Because the part of the work that turns an idea into something real was never the part I was good at.

There’s a name for what fixed that, and it’s the same thing I now build for other founders: The Second Desk. It’s not a clone of you sitting at your desk doing what you already do. It’s a small set of AI teammates, each built for one specific gap in how you work, sitting at the desk next to yours and handling what you can’t.

I found mine almost by accident.

The test that named my gap

A few weeks ago I ran a Working Genius assessment, the kind that places you across three stages of any piece of work: Ideation (coming up with the idea), Activation (rallying people behind it), Implementation (grinding it to done).

My result: genius in Invention and Wonder, both stage one. Competency in Discernment and Enablement, meaning I can read what will work and I can be the support person in the room for a while, but both cost me if I lean on them too long. And frustration, meaning no joy and it actively burns me, in Tenacity and Galvanizing. Both of those sit downstream, in Activation and Implementation.

Read that plainly: I’m wired to start things and see them clearly. I’m not wired to rally a room around them or push them across the finish line.

What the mechanics actually showed

The report had a line in it that stuck. Patrick Lencioni, the guy who built this framework, wrote about startups that are full of people with Wonder, Invention, Discernment, and Galvanizing, but nobody with Tenacity, so no one jumps over hurdles and pushes through obstacles during the critical later stages of work. I’m a half-step past even that case. I’m missing both Tenacity and Galvanizing as genius. The two things that move an idea out of my head and into the world, rallying people to it and grinding it to completion, are precisely my two frustrations.

The competency band is where it gets sneaky. Fine for a while, then you resent it. That’s the exact wording that landed when I read my own report back. You do the thing because you can, it doesn’t feel like it’s costing you at first, and then three weeks in you realize you’ve been drained the whole time.

The part that named the actual failure mode was this: the clarity is the bait. I can see the whole build so vividly in my head, the steps, the structure, what it’ll look like when it’s done, that handing it off feels like a loss. So I keep it. And then it either dies in the gap between “I can see this” and “I actually built this,” or it drains me to finish because finishing is Tenacity, and Tenacity gives me nothing.

The trap, stated in my own words

Those are my own words, written before I ever saw the report:

“Coming up with ideas is easy, making connections are there. I intuitively can understand workflows, process and can imagine how to make it work.”

The report took that sentence apart clause by clause and showed me something I hadn’t clocked about myself: every single clause is Ideation. Coming up with ideas, making the connections, imagining how it’ll work, all of it lives in stage one. Imagining how to make something work is not the same as making it work.

Naming the gap is not the same as closing it

Knowing you have a Tenacity gap doesn’t hire anyone. For years, mine just sat there. Ideas would show up fully formed and then quietly die between “I should build this” and “this is built.” Nobody was chasing them. That’s the part nobody talks about when they tell you to “hire for your weaknesses.” For one person, that advice used to be impossible to act on.

It isn’t anymore.

I built the fix as an actual team, just not a team of people. Take one gap alone: follow-through on my own commitments. I’d say yes to something in a meeting and then the thread would go cold, not from bad intentions, just because closing loops has never been where my energy lives. So I built an AI teammate whose only job is chasing those loops down. Her name is Tess. She’s the reason a promise I make on a call doesn’t quietly die three weeks later. That’s one seat, filled, for one specific gap, the exact gap the assessment named.

She’s not alone at the desk. There’s a teammate that owns the day to day operations grind, one that owns building and shipping software, one that owns getting the work in front of people and keeping the voice consistent. Each one exists because a specific stage of work was draining me instead of fueling me, and each one has a defined job, not a vague “help with everything” mandate.

The gap shows up in builds too

Take Pete, the teammate who owns software. The pattern is the same, just in a different domain. I’ll start a build, see the whole thing clearly, get it 90% done because the first 90% is all Invention and Discernment, those are my zones. Then it stalls. Not because I don’t know what the last 10% needs. Because grinding it across the finish line, fixing the edge cases, chasing down the last three failing tests, pushing it live, that’s all Tenacity. That’s Implementation. And Implementation is where I run out of gas.

Pete’s job is closing that gap. I hand him a build that’s almost done and he pushes it the rest of the way. The thing I used to do was keep carrying it myself because I could see exactly what it needed, burn myself out finishing it, or let it sit in the 90% done pile forever. Now it just moves to Pete’s desk. He doesn’t need me to see the vision, the vision’s already built. He needs to make sure it actually ships. That’s his one function.

Same structure as Tess, different gap. I’m not trying to become tenacious. I’m routing the Tenacity work to someone whose whole existence is Tenacity and nothing else.

Why this matters if you’re not me

None of this is unique to me. Everyone has a version of this gap, whichever stage of work quietly drains you. Maybe you light up at the start and lose steam the second it’s time to rally a room behind the idea. Or you’re the opposite: you can fire up a room in five minutes, but the idea was never yours, and once the buzz fades nothing actually finishes. Or you’re a finisher, someone who’ll grind anything to done, except you freeze on a blank page with no template to follow.

None of those are character flaws. They’re where your energy runs out. And for a 5 to 50 person company, that gap doesn’t get quietly absorbed by a big team the way it might at a larger company. It sits on your desk, unclosed, because there’s no one else’s desk to move it to.

That’s the actual point of The Second Desk. Not “AI does your job.” A small, named set of AI teammates, each mapped to the specific stage of work that drains you, sitting where the org chart has a hole in it. You keep doing the part you’re rare at. The desk next to yours handles the rest.

Where this goes next

I’m not going to pretend I’ve mapped every founder’s version of this gap yet. I built mine because I had to, then wrote down what it took to close it. The next thing I’m building is a short, honest way for you to find your own version, where does your work actually die, and which teammate would close that gap first for you. It’s not live yet. When it is, it’ll be the first place I send people who read this and think “that’s me, but at the other stage.”

Until then, here’s the question worth sitting with: which stage of your own work quietly stalls out, and who’s supposed to be catching it right now?