This guide is for ADHD, autistic and other neurodivergent founders and CEOs who need a clearer way to hold direction, commitments, decisions, people context and external relationships, without relying on memory alone.
It is also for anyone running a company under a similar kind of load, whether or not they identify as neurodivergent. Start with the section that is live for you today.
The plays in this guide help with five questions:
Direction: Are we focused on the few outcomes that matter most?
People: Does important work have a clear owner and enough context?
Execution: Is the important work moving?
Decisions: What genuinely needs my judgement or attention?
External: Which customers, investors, partners or market signals need action?
How each play works
Each play starts with a familiar situation. It then shows one way you can set it up in Humble, what may be useful to check and what becomes easier.
These are patterns, not rules. Adapt them to your company, your team and the way you already work.
How every play works in Humble
A few simple principles appear throughout the guide:
01
Capture before it disappears
Get commitments, ideas and context out of your head while they are still present.
02
One clear owner
Many people can contribute, but one person should own the next step.
03
Context connected to work
Attach the objective, person, meeting, note or document to the task.
04
Dates where they matter
Use deadlines for timing and sequencing, and avoid fake dates that create noise.
05
Now / Next / Later
Separate what needs attention now from what can wait.
06
A small tag vocabulary
Only use tags that repeatedly create useful views.
07
Year-specific quarters
Use tags like #Q4-2026, never a bare quarter tag on its own.
08
Attention on exceptions
Focus reviews on blocked, unclear, overdue or decision-ready work.
Chapter 02~4 min read
Design this around how you think
Ordinary founder systems tend to assume you'll remember, notice and hold everything in view at once. When that assumption breaks down, the system should respond, not the other way round.
These patterns vary from person to person. Use the parts that reduce friction for you, without treating them as a diagnostic checklist.
When this gets hard, the system should respond by
When this gets hard…
The system should respond by…
Working memory
Keeping decisions, commitments and context connected outside your head
Time perception
Making dates, quarters and upcoming commitments visible
Task initiation
Turning vague work into a concrete next action with the context needed to begin
Attention regulation
Separating Now, Next and Later so everything doesn't compete at once
Context switching
Keeping the person, objective, note and source material close to the work
Variable capacity
Reducing the visible commitment on lower-capacity days and making the system easy to return to
Design principles
These patterns show up repeatedly across the plays that follow:
01
Externalise, don't memorise
Put important commitments and context somewhere trustworthy while they're present.
02
One thing at a time
Use Now / Next / Later so the whole backlog doesn't compete for attention.
03
Make tasks concrete
Replace "sort GTM" with "draft the first 10 target accounts".
04
Make time visible
Use real dates, calendar anchors and year-specific quarter tags.
05
Reduce switching
Connect context to the task, person or page.
06
Separate capture from organising
Capture quickly, and add structure only where it helps you find it again.
07
Use evidence of progress
Inspect the record before deciding nothing happened.
08
Create novelty buffers
Capture a new idea immediately, then evaluate it before it changes direction.
Patterns, not diagnoses
These are practical patterns drawn from how founders describe their own working memory, time perception, task initiation, attention regulation and capacity. They are not a diagnostic checklist, and different neurodivergent people need different support. Use whichever parts reduce friction for you.
Chapter 03~6 min read · three plays
Direction
Are we focused on the few outcomes that matter most?
Founders often carry the company direction in their head. That works until the team grows and people start acting from different versions of the plan.
The plays in this section
Turn direction into a few priorities.
Keep the quarter connected across teams.
Stop new ideas becoming accidental strategy.
Play 1: Turn direction into a few priorities
The situation
You know where the company needs to go, but the plan lives across decks, notes, calls and memory. Anyone who wasn't in the room is working from an older version.
One way to set this up in Humble
Create a shared space such as Company Priorities: Q4 2026 through Humble Teams.
Keep it to three to five outcomes.
Add the outcome, rationale, success measure and accountable owner for each.
Connect the tasks, notes, documents and meetings that show progress.
Why this can help: externalising direction reduces the working-memory load of repeatedly reconstructing and explaining the plan out loud.
Check this
The useful question is: does this week's work reflect the priorities we agreed?
What changes: the plan lives somewhere everyone can check, instead of only in your head and in whichever meeting it was last explained.
Play 2: Keep the quarter connected across teams
The situation
The same piece of work matters to more than one view: the quarter it belongs to, the team running it, the wider initiative it's part of. Rebuilding that picture by hand for every question wastes attention you don't have spare.
One way to set this up in Humble
Layer
Example tag
Time
#Q4-2026
Workstream
#GTM, #Product
Initiative
#EnterpriseLaunch
One item, several connections
An Enterprise Launch task could carry #Q4-2026, #GTM and #EnterpriseLaunch, while also linking to each key customer. Select + Add link on the task, then search for a customer's name or domain to connect it. The work stays in one place while still appearing in every relevant view.
Why this can help: visible dates and year-specific quarter tags make time easier to orient around when felt time is unreliable.
Check this
Ask: what is actually moving this quarter? Use the same underlying work to answer that, rather than building a separate report.
What changes: "what's moving this quarter" becomes a filter you can pull up, not a status document someone has to write.
Play 3: Stop new ideas becoming accidental strategy
The situation
A new idea or a piece of customer feedback arrives, and it's genuinely exciting. Without somewhere to put it, it either gets lost or the team suddenly finds themselves working on it, whether or not it was actually decided.
One way to set this up in Humble
Does the new idea or signal change an assumption behind the current plan?
No
Capture it as a note and keep it as context. It doesn't need to become a task yet.
Maybe
Create an investigation or experiment task, with a clear owner and a date to revisit it.
Yes
Record a decision note, then connect the resulting tasks to the relevant priority.
Why this can help: capturing an exciting idea straight away creates a novelty buffer. The idea is safe on record without immediately becoming the new strategy.
Check this
Before anyone starts work on it: has this actually been decided, or does it just feel urgent right now?
What changes: new ideas get a fair hearing without silently overriding what the team already agreed to focus on.
Chapter 04~6 min read · three plays
People
Does important work have a clear owner and enough context?
People need more than a task. They need the context around it: why it matters, who's involved, what was promised and what already happened.
The plays in this section
Make ownership explicit.
Keep people context connected.
Run leadership meetings around outcomes.
Play 4: Make ownership explicit
The situation
A commitment gets made in conversation, but it never turns into a task with an owner. Weeks later, nobody is quite sure whether it's happening, or whose job it was.
One way to set this up in Humble
Turn the vague commitment into a task with one accountable owner and the source context attached, using Who's doing this? to assign it.
Check this: look for
Unassigned strategic work.
Founder-owned work that could move to someone else.
"Look into" tasks with no concrete next step.
Why this can help: a concrete next action reduces ambiguity and makes starting easier, for you and for whoever it's assigned to.
What changes: fewer things quietly depend on someone remembering a conversation correctly.
Play 5: Keep people context connected
The situation
Notes, follow-ups, documents and tasks about the same person or organisation end up scattered, so preparing for the next conversation means reconstructing the relationship from memory.
One way to set this up in Humble
Humble's "connect a note to anything" relationship keeps a note tied to the person, the task it produced and any link it references, so the same conversation is findable from any of the three:
Q3 pricing follow-upShare
Call with Sam — discussed renewal terms and the timeline for the Q3 pricing update.
Today, 2:14pm
Add tagAdd relationship
Related to
Pricing page
humbleai.com/pricing — the public pricing page Sam was reviewing during the call.
Linked 2 days ago
Follow up
Send Sam the updated proposal and confirm renewal terms before end of week.
Due in 2 days
#QAShared with Alex +1 other
Sam Torres
Sales lead at Acme Co, and main contact for the Q3 renewal conversation.
Acme Co · Sales
acme-inc.com
linkedin.com/in/samtorres
Hover over or tap a circle to see what's connected
Check this: before a conversation
What happened last time?
What did I promise?
What do they care about?
What is still open?
What changes: preparing for a conversation becomes reviewing a connected history instead of trying to recall it.
Play 6: Run leadership meetings around outcomes
The situation
Leadership time gets spent on people talking through status out loud, which is slow, uneven and hard to hold onto afterwards.
One way to set this up in Humble
Use leadership time for what actually needs the room: priorities needing attention, material changes, blockers, decisions required and cross-functional dependencies. During the meeting, let the format do the translating:
Decision→Note→Action→Task & owner→Deadline
Check this
At the end of the meeting: does every decision have a note, and every action have an owner and, where timing matters, a deadline?
What changes: leadership time produces a record you can check later, rather than a conversation you have to remember correctly.
Chapter 05~6 min read · three plays
Execution
Is the important work moving?
Founders can end up becoming the company's status system. Humble should help you inspect what's already visible, then ask people only for the judgement or context that's genuinely missing.
The plays in this section
See progress without chasing.
Keep initiatives moving.
Manage by exception.
Play 7: See progress without chasing
The situation
A status update means asking someone to stop and explain where things stand, even though most of that information already exists somewhere in the system.
One way to set this up in Humble
Review the project, person, team or initiative before asking for another update. An initiative view might surface something like this:
Screenshot needed
An initiative view: objective, owner, connected tasks and any exception tags together.
What to look for
Progress first. Review the project, person, team or initiative before asking for another update.
Exceptions only. Use #Blocker or #NeedsAttention for genuine items that need intervention.
Shared initiative picture. Connect the objective, target date, owner, source documents and workstream tasks.
Evidence over recall. Inspect the record before interpreting a blank memory as a lack of progress.
Check this
Before asking anyone for an update: what can I already see? Then ask only for the missing context.
What changes: fewer status conversations, and the ones that still happen are about the thing that's actually missing.
Play 8: Keep initiatives moving
The situation
An initiative quietly stalls because nobody's asking the right question about it, not because anyone dropped it deliberately.
One way to set this up in Humble
Check this: on review
What moved since last time?
What's stuck?
Who owns the next step?
What decision is needed?
What depends on it?
What changes: a stall gets caught by a review question rather than by someone eventually noticing.
Play 9: Manage by exception
The situation
The company can be running a lot of work at once. Trying to hold all of it in view at the same level of attention is exactly what makes everything start to blur.
One way to set this up in Humble
Now
Work tagged #Blocker or #NeedsAttention: the small number of genuine exceptions.
Next
Initiatives on track, moving without needing your intervention this week.
Later
Completed or dormant work, kept as a record rather than something to keep checking.
Check this
Ask: does this genuinely need me, or is it moving fine without my attention?
What changes: the system can hold a lot of work while you see only the small number of items that actually need you.
Chapter 06~7 min read · three plays
Decisions
What genuinely needs my judgement or attention?
Founder attention should go to work that needs judgement, authority, relationships or taste. Everything else needs a better owner or a later slot.
The plays in this section
Write a decision down properly.
Sort what actually needs you.
Capture before it disappears.
Play 10: Write a decision down properly
The situation
A material decision gets made in a conversation, and a few weeks later nobody, including you, can reconstruct why. The rationale evaporates even when the decision itself survives.
One way to set this up in Humble
Keep a decision note with the same shape every time:
Question
Why now
Options
Evidence
Owner
Decision date
Decision and rationale
Resulting actions
Check this
Not every choice needs the full template. Use it where the rationale would genuinely be useful to have later.
What changes: a decision becomes something you can revisit, instead of something you have to trust you remembered right.
Play 11: Sort what actually needs you
The situation
Everything that reaches you gets treated as equally urgent, because it's all arriving in the same inbox, the same task list, the same headspace.
One way to set this up in Humble
Do
Needs your judgement now.
Delegate
Needs another clear owner.
Defer
Valid, but not now.
Remove
No longer worth keeping.
Why this can help: a small, visible Now list stops the full backlog from competing for attention all at once.
Check this
For anything sitting in your list unactioned: which of these four does it actually belong to?
What changes: your attention goes to the handful of things that genuinely need it, not to everything that happens to be in front of you.
Play 12: Capture before it disappears
The situation
A task, a thought or a useful link crosses your mind mid-conversation or mid-browse, and if it isn't captured in the next few seconds, it's gone.
One way to set this up in Humble
Capture the task, note, link or thought straight away.
Connect it to the person, project or page when useful.
Why this can help: fast capture protects working memory. Organising can happen later, when there's more capacity for it.
Check this
The rule that matters: capture needs to be faster than forgetting.
What changes: fewer good ideas and follow-ups disappear between the moment you have them and the moment you'd otherwise write them down.
Chapter 07~7 min read · four plays
External
Which customers, investors, partners or market signals need action?
Founders carry investors, customers, partners, advisers, market signals and promises made in passing. Those relationships need context and follow-through, not just goodwill.
The plays in this section
Run fundraising as a personal investor CRM.
Keep customer context connected.
Track partners and service providers.
Capture signals before turning them into action.
Play 13: Run fundraising as a personal investor CRM
The situation
Investor relationships live across LinkedIn messages, email threads and memory, so preparing to re-approach someone means reconstructing the relationship from scratch.
One way to set this up in Humble
While viewing an investor's profile on LinkedIn, add them to Humble.
Connect the person to their fund and to your Fundraising workstream.
Add tags for the stage, sector or theme they invest in.
Record their thesis, relevant conversations and anything worth remembering.
Before an investor conversation: what's their thesis, what did we last discuss, and is there a deadline sitting unactioned?
What changes: fundraising becomes a list you can work from, rather than a set of relationships you're hoping you remember correctly.
Play 14: Keep customer context connected
The situation
A piece of customer feedback lands, but by the time it's relevant to a product or commercial decision, nobody can find it or remember which customer said it.
One way to set this up in Humble
Connect customer notes to the relevant person or organisation, and link feedback to the product, commercial or strategic question it affects.
When a decision is being made: which customers said something relevant to this, and can I actually find it?
What changes: customer signal is findable by the question it affects, not just by memory of who raised it.
Play 15: Track partners and service providers
The situation
After an external meeting with an accountant, lawyer or partner, requests and deadlines arrive by email and get answered piecemeal, with no shared view of what's outstanding.
One way to set this up in Humble
After external meetings, ask what was promised, who owns it internally, when it matters and what context they need. Where accountants, lawyers or other service providers need access, use a Humble Teams shared space to keep their requests, documents, deadlines and your responses together.
Check this
Ask: does this provider need their own shared space, or is one thread of tasks enough? Create the space only when several people genuinely need the same context.
What changes: outstanding requests from external providers live in one place both sides can check, instead of an email thread only you're tracking.
Play 16: Capture signals before turning them into action
The situation
A piece of market information arrives, a competitor move, a shift in customer behaviour, and it's tempting to react to it immediately, before it's clear whether it actually changes anything.
One way to set this up in Humble
Capture market information as a signal first. Ask what assumption it changes before turning it into action, using the same "does it change an assumption" question from the Direction chapter.
Check this
Is this a pattern, or a single data point?
What assumption behind the current plan does it touch?
Does it need a decision, or just watching for now?
What changes: market noise gets a place to land that isn't either "ignored" or "immediate pivot".
Chapter 08~3 min read
The neurodivergent founder operating rhythm
A simple rhythm beats a perfect system. The example below is a starting point, not a fixed schedule.
Daily: orient around attention
You might review:
Today's commitments, meetings and decisions.
Blockers that need you specifically.
The small number of tasks in Now.
On a lower-capacity day, make the Now list smaller rather than pushing through it.
Monday: check the shape of the quarter
It may help to review:
#Q4-2026 and this week's outcomes.
Founder attention: what's actually in Now.
Likely blockers before they become urgent.
Midweek: check critical initiatives
Blockers and decision-ready work.
Anything missing context it needs to move.
Leadership meeting: decide and unblock
Use the meeting to decide and unblock, not to rebuild status out loud. Decisions become notes, actions become tasks, owners become assignees.
Friday: close loops
A short review might ask:
What moved this week?
What needs to move to Next or Later?
Inspect the record before deciding that nothing moved.
Protect breaks and recovery
Breaks are part of capacity planning, not a reward for finishing everything. Put them in the calendar before the day fills up. Leave decompression time after demanding meetings, and don't automatically turn every open slot into another commitment.
For some neurodivergent founders, hyperfocus or delayed awareness of fatigue can make stopping cues easy to miss, which makes a calendar anchor more reliable than waiting to notice you need one.
Chapter 09~4 min read
How to organise this in Humble
There is no single correct setup. The structure below is a useful starting point for keeping the system simple and findable, not a rulebook.
Create a shared space through Humble Teams when different people genuinely need access to the same work. A shared space is an access boundary, not just another way to filter. Depending on your stage, a small number might include:
Company Priorities
Leadership
Fundraising, when active
Major cross-functional initiatives
Selected major customers or partnerships
Accountants and service providers who need access to requests, documents and deadlines
Useful tags
Time
#Q4-2026#Q1-2027
Workstream
#GTM#Product#People#Finance#Fundraising
Type, only where useful
#Decision#Blocker#NeedsAttention
Never use #Q1 or #Q4 on their own. Otherwise current work and older work get mixed together when the same quarter number comes round again next year.
A tag is useful when it repeatedly helps you find or review something. If you can't name the view or recurring question a tag supports, you probably don't need it.
Connected integrations
Connect tools such as Linear, GitHub, Outlook and Google Calendar. Humble pulls the relevant activity into your timeline, so you can see outside work alongside your tasks, notes and decisions.
Set up one useful view, then let the system become more specific as repeated use shows you what you actually need. Complexity isn't sophistication if nobody trusts or uses it.
0–2 minConnect your calendar or the work tool that matters most. Add the browser extension or Humble in Slack if useful.You'll have: one connected tool to start from.
2–5 minAdd three current priorities: the outcome, why it matters and the accountable owner. Keep it rough enough to start.You'll have: a short, visible list of what actually matters right now.
5–7 minAdd the current quarter as a year-specific tag, such as #Q4-2026, plus only the workstream tags you already need.You'll have: the current quarter in view, without a bare tag to confuse with next year's.
7–10 minChoose what's Now, Next and Later. Put only the immediate commitment in Now.You'll have: a Now list you can trust, instead of a full backlog competing for attention.
That's enough to begin
Create a Humble Teams shared space only when other people need access. Connect more work, people and context as you use Humble.
The end state
You should be able to answer:
What needs attention today?
Are we focused on the few outcomes that matter?
Does important work have a clear owner?
What genuinely needs my judgement?
Which external relationship needs action?
You provide the judgement. Humble reduces the amount of company context your brain has to manually hold, reconnect and reconstruct.
See how it works in Humble
The plays in this guide use features available in Humble today.
See how Humble keeps your priorities, people, decisions and follow-through connected.
This guide is written for ADHD, autistic and other neurodivergent founders and CEOs, based on the work Humble supports today. It draws on the same "Using Humble by role" approach as the guides for chiefs of staff and for executive and personal assistants.
It is a practical guide to one way of working, not an independent or definitive account of neurodivergence or of founding a company. Every founder, team and organisation works differently, so use the parts that are helpful and adapt them to your context.
The guide describes Humble as of September 2026. Some product details may change over time.
Receive new role guides as they are published. Occasional, not frequent.
We will email you a confirmation link first. Nothing is sent until you confirm, and you can unsubscribe at any time. How we use your email.
Want to try it yourself first?
No team rollout and no commitment. Use Humble yourself and see whether having your priorities, people, decisions and follow-through connected makes the work easier to hold.
