Thriving in Practice

Key Principles

1. Accommodations work best when culture backs them up

The research is clear: it is not enough to have an accommodation on paper. Studies consistently show that accommodations improve engagement, productivity, retention, and well-being — but only when they are consistently applied and backed by genuine organizational support. When implementation is inconsistent or leadership is indifferent, the same accommodations show limited impact.

Manager behavior is the single most important variable. Research on autistic employees finds that those supported by managers with emotional intelligence and clear communication showed significantly higher success rates. Trust, transparency, and reduced fear of disclosure all run through that relationship.

2. Design for yourself, not for your diagnosis

A common mistake in accommodation planning is anchoring requests to diagnostic labels — "I have ADHD so I need X." Research shows that sensory preferences and cognitive needs vary significantly within diagnostic groups, not just across them. Two autistic engineers may have opposite sensory profiles: one thrives in stimulating open-plan environments, the other needs acoustic isolation.

Effective accommodations require moving from category to person. The goal is customizable control — over lighting, noise, workspace configuration, schedule flexibility — that you can adjust based on what you need for a given task on a given day.

3. Barriers are design problems, not personal deficits

The social model of disability frames neurodivergence not as a deficit to be fixed but as a mismatch between a person and an environment. Workplaces designed around neurotypical norms — mandatory synchronous meetings, implicit expectations, penalization of direct communication, no written documentation — are themselves the barrier.

This reframing matters practically. It shifts the question from "how do I adapt to fit this environment?" to "what does this environment need to change so that I can work at my best?" That is both a more accurate description of the problem and a more effective basis for making requests.

4. On-call and incident response are high-cost events that need deliberate design

On-call rotations produce significant, documented stress through repeated sleep disruption, alert fatigue, and the cognitive overhead of constant readiness. Cumulative sleep disruption reduces mental clarity and increases the risk of poor decisions during incidents — the moments when the cost of error is highest.

Incident response itself operates under time pressure and elevated stress, which compounds the effects of an already demanding on-call state. For engineers already managing higher baseline stress — whether from masking, sensory demands, or prior burnout — these spikes deserve explicit mitigation, not just endurance.

5. Engineering culture adds a specific layer of pressure

Tech sector workplace culture amplifies masking pressure in a distinctive way. Engineering environments often claim advancement is purely meritocratic while simultaneously requiring cultural fit, informal social bonding, and participation in norms that neurodivergent engineers may not naturally share. This contradiction makes it harder to request accommodations without appearing "less capable" — even when the accommodation would improve performance.

Recognizing this dynamic is not pessimism. It is accurate situational awareness that lets you plan more deliberately: when to advocate, how to frame requests, and where you are likely to find genuine allies.

6. Your accommodations benefit your whole team

The curb-cut effect is the well-documented phenomenon where accessibility features designed for specific users turn out to benefit everyone. Asynchronous communication reduces context-switching costs for all engineers. Written documentation makes onboarding faster for any new hire. Predictable processes reduce cognitive overhead across the team, not just for neurodivergent members.

Universal design principles — designing so that all people can participate without requiring adaptation — apply directly to software team process. Framing your accommodation requests through this lens (what benefits me also benefits the team) is both honest and strategically effective.

---

Annotated Case Study

Setup: Amara is a senior software engineer with ADHD and an anxiety disorder. She joined a mid-size SaaS company eight months ago. She is technically strong but finds the current on-call rotation exhausting, feels a spike of dread whenever she is paged at night, and has been masking her struggles with the team's norm of unstructured verbal standups. Her previous manager was supportive; her new manager is technically competent but communicates through quick Slack messages and rarely follows up in writing. Amara wants to make changes before she hits another burnout cycle.

---

Step 1: Identify the actual friction points, not just the surface symptoms.

Amara's exhaustion is not just about on-call. When she maps it out, she identifies three distinct problems: (a) on-call wakeups disrupt her sleep enough to impair the following day; (b) verbal standups are high-cognitive-overhead for her because unstructured verbal exchange is hard to track in real time; (c) the new manager's communication style leaves her without the written context she needs to feel oriented.

Why this matters: Sensory and cognitive needs vary within diagnostic groups. Requesting "ADHD accommodations" without specificity is less effective than naming what, concretely, needs to change and why.

---

Step 2: Separate what needs a formal accommodation from what can be designed into her own workflow.

Not every friction point requires a formal request. Amara can immediately: mute all non-pager notifications after 9pm, use a written async daily update instead of speaking in standups (framing it as a communication preference rather than a disability disclosure), and use a structured incident checklist she builds herself so that she can execute well even when fatigued.

What needs a conversation: the on-call rotation structure. She wants a predictable shift window (e.g., weekdays only, or a shorter consecutive span) and explicit recovery time built in after consecutive-night incidents. These need manager buy-in.

