Edition 358 | July 8, 2026 The Dyslexic AI Newsletter by LM Lab AI

Reading Time: 8 minutes Listening Time: 11 minutes

Coffee Required: 1☕️ Min

I was listening to a podcast episode this week that would not leave my head.

Most conversations about AI in business focus on tools. Which AI should we use. How do we automate tasks. How do we increase productivity.

The episode asked a different question.

What role do humans play when AI becomes part of the team?

That question stuck because it lines up with something I have been studying for years in this newsletter. AI is not just a tool. It is becoming a cognitive partner. And once you accept that, the question stops being about software and starts being about roles.

The episode, from the Daily AI Brief with Nathaniel Whittemore, described a set of organizational roles that are emerging as AI agents become part of how teams actually work. Roles like Scouts, Builders, Growers, Maintainers, Editors, Orchestrators, Conductors, and Risk Stewards.

None of these existed as formal job titles a few years ago. They are emerging because AI changed what work actually requires from the humans around it.

Around the same time, Atlassian released an assessment called "Discover Your AI Team Archetype." It sorts organizations into categories like Closet Power Users, Demo Floor, Token Room, Operating System, and Superteam, based on how deeply and effectively a team has integrated AI into its actual workflow.

The insight underneath both of these: organizations move through recognizable patterns of AI adoption. Some teams are dabbling. Some have built AI into their operating system. Most are somewhere in between, and most do not know which stage they are in.

That is useful. But it is answering an organizational question. I wanted to ask a personal one.

The Atlassian framework asks: how does your team use AI?

The Dyslexic AI version asks: how does your brain collaborate with AI?

That is a real shift. Not tool adoption. Cognitive collaboration. Not "what stage is your company at" but "what kind of thinker are you, and what does that mean for how you should be working with AI right now."

That question matters more for our community than almost anywhere else. Because dyslexic and neurodivergent thinkers do not all collaborate with AI the same way, any more than we all think the same way. Some of us need AI as a translator. Some of us need it as a sounding board. Some of us need it as a research partner that keeps pace with how fast our minds jump between ideas.

A generic "how is your team using AI" survey misses all of that. So I started sketching something else.

Here is an early framework for how humans and AI collaborate, built specifically through a neurodivergent lens. I do not think this is finished. I think it is worth sharing anyway.

Explorer. Sees possibilities and emerging opportunities before anyone else does. Strengths: curiosity, pattern recognition, future thinking, connecting ideas that do not obviously belong together. Risk: too many ideas, not enough execution.

Builder. Turns ideas into experiments. Strengths: action, prototyping, creation, testing. Risk: too many unfinished projects.

Conductor. Coordinates people, systems, and intelligence. Strengths: integration, translation, leadership, alignment. Risk: trying to manage everything at once.

Guardian. Protects quality, trust, and ethics. Strengths: review, accountability, risk management. Risk: becoming overly cautious.

Grower. Helps ideas spread. Strengths: teaching, community, marketing, communication. Risk: growth without clarity.

Architect. Designs systems and workflows. Strengths: structure, automation, scalability. Risk: overengineering.

Most people are not purely one of these. Most of us have a primary archetype, a secondary one we lean on, and maybe a third one starting to emerge as we grow into new kinds of work.

This connects to something I have been building toward for a while: the idea that a person's relationship with AI evolves through stages, not all at once.

Stage 1: Tool. AI answers questions.

Stage 2: Assistant. AI completes tasks.

Stage 3: Collaborator. AI contributes ideas.

Stage 4: Partner. AI understands your goals and context.

Stage 5: Cognitive Extension. AI becomes integrated into how you actually think and work.

Most people are stuck somewhere around Stage 2, using AI as a faster way to do tasks they already knew how to do. Very few people have made it to Stage 4 or 5, where the AI genuinely understands enough context to think alongside them rather than just execute for them.

