The Three-Lever Focus Framework: An ADHD-Informed Playbook for Executives Who Own Too Many Tools

You have eleven tabs open and none of them are the work. There is a task manager you stopped trusting in March, a notes app with three versions of the same client brief, a CRM you open only before calls, and a follow-up you know you owe someone but cannot place without scrolling. None of it is a discipline problem. It is a system problem, and it is costing you the exact resource you cannot buy back: attention.

I work with busy professionals and entrepreneurs whose focus is not just a habit to fix. Their brains are interest-driven, deadline-driven, and easily pulled toward the newest shiny system. That is why "just be more organised" falls flat. What works instead is a small set of decisions that shrink how much you have to remember. I call this the Three-Lever Focus Framework, and it is the structure I walk through on nearly every intro call I take. This playbook is the version of it you can start on today, with a specific emphasis on consolidating tools and automating follow-ups so you can scale without burning out.

Why ADHD executive focus breaks down when your tools multiply

Every app you add asks for a little maintenance. Log in, update statuses, copy something from one place to another, remember which one is "the real one". Individually those are tiny. Together they become a background tax on working memory, and working memory is usually the most stretched part of an ADHD brain.

Here is the loop I see most often, described in generic terms because every situation is different:

• You take on a new client or a new project, so you add a tool to handle it.
• For two weeks it feels great. You feel organised and in control.
• Then a second project needs a slightly different setup, so a second tool appears.
• Now nothing is complete, so you keep a mental list of the gaps.
• The mental list becomes exhausting, so you stop looking at the tools and start running from memory.
• Running from memory works for a while. Then a follow-up slips, a deal goes quiet, and you add another tool out of panic.

The problem is not that you are disorganised. The problem is that your system has more moving parts than your attention can supervise. For an ADHD-informed approach, the goal is not a perfect system. It is a system with fewer places to look, so checking it takes seconds rather than resolve.

The Three-Lever Focus Framework explained

Three levers, one at a time. Each one reduces the load the next one has to carry.

1. Consolidate. Reduce the number of places where work lives.
2. Capture. Make sure nothing important depends on you remembering it.
3. Rhythm. Review on a predictable schedule so the system stays trustworthy.

Most people try to jump straight to automation, buying a workflow tool before they have consolidated anything. That is how you end up with an automated mess, running faster in several directions at once. Order matters. Consolidate first so automation has one home. Capture second so automation has something reliable to act on. Add rhythm last so the whole thing does not decay after a busy month.

Lever one: Consolidate to a three-layer stack

"Consolidate my tools" is the request I hear most, and it is usually imagined as a big one-time migration. It does not need to be. It needs a target shape.

A workable stack for an ADHD executive or solo founder has three layers and rarely more:

• A thinking layer. One place for notes, drafts, and half-formed ideas. It should be fast to open and require no decisions.
• A doing layer. One place where tasks and next actions live. This is where your commitments are visible.
• A relationship layer. One place where people, conversations, and follow-up dates live. For many clients this is a CRM, but a well-structured spreadsheet can work if you will actually open it.

Everything else is either a tool that produces something you export into those three layers, or it is clutter. Meetings produce notes for the thinking layer. A proposal lives in the relationship layer until it becomes a task. That is the whole architecture.

Run a tool audit in ninety minutes

Do this once, in a single sitting, with your phone face down. Ninety minutes is the budget; set a timer and stop when it goes off even if you are not finished. Partial consolidation beats an abandoned migration.

1. List every tool (15 minutes). Open your browser, your dock, your phone, your subscriptions. Write every single one down, including spreadsheets and paper notebooks. Do not judge yet.
2. Mark the last time you opened each one (15 minutes). Use your best memory. If you cannot remember, that is your answer.
3. Ask one question per tool (30 minutes). "If this disappeared tomorrow, what would actually break?" If the answer is "nothing much", it goes to a keep-for-later list. If the answer is "I would lose a client commitment", it is load-bearing and needs a home in the stack.
4. Assign each survivor to a layer (20 minutes). Thinking, doing, or relationship. If a tool does not fit a layer, it is a producer, not a home.
5. Choose the closure rule (10 minutes). Pick one date, usually within two weeks, when the retired tools get logged out and cancelled. Put that date in your doing layer so the audit does not end up half-finished.

Example: A consultant I worked with had notes spread across three apps, a CRM, a task manager, and a whiteboard in her office. Her audit showed that two note apps held nothing she had opened in months, and that all her real follow-ups lived in email. She kept one note app, made it her thinking layer, used her task manager as the doing layer, and moved follow-up dates into her CRM. The whiteboard became a capture surface for the day only, wiped every evening. That is four surfaces reduced to three, plus a temporary one. Nothing fancy, and it was enough to make the system legible again.

Lever two: Capture and automate follow-ups without losing the human thread

Follow-up is where busy professionals lose money quietly. Not through catastrophe, but through the polite message you meant to send on Tuesday that became three weeks. For ADHD brains, the failure is almost never forgetfulness in the simple sense. It is that the intention never landed anywhere your future self would look.

So the rule is: any commitment you make out loud gets written down within the same conversation. Not later. Same conversation. A phrase I teach clients is "close the loop out loud", because saying "I will send that by Thursday" while typing it turns a verbal intention into a tracked one.

Once follow-ups are captured, automation becomes useful. But not every follow-up should be automated.

The automation decision test

Before you automate anything, run it through three questions.

• Is it repeatable? If the steps are the same each time, automate. If it needs judgement, keep it manual.
• Is it low stakes if it goes slightly wrong? A reminder to yourself is low stakes. A message to a client that arrives with the wrong name is not.
• Does it remove a decision or just move it? Good automation removes a decision. Bad automation creates a new inbox you now have to check.

Two automations are usually enough to start: one that creates a follow-up task with a date whenever you log a conversation, and one that surfaces stale follow-ups in a single weekly list. If you are tempted to build a third, ask whether it removes a decision or creates a new place to check. A new place to check is the opposite of focus.

The most important takeaway: automate the remembering, never the relating. Your follow-up system should remove the mental tab, not the human warmth.

Lever three: The weekly rhythm that keeps the system trustworthy

Consolidation decays. Automation drifts. Without a review, you will be back to eleven tabs within two months. The fix is not more discipline, it is a short, scheduled rhythm that you can do on a bad week.

Structure the week in three small passes:

1. Monday, ten minutes. Look at the doing layer and pick the three commitments that matter most this week. Write them somewhere visible. Three, not twelve.
2. Midweek, five minutes. Scan the relationship layer for anything with a date in the past. Close it, reschedule it, or delete it. Deleting is allowed.
3. Friday, fifteen minutes. Capture loose ends from the week into the right layer, then close the laptop. Do not start new work in this window.

Thirty minutes a week total. That budget is deliberate: if a system needs two hours of upkeep, an ADHD brain will skip it the first week it gets busy, and skipping once makes skipping twice easier.

If thirty minutes still feels like a lot, cut the midweek pass first. Monday and Friday carry most of the value.