Much collaboration fails before it starts.

Not because people don’t care. Not because the work isn’t good. Because the default assumption built into most working environments is that everyone processes, communicates, and participates the same way. That assumption is wrong, and neurodivergent people pay the highest price for it.

A collaboration manual is one way to change that.

What a Collaboration Manual Is

A manager readme, a user manual, a handbook—the concept has different names but the same core move: write down how you work before people have to figure it out.

The idea has been circulating in tech leadership circles for a while. Paolo Belcastro’s handbook is a clear example of the form: communication preferences, what motivates you, what depletes you, how to give you feedback, what you bring. The TTL newsletter framed it well: a “manager handbook” forms in every team member’s mind over time whether you write it down or not. You’re either giving people accurate information or leaving them to build inaccurate models from incomplete signals.

Writing it down takes the guesswork out. It gives everyone the same information. It accelerates trust.

For neurodivergent people, this practice becomes something larger.

Why Neurodivergent People Need This More—and Why the Framing Has to Change

Neurodivergent people spend extraordinary energy making ourselves legible to systems that were never designed with us in mind. We learn to mask. We learn to manage others’ confusion about why we communicate differently, go quiet, need more time, or can’t handle the open-plan office. We spend cognitive and emotional resources explaining ourselves that could have gone into the work.

A standard manager readme is about preferences. A neurodivergent collaboration manual is about something more structural: the operating conditions under which someone can actually function.

There is a difference between “I prefer async communication” and “real-time verbal demands can make speech inaccessible to me.” There is a difference between “I like deep work blocks” and “my attention is monotropic, and context-switching has real neurological cost.” These aren’t preferences to accommodate. They are properties of how a nervous system works in interaction with an environment.

The frame matters. We are not broken. The systems we’ve been asked to fit into are often poorly designed—for us and, frankly, for many people who’ve been quietly struggling without a name for it. Broken systems, not broken people.

A neurodivergent collaboration manual doesn’t just describe how to work with one person. It names the structural patterns underneath. It makes visible what has been invisible. It does, quietly, what good design does: shifts the question from what is wrong with this person to what is happening in this environment.

What Makes It Neurodivergent

A standard user manual tells you how someone communicates. A neurodivergent collaboration manual goes deeper.

It names nervous system patterns—monotropism, sensory load, processing time—and explains what those patterns mean in practice. It describes the difference between a communication preference and a communication need. It accounts for variability: the fact that capacity isn’t fixed, that Autistic burnout is real and cumulative, that a person who was highly functional last week may need different conditions this week.

It links the personal to the systemic. I need asynchronous communication becomes an entry point to why async matters for neurodivergent people broadly. I experience rejection sensitive dysphoria opens a frame for understanding why vague feedback causes harm, not just discomfort.

This is what the Stimpunks collaboration model is built on. Collaboration doesn’t only depend on tools. It depends on attention, energy, environment, communication rhythms, and shared knowledge systems. The model names those layers explicitly: human nervous systems, communication, collaboration rhythms, participation infrastructure, environments, knowledge systems. A neurodivergent collaboration manual is a personal navigation document for that stack.

Who Benefits

The person who writes one.

Self-reflection required to produce a collaboration manual is not a side effect. It is the point. Understanding your own patterns clearly enough to name them—including the ones that have been pathologized, masked, or never given language—is itself a form of repair.

The people who work with them.

Not because they’re spared the inconvenience of figuring you out, though that too. Because they’re invited into genuine collaboration rather than a performance of normalcy. Because they can stop misreading silence as disengagement, slowness as incompetence, intensity as difficult personality.

And—less visibly—every neurodivergent person who comes after.

When one person names their patterns clearly, it becomes easier for the next person. When one organization learns that intermittent collaboration produces better outcomes than constant availability, that knowledge generalizes. When one team discovers that async-first design helps their neurodivergent members and harms nobody, they’ve done design work that outlasts any individual accommodation.

How to Write Your Own

Start with the patterns that show up most in your working life—not as deficits, but as facts.

What does your attention do? What does your communication need? What depletes you? What replenishes you? What do people consistently misread about you, and what’s actually happening?

Then go one level deeper: what is the structural pattern underneath that experience? Is it monotropism? Demand avoidance? Exposure anxiety? Sensory load? Name it. Link to the research and community knowledge that describes it. You are not alone in it, and you don’t have to explain it from scratch.

Our glossary, pattern library, and experiences exist for exactly this: to give language to patterns that have been unnamed, misnamed, or pathologized. Use them.

Write for your collaborators, but also write for yourself. Be honest about what you bring. Include what you need and what you offer. This isn’t a list of accommodations to be granted. It’s a map to productive collaboration.

Make it a living document. You will learn more about yourself. Your conditions will change. The document should too.

A collaboration manual is useful. A shared collaboration manual is transformative.

Sharing it says: this is how I work, and I am not apologizing for that. It models transparency as a professional practice. It invites reciprocity—other people writing their own, and the gradual emergence of teams that understand each other structurally, not just personally.