Why this matters: Accommodations are more effective when management actively supports them. A formal request that the manager does not understand or is ambivalent about will be inconsistently honored under pressure. Amara's goal is to get her manager invested, not just compliant.

---

Step 3: Frame the accommodation request around outcomes, not diagnosis.

Amara drafts a short written proposal for her manager. It does not lead with a diagnosis. It leads with: "I want to make sure I can respond effectively when I'm on call and not carry the cost of that rotation into the rest of my week." She proposes a fixed on-call window, an expectation of a recovery hour (no meetings) after any middle-of-the-night page, and explicit escalation criteria so she does not second-guess every alert.

She sends it in writing before their 1:1 so her manager can read it rather than receive it cold in a verbal conversation.

Why this matters: The social model frames this correctly — she is identifying a design problem in the team's process, not asking for special treatment. The framing also activates the curb-cut logic: a clearer on-call escalation matrix and a recovery norm benefit every engineer on the rotation.

---

Step 4: Evaluate whether the environment will actually support this.

After the conversation, Amara pays attention to whether her manager follows up in writing, remembers the agreement the following month, and whether the team adopts the escalation matrix or it quietly dies. Research is clear that inconsistent application limits impact regardless of what was agreed.

If the environment does not support the accommodation, Amara has two inputs: whether this is a relationship she can invest in repairing, and whether the pattern points to a structural culture problem worth escalating or accepting as a constraint.

Why this matters: Engineering cultures can claim meritocracy while requiring cultural conformity. Amara knowing this in advance helps her avoid personalizing organizational failure.

---

Step 5: Build the sustainability layer that does not depend on anyone else.

In parallel with the accommodation conversation, Amara builds her personal sustainability stack: she identifies her deep-work hours and protects them as her primary coding blocks; she creates a personal incident runbook so her decision-making is scaffolded rather than fully improvised under fatigue; she sets a deliberate offboarding routine at the end of on-call shifts to re-regulate; and she keeps a two-sentence weekly log of what drained her and what restored energy so she can spot early signals of a burnout slope.

Why this matters: Sustainable practice cannot depend entirely on accommodation requests being honored. On-call stress and sleep disruption compound over time — personal scaffolding that operates regardless of team process is a genuine resilience asset.

---

Active Exercise

This exercise builds your personal sustainability plan in three layers. Set aside 45–60 minutes without interruption.

Layer 1: Accommodation audit (15 min)

Write down the three situations at work that cost you the most cognitive or emotional energy. For each one:

• Is the cost coming from the work itself, or from a process design that doesn't fit how you work?
• If it's a process problem, what would a concrete change look like?
• Would that change require someone else's agreement, or can you implement it yourself?

Use the social model as your frame: you are not asking "what's wrong with me?" You are asking "what is this environment asking of me that it doesn't need to?"

Layer 2: On-call and incident response design (15 min)

If you are currently on an on-call rotation, answer the following:

• What is the first sign that an on-call shift is accumulating stress rather than being manageable? (Sleep quality? Irritability the following morning? Avoidance?)
• What is one structural change to your rotation that would meaningfully reduce that accumulation? (Shift length, escalation clarity, recovery time, handover ritual)
• What is one personal practice you can add that does not require anyone else's agreement?

If you are not currently on-call, answer the same questions for a recent incident or high-stakes deployment.

Layer 3: Accommodation request draft (15–20 min)

Pick one accommodation from Layer 1 that requires someone else's agreement. Write a request in the following structure:

1. The outcome you want to achieve (two sentences, no diagnosis required).
2. The specific change you are proposing.
3. How this benefits the team, not just you (activate the curb-cut framing).
4. How you will know it's working (make it evaluable).

You do not need to send this today. The goal is to have it written — a specific, outcome-oriented, team-framed ask — so that when the right moment arrives you are ready.

---

Stretch Challenge

You have mapped your own accommodations and sustainability plan. Now go one level up.

Imagine you are designing the onboarding process for a new neurodivergent engineer joining your team — one whose profile you do not yet know. Using what you know about the curb-cut effect and inclusive process design, draft a one-page onboarding checklist that:

1. Provides written documentation of team norms, communication expectations, and decision-making processes.
2. Identifies an explicit point of contact for questions (an "office buddy" function, not just "ask in Slack").
3. Builds in a structured two-week check-in to surface friction before it becomes attrition.
4. Describes the on-call rotation clearly: what triggers a page, who escalates, and what the recovery expectation is.

Then ask yourself: which of these elements does your current team actually have? Which ones are missing — and what would it take to propose adding them?

Research on inclusive onboarding shows that structured processes improve retention and productivity not just for neurodivergent engineers, but broadly. Your checklist is not charity work. It is good team design.