I Built Myself a PM Because My ADHD Wouldn't Let Me Be One

I'm building a productivity platform. The irony isn't lost on me.

I'm the founder of Prolific Personalities — a research-backed system that helps people find the productivity approach that actually fits their brain. I've written the frameworks. I've studied the science. I've designed the archetypes. I know, intellectually, how all of this works.

And I still can't keep myself on track.

Not because I'm lazy. Not because I don't care. But because my brain does this thing where it convinces me that reorganizing my entire Notion workspace at 11pm is more important than finishing the feature I promised myself I'd ship by Friday.

Sound familiar?

The Problem Isn't Motivation. It's Architecture.

Here's what my typical work session used to look like:

I'd sit down to work on the mobile app. Twenty minutes in, I'd notice the onboarding flow could be better. So I'd sketch that out. Which reminded me that the email sequence needed updating. Which made me think about the content calendar. Which led me to redesign the whole marketing strategy.

Three hours later, I'd have five new ideas, two half-finished documents, and zero progress on the thing I actually needed to ship.

This isn't a willpower problem. It's an executive function problem.

And the cruel twist? I'm building a platform that literally categorizes this pattern. My own archetype research explains exactly why this happens — the oscillation between Novelty Seeker energy (new ideas, new systems, new everything) and Strategic Planner energy (meta-optimization, architecture refinement, planning about planning).

I know the theory. My brain just doesn't care.

What I Actually Needed

I didn't need another task manager. I have Notion. It's fine.

I didn't need another productivity system. I literally design those for a living.

I didn't need someone to tell me to "just focus." That advice has never worked for anyone, ever, in the history of advice.

What I needed was constraint.

Specifically, I needed something that would do three things every single day:

One — anchor me to a single weekly outcome. Not a list of goals. Not a roadmap. One shippable thing.

Two — interrupt me when I drift. Not after I've spent three hours on a tangent. In the moment, when the drift starts.

Three — refuse to let me start something new before the current thing is done.

A human PM would do this. But I don't have a PM. I have an AI assistant that knows my entire project inside and out.

So I turned it into one.

The Executive Function Layer

I didn't build a tool. I didn't create a dashboard. I didn't automate anything.

I wrote a set of behavioral instructions — a protocol — that changes how my AI assistant interacts with me during work sessions.

Here's the core of it:

Every time I start working, the AI asks me three questions:

What is this week's single shipping outcome?

What is today's one non-negotiable execution task?

What did you commit to in the last session?

That's it. Three questions. Before we do anything else.

Then it tracks a simple board:

Active projects — maximum three. Not five. Not "a few priorities." Three.

This week's ship — one thing, defined as something that gets published, deployed, delivered, shared, sent, or activated. Not "researched." Not "designed." Not "reorganized."

Today's non-negotiable — the one task that moves the ship forward.

Parking lot — where every shiny new idea goes until the current sprint is done.

The Rules That Actually Matter

The tracking is useful. But the rules are where it gets real.

If I try to start a fourth active project, the AI forces a decision: finish one, kill one, or park one. No exceptions.

If I start reorganizing systems, redesigning architecture, optimizing something that doesn't need optimizing, or chasing a new feature mid-sprint, the AI asks one question:

"Is this directly required to ship this week's outcome?"

If no — and it's almost always no — back to the parking lot. Back to execution.

If the conversation drifts into meta-level planning without concrete next actions, the AI converts it into a specific task and pushes me into a 90-minute execution block.

Every Friday, it requires a review: What shipped? What didn't? Why? What needs to be communicated to my team?

If nothing shipped, we analyze what actually went wrong. Not with shame. With honesty.

