We have all been there. You are deep in the flow state, mentally untangling a complex C# architecture or a massive SQL join, and suddenly, a wild Project Manager appears.
"Hey, do you have two minutes for a quick status update on the current sprint?"
For a neurotypical developer, this might be a mild annoyance. They pause, read the data from their short-term working memory, give a percentage, and go back to coding.
For a dyslexic developer, this interruption triggers a complete system crash. My brain doesn't just pause; it drops the entire architectural mental model I was holding. And when I try to answer the PM's question, I experience what I call the "Cold Boot."
If you are a neurodivergent dev (or a PM trying to understand one), here is what is actually happening in those first fuzzy minutes of a status update.
Phase 1: The Fuzzy Re-Render (Loading the Mental Model)
When the PM first asks me what is in flight, my initial answer is usually vague. “Uh, yeah, it’s going okay. I’m working on the backend ticket.”
I am not being evasive, and I haven't forgotten what I'm doing. The problem is that dyslexic brains often struggle with short-term working memory. We don't store project statuses as bulleted lists. We store them as complex, interconnected, holistic systems.
When I get interrupted, that system drops out of my RAM. The first 60 seconds of the conversation is just my brain frantically trying to re-render that massive 3D mental model from scratch. The details are fuzzy because the high-resolution textures haven't loaded yet.
Phase 2: The Associative Flood
But then, as the PM keeps talking and prompting me, something magical happens. They mention a specific API endpoint or a frontend bug, and a single node in my mental web lights up.
Dyslexic brains are elite at associative thinking. We might have a weak working memory, but our associative memory is a superpower.
As soon as that first detail clicks into place, the floodgates open. The fuzzy picture suddenly snaps into hyper-focus. I don't just remember the status of the ticket; I remember the entire ecosystem surrounding it.
Phase 3: The Chain Reaction
This is where the conversation takes a wild turn. Because my brain connects concepts holistically rather than linearly, remembering the current task instantly triggers a chain reaction of dependencies.
I will suddenly stop the PM and say, "Wait, the reason I am on this C# task right now is because I realized yesterday that if we don't refactor this specific service first, the JavaScript update on Thursday is going to break. Which means I actually need to ping DevOps about..."
I didn't plan to give a massive architectural update. But my brain doesn't isolate tasks. It sees the entire domino effect. Once the mental model is fully booted up, I can see exactly how the current ticket impacts a seemingly unrelated task three weeks down the roadmap.
Is this just a "Dyslexic Thing"?
While everyone hates context-switching, this specific "Fuzzy to Flood" pipeline is deeply tied to neurodivergence.
Standard Agile workflows expect linear updates: I did X yesterday, I am doing Y today, Z is my blocker. But highly systemic, dyslexic thinkers don't operate linearly. We operate structurally. We need a minute to rebuild the structure in our heads, but once we do, we can give you a level of interconnected insight that a linear thinker might completely miss.
A Quick Tip for PMs and Devs
For the PMs: If you ask a dyslexic dev for an impromptu update and they look at you blankly or give a fuzzy answer, don't assume they are lost or behind. You just caught them and their RAM has cleared. Give them 60 seconds to talk it out. Let the associative memory boot up. The insights you get will be worth the wait.
For the Devs: Stop feeling guilty for not having an immediate, bulleted list ready to go at all times. Your brain is rendering a 3D map while everyone else is reading a sticky note. It takes a little longer to load, but it's a far more powerful engine.
Top comments (0)