You don’t have to share everything. You don’t owe anyone more disclosure than you choose to give. But in contexts where you have the safety and the choice, sharing openly is a form of advocacy. It makes the invisible visible. It makes neurodivergent ways of working legible—not as edge cases, but as design requirements.

The goal isn’t for neurodivergent people to become more readable to neurotypical systems. The goal is for systems to be designed so that different minds can contribute. A collaboration manual is one move in that direction.

Below is mine.

Working With Me: A Neurodivergent Collaboration Manual

A personal handbook and field guide to collaboration across different minds and nervous systems.

This is a user manual. Not a performance review. Not a list of accommodations I need you to tolerate.

It is an act of radical transparency about how I work, why I work that way, and what makes collaboration sustainable for people like me. The patterns described here are not unique to me. They are patterns of neurodivergent life. I’m naming mine so you don’t have to guess—and so the next neurodivergent person you work with doesn’t have to start from scratch explaining themselves.

The frame is Stimpunks Foundation’s: broken systems, not broken people. Everything here reflects that orientation. You’ll find links throughout to our glossary, pattern library, and experiences—because my experience is documented there, and so is the design thinking for how to work well with people like me.

Who this is for

You. Whether you’re a collaborator, a colleague, a co-creator, a funder, or someone who just wants to understand what’s actually happening when I go quiet mid-meeting.

This manual helps you work with me. It also, I hope, helps you work with other neurodivergent people whose manuals you haven’t read yet.

How I Communicate

Text is my native language

I am hyperlexic. I read early, read compulsively, and read deeply. Written language is where I am most fluent and most myself. I process text faster than speech. I respond better to written prompts than verbal ones. I will likely remember what you wrote better than what you said.

If something matters, write it down. Not to paper-trail the relationship—to give my brain the format it works best in.

This also means I often think by writing. A long message isn’t a problem. It’s how I work out what I mean.

I am sometimes unable to speak

I have situational mutism. In certain contexts—crowded rooms, high-stakes conversations, unfamiliar people, moments of overwhelm—speech becomes difficult or impossible. This is not rudeness. It is not disengagement. It is not a sign that something is wrong between us.

What it is: my brain is doing something else, and the resources required for real-time speech production are not currently available.

If I go quiet: wait. Don’t repeat the question. Don’t rephrase it. Don’t increase the pressure. The pressure is part of the problem.

Better: send me a message. Give me time. Let me come back in the medium that works.

Asynchronous communication is not a workaround. It is the default.

Asynchronous communication is when you send a message without expecting an immediate response. This is my preferred mode. It allows me to process what you’ve said, access what I actually think, and give you a substantive response instead of a survival response.

Real-time conversation demands I manage incoming information, process it, formulate a response, and speak—simultaneously, on someone else’s timeline. For many neurodivergent people, that’s not a conversation. That’s a performance.

Async removes the performance demand. What you get instead is actual thinking.

Processing time is not hesitation

When I pause, I am not stalling. I am processing.

Autistic and ADHD people often require more time to process new information, questions, and unexpected changes. The temptation—if I don’t respond immediately—is to repeat the question or rephrase it. Please don’t. Rephrasing resets the clock. Waiting is faster.

A simple “take your time” changes the entire environment.

How My Attention Works

I am monotropic

Monotropism is an attention theory of autism. Monotropic people have an interest-based nervous system. We focus deeply on fewer things at once. We enter attention tunnels. Things outside the tunnel may get missed—not because we don’t care, but because the tunnel is genuinely consuming available cognitive resources.

What this looks like:

Deep, sustained focus on things that matter to me
Difficulty switching between tasks or contexts without transition time
Missing things mentioned in passing while I’m deep in something else
Seemingly disproportionate investment in specific topics or problems

Working well with monotropism means respecting transitions. Give me a heads-up before we change topics. Don’t throw agenda items at me cold. Understand that my intensity isn’t pathology—it’s how I do good work.

I need to move between cave, campfire, and watering hole

Intermittent collaboration is the research-backed sweet spot: group work punctuated by time to think and work alone. It’s not a concession to introverts. It’s optimal design for anyone doing complex work.

I operate in rhythms. Sometimes I need the cave—solitary, low-stimulation, deep work. Sometimes I need the campfire—small group, focused conversation, real exchange. Occasionally I want the watering hole—open, social, ambient.

Don’t mistake cave time for withdrawal. It’s where some of my best work happens. Let me signal where I am.

What Depletes Me

Sensory load is cumulative

Sensory load accumulates. Background noise, visual clutter, multiple simultaneous demands, social pressure, rapid context switching—each one draws from the same pool. The pool doesn’t replenish instantly.

What looks like irritability, shutdown, or “suddenly not being present” is usually the nervous system reaching saturation. It’s not personal. It’s environmental.

Environments built without considering sensory load are the problem. Broken systems, not broken people.

Design implications: reduce unnecessary noise and clutter. Allow flexible lighting when possible. Normalize breaks. Build in recovery time. This helps everyone.

Exposure anxiety makes being seen feel threatening

Exposure anxiety is an acute self-consciousness—a persistent, sometimes overwhelming fear of interaction in which attention from other people can feel threatening. Being watched while I work. Being complimented unexpectedly. Being asked to perform knowledge on the spot.