Why This Works (When Planners and Apps Don't)

I've tried every tool. Todoist. Asana. Trello. Obsidian setups that took longer to build than the projects they were supposed to organize.

None of them worked because they all have the same problem: they're passive. They wait for you to come to them. They organize whatever you put in. They don't push back.

My AI PM pushes back.

It has permission — explicit, written-into-the-instructions permission — to say no. To refuse expansion. To challenge unnecessary optimization. To redirect me when I'm drifting.

That's the piece most productivity systems are missing. Not the tracking. Not the templates. The friction.

Good friction. The kind that says, "Hey, I know this new idea feels exciting, but you told me yesterday that you were shipping the payment integration by Friday. Are we still doing that?"

It's the difference between a notebook and a co-founder who actually holds you accountable.

The Deeper Lesson (And Why I'm Sharing This)

I build Prolific Personalities because I believe generic productivity advice fails most people. The research backs this up. Your brain has a specific cognitive profile — a set of strengths, weaknesses, and tendencies that determine which strategies will actually work for you and which will become another abandoned system collecting dust.

But here's what building this PM layer taught me about my own product:

The frameworks aren't enough.

Knowing your archetype is valuable. Understanding why you drift, procrastinate, or overcomplicate things — that's genuinely useful. But knowledge doesn't change behavior. Structure does. Constraint does. The right kind of accountability does.

That's true for me, and it's true for the people I'm building this for.

If you've ever read a productivity book, felt inspired for a week, and then found yourself right back where you started — you're not broken. The book just gave you information without giving you infrastructure.

The information tells you what to do.

The infrastructure makes sure you actually do it.

What This Looks Like In Practice

Last week, my weekly ship was: deploy the premium content delivery flow so users can purchase and access their archetype playbook.

That's specific. That's shippable. That has a clear "done" state.

On Tuesday, I had the urge to completely restructure how the assessment scoring algorithm works. It wasn't broken. It didn't need restructuring. But my brain decided it would be really satisfying to optimize it.

My AI flagged it. Parking lot.

On Thursday, I wanted to start designing the AI coaching feature — something that's months away on the roadmap. It felt urgent. It wasn't.

Parking lot.

Friday, the payment flow was live. Users could buy and access their playbook. It wasn't perfect. But it shipped.

That's the whole game. Not perfection. Shipping.

You Don't Need My Exact Setup

I'm not writing this to tell you to go build a custom AI PM protocol. (Though if you want to, it's genuinely not that hard.)

I'm writing this because the principle underneath it matters:

If your brain doesn't naturally constrain itself — and most brains don't, especially if you're neurodivergent, high-novelty-seeking, or prone to over-planning — you need external structure that does it for you.

That might be:

A co-founder who asks you hard questions every Monday morning.

A weekly standup with one other person where you declare what you're shipping.

A rule — written down, not just in your head — that says you can only work on three things at a time.

A Friday ritual where you honestly answer: what shipped, and what didn't?

The format doesn't matter. The constraint does.

The Uncomfortable Truth

The hardest part of building this wasn't the instructions or the protocol. It was giving the system permission to push back on me — and then actually listening when it did.

Because here's what happens when you're the founder, the PM, the strategist, the creator, and the decision-maker all at once: every impulse feels justified. Every tangent feels strategic. Every detour feels like it's "just this one thing."

And sometimes it is.

But most of the time, it's your brain choosing the dopamine hit of novelty over the discomfort of finishing.

I know this because I study it. I write about it. I built an entire assessment framework around it.

And I still need help doing the thing.

That's not failure. That's self-awareness turned into action.

You're Not Lazy. You're Not Broken. You Just Need a Different Approach.

If you've been cycling through productivity systems, feeling like you should be able to "just focus," wondering why you can start everything and finish nothing — you're not alone.

Your brain isn't broken. It's just running without the right constraints.

Find yours. Build them. And then — this is the hard part — let them work.

Even when it's uncomfortable.

Especially when it's uncomfortable.

Related reads

  • Your Resistance Isn't Laziness. It's Data.
  • Why Gamification Makes You Less Productive (Not More)
  • The Productivity Paradox: Why Doing What You Want Gets You Further Than Doing What You Should
  • Why Do I Have 100 Unread Tabs? (And What It Says About Your Brain)