Working memory — the brain's ability to hold multiple pieces of information at once — is one of the areas most affected by ADHD.
It's not that you forget. It's that the information never makes it to stable storage in the first place.
Here's the good news: QA has a built-in cure for this.
Learning Objectives
By the end of this lesson, you will be able to:
- Explain how ADHD affects working memory and why this matters in QA
- Use issue trackers (Jira, Trello, Linear) as external cognitive support
- Build a habit of writing information down immediately instead of trusting memory
The ADHD Working Memory Problem
Imagine your brain as a computer.
A neurotypical brain has decent RAM — it can hold a task list, a context, a conversation thread, and a recent finding, all at once.
An ADHD brain has fast but leaky RAM. You can process information quickly, but unless it gets written somewhere, it evaporates. Not because you're careless — because the neurological encoding process works differently.
This creates specific problems in QA:
- 🔴 You found a bug, planned to log it, got interrupted, and forgot
- 🔴 You remember a bug exists but not the exact steps to reproduce it
- 🔴 You're in the middle of a test run and lose track of which tests you've already run
- 🔴 Someone mentions a regression in standup — you know you tested that area but can't recall the result
None of this is laziness. It's neurology.
Pro-tip: The rule for ADHD testers: if it's not in the tracker, it doesn't exist. Log it the moment you see it. Even a 3-word placeholder is better than "I'll come back to this."
Your Tracker Is Your Second Brain
Issue trackers — Jira, Trello, Linear, GitHub Issues — are designed to hold the state your brain can't reliably hold:
| What your brain forgets | What the tracker remembers |
|---|---|
| Reproduction steps | Detailed description field |
| Bug priority | Labels and priority settings |
| What you were working on | Status column (In Progress) |
| Who needs to know about this | Assignees and @mentions |
| What was decided in that meeting | Comments and linked tickets |
In QA, you're not supposed to hold all this in your head. The tracker is the memory. Your job is to put things into it — and trust it when you need things back.
The ADHD Logging Habit
The hardest part: the moment between finding something and logging it. That's where information dies.
Build this habit:
- See something → Open tracker immediately (not "in a minute")
- Write a title first — even if it's just "weird behavior on checkout page"
- Add one screenshot — worth 1000 words and 0 working memory
- Add reproduction steps as bullet points — while you still remember them
- Tag it — feature area, severity, whatever your team uses
Don't try to write a perfect bug report in one sitting. Log fast, refine later.
Pro-tip: Keep a running "Quick Notes" document or tracker column for unprocessed observations. Dump everything in there during testing. Refine into proper tickets during downtime. Never lose a finding to "I'll remember it."
Summary
- ADHD affects working memory — information is processed quickly but doesn't reliably make it to stable storage without external scaffolding
- Issue trackers are cognitive prosthetics: they hold the state your brain can't reliably maintain
- The habit: log immediately, log imperfectly, trust the tracker — never trust your memory alone
🏆 +4 XP for completing this lesson. Quiz time!