When Your Employee Discloses: A Manager's Guide

The first sentence is the one that matters. Three responses that signal the conversation can keep going:

• "Thank you for telling me. What would be most useful to talk about right now, and what should we save for a follow-up when we both have time?"
• "I want to make sure I respond to this well. Can I ask a few clarifying questions, and then come back to you in a day with a follow-up?"
• "I appreciate you trusting me with this. I don't have a good script for this conversation yet — I'd rather take a beat and come back than improvise badly. Is tomorrow okay?"

Each one does three things at once: thanks the employee, names that the manager wants to do this well rather than perform doing it well, and creates space to follow up rather than over-respond on the spot.

What to avoid in the first sentence:

• "I had no idea — you're so high-functioning." The phrase "high-functioning" carries a long history in disability community discourse and is widely considered outdated and othering. Even if meant as a compliment, it lands as a signal that the manager is now reading every behavior through a deficit lens.
• "Let's not make a big deal of it." Reads as "I'd prefer this didn't change anything between us" — which the employee correctly translates as "I'd prefer you not bring this up again."
• "We'll set up accommodations right away." Promises a process the manager doesn't fully control, and skips the step of asking the employee what they actually want.

What changes structurally — and what doesn't.

The most effective changes in the first 30 days are usually invisible to the rest of the team. They're framed as workflow norms, not as accommodations. The employee gets what they need; nobody else has any reason to ask why.

Written meeting follow-ups as a team-wide practice. Many neurodivergent employees process verbal information more slowly than verbal-fluency-biased meeting culture allows. Adopting a team-wide norm of written follow-ups after every meeting addresses this without singling anyone out. The neurodivergent employee benefits; everyone else benefits too.

Calendar protection for focus time. A two-hour block of protected calendar time, defended explicitly as "deep work" time, is one of the most effective accommodations there is — and it works as a team-wide practice rather than an individual exception. Several productivity-research-backed companies use this format universally.

Async-first communication norms for sensitive feedback. Performance feedback that arrives in real time, in a synchronous meeting, is harder to process well — and not just for neurodivergent employees. Shifting feedback toward written first, with synchronous follow-up after the employee has had time to read and respond, is a universal-design improvement that disproportionately benefits neurodivergent reports.

Explicit role expectations and success criteria. Many neurodivergent employees are diagnosed by the gap between their performance and their inferences about what's expected. Make the inferences unnecessary by writing out the role's success criteria explicitly — what does excellent performance look like in this job, in concrete terms? — and revisiting the document quarterly.

What does not change: the work. The performance bar. The deadlines. Lower bars are not what neurodivergent employees are asking for; they're asking for the conditions under which they can meet the bar that already exists.

The four most common manager failure modes. Each is well-intentioned. Each costs the employee.

• The "let me carry this for you" failure. Overcompensating by removing responsibility. Reassigning the high-visibility project to a peer "to take pressure off." Quietly excluding the employee from stretch opportunities "until things settle." These read as protection; they land as career-ceiling. Don't shrink the role. Adjust the conditions of the role.
• The "let's keep this between us" failure. Implicit signal that the disclosure is a secret, which signals that disclosure is shameful, which signals that the manager will treat any future reference to it the same way. Confidentiality is the employee's choice, not a default the manager imposes. Ask: "How would you like me to handle this if it comes up in a context where I think it's relevant?"
• The "I'll just go to HR for you" failure. Escalating without consent. The employee disclosed to the manager, not to the company. The manager's job is to handle what's handlable at the manager-relationship level and to involve HR with the employee's explicit knowledge of what gets shared and why.
• The "I'm going to share this with the team for awareness" failure. Disclosing on the employee's behalf. The employee chose to disclose to one person. They did not authorize broadcast. Even with the best of intentions, broadcasting is not the manager's call to make.

Frequently asked questions

What if the employee discloses something I can't share but a peer needs to know?

Default: you don't share without explicit consent. The narrow exception is when a specific accommodation requires another person's awareness to function — for example, a teammate who runs a recurring meeting needs to know the employee is requesting written meeting notes. In that case, ask the employee how to frame the request. The phrasing usually doesn't require disclosing the underlying condition: "we're moving toward written meeting notes for the team" is a legitimate practice change that doesn't require naming who requested it.

Do I need to document the disclosure for compliance purposes?

It depends on what was said and what triggered the conversation. If the employee made a specific accommodation request, the request should be documented and routed through HR per your company's interactive-process policy under the ADA. If the employee shared context without a specific request, no formal documentation is required — but a brief private note for your own reference is reasonable. The legal floor is set by ADA.gov and your company's policy. Confirm with HR if you're uncertain.

What if I don't believe the employee's disclosure is accurate?

It's not your job to evaluate the diagnosis. It's your job to manage the work and respond to specific accommodation requests through the proper channel. The ADA's interactive process is designed to handle this exact scenario: when an accommodation is requested, the employer can request reasonable medical documentation to support the need. That documentation request goes through HR, not the manager. Your role is to keep the work conversation grounded in performance and to route the formal request without judgment.

Should I tell my own manager about my employee's disclosure?

Default no. The disclosure was to you, not to your management chain. Exceptions are narrow: when a specific accommodation requires upward approval (for example, a budget allocation or a policy deviation), or when your own manager is also responsible for performance evaluation of the employee and the disclosure is materially relevant to a current performance conversation. Even then, share only what's required to handle the specific request, and tell your employee in advance that you're doing so.

What if my employee discloses on day 47, after I've already given them a critical performance review?

Don't retroactively change the review. Do change what comes next. Re-read the feedback themes through the lens of the new context. Ask the employee whether any of the feedback is downstream of an unaccommodated condition. If so, adjust the development plan to focus on accommodations that address the underlying issue, rather than performance pressure that won't fix it. The previous review stays on the record; the next one is yours to shape.

How do I know if my response was actually good?

The signal is a few weeks later, when the employee comes to you with a follow-up question, not just a one-time disclosure. That's the relationship continuing. If the disclosure ended the conversation — if the employee never raises anything related again, even when something work-relevant comes up — your response probably closed a door. The repair is usually a low-stakes check-in: "I've been thinking about our conversation a few weeks ago. Is there anything I should be doing differently in our 1:1s that I'm not?"