All of these can trigger a self-protection response that looks, from the outside, like avoidance or shutdown.

It is not avoidance. It is armor.

What helps: low-pressure interaction. Side-by-side collaboration rather than face-to-face scrutiny. Predictable check-ins rather than spontaneous evaluation. Letting me demonstrate competence in my own form, on my own timeline.

Demands can spiral into avoidance

Demand avoidance is driven by anxiety, not defiance. When demands feel coercive, unpredictable, or excessive, the nervous system resists. This isn’t about whether the task is reasonable. It’s about the cumulative weight of obligation, especially when autonomy feels absent.

Low-demand collaboration works. High-demand urgency breaks things.

Frame requests as invitations. Offer choice wherever possible. Don’t manufacture urgency. If something is actually urgent, explain why—the context helps.

Rejection sensitive dysphoria hits hard and fast

Rejection sensitive dysphoria (RSD) is an extreme emotional pain triggered by the perception—real or not—of rejection, criticism, or failing to meet expectations. The key word is perception. It doesn’t require actual rejection. It can hit on the strength of an ambiguous email, a brief silence, an uncharacteristic tone.

The pain is physical. It is wordless. It is not proportional, and it does not respond to logic in the moment.

What helps: directness. If something isn’t working, say so clearly and with care. Ambiguity is the enemy. The anxiety of not knowing is often worse than whatever the actual feedback is.

What doesn’t help: hints, hedging, delayed difficult conversations, or vague positive feedback that doesn’t quite land. I will fill in the gaps with the worst possible interpretation.

If you have a concern, say it. If you don’t have a concern, say that too.

Burnout Is Real. Watch the Signs.

Autistic burnout comes from the accumulated cost of masking, navigating hostile environments, and sustaining demands beyond my capacity. It is not a mood. It is not laziness. It is a neurological depletion that can take weeks or months to recover from.

Signs: I get slower to respond. My writing gets shorter or stops. I become less available. I may disappear from async channels. Tasks that were easy become difficult.

When this happens: reduce demands. Don’t pile on. Don’t interpret absence as disengagement. Let me rest without having to explain myself.

Prevention is better than recovery. This means not accumulating the conditions that lead to burnout in the first place—which is what this entire document is about.

Working Together Well

The short version

Instead of this	Try this
Synchronous-first meetings	Async by default, sync by choice
Rapid-fire verbal questions	Written questions with response time
Repeating yourself when I don’t answer immediately	Waiting, then asking once in writing
Surprise agenda items	Shared agenda in advance
Implicit expectations	Explicit and written
Constant availability expectation	Agreed response windows
Feedback by implication or tone	Direct, written, specific feedback
Marathon sessions	Intermittent collaboration with breaks
Open-plan noise environments	Sensory-managed or remote

Communication channels

Writing first. Email, document comments, shared documents—these are where I work best and respond most fully.

Async by default. Don’t expect immediate responses. Do expect thoughtful ones.

Signal before switching. If we’re moving from one topic or mode to another, give me a beat. Transitions are real costs.

Don’t perform urgency. If it’s actually urgent, say so and say why. If it’s not, let it be async.

Feedback

Give it in writing. Give it specifically. Give it promptly—delay breeds uncertainty, and uncertainty breeds catastrophizing.

I want critical feedback. I can work with it. I cannot work with vague unease or withheld concerns.

If you’re unsure how I’ve received something, ask. I’ll tell you.

Meetings

If there must be a meeting: agenda in advance. Purpose stated clearly. Time-bounded. Not a stand-up. Not a status report masquerading as a conversation.

Prefer: asynchronous document-based collaboration, or small-group conversations with shared context already established in writing.

Video calls: I can do them. They are more draining than async. I may be quieter than expected. That silence is not absence.

What I Bring

Monotropism produces depth. When I’m in an attention tunnel on something that matters, the quality of attention is extraordinary.

Hyperlexia means I read everything and remember it. I am a research machine and a synthesizer.

Pattern recognition across large bodies of text is a genuine cognitive gift. I will find the connection you missed. I will find the citation that changes the argument.

My investment in equity, language, and epistemic justice is not performative. It is structural to how I think. It will show up in everything I touch.

I am at my best when I have autonomy, time, low ambient pressure, and a shared frame of purpose. Under those conditions, I produce work I’m proud of and you’ll be glad you have.

A Note on This Document

This manual is both personal and structural. The patterns described here—monotropism, exposure anxiety, processing time, demand avoidance, RSD—are documented neurodivergent experiences shared by many people. The collaboration design this document implies is better for neurodivergent people and no worse for anyone else.

Neurodivergent collaboration design is not special accommodation. It is good design.

The Neurodivergent Collaboration Model at Stimpunks describes a full stack: human nervous systems, communication, collaboration rhythms, participation infrastructure, environments, and knowledge systems. This manual maps to that stack. Follow those links if you want the broader frame.

The pattern library has design implications for each pattern. If you work with neurodivergent people, read it.

This is a living document. It will change as I understand myself better, as the patterns develop, and as the collaboration does.

Last updated: 2026

Write a Neurodivergent Collaboration Manual

▶ Table of Contents