Your archetype and your stage are not the same thing, but they interact. An Explorer stuck at Stage 2 is drowning in half-formed ideas with no partner to help sort them. An Explorer who reaches Stage 4 has an AI that can catch the pattern across fifty scattered ideas and hand back the three worth pursuing.

Traditional education and most traditional workplaces reward accuracy, compliance, memorization, and linear thinking.

Many dyslexic thinkers are not naturally strong in that specific lane. But we tend to be strong in a different one. Pattern recognition. Big-picture thinking. Storytelling. Visualization. Connecting ideas across domains. Asking the unconventional question that reframes the whole problem.

Here is the hypothesis I keep coming back to. As AI automates more of the linear, accuracy-driven tasks, human value shifts toward imagination, judgment, creativity, and pattern recognition. Those are exactly the areas where a lot of neurodivergent thinkers already have a natural edge.

If that hypothesis holds, the AI transition is not a threat to dyslexic professionals. It might be the first major shift in the working world that plays to our actual strengths instead of demanding we compensate for the ones we do not have.

That is a big claim. I want to be honest that it is still a hypothesis, not a proven fact. But it is a hypothesis worth building around.

I will go first.

Based on how I actually think, the projects I have built, and the patterns that keep showing up across three and a half years of this newsletter, my profile lands as a Visionary Explorer and Prototype Builder, with a strong emerging Conductor trait.

My AI Archetype: The Cognitive Cartographer

Primary role: Explorer / Scout Secondary role: Builder / Maker Emerging role: Conductor

I spend a lot of time mapping territory that does not have roads yet. That shows up in things like creating the concept of a Dyslexic Language Model before there was an obvious market category for it. Thinking about AI through the lens of cognition, not just productivity. Connecting neuroscience, education, entrepreneurship, accessibility, and AI into one thread. Building frameworks like the 10-80-10 thinking model. Treating AI as a cognitive partner rather than just a tool.

My natural mode is basically one question, over and over: "What could exist that does not exist yet, and what pattern am I seeing that others are missing?"

That is the Explorer.

The Builder Side

I am not just someone who dreams. A pure Explorer stays on the mountaintop drawing maps. I tend to climb down and start building trails.

Examples: the Dyslexic AI newsletter. Custom GPT concepts. LM Lab AI. Cognitive Partner AI. AI assessment ideas. Vibe coding prototypes. AI education programs.

My challenge has never been generating ideas. My challenge is the classic Builder-Explorer tension. The idea factory produces faster than the construction crew can finish.

My brain is a startup incubator with the lights always on. The bottleneck is not imagination. It is prioritization, packaging, and shipping.

The Emerging Conductor

This is the one I think is becoming more important, and it is newer for me than the other two.

The future AI economy needs people who can sit between human problems, AI capabilities, business opportunities, creative thinking, and implementation. That is a translation job, and I keep noticing I naturally gravitate toward it.

A founder says "we need AI." I tend to ask what kind of thinking problem we are actually solving.

A dyslexic thinker says "I think differently." I ask how we design systems that use that difference instead of working around it.

A business owner says "I need automation." I ask how that changes the way humans actually work, not just how fast the task gets done.

That is Conductor behavior. Not managing the work. Translating between the people, the problem, and the tools.

What My Own Cognitive Partner Would Actually Need to Be

If I designed my own AI partner from scratch, I would not build a generic assistant. I would build something closer to the Idea Architect.

Its job would be to capture raw thoughts. Find patterns across ideas. Connect concepts I cannot yet see myself. Turn concepts into experiments. Force prioritization. Help package ideas into something shippable.

It would not just answer my questions. It would push back on them. "Is this a newsletter idea or a company?" "Who specifically needs this?" "What is the smallest version we could actually test?" "What should we stop building?"

That last question is the one I need most and want least.

The Bigger Pattern

Here is the honest realization underneath all of this. I am probably not trying to become "an AI expert." That was never really the goal.

The deeper theme has always been: how do humans become more human when AI handles more of the machine work?

