Free — no signup required

Psychological Safety and Disclosure

2 min read

A neurodivergent engineer will only disclose their condition if they believe it is safe to do so. In most organizations, it is not — and they are right to be cautious.

The Disclosure Dilemma

Disclosure carries real risk. An engineer who discloses an ASD diagnosis may find themselves suddenly excluded from high-visibility projects ("we thought the client meetings would be stressful for them"), passed over for promotion ("they struggle with leadership presence"), or treated as fragile rather than capable. These outcomes are common enough that many neurodivergent engineers choose to mask indefinitely rather than disclose.

The result is that the organization never learns what accommodations would unlock the engineer's full performance, and the engineer burns out managing the gap between their natural operating mode and the environment's demands.

Creating Conditions for Safe Disclosure

Normalize the conversation. If neurodiversity is only discussed in the context of HR policies and disability accommodations, it signals that it is a problem to be managed. If it is discussed as a cognitive diversity that the team actively values — in team retrospectives, in engineering blog posts, in how managers talk about different working styles — it signals safety.

Separate disclosure from accommodation. An engineer should not have to formally disclose a diagnosis to receive reasonable adjustments. "I work best with written instructions rather than verbal ones" should be a normal working preference, not a medical accommodation requiring HR paperwork. When common neurodivergent accommodations are available to everyone by default, the cost of disclosure drops.

Model vulnerability from leadership. When senior engineers and managers openly discuss their own working styles, preferences, and challenges — including neurodivergent traits — it signals that the organization values authenticity over performance of neurotypicality.

The Manager's Role

When an engineer does disclose, the manager's job is straightforward:

  1. Thank them for trusting you. Disclosure is a risk. Acknowledge it.
  2. Ask what would help. Do not assume. "What adjustments would make your work easier?" is the right question.
  3. Implement what you can. Not every request will be possible, but most are low-cost.
  4. Keep it confidential. Disclosure to a manager is not permission to inform the team.

This is one of 18 chapters

Every chapter is free — Kubernetes, Terraform, SRE, distributed systems, and more — with fast daily review built in.

Sign up free