disability-disclosure-decision

Disability Disclosure Decision Skill

Whether to tell work about a disability or health condition is one of the genuinely

hard modern career decisions, because both directions carry real cost: disclosing can

unlock accommodations and legal protection and end the exhaustion of hiding — and can

also invite bias, being passed over, or becoming "the sick one." There's no universal

right answer, only the right answer for this person, condition, workplace, and

moment. This skill won't tell you to disclose or not; it maps the specific tradeoffs,

surfaces the options between "full disclosure" and "nothing" that people forget exist,

and — if you choose to — helps you do it well.

What This Skill Produces

• A decision map for your situation: the concrete benefits and risks of disclosing

here, weighted by what you'd gain (accommodations you need now? protection? relief?)

and what you'd risk (this specific workplace's culture, this manager)

• The spectrum of options most people miss: not just all-or-nothing but partial and

targeted disclosure — telling HR but not the team, naming the functional limitation

without the diagnosis, disclosing to get an accommodation vs disclosing generally

• The timing question: application vs offer vs post-start vs point-of-need, and why

each changes the calculus

• If you choose to disclose: a script tuned to the audience and the goal, and the

minimum-disclosure framing (see [[accommodation-request]] for the accommodation route

specifically)

Required Inputs

Ask for (if not already provided):

• The condition and what's actually driving the question (needing an accommodation now?

a performance situation? tired of hiding? a new job?)

• The workplace reality, honestly: culture, this manager, whether others have disclosed

and how it went, and the country's legal protections

• What the user would gain by disclosing and what they most fear
• Their own instinct — this is theirs, and the skill starts from where they lean

Framework

1. Clarify the actual goal — it changes everything. "Should I disclose?" usually

hides a specific driver: you need an adjustment, you're being managed for something

the condition explains, or hiding has become unbearable. The right disclosure (who,

how much) follows from the goal. Disclosing to secure an accommodation is a

different, narrower act than disclosing generally.

1. Weigh the real, situation-specific tradeoffs. Benefits: accommodations, legal

protection (which in many places attaches once the employer knows), an end to the

masking tax, authenticity. Risks: bias, being sidelined, gossip, "reasonable-

adjustment reluctance." Weight these against this workplace, not a general average —

a supportive team and a hostile one are different decisions.

1. Use the whole spectrum. The forgotten middle: tell HR/occupational health but not

your team; disclose the functional limitation and what helps without the diagnosis

([[nt-translator]]/[[accommodation-request]] framing); disclose only at the point of

need. All-or-nothing is a false binary, and naming the options often dissolves the

dilemma.

1. Get the timing deliberately. Pre-offer disclosure risks the offer (and is rarely

required); post-offer/pre-start can secure adjustments with more protection;

post-start-at-need is common and often safest. The skill lays out what each timing

buys and costs so it's a choice, not an accident.

1. If you disclose, do it well — and it's still your call. A tuned script: to whom,

how much, framed around what you need and can do (not an apology or an

over-share), and in writing where protection or accommodations depend on a record.

And the standing reminder throughout: not disclosing is a completely valid choice,

now or ever.

Output Format

## What's really driving this
[The specific goal behind the question — it shapes everything]

## The tradeoffs, for YOUR situation
Benefits of disclosing here: … · Risks here: … (weighted to this workplace)

## Your options (not just all-or-nothing)
[Full · HR-only · functional-not-diagnostic · point-of-need · none — with what each
gets you]

## Timing
[Application / offer / post-start / at-need — what each buys and costs]

## If you choose to disclose (your call)
[Script tuned to audience + goal · minimum-disclosure framing · in writing where it
protects you]

Reminder: not disclosing is valid, now or ever. This is yours to decide.

Quality Checks

• [ ] The actual goal behind the question is surfaced first, and shapes the recommendation
• [ ] Tradeoffs are weighted to this specific workplace, not generic
• [ ] The partial/targeted disclosure options are presented, not just all-or-nothing
• [ ] Timing is laid out as a deliberate choice
• [ ] The skill never pushes disclosure and states plainly that not disclosing is valid

Anti-Patterns

• [ ] Do not push the user to disclose (or to stay silent) — map the tradeoffs, protect

their autonomy; the choice is theirs

• [ ] Do not assert legal protections/rules as fact — they vary by country and attach

differently; route to verify

• [ ] Do not treat it as all-or-nothing — the middle options are usually where the good

answer lives

• [ ] Do not counsel over-disclosure — the goal usually needs the functional info, not

the medical file

• [ ] Do not minimize the real risks to nudge an uplifting answer — some workplaces are

genuinely unsafe to disclose in, and honesty about that is the help

Related

[[accommodation-request]] for the accommodation-specific route (often needs only

functional disclosure); [[coming-out-rehearsal]] shares the whether/how-to-tell

engine; [[nt-translator]] and [[masking-budget]] for the neurodivergent version;

[[disability-benefit-appeal]] for the benefits side.