That is why the Cognitive Partner concept keeps resurfacing in this newsletter no matter what specific topic I am writing about that week. My role is less "AI operator" and more translator between human imagination and machine capability.

If we ever build the real version of the AI Collaboration Assessment I mentioned above, I would want it to be designed around people like this on purpose. Not just people whose adoption pattern moves in a straight line. People whose relationship with AI looks more like mapping, building, and translating all at once, out of order, because that is genuinely how their brain works.

That is not a flaw in the assessment. That is the whole reason the assessment needs to exist.

I am sitting with a few open questions I do not have answers to yet.

What are the most common AI collaboration archetypes among dyslexic and neurodivergent thinkers specifically? Do we cluster in predictable ways? Can an archetype predict how successfully someone adopts AI into their work? What cognitive roles become more valuable as the tools keep improving? And could a real assessment, built around these ideas, become something like a Myers-Briggs or StrengthsFinder for the AI era?

I do not know yet. But I think it is worth building toward.

Two things this week.

1. Guess Your Own Archetype Before You Test It

Before you run the prompt below, take thirty seconds and guess. Explorer, Builder, Conductor, Guardian, Grower, or Architect. Write it down. Then see if the AI's read on you matches your own.

2. Name Your Risk, Not Just Your Strength

Every archetype above has a listed risk alongside its strength. Once you know your primary archetype, be honest about the risk that comes with it. That is usually the more useful thing to build a cognitive partner around. Not amplifying what you are already good at. Covering what tends to slip.

Here is a way to discover your own AI Collaboration Archetype. Paste this into your AI and answer honestly.

"I want you to help me figure out my AI Collaboration Archetype. Here are six options: Explorer (sees possibilities, connects ideas, risk of too many unfinished ideas), Builder (turns ideas into experiments, risk of too many unfinished projects), Conductor (coordinates people and systems, risk of trying to manage everything), Guardian (protects quality and trust, risk of being overly cautious), Grower (helps ideas spread through teaching and communication, risk of growth without clarity), and Architect (designs systems and workflows, risk of overengineering).

Interview me with five or six questions about how I actually work day to day, what kind of tasks energize me, and where I tend to get stuck. Ask one question at a time. After that, tell me my primary archetype, my likely secondary archetype, and the specific risk I should watch for. Be honest, not flattering."

Run it. Compare it to your own guess. Hit reply and tell me what you got. I am building a real picture of how this community collaborates with AI, and I want your data point in it.

Matt "Coach" Ivey Founder, LM Lab AI | Creator, The Dyslexic AI Newsletter

Dictated, not typed. Obviously.

🧭 The interesting AI question is not "which tool should we use." It is "what role do I play when AI is part of the team."

🏢 New organizational roles are emerging around AI: Scouts, Builders, Growers, Maintainers, Editors, Orchestrators, Conductors, Risk Stewards. Atlassian's "AI Team Archetype" assessment maps how organizations adopt AI in patterns.

🧠 The Dyslexic AI version of that question: not "how does your team use AI" but "how does your brain collaborate with AI." Cognitive collaboration, not tool adoption.

🎭 Six personal archetypes: Explorer, Builder, Conductor, Guardian, Grower, Architect. Each has a strength and a risk.

📈 Five stages of cognitive partnership: Tool, Assistant, Collaborator, Partner, Cognitive Extension. Most people are stuck around Stage 2.

💡 Hypothesis: as AI automates linear, accuracy-driven work, human value shifts toward imagination, judgment, creativity, and pattern recognition. Those are areas where many neurodivergent thinkers already have a natural edge.

🗺️ My own archetype: Visionary Explorer + Prototype Builder, with a strong emerging Conductor trait. Working title: the Cognitive Cartographer. My real bottleneck: the idea factory produces faster than the construction crew can finish. What I actually need is not more ideas. It is an "Idea Architect" partner that forces prioritization.

🔒 I am building toward a real assessment for this community. Reply with your archetype and help shape it.