GIF created by Jen Benford, The Divergent Talent Alchemist

Collaborators’ Note

This essay is a work of fiction grounded in the collaborators’ lived realities. Lula is a composite character. She is not any one person, and the workplace she moves through is not any one company. Her arc is built from experiences we’ve lived, witnessed, and heard repeated across the neurocomplex (neurodivergent) community with enough consistency to form a recognizable pattern. The names belong to Jen’s pets. The organizational dynamics depicted are real — and they are a real problem.

Chris Stephens, CPA, writes primarily about the late-diagnosed neurocomplex experience at work, in parenting, and in life. Jen Benford helps neurodivergent and multipassionate people stop apologizing for their range and build a life — work, voice, identity — on their own terms.

Between us, we’ve seen this story from enough angles to know Lula is not an anomaly. She’s a pattern we’ve watched play out. And patterns can be changed.

If you recognize your organization on these pages, we hope you’ll sit with that discomfort long enough to act. If you recognize yourself in Lula, we wrote the last section for you.

Content note: This piece names workplace harm, retaliation, and gaslighting. Take care of yourself as you read.

What you’ll find in this piece

We shaped five composite scenes to trace how these patterns unfold — from the first quiet report to the quiet exit. Between the scenes, we’ve layered in the diagnostic frame: what the nervous system is doing when the workplace stops making sense, who gets to define reality, and what genuine change would actually take.

• Scene 1 — The First Report. What happens when raising a concern becomes the concern.

• Scene 2 — The Documentation. How diligence gets rebranded as pathology.

• Scene 3 — The Product. When the concern is about the work itself, not the people.

• Scene 4 — The Role Reassignment. How retaliation dresses itself up as opportunity.

• Scene 5 — The Diagnosis. The moment the system says the quiet part out loud.

We close with what a system committed to actually not producing this outcome could look like — and a section for Lula, if you happen to be her.

A quick word on the word. Gaslighting is often used casually, but the American Psychological Association defines it more precisely: manipulation that leads someone to doubt their perceptions, experiences, or understanding of events. It’s a pattern, not an incident. That distinction matters here. Lula’s story isn’t about one conversation. It’s about what happens when the pattern becomes the environment.

Lula goes to work every day expecting one thing above everything else: to be safe.

Just safe. Safe enough to exist as herself without being mocked. Safe enough that if anyone crosses a line, someone with the power to do so will act. Safe enough that the people responsible for the environment she works in take that responsibility seriously.

That’s not a high bar. It’s the floor.

This is the story of what happened when the floor gave way. It’s also the story of what that floor is made of, who builds it, who gets to stand on it, and what it costs when organizations decide it isn’t worth maintaining.

Scene 1: The First Conversation with HR

Lula: “Mylo keeps imitating how I stim during meetings. It’s making it hard to focus.”

HR Partner: “Are you sure he’s not just being friendly? Try not to read so much into things.”

Lula walked into an HR conversation; she wasn’t filing a formal complaint. She was asking her employer to do its job. She wanted Mylo to stop. She wanted someone to talk to him, make it clear that mocking how a colleague’s nervous system regulates itself isn’t acceptable, and ensure she could sit in a meeting and participate fully without bracing for what he might do next. She wanted to know her employer had her back.

According to Gallup, research shows that neurodiverse individuals offer unique abilities in creativity, innovation, and complex problem-solving — skills organizations often say they want. But Gallup also finds that 37% of employed neurodiverse individuals choose not to share their condition with coworkers, feeling that peers and leaders will stigmatize their natural ways of thinking, feeling, and behaving. Further, 46% don’t ask for accommodations during the application process, feeling it would be a disadvantage and might get them labeled “high maintenance,” “difficult,” or “needy.” And while 45% say they told their manager or supervisor about their neurodivergence, many still mask at work.

Deloitte’s recent global disability inclusion research adds another layer: even in workplaces that publicly welcome neurodivergent employees, only about 3–4% self-identify. Deloitte’s 2024 survey found that 41% of respondents with disabilities, chronic health conditions, or neurodivergence had experienced workplace discrimination — most commonly through microaggressions, bullying, or harassment.

Masking isn’t a preference. It’s a protective response. A 2023 study in PLOS ONE of 472 adults found that autistic, non-autistic neurodivergent, and neurotypical workers alike described workplace masking as an adaptive response to socially grounded workplace challenges — usually employed as a strategy to safeguard against negative social and employment outcomes. Which is a clinical way of saying: people hide because they’ve learned it’s not safe not to.

What Lula shouldn’t have had to consider was whether to suppress her stims — to hold her body still when it needs to move. Some might call it masking, but stimming isn’t a behavior to be managed or hidden. It’s how some nervous systems regulate themselves. Suppressing it doesn’t just cost Lula her social comfort. It costs her focus and can tip her into dysregulation at exactly the moments when she needs to be most present.

The fact that Mylo’s mockery may have forced Lula to choose between showing up without the effort of suppression and protecting herself from ridicule is its own injury, compounding with every meeting, every room, every moment when she has to calculate the cost of being visible. That calculation is exhausting, and it should not be Lula’s to carry.

Lula wanted sensitivity training, accountability, and the basic assurance that she deserved to come to work and be a whole human being. Each of those things was within the organization’s power to provide. None of them required an investigation, a formal process, or anything more than taking her seriously.

Instead, she was asked if she was sure.

That question did something specific. It didn’t merely fail to address Mylo’s behavior. It shifted the burden of proof to Lula, cast her perception as potentially unreliable, and signaled that the cost of raising this concern would fall on her — not on him, and not on the organization that employs them both. All in two sentences.

This is the ground level of psychological safety, and the employer failed to maintain it.

When psychological safety exists, the American Psychological Association describes it as an environment in which team members can take risks, admit and discuss mistakes, openly address problems and tough issues, seek help and feedback, and trust that they are a valued member of the team.

If you’re a workplace that says you care about psychological safety and true belonging, this is one of the uncomplicated routes HR could have recommended — and the company could have taken — while handling the situation with care.

Talking to Lula and understanding her needs is a simple step. Then talking to Mylo separately, with genuine curiosity rather than a predetermined conclusion. Too often, HR representatives skip the basic due diligence of hearing both sides — because HR is often undertrained and laser-focused on risk management instead of the actual human experience at work. Mylo’s behavior needs to stop, regardless of what this conversation uncovers. It may not be illegal to be a jerk at work but dismissing behaviors (especially repeatedly) that harm someone’s ability to function, focus, and feel safe isn’t just unfair. It’s a choice, and it has real consequences.

Why it happened is relevant to what comes next. If it came from thoughtlessness, that gets addressed differently than if it came from something else. As people and culture leaders, we have to look at intent where possible, instead of automatically backing the more senior person or walking into conversations with our minds already made up because of implicit biases about a person or a community.

Let’s just say it: 1 in 5 people are neurodivergent, making up around 20% of the population. And if Mylo is also neurocomplex, that introduces a layer worth understanding — not as an excuse, but as context that shapes how the conversation happens and what support might look like for all parties.

These situations are nuanced, and there are many different scenarios in the people relations space. Sometimes the person sharing the information with HR or their manager isn’t comfortable being in the same room with the person who is making them feel unsafe. A best practice is that bringing them into the same room happens only if both parties feel safe doing so, and only after both have spoken with HR or the designated managerial stakeholder separately. If the conversation reveals a gap in awareness that others on the team might share, that’s information worth acting on — through broader sensitivity training or resources that teach people with different brain and nervous system wiring how to work together well. But none of that replaces individual accountability, and none of it changes the fact that Lula’s experience was real and deserved to be taken seriously from the first sentence she spoke.

The harder truth is that a genuinely inclusive environment reduces the likelihood that this happens in the first place. Explicit policies, leadership that models the behavior it expects, and a culture where difference isn’t treated as something to manage or poke fun at — these are what make the floor solid before anyone has to report that it isn’t.

What the Nervous System Already Knows

Every person in a workplace reads their environment, whether they know it or not. Is what I’m seeing real? Does what I hear match what’s actually happening? Can I trust the feedback I get?

People don’t typically sit down and ask themselves these questions. They run beneath the surface, processed by the nervous system the same way it monitors the temperature of a room or the pitch in someone’s voice — automatically, and without permission. Staying oriented isn’t a choice. It’s a survival function.

​Orientation as a survival function isn't learned. It's the baseline condition the nervous system is always trying to maintain. This is consistent across multiple research frameworks — Porges on neuroception, LeDoux on nonconscious threat detection, and Barrett on predictive processing — each arriving from different directions at the same core finding: the nervous system continuously and automatically scans the environment for cues of safety or threat, below the level of conscious awareness. The capacity is innate, not acquired. What shifts over time is what the nervous system learns to treat as a threat, and how we respond when orientation breaks down.

For Lula, that function had worked exactly as intended. She saw something real. She reported it through the “proper channels.” The problem wasn’t her perception. The problem was that the pathway designed to receive this kind of information responded by questioning her ability to perceive.

When an institution consistently dismisses valid concerns, it corrupts one of the nervous system’s most important functions: a reliable signal from the outside world. The employee’s careful observations — what they’ve seen, heard, and experienced firsthand — are treated as unreliable. Because the institution holds structural authority over what counts as true, its version tends to win regardless of accuracy. And the person who raised the concern walks away not only unheard, but less certain of their own ground.

And it’s almost as if the system is doing what it was designed to do. Is the system trying to gaslight the reporter into believing they are the problem? For having human emotions? For speaking up when someone or something makes them uncomfortable — probably exactly the way policy and canned trainings told them to?

Most people know it as dread. Or as exhaustion that arrives before the workday begins. Or as a specific form of hypervigilance that makes a calendar notification feel like a threat. It’s often a sign that the environment is broken, but if the environment can’t process that information, it gets routinely framed as the employee’s fault. Institutions that gaslight — whether by design or default — count on their employees to misinterpret the strain, to see it as personal failure rather than as evidence that something outside them has gone wrong.

Lula didn’t misread it. She documented it. And then she became “the problem.”

Scene 2: The Documentation

Lula: “I have fourteen incidents documented over six weeks. Here’s the document.”

Manager: “Wow. You really fixate on things, don’t you?”

Fourteen incidents. Six weeks. A spreadsheet.

In any organization that truly values the human experience, a situation like this should be taken seriously. This is exactly what someone is supposed to do when a concern goes unaddressed: document it. Create a record. Demonstrate that this isn’t a one-time misunderstanding but a pattern, with dates, details, and frequency. Lula did everything the way she was taught.

The response she received reframed her diligence as dysfunction. The same thoroughness that would have been praised in any other context became evidence of a “personality problem” — a workplace euphemism for someone who recognizes patterns and speaks up. In doing so, the organization discredited the documentation without engaging with a single line of it.

By the time Lula arrived with a spreadsheet, the organization had already failed her once by not taking her feedback seriously. The documentation existed because the first conversation had yielded nothing. That context is key. A manager receiving fourteen incidents over six weeks isn’t receiving a first report. They’re receiving evidence that a prior concern was dismissed, that the behavior persisted, and that Lula had to build her own case because the system did not take her concerns into consideration in this example.

The human response at this stage is harder than in Scene 1, because trust has already been damaged. But it isn’t impossible. The organization could still take the documentation seriously — reading it as the detailed, careful record it is, rather than as a symptom of the person who compiled it. And sadly, this story seems to be true for many people, who are positioned as liabilities to an organization instead of human beings with genuine concerns.

Reopen the conversation with Mylo, bringing the full weight of the record to bear. Acknowledge, at least internally, that the organization’s earlier response made this moment harder than it needed to be. But do organizations take accountability? Or do they shift blame to the person who is less senior on the invisible (or visible) org chart within the institution?

In an environment where inclusive behavior is modeled from the top and codified with teeth in policy, a manager receiving this documentation would feel the weight of institutional expectation to do the right thing. In an environment where it isn’t, the manager’s instinct is to protect the status quo. That instinct is what labeled Lula’s diligence as fixation rather than what it actually was: a record of her own real experience.

This is the move we often see. Use the person’s most reliable tool for establishing reality to show they can’t be trusted to handle it. It works because the institution has the authority to make that reframing stick, at least within its own walls. Linguists have been documenting this dynamic for decades. In critical discourse analysis — the field founded by Norman Fairclough — institutions don’t just describe reality; they possess the discursive authority to shape which version of events reads as common sense and which reads as fringe.

The result is a loss of orientation and identity. Lula can no longer fully trust her judgment. She begins questioning not only the specific incident but her overall ability to perceive accurately. Over time, the doubt stops being a response to what’s happening around her. It becomes the voice she hears first.

Underneath it all runs a current that rarely gets named: Lula needs this job. Not as an abstraction, but concretely. She needs the income, the benefits, the professional continuity. The organization knows this, even if no one says it out loud. That knowledge shapes every calculation she makes about how hard to push, how much to document, how loudly to object. It is no coincidence that the people with the least institutional power are often the ones with the least financial cushion to absorb the cost of standing up for themselves.

Psychological safety isn’t a value posted on a wall. It’s built or eroded in moments like this, consistently, over time. By this point, Lula had raised one concern through the proper channels and left the conversation without it being addressed. The organization has now had two opportunities to address Lula’s concerns. It has not acted on either one in this scenario.

To any organization reading this: this is a real problem. Whether deliberate or not, when you take someone who was functioning well, seeing clearly, and advocating for herself through the exact channels you told her to use, and you make her doubt herself — that’s not a neutral outcome. That’s harm.

For context, here is Lula:

Who Gets to Define Reality

Every workplace keeps some things visible and others private. Some employees are rewarded, others punished. Some voices carry weight, others don’t. Power shapes all of it, and it is never evenly distributed.

Power determines who defines reality. And the people in power almost always dictate the paper trail of what happens in the organization, regardless of the truth.

In a healthy system, reality is established through evidence, dialogue, and accountability that flow in every direction — not just downward. Feedback flows up, across, and back again. Everyone is accountable to everyone else. In a gaslighting system, reality belongs to whoever has the most authority to impose their interpretation. That authority rarely gets questioned — not because people don’t see the problem, but because they’ve already seen what happens to those who try to shed light on it.

These are often the same organizations with open-door policies and annual engagement surveys. The gap between what they say they want and what happens to the person who takes them at their word is where gaslighting thrives.

Scene 3: The Product

Lula: “Has anyone actually validated this with the users we’re pitching it to? Because I don’t think it does what we’re telling them it does.”

Director of Sales: “Let’s not create problems where there aren’t any.”

This is a different kind of concern. Lula isn’t reporting on how she was treated. She’s reporting what she can observe about the organization’s product — the one they’re actively selling as a primary revenue source. The product is being positioned for a market it wasn’t originally built for. Lula has looked at it closely enough to know there’s a mismatch between what’s being pitched and what the product actually does, and as far as she can tell, no one has stress-tested it with the audience they’re now selling to.

She raises it the same way she has raised everything else: through the proper channel, with the right person, in good faith.

The response doesn’t address the product gap. It reframes Lula’s valid concern as the problem. “Let’s not create problems where there aren’t any” isn’t an answer. It’s a signal: the concern is unwelcome, the person raising it is a liability, and momentum takes precedence over integrity.

This is also where the systemic pattern becomes undeniable. One incident may be dismissed. Two can be written off as coincidence. But when the institutional response to every concern Lula raises is a variation of “the problem is you,” that’s not a series of unfortunate misunderstandings. That’s a system whose primary function is to protect itself — one that sees Lula’s pattern recognition as a threat rather than a value add.

High-fidelity perception is too often punished in environments that require perceptual compliance to function. Some people notice more because their processing isn’t softened by the same social conditioning that renders incoherence invisible to others. They notice what doesn’t add up and name it without strategic delay, careful political framing, or the instinct to protect the room from discomfort. In a healthy organization, that is a value add. In a gaslighting one, it is a threat.

When someone clearly sees a contradiction and names it directly, they are perceived as disruptive, even when they are correct. Especially when they are correct — because the accuracy is the problem. A system that runs on managed perception cannot afford people who see through it.

This pattern draws primarily on our lived experiences and the many stories we’ve read across the neurodivergent community here on Substack. For supporting data, see Hartman et al. (2023), cited in Neurodiversity in the Workplace: An Agenda for Research and Action (Wiley, 2024), which found that neurodivergent employees are more likely than neurotypical employees to identify and report inefficient processes and dysfunctional practices in the workplace.

What “right” looks like here is simple: take the question seriously. Not as an attack on the product team or a threat to the sales pipeline, but as exactly what it is — a legitimate concern from someone who has carefully reviewed the product and is doing her job. Investigate the claim. Test the use case. If the fit isn’t there, it’s better to know before customers do, so the organization can reshape the messaging. That’s not creating a problem. That’s preventing one. Everyone makes mistakes or has oversights as part of the human condition. But integrity lives in what you decide to do next.

Scene 4: The Role Reassignment

Lula: “Why was I quietly removed from the project I literally built?”

Director: “It’s a growth opportunity! Completely unrelated to your complaint.”

The U.S. Department of Labor defines retaliation as what happens when an employer fires an employee or takes any other type of adverse action against them for engaging in protected activity. An adverse action is one that “would dissuade a reasonable employee from raising a concern about a possible violation.”

Retaliation is not a fringe concern. Retaliation charges have been the most frequently filed category with the EEOC for seventeen consecutive years. In fiscal year 2024, retaliation accounted for 42,301 charges — roughly 48% of all discrimination charges filed. The reason it dominates is structural: retaliation can attach to any underlying complaint. Once someone raises a concern, whatever happens next is under a different kind of scrutiny.

And yet, retaliation rarely reveals itself as retaliation. It presents itself as an opportunity, a restructuring, a role clarification — or, in Lula’s case, growth. But the person on the receiving end knows exactly what it is. The institution maintains plausible deniability, and the gap between these two realities is yet another thing Lula is expected to carry in silence.

By Scene 4, the organization has built a story about Lula. Not from her work, which, by every indication, has been substantial. But from the discomfort she caused by naming what was true. This story is now doing its own work on her personal brand and her sense of worth. The reassignment in this scenario isn’t just an example of retaliation, though it seems that way on the surface. It’s also the organization acting on a narrative it constructed about her — one that has almost nothing to do with her performance and everything to do with how much it has cost them to be clearly seen.

What’s often true of people like Lula is that they’re praised for their work right up until they say something uncomfortable. The quality of the contribution remains the same. The system’s comfort level changes, and once it shifts, the narrative follows. The same focus that made Lula valuable becomes fixation. The same directness that made her effective becomes aggression. The same pattern recognition that first identified the problem becomes the reason she can’t be trusted. The label the organization applies says more about what the system can tolerate than about the person wearing it.

This is what the costs look like when they accumulate.

When someone is required to maintain orientation in an organization that’s actively undermining it, they expend enormous energy on constant recalibration. Every meeting becomes a decoding problem. Every piece of feedback must be evaluated for distortion. Every interaction with institutional authority requires defensive processing that has nothing to do with the actual work and everything to do with survival. This load doesn’t appear in any performance review. It doesn’t appear in any organizational budget. But it’s real, and it’s cumulative.

The person carrying it has less capacity for the work they were hired to do, for the relationships that sustain them, and, over time, for the focus and self-assurance that made them effective in the first place. The organization extracts this capacity while simultaneously penalizing Lula for running low.

The right thing to do here is to be honest, even when it’s uncomfortable. If this reassignment was based on Lula’s complaints, say so and address it directly. If there were legitimate performance or behavioral concerns, name them specifically and give her the opportunity to respond to actual input rather than a managed narrative. If the project genuinely was a growth opportunity, explain how and why in terms that withstand scrutiny. Lula isn’t asking much. She’s asking for a straight answer. The organization’s inability to give her one tells her everything she needs to know — and she already knew it.

To the organization reading this: Lula built something you benefited from. You removed her from it, handed it to someone else, and told her it was in her best interest. You didn’t just take the project. You took her contribution, reassigned it, and made her responsible for accepting the reassignment gracefully. That’s not a growth opportunity. That’s a message. And she received it.

Scene 5: The Diagnosis

HR Partner: “Have you considered that maybe... the issue is you?”

Lula: *quietly opens LinkedIn*

By the time HR asks Lula whether she’s considered that the issue might be her, the organization has already answered its own question. Every scene has been a variation on the same verdict. This is just the first time they’ve said it outright.

This is where many people’s stories end. Not with a confrontation. Not with a formal complaint, a legal filing, or a dramatic exit. With a quiet decision, made alone, that the cost of staying has finally exceeded the cost of leaving.

The organization will likely never record this failure as a failure. There will be no line item for what Lula knew, what she built, what she tried to protect, or the cost of walking away. The system will remain intact, having successfully routed around the person who saw it most clearly. And six months later, someone else will sit in Lula’s chair and notice that something seems a bit off.

Most people don’t test the same wall twice. They get the message. The next time something feels wrong, they hesitate. They weigh the cost of speaking up against the cost of staying quiet, and they choose silence — not because they stopped seeing clearly, but because they learned what happens when they say it out loud. The organization never has to silence them again. They’ve learned to do it themselves.

This is the most efficient outcome a gaslighting system can produce: employees who self-censor, absorb the dysfunction without naming it, and perform well on paper while slowly losing sight of why they came here in the first place.

What the organization will do next is tell itself a story. That Lula wasn’t the right fit. That she was hard. That they tried. They’ll post the role, interview candidates, and put another person in the chair. Maybe they’ll split her role up and hand it off to multiple people, since she was doing the job of more than one person. If the environment that produced this result remains intact, the next Lula will arrive full of capacity and good faith, and the cycle will begin again.

There is no “what right looks like” in Scene 5. That window closed in Scene 1. What remains is a choice about whether the organization is willing to go back to the beginning — not to fix what happened to Lula, but to build something that doesn’t produce this outcome. The culture, the policies, the modeling, the oversight structures. Not canned sensitivity training. Not an engagement survey. The whole thing from the ground up. A system that truly values the people who show up every day to keep the wheels on the bus.

What often goes unacknowledged is how difficult it can be to leave, even when staying is clearly the wrong choice. Some organizations, consciously or not, make the exit as difficult as the environment itself. They pull people back with promises, sudden recognition, and the suggestion that things are about to change. Even when the person knows it’s time to go, it can feel like a real possibility. It isn’t. It’s the system protecting its own continuity.

Lula sees right through it. She closes the tab she’s been living in for months. She opens a new one.

What It Would Actually Take to Change

Lula’s story doesn’t have to keep repeating itself. But preventing it takes more than good intentions.

Individual resilience is not a long-term solution. The problem isn’t that Lula or anyone like her lacks sufficient coping mechanisms. The problem is that she operated in an environment specifically designed to deny her experience and protect those who created it.

Change requires structural accountability — systems where the person who raises a concern isn’t automatically required to prove it without support, where the institutional response to documented harm doesn’t default to protecting the hierarchy, and where the burden of dysfunction is distributed proportionally rather than concentrated on whoever has the least power to refuse it.

It requires signal integrity. A genuine organizational commitment to honest feedback over a managed narrative. That means creating conditions in which bad news can travel upward without being intercepted, reframed, or punished. It also means trusting that the person closest to a problem often has the most accurate read of it — even if they are junior, different, or their delivery is imperfect.

It requires reciprocity. When one person is perpetually required to carry the unseen burden of a system’s dysfunction while others are protected from the consequences of creating it, that relationship is extractive. Extraction isn’t sustainable or just.

And it demands that organizations reckon with the gap between what they say they value and what they actually do when they have the opportunity to take someone at their word. If you read Lula’s story and recognize your organization, that recognition is the beginning of something. We do not have all the answers and every workplace is different, but this is a start.

For Lula

If you’ve lived through this, you were not wrong. What you saw was real. What you felt was real. The alarm that kept going off wasn’t a malfunction. It was your nervous system doing exactly what it’s supposed to do in an environment that was as broken as you knew it was.

The fact that you couldn’t prove it at the time doesn’t mean it didn’t happen. The fact that the system closed ranks doesn’t mean your perception was wrong. The fact that it cost you something real doesn’t mean you should have stayed silent.

And if you’re still inside it, weighing whether to stay or go, know this: the job market is precarious, and these dynamics are rarely visible from the outside during an interview. You’re not naive for not seeing it coming. These environments are designed to look functional until you’re already in them. The decision of when and how to leave is yours alone. There is no wrong answer to an impossible question.

What was asked of you was unreasonable. What happened to you had a name. The clarity you’re rebuilding now, on the other side of it, is not small.

And here’s what your clarity actually is: not a wound. Not a liability. Not something to unlearn. The same pattern recognition that made you a threat in a broken system is exactly what will help you find — or build — one that isn’t. That doesn’t happen in a straight line. But you’re not starting over. You’re starting from here, with everything you now know.

There are workplaces, collaborators, clients, and communities where what you see clearly will be received as what it is: a gift, not a threat. They exist. Some of them are already looking for you. And when you find them — or build them — you’ll know exactly what to look for, and exactly what to walk away from.

Lula deserved better. And so do you. And what you now carry is worth more than any workplace that couldn’t hold it.

About Jen

Jen Benford helps neurodivergent and multipassionate people stop apologizing for their range and build a life — work, voice, identity — on their own terms. She writes The Divergent Talent Alchemist on Substack, where she moves between neurodivergent identity, creative reinvention, career shape-shifting, and coming home to yourself when the systems you grew up in weren’t built for you. Subscribe at

The Divergent Talent Alchemist

Storytelling shaped by wellness, for creators and aspiring entrepreneurs building work and life on their own terms. Neurodivergence, brand, thoughtful AI, and the nervous-system work underneath all of it. Rewriting the rules, one unmasked truth at a time.

By Jen Benford

Jen also offers 1:1 coaching for neurodivergent and multipassionate people working through identity, work, and the shape of a life that fits them. She recently launched The Divergent Brand Cohort — a group container for people building a body of work on their own terms — with future cohorts opening for the same. Reach out at hello@benfordtalentalchemy.com if you’d like to talk.

If this piece resonated, be sure to subscribe to The Divergent Talent Alchemist and start with the following pieces:

• Are You a Polymath, Multipassionate, or Neurodivergent? The difference, the overlap, and why it matters.

• Beyond Bright: Helping Gifted Adults Find Work that Fits

• The Inventory: Turning the Lens Inward

We’re also hosting a live session on The Divergent Talent Alchemist on Gaslighting in the Workplace on Wednesday, July 22 at 7:00 AM (PT) / 8:00 AM (MT) / 9:00 AM (CT) / 10:00 AM (ET) / 3:00 PM (BST). Click here to join.

Photo by Andrej Lišakov for Unsplash+

Author’s Note

What follows is the letter I wish I could hand to every potential employer or collaborator before we begin. I wouldn’t classify it as a disclaimer, but as a map to something genuinely rare. I’m publishing it because the right people will immediately recognize themselves in it.

There’s a particular loss I want to name first. I used to be good at interviews. Genuinely good, in the way that comes from being present with another person and letting something real pass between you. That version of hiring still exists somewhere, but it’s become harder to find.

What’s replaced it, in too many places, is a process so abstracted from real relationships that it selects against exactly the qualities it claims to want. Five rounds. Structured rubrics. Panels of people with no brief to know you, only to assess you. The expectations for extractable facts keep rising while the space for genuine fit keeps shrinking.

I know this because I recently encountered the exception. A company was doing the relational work. There were five rounds that felt like something was building. They were moving toward hiring me, but a key person left, they had to pivot, and I was tabled for “at least a month.” I don’t fault them for it. But I sat with how that felt and made a decision: I'm no longer willing to keep sending resumes into algorithmic filters and spending myself on interviews that cost me something real and offer nothing guaranteed in return. I built my consulting practice instead. My website and this letter are both part of that.

This open letter is also for everyone who has felt the same loss and wondered whether something was wrong with them. Nothing is wrong with you. The process changed. You didn’t.

Dear Potential Employer,

I want to tell you something true before we spend another hour on credentials: I am exactly the kind of person you’ve been looking for, even as you quietly doubt such a person exists.

I’m not exceptional at just one thing. I’m exceptional in the way that actually moves organizations. I see systems clearly, connect what others keep separate, and speak honestly before issues become expensive. I lead with intelligence and stay grounded in wisdom. The first captures attention. The second sustains value.

Here’s what this looks like in practice: problems you’ve been circling for months start resolving. The concerns everyone privately carries but rarely voices are named — calmly, constructively, at the right moment. You find yourself trusting my judgment, and being right to. The work gets better. So does the room.

What makes this possible is specific.

My energy isn’t uniform. Some days I produce at a level that will surprise you — the volume, the quality, the speed. Other days are quieter, and those days are part of how the first kind happens. I won’t pretend otherwise, and I won’t let you mistake an exceptional week for a pace I can sustain indefinitely.

I’ll also need you to be honest with me about what this role actually holds: that it was scoped for one person working reasonable hours, not inherited from whoever burned out before me. If nobody knows what the job should actually entail, or the answer is “that’s just how it is here,” that’s a condition I won’t accept. I’ve stayed too long in rooms where I was the only one who understood the load, kept raising the concern, and was told it would get better. It didn’t. I’m not available for that ever again.

That experience is part of how I know my own capacity with the exactness I do now. I knew it before. I know it with painful precision now. If the work can be done by one person within a given timeframe, it will be done. It simply won’t arrive on the steady, clockable rhythm that most workplaces are built to expect.

I need the relational ground to be solid. I don’t need protection from hard feedback, high standards, or direct conversation. I need what’s said in the room to match what’s said outside it. I need expectations to be stated. I need to be evaluated by the rules I was actually given. When I trust the environment, a remarkable amount of my capacity becomes available for the work. When I don’t, I spend it reading the room instead, and you get only a fraction of what’s possible.

This is the offer: give me coherence, good faith, and the space to tell you what I see, and I will give you someone who shows up fully, thinks beyond the edges of her role, and cares about your outcomes as if they were her own.

That’s a rare thing. I know it, and I suspect you do too.

With honesty and genuine interest,

Chris Stephens, CPA

Where This Is Coming From

I lost my job nearly a year ago under circumstances beyond my control. At the time, I was the primary earner in my family and had benefits. We lost both at once. I have spent much of that time healing. I wasn’t able to search for work until a couple of months ago, and only a small fraction of my income has returned in that short time.

Refusing the algorithm feels right. What I can’t tell you yet is whether it will work — it’s only been a few weeks, and I’m writing this from inside the uncertainty, not from the other side of it.

My regular readers know most of this, but new people find their way here every day, and I wanted you to have the context. This letter wasn’t written from safety. It was written from clarity, which is different and, in some ways, harder to come by.

I’m trusting that the right people will find their way here. This is part of how I’m making it possible.

Photo by Getty Images for Unsplash+

Author’s Note: This essay is part of Work, Lately, a monthly series exploring how work functions, how it fails, and what it costs to navigate systems that weren’t built for the way some of us think.

There’s an accounting principle called substance over form. The financial reality of a transaction determines how it is reported, rather than its legal form, documentation, or invoice details.

Bill-and-hold is the clearest example. A customer pays and signs the paperwork, and the goods remain in your warehouse. Every formal signal says: sale. But the goods haven’t moved yet. The risk hasn’t transferred. The economic event hasn’t occurred. Intelligent people failed that exam question because the form seemed like the answer.

It never felt that way to me. The substance has always been obvious.

I passed all four sections of the CPA exam on the first try and, if I’m honest, found it relatively easy. Not because I studied harder, but because I was already reading at the level the profession was trying to teach.

What I didn’t understand then was that this isn’t a professional skill. It’s how I process everything. Relationships. Organizations. Conversations. I read the underlying reality first, then figure out what the words are trying to say about it. The gap between form and substance isn’t confusing to me. It’s just visible.

The friction is that the world runs on form. Hierarchy, credentials, titles, and procedures. Not because form is true, but because it is legible to most people and most systems. Living substance-first means running a translation layer in reverse, constantly, in every relationship and every room.

I know the form. Fluently. I've spent a career moving between both layers, translating in both directions. The issue was never that I couldn't read the document. It's that I already knew what was in the warehouse.

And yet I chose it too. Not because I knew any of this about myself. I chose it because I was good at math and business in high school and believed it would offer more independent work and less need to perform in front of people. For someone who processes the world the way I do, both of those things mattered enormously. It turned out to be a reasonable bet, even if the reasons ran deeper than I understood at the time.

And for the most part, it worked. My career succeeded largely because of the people I worked with. Most were respectful, and some were excellent mentors. They needed what I was good at, and I was genuinely happy to go above and beyond for them. That part was never hard. The work itself was never hard. The container was the problem, not the content.

My CPA career succeeded despite never looking like other CPAs’. I never worked in public accounting. I earned my license through complex private experience, forged my own path, and built real technical judgment outside the standard form. But big-firm experience is treated as the only valid credential, not because it produces better accountants, but because everyone agrees it’s the form. I knew the substance of my experience was legitimate. But for those who need the form, a lack of big-firm experience is the end of the conversation.

The same pattern. The same error. Goods are still in the warehouse, but everyone calls it a sale.

There’s one additional misunderstanding that deserves mention. Ask a lot of detailed questions up front, and people assume you’re the stereotype. The stuffy, detail-oriented accountant who lives in the numbers. But that was never me, and those questions were never about the details. They were about mapping the system. I need the full contextual frame before I can see how the variables connect, because I process everything at once. That’s not granularity. That’s gestalt.

The accountant stereotype trusts the numbers because they feel like form. Solid, pointable, defensible. I was using the numbers to get to the substance. Different thing entirely.

So I never fit in there either. Too unconventional for the standard path. Misread as the stereotype I was least like, and I sometimes even absorbed it as truth. Operating at a different level than the container I was in.

The profession accidentally named my entire perceptual architecture with one principle.

And then used the form to question my legitimacy anyway.

That’s not irony. That’s simply what it costs to live substance-first in a form-dominant world.

And now that I see myself clearly, I’ve started telling potential clients and employers, “I’m not your typical accountant.”

Photo by Joshua Earle for Unsplash+

This essay is the third in a series.

The first piece, What Your Most Capable People Aren’t Saying, described the structural problems that suppress the signal of pattern-recognition-forward professionals in organizational environments.

The second, Short Version: What Your Most Capable People Aren’t Saying, distilled the core framework in shorter form and includes an audio companion, research citations for the claims made in this series, and a glossary of terms.

This piece names what to do about it.

The distinction between accommodation and design is not semantic.

Accommodation is reactive. It identifies an individual as requiring adjustment and makes specific provisions for that person. It centers the exception, and in doing so, often fails to produce the outcome it promises.

Design is structural. It asks what conditions produce the best work from the people doing it and builds those conditions into how the organization functions. It centers the outcome, which negates the need for exception.

In most cases, the professionals affected have already been naming these things. The question is whether the organization is a place where that’s safe to do, and whether leadership has been listening.

What follows is organized around the structural problems the previous essay described. For each one:

what the problem costs the individual,

what it costs the organization,

and what design changes address it.

Not every organization will recognize itself in every section. These problems do not always travel together, and the design changes are not interdependent. Each one addresses a discrete cost and returns discrete value on its own. A single manager implementing one of them this week will change something real for someone on their team. The goal is direction and fit, not completeness. Any movement toward better design is better than none.

Structural redesign is the more durable solution, but accommodation is not without value. When systemic change isn't yet possible, targeted accommodation reduces real harm in the meantime. It is not the destination, but it is not nothing.

If there is a place to start, it may be the simplest and the hardest: foster an environment where honesty is not punished. Not on the surface, and not underneath. Most of what follows depends on it.

Make Role Clarity Infrastructure, Not Personality Management

Ambiguity is not just uncomfortable for pattern-recognition-forward professionals. It is often metabolically expensive. Filling in what is not stated requires continuous inference load, and that load runs even when no one is asking it to.

Without a structural container, that inference also varies: the same gap gets filled differently by different people, and the organization doesn’t see the divergence until it surfaces downstream as misalignment no one can trace back to its source. An under-structured environment doesn’t just make work harder. It makes both the overhead and the variance invisible.

What it costs the individual: Capacity consumed by continuous inference, chronic low-grade disorientation, and decisions made from an incomplete picture that never stopped shifting.

What it costs the organization: The inference work either gets done invisibly, in which case the organization benefits without accounting for it, or it doesn’t get done at all, and the gaps surface downstream as miscommunication, misaligned priorities, and rework that no one can trace back to its source.

Design change: Treat written expectations for scope, decision authority, and escalation paths as information architecture, not micromanagement. This reduces inference load for everyone, but it is especially significant for professionals whose baseline processing is already high-bandwidth.

In remote and asynchronous environments, this extends to explicit norms about response time, availability, and communication channel use. Flexibility is a reasonable offering. Ambiguity is not the same thing. Flexibility should have a defined shape.

Build the Integration Window into Standard Workflow

Some professionals think before they speak. This is not a deficiency in real-time processing. It is a different sequencing of the same work. Integration-forward cognition produces output that accounts for more variables and longer time horizons, but it produces that output on a different timeline than most environments accommodate.

What it costs the individual: Their most complete thinking arrives after the window has closed. In environments that reward speed, this reads as hesitation, lack of confidence, or disengagement. The professional learns that their best contribution is unwelcome at the moment it is most needed, and they begin to adapt by either forcing premature output or withdrawing from the process entirely.

Either way, they are still watching. The errors they anticipated accumulate and carrying that knowledge without a legitimate avenue to act on it becomes its own form of load.

What it costs the organization: Decisions made before synthesis is complete, with the most complete input arriving after the meeting has ended and the conclusion has already been documented. The organization pays for this in rework, in miscalculated risk, and in the slow erosion of trust from people who were right but too late.

Design change: Agendas sent in advance, not as a courtesy but as a norm. Questions shared before meetings, not in them. Follow-up as a normalized part of the workflow rather than a workaround for people who “need more time.” When these structures are standard, they serve everyone, and they no longer signal deficit.

Close the Gap Between What Different Groups Are Told

When the same situation, expectation, or decision is communicated differently to different people, and those accounts contradict each other, professionals who detect the inconsistency are placed in an unworkable position. They are not imagining the discrepancy. They are accurately reading two incompatible realities running simultaneously.

The same is true when stated expectations diverge from actual consequences: when what is said to be valued differs from what is rewarded, or when what is said to be unacceptable differs from what goes unaddressed. Both forms of inconsistency generate the same problem. The professional who notices is left holding knowledge that has no safe outlet and no clean resolution.

What it costs the individual: They must choose between naming what they see, which is often unsafe, and carrying the knowledge silently, which is its own form of load. Either path is costly. And the bind is circular: the incoherence they are detecting is frequently generated by the same people or structures they would need to name it to. There is no clean path out. The one that protects the professional is rarely the one that serves the organization, and the professional knows it.

What they are often withholding is precisely the signal that would restore coherence: the gap they have named internally, the misalignment they have tracked, the fix they have already identified. Whether it reaches the organization depends entirely on whether the organization has demonstrated it can receive it and do something with it. When it hasn't, the signal stays internal. The organization continues without it, and the cost accumulates on both sides.

What it costs the organization: The people most attuned to incoherence are precisely the people whose pattern recognition the organization depends on. When the environment teaches them that accurate perception is a liability, they learn to suppress the signal. The organization loses the early warning function it didn’t know it was relying on.

Design change: Establish consistency in how situations, expectations, and decisions are communicated across the organization. When different people or groups receive materially different accounts of the same thing, the people most attuned to that gap carry the cost of holding it.

Signal integrity is not a communication style preference. It is an organizational coherence condition. Individual managers can model it within their teams and provide partial relief, but this particular condition cannot be solved at the departmental level. It is generated at the organizational level and has to be addressed there.

If the leader at the top is not modeling it, not requiring it, and not providing the kind of structural container that makes honesty safe throughout the organization, the ask becomes circular: be more transparent in an environment that penalizes transparency.

This is culture change, which means it requires sustained commitment at the top, explicit expectation-setting across all levels, and enough consistency over time for the culture to actually shift. It cannot be delegated downward and it cannot be mandated without being modeled. That would be its own form of incoherence.

Treat Information Flow as a Leadership Responsibility

When inputs are incomplete, delayed, or withheld, the people responsible for downstream decisions have to infer what they should have been told. That inferencing is invisible labor. It also introduces appropriate tentativeness into outputs: not because the person lacks confidence, but because sound judgment requires adequate information, and caution is rational when it is missing.

What it costs the individual: The professional operates from a partial picture while being held accountable for decisions that required a complete one. When things go wrong, the information gap is rarely named. What gets named instead is the decision that was made without it.

What it costs the organization: Delayed, incomplete, or siloed information doesn’t stay contained. It moves through the system as compounding error. Each downstream decision made on incomplete inputs introduces new variance, and the source of that variance becomes harder to trace with every step removed from the original gap.

Design change: Document who needs to know what, and when, to do their job well. If that question doesn't have a maintained answer, the load falls on individuals, disproportionately on those whose work requires a complete picture to produce accurate output, regardless of what their role is called.

This matters in a particular way for bottom-up processors, who tend to work sequentially from what they are given. In the organizations I have observed, they are often provided what leadership believes is sufficient for the role and may not ask outside of that. The gap goes unnoticed because no one flags it, but the output is still constrained by the incomplete input.

For top-down, gestalt processors, the dynamic is more visible but no less costly. Gestalt processors often know what they need and will ask for it directly, until they receive signals that tell them that asking isn’t productive or safe.

When the person positioned to provide that information doesn’t share the same cognitive architecture, the request can read as unnecessary, excessive, or difficult, and it gets blocked without discussion. The professional is often not being unreasonable. They are accurately identifying what their process requires.

Building documented, maintained pathways to necessary information removes that dynamic from the interpersonal layer entirely. The pathway exists or it doesn’t. Whether someone understands why it’s needed becomes irrelevant.

When those pathways don’t exist or are blocked, gestalt processors tend to self-accommodate: building informal networks, finding lateral routes, assembling the picture from whatever is available. This is adaptive and it works, which means it gets praised.

The gestalt processor is resourceful, connected, proactive. What doesn’t get named is that the workaround was unpaid labor generated by a structural failure. And when something goes wrong, or when the informal route is later questioned, the organization can say it never asked for that work, which places the cost of a necessary accommodation back on the person who did it.

The skill that earned praise becomes the basis for a liability. This is another circular trap: self-accommodation is required to do the work, invisible as labor, celebrated as personality, and disavowed when it becomes inconvenient. Documented information pathways don’t eliminate the gestalt processor’s ability to integrate across systems. They eliminate the condition that forces it to happen informally and without recognition.

Close the Loops That Are Still Running

Open questions do not sit quietly. For autistic professionals in particular, an unresolved loop continues processing in the background until it is closed, drawing on capacity that is then unavailable for everything else. This is not anxiety in the clinical sense, though it can look like it. It is the nervous system doing exactly what it is designed to do: resolving prediction error until the error is resolved. Other neurotypes are not immune to the cost of unresolved loops, but the mechanism here is specific, and so is the intensity.

What it costs the individual: Unresolved loops accumulate. A professional carrying multiple open questions, none of which they have the information or authority to close, is operating at a permanent capacity deficit. The loops run whether or not anyone has asked them to, and they do not stop running because the workday has ended.

What it costs the organization: It is receiving partial cognitive output from people who are partially elsewhere. The capacity that would otherwise go to their assigned work is occupied by questions the organization has not answered, commitments it has not fulfilled, or outcomes it has not communicated. The fix is often simple. The cost of not doing it is not.

Design change: Treat loop-closure as a leadership responsibility. When a decision has been made, communicate it to the people who were waiting on it. When a commitment has been given, follow through or explicitly revise it. When a process has concluded, close it out for everyone who was part of it. These are not courtesies. They are structural acts that return capacity to the people the organization depends on. The investment is small. The return is disproportionate.

Name the Integration Function and Route It Deliberately

Siloed organizations create de facto integrators: people who notice misalignment across teams and quietly absorb the repair work that misalignment generates. For gestalt processors, this is rarely a choice in any simple sense. Misalignment is something they detect automatically, and operating inside unresolved incoherence generates its own load.

The integration work is as much self-accommodation as it is organizational service: a way of restoring enough coherence to function. This work is never in anyone's job description. It is also rarely credited. Over time, it accumulates into a form of structural extraction. The organization benefits from the integration while the cost stays invisible and the work goes unrecognized.

What it costs the individual: The integrator carries load that belongs to the system. They are doing work no one assigned and for which no one is accountable except them, by default. Over time, this creates a specific kind of depletion: not from the work itself, but from the sustained mismatch between contribution and recognition.

What it costs the organization: Integration work done informally and invisibly is integration work done without authority, without resources, and without continuity. When the person carrying it leaves, the organization rarely discovers what it depended on in any clean or actionable way.

What it experiences instead is a strain it cannot place: things take longer, misalignments surface more often, something feels off but no one can name it. The person becomes a fond memory. "Remember how good they were?" The structural function they were performing never gets named, which means it never gets rebuilt. The organization absorbs the loss without understanding it, and the condition that made that person's contribution necessary remains unchanged.

Design change: Name the integration function rather than leaving it to whoever notices the gap. In any given project or domain, someone should be explicitly responsible for cross-functional coherence: ensuring that what is happening in one part of the organization is legible to, and compatible with, what is happening in others.

That responsibility requires scope and authority to match. Concretely, this means a named role or accountable person, a documented purview, and inclusion in the decision-making process for the domains they're responsible for spanning. When the answer to "who handles cross-functional coherence?" is "whoever notices it," the work will continue to fall on the people most attuned to it, without recognition or authority to act on what they see.

Examine What Your Communication Norms Actually Reward

Direct, precise communication is not the same as abrasive communication. Professionals who communicate with high accuracy and low social cushioning are not failing at professionalism. They are optimizing for a different variable.

When the default expectation is softened, hedged output, direct communicators are doing continuous translation just to be heard without triggering defensiveness in their audience. And the cushioning itself is not neutral. It buries the lead.

The most important information gets surrounded by material designed to make it easier to receive, and in that process, it becomes harder to locate. The person who needed to hear it clearly may never register that they did.

What it costs the individual: The translation is never finished. Every communication requires an additional pass: what is true, and then how to say it in a way the room will accept. That second pass consumes capacity and introduces distortion. The professional becomes less precise over time, not because their thinking has changed, but because precision keeps creating friction.

What it costs the organization: Accurate information arrives pre-softened, which means it arrives degraded. The organization is making decisions on a version of reality that has been processed for palatability. The gap between what someone knows and what they feel safe saying is a gap in the organization’s ability to see itself clearly.

Design change: Make communication norms explicit and examine them for what they reward. If the operating expectation is that accurate information should be softened before it’s shared, then accuracy is systematically losing signal in transit.

High-trust environments reduce the need for that translation by establishing that directness is valued: not as a style preference, but because information degrades when it has to pass through multiple layers of social packaging first.

The social elements of workplace communication are real and worth addressing, but they can be addressed through other means: team norms, relational investment, psychological safety work. Collapsing them into the communication channel itself is where signal loss happens.

Organizations that separate the two, accurate information moving cleanly and relational care expressed through other channels, create conditions where neurodivergent social needs are no longer a liability and direct communicators no longer have to choose between clarity and being heard.

This matters across the full range of those needs: some neurodivergent professionals thrive in high social engagement environments, and some do not. The goal is not to flatten that variation but to stop making either end of it a professional liability.

This is one area where department-level change can provide real relief even without org-wide adoption. A manager who establishes explicit norms around directness within their team, and holds that container consistently, creates a pocket of coherence that neurodivergent professionals can orient to. It doesn't solve the broader culture, but it reduces the translation load within the domain where that manager has authority. That is worth doing while the larger shift is still in progress.

Redesign Meeting Culture to Include Everyone

Professional culture equates speed with competence. Meetings reward immediacy. Thinking out loud reads as confidence. For integration-forward processors, this environment systematically disadvantages their actual cognitive strengths, which are completeness and the synthesis that completeness makes possible, not speed.

What it costs the individual: They are evaluated on a metric that is inversely related to their strongest mode of contribution. The professional who would produce the most complete synthesis is penalized for the timeline that synthesis requires, while faster but less complete output is read as more capable. Over time, this produces either forced adaptation, with its attendant quality loss, or a growing conviction that the environment is not designed for them.

What it costs the organization: It selects for speed at the expense of completeness and then calls the result decisiveness. The professionals most likely to catch what everyone else missed are the ones least likely to surface it in a format the meeting culture rewards.

Design change: Meeting agendas and questions sent in advance, not as a courtesy but as a norm. The analysis that emerges thirty minutes after a meeting can begin before the meeting instead if the question arrives in time and if the meeting won't bring new context to the discussion. Either way, a partial analysis can happen in advance and placeholders for missing context are easier to fill in.

This discipline has a secondary effect worth naming. It requires the meeting organizer to clarify purpose and intended outcome before the meeting happens.

What needs to be discussed?

What needs to be decided?

What information does each participant need to contribute meaningfully?

Answering those questions in advance doesn’t just serve integration-forward processors. It eliminates meetings that cannot survive the scrutiny, and it makes the ones that remain more useful for everyone in the room.

Follow-up as protocol. “I’ll send thoughts by end of day” should require no explanation or special permission.

Meeting notes and transcripts as standard. Real-time note-taking competes with real-time processing. When records exist, professionals can attend meetings rather than document them simultaneously.

For remote meetings, camera use should be optional rather than assumed. Mandatory camera-on policies introduce a layer of self-monitoring and environmental management that consumes capacity without contributing to the work.

Expectations about participation more broadly should be explicit and designed with the full range of neurotypes in mind: how people are expected to signal engagement, ask questions, or contribute input should not default to a single mode that advantages some participants and disadvantages others.

Build Flexibility into the Schedule Wherever the Work Allows

Neurodivergent professionals often function better in flexible working arrangements. Not because structure doesn’t matter, but because flexibility, when it is well-contained, allows them to work in alignment with how their nervous system actually operates rather than against it.

What it costs the individual: Rigid scheduling that doesn’t account for neurological variation forces the professional to perform availability and presence on a timeline that may not match their genuine capacity windows. The result is hours logged that don’t reflect hours of actual productive output, and a sustained mismatch between when the person is expected to be “on” and when they are genuinely capable of their best work.

When that mismatch is visible, and it often is, others read it as evidence of low commitment, inconsistency, or limited capability. Those readings are rarely accompanied by curiosity about what is actually happening. They accumulate into a reputation that has nothing to do with the quality of the person’s thinking or the value of their contribution, and everything to do with how well they conform to a schedule that wasn’t designed for how their nervous system works.

What it costs the organization: It is paying for presence rather than output, and conflating the two. Professionals who would produce higher-quality work in a different arrangement are instead producing constrained output on a mandated schedule, and the organization has no mechanism to see the difference. It is also, in many cases, losing the person’s trust incrementally, as the gap between what the environment demands and what it is willing to offer makes itself felt over time.

Design change: Where the position, applicable labor law, and operational needs allow, build flexibility into how schedules are structured. Exempt and non-exempt classifications carry different legal constraints that govern what flexibility is possible, and those constraints matter and should be understood. Within them, the goal is to offer as much scheduling autonomy as the role can support.

Flexibility without structure is not the answer. Neurodivergent professionals need both. The container that makes flexibility workable includes: predictable meeting windows that don’t shift without notice, explicit shared definitions of urgency and expected response time, clear norms about when synchronous availability is required versus when asynchronous is sufficient, and consistent expectations that don’t require the professional to be perpetually available in order to demonstrate engagement.

When those structural elements are in place, flexibility stops being a special accommodation and becomes a design feature that serves the full range of people doing the work.

Stop Treating Professional Affect as Free

Regulation is work. For many neurodivergent professionals, this is not situational. Sensory, cognitive, and communication differences require continuous management simply to remain legible in most workplace environments, regardless of how calm or capable the person is on the surface.

When someone is also managing their facial expressions, body movements, and vocal tone, tracking interpersonal dynamics, and translating their own processing style for a room that doesn't share it, that work does not disappear because it is invisible. It draws on the same capacity as every other form of work.

What it costs the individual: The professional doing this all day has less available for the work they were hired to do. The depletion is real, but because it isn't visible and isn't tracked, it tends to be misread as disengagement, low output, or attitude.

The person is penalized for the cost of a tax the environment is levying on them. And the tax doesn't clock out. The capacity consumed by continuous regulation at work is capacity that doesn't return at the end of the day. What the organization experiences as inconsistent output, the professional experiences as having nothing left.

What it costs the organization: It hired a person's full capacity and is receiving a fraction of it. But that fraction is not a fixed property of the person. It is a function of the environment.

The same professional, in a setting designed with their neurotype in mind, can produce work that is markedly different in quality, consistency, and volume, not because they are trying harder, but because they are no longer spending the majority of their resources on managing the conditions around the work.

What looks like underperformance, inconsistency, stress, or anxiety is often the visible edge of an invisible tax. Change the environment, and the tax lifts.

Design change: Building psychological safety is not about requiring leaders to be consistent in ways that aren’t human. People have hard days. Moods shift. Energy varies. The goal is not affective consistency. It is an environment where fluctuation is understandable and relational reality can update openly rather than being decoded through behavioral cues.

Concretely, this means several things. Leaders whose tone or availability shifts without explanation generate monitoring load regardless of intent. A brief acknowledgment, “I’m dealing with something today, it isn’t about you,” does more to reduce ambient vigilance than a week of careful management. Neurodivergent professionals are often running continuous pattern detection on the people around them. Named reality is easier to process than inferred reality.

It also means direct, scheduled feedback rather than implicit signals. Neurodivergent professionals often cannot reliably read indirect feedback, which means they operate on continuous uncertainty about where they stand. Knowing where you stand, even when the news is hard, is less costly than not knowing.

Importantly, that directness needs to be paired with kindness and genuine curiosity. Feedback that is blunt but incurious, or that frames neurological difference as a performance problem, does not produce safety. It produces a different kind of vigilance.

The goal is a manager who can say hard things clearly, and who approaches the professional's experience with enough curiosity to understand what is actually happening before drawing conclusions about what it means.

This looks like no social penalty for direct communication or atypical presentation. If the professional has learned that their natural style generates negative relational consequences, they will manage against that continuously and invisibly.

And it means separating performance feedback from relational temperature. When a manager’s warmth tracks with their assessment of the professional’s output, the professional cannot distinguish “I am safe here” from “I am currently performing adequately.” That conflation is its own source of instability, and it is one of the more common ones.

It is also worth naming that for many neurodivergent professionals, the relationship with authority is not a blank slate. Repeated experiences of being penalized for their neurology, whether explicitly or through the accumulation of small corrections, misreadings, and social consequences, can mean that even a genuinely safer environment takes time to register as safe.

The nervous system updates on evidence, and evidence accumulates slowly when the prior history runs in the other direction. Managers who are implementing these changes in good faith should expect that trust may rebuild gradually, and should not interpret a slow response as confirmation that the changes aren’t working. It may simply mean the professional has learned, reasonably, to wait and see.

When these conditions are in place, the monitoring load drops. Not because nothing ever shifts, but because shifts can be named, reality can be updated, and the professional is no longer required to hold uncertainty in the background indefinitely.

Distinguish Recovery from Output and Recovery from Structural Stress

Rest addresses depletion caused by workload. It does not address dissonance.

What it costs the individual: A professional who has been operating in a low-coherence environment for an extended period is not suffering from insufficient rest. They are suffering from insufficient structural support for how their nervous system processes load.

A weekend or a vacation doesn't resolve a coherence problem. It interrupts it temporarily. The person returns to the same conditions and, depending on what has continued to develop in their absence, they may return to more than they left. The depletion doesn't reset. It resumes, and it accumulates.

What it costs the organization: It loses people it cannot easily replace, and it loses them in ways that look like personal decisions. The professional who resigns after a long period of structural stress rarely cites the structural conditions in their exit interview. They cite burnout, a better opportunity, a need for change.

This is not evasion. By the time someone is leaving, the organization has usually already demonstrated that it cannot receive that signal accurately. Naming the structural conditions would require trusting a system that has shown it doesn't process that kind of input well. So the professional protects themselves one final time, and the organization records an attrition event and misses the design problem that generated it.

Design change: Distinguish between recovery from output and recovery from structural stress. The first is addressed by reasonable workload and adequate time off. The second is addressed by fixing the structural conditions that are generating the stress. When organizations diagnose burnout as individual failure, they miss the organizational source of the depletion, and the depletion continues.

Adequate time off also requires that the person can actually be away. In smaller organizations where roles carry multiple responsibilities and coverage is thin, time off can generate as much load as it relieves: work accumulates, loops stay open, and the professional returns to more than they left.

Cross-training is the structural answer, and it is often deprioritized until someone leaves and the organization discovers what they were holding. Investing in coverage capacity before it becomes urgent is not a luxury. It is what makes recovery functionally possible, and it distributes organizational risk at the same time.

What Organizations Gain

The premise of this piece is that these changes benefit the organization, not as a side effect, but as the primary mechanism.

When role clarity is infrastructure, when integration is a named function with authority behind it, when communication norms reward accuracy and meeting culture accommodates different processing timelines, the organization gets better information, cleaner decisions, and the full capacity of the people doing the work.

The professionals described in the previous essay are not edge cases to be managed. They are high-signal contributors operating in environments that were not designed with their neurotype in mind.

When the environment changes, the output changes with it: not because the person has finally adjusted, but because they no longer have to spend their capacity compensating for conditions that were working against them. The goal is not to extract more from them. It is to build the conditions in which they can do their best work without it costing them their health to do so.

Organizations that get this right keep the people who were already doing the integration, the pattern detection, and the coherence repair, before those people conclude that a different choice is necessary. By that point, the organization has already lost something it didn’t know it depended on.

This is not a diversity or inclusion argument. It is a performance argument. And it applies to everyone the environment was failing, whether or not anyone ever named it.

For those who find visual frameworks useful, here is an infographic generated by Google NotebookLM illustrating the circular traps described in this essay.

Infographic generated from source material using Google Notebook LM

The core argument

Some people are wired to see problems before they're visible, connect dots across systems, and identify emerging patterns from available signal faster than most people can articulate the question.

In healthy environments, this is an organizational superpower. In poorly designed ones, it becomes a burden the person carries alone until they can’t anymore.

This piece is about what happens to those people in remote and hybrid workplaces, why they go quiet, burn out, or leave without warning, and what leaders can do differently.

What’s actually happening

When expectations are ambiguous, people can’t protect their time or trust their read of the environment. For people whose thinking depends on having a stable, coherent picture of the whole, ambiguity isn’t just inconvenient. It breaks the architecture they work from.

When the official story and the real story don’t match, these professionals get stuck holding both simultaneously with nowhere to put what they know. For autistic people specifically, this isn’t just stressful. It is a loop the brain cannot stop running. It has no natural off-ramp.

Unresolved decisions and open questions don’t sit quietly in the background. They run continuously, draining capacity whether or not the workday has ended. Rest doesn’t close them. Only resolution does.

Softening communication, managing tone on video calls, editing precision into palatability: all of this is work. It draws from the same reserves needed for complex thinking. Environments that require it in only one direction eventually run those reserves dry.

Being put on the spot is only a problem when the picture isn’t complete yet. It’s not a permanent limitation. It’s a timing problem with a simple fix.

What better design actually looks like

Written expectations. Predictable meeting windows. Agendas in advance. Protected focus time. Clear and consistent organizational priorities. Decisions that get communicated when they’re made. Open questions that get answered or explicitly deferred.

None of this requires a formal program. It requires leaders who operate this way as a matter of course. Many already do. Their teams know the difference, and so do their results.

None of this should require anyone to disclose a diagnosis or explain how their brain works. When the design is right, the benefits are available to everyone.

Audio companion

This essay was also produced as an audio discussion. If you prefer to listen, you can access it here.

Audio companion generated from source material using Google Notebook LM

Research and further reading

The analysis in this piece is grounded in lived experience and pattern recognition, but it is not without research support. The following threads informed the thinking, particularly around predictive processing, gestalt communication, allostatic load, and autistic burnout. Readers who want to go deeper will find these a useful starting point.

Sinha P, Kjelgaard MM, Gandhi T.K., et al. Autism as a disorder of prediction. Proc Natl Acad Sci U S A. 2014;111(42):15220-15225. doi:10.1073/pnas.1416797111

Note: the deficit framing in this title reflects the diagnostic culture of its context. The predictive processing mechanism it describes is what matters here, not the pathologizing of difference.

Pellicano E, Burr D. When the world becomes ‘too real’: a Bayesian explanation of autistic perception. Trends Cogn Sci. 2012;16(10):504-510. doi:10.1016/j.tics.2012.08.009

Van de Cruys S, Evers K, Van der Hallen R, et al. Precise minds in uncertain worlds: predictive coding in autism. Psychol Rev. 2014;121(4):649-675. doi:10.1037/a0037665.

McEwen BS. Stress, adaptation, and disease. Allostasis and allostatic load. Ann N Y Acad Sci. 1998;840:33-44. doi:10.1111/j.1749-6632.1998.tb09546.x.

Cage E, Troxell-Whitman Z. Understanding the Reasons, Contexts and Costs of Camouflaging for Autistic Adults. J Autism Dev Disord. 2019;49(5):1899-1911. doi:10.1007/s10803-018-03878-x

Milton, Damian. (2012). On the ontological status of autism: The ‘double empathy problem’. Disability & Society - DISABIL SOC. 27. 1-5. 10.1080/09687599.2012.710008.

Note: Milton's double empathy problem reframes communication difficulty as a bidirectional mismatch rather than a deficit located in the autistic person, directly relevant to the translation load section of this piece.

Trujillo JP, Holler J. Interactionally Embedded Gestalt Principles of Multimodal Human Communication. Perspect Psychol Sci. 2023;18(5):1136-1159. doi:10.1177/17456916221141422

Raymaker DM, Teo AR, Steckler NA, et al. "Having All of Your Internal Resources Exhausted Beyond Measure and Being Left with No Clean-Up Crew": Defining Autistic Burnout. Autism Adulthood. 2020;2(2):132-143. doi:10.1089/aut.2019.0079

Hoerricks, J. (2026). The Script is Not the Silence: Autotheory of a GLP Mind in a Pathologized World. Neurodiversity, 4.

Bluma Zeigarnik, original research 1927. Widely cited in cognitive psychology literature on open tasks and working memory load.

Coming this Friday

The solutions piece maps each of these dynamics to specific organizational practices. If you recognized your organization in the full essay, that piece is for you.

If this piece resonated, I’d love to hear from you in the comments or by message.

Glossary

A note before you read: the terms below describe cognitive mechanisms, load patterns, and survival strategies. They are not a catalog of deficits. Autistic people are people, with the same rights, worth, and capacity for meaningful contribution as anyone else. These terms exist to name what is real so that it can be addressed, not to pathologize difference or locate the problem in the person. The problem, as this piece argues, is in the design, and in the thousands of choices made every day to leave harmful conditions unchanged.

Allostatic load — the cumulative physiological cost of sustained stress and adaptation. Coined by Bruce McEwen, the term describes what happens to the body and brain when they are required to maintain stability through prolonged or repeated strain. Unlike acute stress, which resolves and allows recovery, allostatic load accumulates over time and changes the architecture of the stress response itself. Relevant here because the cognitive and regulatory demands described in this piece do not simply exhaust available energy. When sustained long enough, they alter the baseline from which recovery is possible. Rest reduces exhaustion. It does not automatically reduce allostatic load.

Ambient monitoring — the low-level, continuous effort of inferring what’s expected when expectations haven’t been stated or consistently modeled. Common in under-structured environments. Exhausting not only because it never stops, but because the person inferring carries the full risk of getting it wrong with no authoritative source to check against.

Bottom-up processor — someone who builds understanding from individual inputs upward. Detail comes first, and the whole picture emerges from accumulation. Can often keep working while some things remain unresolved.

Double empathy — a reframing of communication difficulty between autistic and neurotypical people, proposed by Damian Milton in 2012. The traditional deficit model locates the problem in the autistic person, who is understood to lack social or empathic capacity. Milton’s double empathy problem argues instead that communication difficulty is bidirectional: autistic and neurotypical people have genuinely different ways of processing and expressing experience, and neither fully understands the other without effort. The burden of bridging that gap, however, falls almost entirely on autistic people in most professional and social contexts. This is the structural condition that makes translation load necessary in the first place.

Emotional suppression — the active effort of containing, modifying, or concealing emotional responses in order to meet professional or social expectations. A component of masking, but distinct enough to name separately because the mechanism is different. Where translation load is about converting communication style, emotional suppression is about managing internal states that the environment does not have space for. The cognitive load of sustained environmental strain generates emotional responses. Those responses then require suppression. The effort of suppression draws from the same finite reserves needed for complex thinking, creating a compounding drain that is rarely visible and rarely credited. When suppression capacity is exceeded, the accumulated pressure surfaces as a larger external expression than the immediate situation appears to warrant. Autistic people are frequently blamed or punished for that expression without recognition that the environment produced it incrementally over time. The outburst is visible. The accumulation that caused it is not.

Gestalt or top-down processor — someone who needs the whole picture before the details make sense. Meaning is built from context first, not from accumulating individual facts. The frame has to hold before anything inside it can integrate.

Not all gestalt processors are autistic, and not all autistic people are gestalt processors. The overlap is significant enough to be relevant here, but the two are not the same thing.

Integration window — the interval between taking in new information and being ready to respond to it. Not hesitation. The actual work of making sense of something before speaking.

Loop closure — the resolution of an open question, incomplete process, or pending decision. For gestalt processors, unresolved loops that intersect with their work don’t rest. They run. Even during sleep. Closing the right loops at the right time is a functional requirement, not a courtesy.

Masking — the cognitive and behavioral effort of suppressing, modifying, or translating one’s natural communication style, emotional responses, and ways of processing in order to meet neurotypical social expectations. Often described as “passing” or appearing neurotypical. Masking is not deception. It is the continuous work of making one’s thinking, behavior, and presence legible to environments not designed to receive them, undertaken primarily for survival: financial security, social belonging, professional standing, and safety. In this piece, translation load refers specifically to the communication dimension of masking, and emotional suppression is another distinct component. Both are worth naming separately because they draw from the same finite cognitive reserves through different mechanisms. Cognitive load itself generates emotional responses that then require suppression, compounding the drain in a specific and often invisible direction. Masking is the broader phenomenon of which both are part.

Neurodivergent — an umbrella term for people whose neurological development, functioning, and perception differ from what is considered typical. Includes autistic people, those with ADHD, dyslexia, dyspraxia, and others. The term is not a diagnosis. It is a framing that locates difference in neurological variation rather than deficit, and that recognizes neurodivergent people as a population with distinct cognitive profiles rather than broken versions of a neurotypical standard.

Prediction error — what happens when the brain’s model of reality doesn’t match what’s actually happening. The brain is wired to resolve this. When resolution is blocked or unavailable, the loop runs continuously.

Prediction error loop — the mechanism by which the brain attempts to resolve the gap between its model of reality and what is actually happening. Prediction error loops are normal and continuous. Under ordinary conditions, resolution closes them quickly. The problem arises when resolution is blocked or unavailable, leaving the loop open and running indefinitely. When multiple unresolved loops stack, they run simultaneously in the background, compounding the drain on cognitive capacity. For autistic people, stacked unresolvable loops are not a temporary inconvenience. They are a sustained physiological demand.

Signal integrity failure — when the official version of events and the real version are in active contradiction. Different from ordinary ambiguity. Creates a specific kind of cognitive trap for people who are accurate at reading both.

Translation load — the cognitive effort of converting direct, precise communication into a form that meets social expectations. Constant in environments that require cushioning. Draws from the same reserves as complex thinking.

Photo by Curated Lifestyle for Unsplash+

Some professionals see around corners. They detect misalignment before it surfaces, notice second-order effects before they’re named, and identify emerging problems faster than most people can articulate the question. In well-designed environments, this capacity is a significant organizational asset. In poorly designed ones, it becomes a liability for the person carrying it, and quietly, for the organization too.

This piece is about what happens to pattern-recognition-forward professionals in remote environments that weren’t designed to support them. It’s about the structural conditions that silence good signal, the invisible load that accumulates when they compensate anyway, and what better design actually looks like.

This cognitive style shows up disproportionately among neurodivergent professionals, but it is not exclusive to them. The dynamics described here affect anyone whose processing prioritizes accuracy over false confidence.

The analysis that follows is drawn primarily from a gestalt or top-down processing experience, one where meaning is context-dependent, the frame must hold before detail can integrate, and coherence is not a preference but a functional precondition.

Without it, the work cannot begin, cannot complete, or must be rebuilt from the frame down before it can resume. Other neurodivergent cognitive profiles, including bottom-up processors and those with ADHD-forward load patterns, will recognize parts of what follows and may find their own experience running alongside it rather than inside it. The design principles at the end are intended to serve all of them. The analysis in between makes no claim to speak for experiences it cannot verify.

Why Remote Work Amplifies the Problem

Remote environments make these dynamics more visible, but they are not the only place they occur. Hybrid and in-person settings produce the same effects when the underlying design problems are present.

The demand starts with ambiguity, not the tools themselves. When expectations around availability, responsiveness, and decision-making are left implicit or applied inconsistently, workers lose the ability to protect their own time. Time blocking requires predictability, the confidence that a two-hour window will not be interrupted by an urgent Slack message with no shared definition of urgency. Without that predictability, sustained attention becomes impossible to plan for and difficult to defend.

In remote environments, Slack, email, task platforms, and video calls accelerate this dynamic. The workday fragments into interruptions, each requiring reorientation, and attention shifts toward constant monitoring: tracking tone, anticipating shifts in urgency, inferring what is actually required. That monitoring is exhausting, and it consumes exactly the cognitive capacity that makes these professionals valuable in the first place.

Structure isn’t the opposite of flexibility. It’s the alternative to ambiguity. Flexible hours, variable workflows, and autonomy work best when they exist within a shared framework. Without that framework, “do what works for you” is not a form of flexibility. It is an absence of design, and the cost of that absence doesn’t disappear. It gets redistributed onto the people most attuned to the gaps.

The Integration Window

Pattern-recognition-forward professionals build understanding differently. Some work bottom-up, constructing accurate pictures from concrete inputs before the whole comes into view. For gestalt or top-down processors, the process runs in the opposite direction: meaning requires a contextual frame first, and detail integrates only once that frame is in place. The frame is not a starting preference. It is load-bearing. Everything downstream depends on the frame holding.

For the latter, this process is frequently misread as excessive attention to detail or excessive caution. It is neither. It is the refusal to conclude before the frame is complete and the data within that frame holds.

There is often a brief but meaningful interval between taking in new inputs and translating them into language that fits organizational expectations. For gestalt processors, this interval is only possible when the contextual frame is intact and the incoming data fits within it.

When conditions are unstable, the interval is not simply longer. The frame itself may need to be rebuilt before integration can resume, which is a qualitatively different and significantly more expensive process. Either way, what appears externally as silence or delayed response is actually the work of integration. Once it completes, the resulting insight tends to be durable, recall is strong, and downstream decisions become faster and more accurate.

This is not slower thinking. It is a different efficiency profile. Time spent integrating constraints up front consistently reduces rework, misalignment, and downstream correction. And for gestalt processors, in particular, it is not optional.

In environments that reward immediacy over integration, this window is routinely disrupted. “Let’s just meet quickly to talk it through” can dismantle carefully built focus, forcing premature conclusions before the full shape of a problem has emerged. What looks efficient in the moment often generates rework later, as constraints that were not yet articulated resurface downstream and are often absorbed by the same people who tried to flag them early.

When the Environment Stops Making Sense

Remote environments introduce a particular kind of monitoring demand. When expectations around availability, responsiveness, and decision-making are left implicit or applied inconsistently, attention shifts away from the work itself and toward constant signal-checking: inferring what is actually required, anticipating changes in urgency, reading behavior for cues that policy never provided.

For gestalt processors, this is not merely distracting. Every inconsistent signal is a potential update to the working model of the environment. When signals are unreliable, the model cannot stabilize. Orientation stays incomplete. The processor remains permanently mid-build, consuming capacity not on the work itself but on the continuous attempt to establish a coherent picture of the conditions under which the work is supposed to happen.

This is ambient monitoring, the ordinary tax of under-structured environments. It accumulates quietly, consumes cognitive capacity, and is largely unintentional. It is also largely fixable through better design.

But there is a second, more acute version that is qualitatively different.

When the official signal and the real signal are running simultaneously and in active contradiction. When what is said publicly diverges consistently from what is communicated privately, or when stated priorities bear no relationship to actual consequences, pattern-recognition-forward processors face a specific kind of coherence collapse. They are not just carrying inference load. They are tracking two incompatible realities at once, with no legitimate way to act on what they know.

The more accurately they read the environment, the worse the position becomes. Accurate tracking confirms the contradiction but offers no path to resolution. The knowledge has to go somewhere, and there is nowhere sanctioned for it to go. Over time, every public statement, every email, every meeting becomes another data point that widens the gap between the official version and the real one. The load is not ambient. It is constant, acute, and self-compounding.

What is being described here is prediction error. For autistic processors in particular, unresolved prediction error is not merely cognitively expensive. It is a sustained threat signal, one the nervous system is wired to resolve. When resolution is blocked because the contradiction is real but unspeakable, the predictive model runs continuously, looking for a version of the data that coheres. It never finds one. The loop doesn’t close. What results is not just high load. It is cognitive overload that has no natural off-ramp.

Organizations have a direct responsibility here. Maintaining contradictory realities, public and private, official and actual, is not a neutral management style. For autistic employees, it is an active harm. The nervous system cannot distinguish between a contradiction that is resolvable and one that is not. It will keep trying. Leaders who understand this understand that integrity is not just an ethical position. It is a structural safety requirement.

This is worth naming separately, because the people who experience it are frequently told they are reading too much into things. In many cases, they are not. They may be accurately detecting that two incompatible realities are being maintained at once. The problem, in that case, is not their perception. The problem is what they are being expected to keep quiet.

When Inputs Are Constrained or Withheld

The integration process becomes significantly harder when the inputs required to do the work are incomplete, delayed, or selectively shared. This is not about context or strategic clarity, though those matter too. It is about the functional materials without which the work itself cannot proceed: data that hasn’t been shared, decisions that upstream roles haven’t made, access that hasn’t been granted, documentation that doesn’t exist. In many organizations, these gaps are treated as the individual’s problem to work around rather than a system’s failure to provision adequately.

When inputs are constrained, responses naturally become more tentative. That tentativeness is sometimes misread as lack of confidence. But it is often professional discipline. Sound judgment depends on adequate information. When context is missing, caution signals that the system has not yet made a good answer possible, not that the person is incapable of providing one.

For pattern-recognition-forward processors, this creates a specific bind, especially if the work being done requires pattern mapping, complex problem-solving, or forward projections. The responsibility to anticipate risk remains, but the materials needed to do so cleanly are unavailable. Additional cognitive effort is spent triangulating, inferring, and translating partial signals. That work is rarely visible and rarely credited.

Well-designed systems reduce this friction by treating information flow as a leadership responsibility rather than an individual burden. When inputs are shared early and consistently, confidence rises naturally, because decisions are grounded in reality rather than inference.

How Silos Multiply the Load

Siloed environments compound these dynamics by fragmenting both information and authority. When context is unevenly distributed across teams or roles, individuals are forced to assemble a working picture from partial views. Decisions made in one area surface downstream as constraints or risks elsewhere, without shared visibility into how or why they were introduced.

In remote settings, silos are easier to maintain and harder to permeate. For those who read organizational structure intuitively, the boundaries are often visible. For those who don’t, they may go unrecognized entirely until the cost surfaces downstream. Private channels, asynchronous tools, and informal decision paths can create the appearance of alignment while quietly increasing translation and repair work. Information does not travel cleanly, but responsibility still does. And this often results in multiple people solving the same problem simultaneously without collaboration, increasing duplication of effort and confusion, both of which cost the organization money.

The people most attuned to cross-functional impact often become de facto integrators. They notice misalignment early, flag second-order effects, and attempt to restore coherence across systems that were never designed to stay aligned on their own. Over time, this integration work becomes expected but unnamed, absorbing significant cognitive capacity without formal recognition or authority.

This is not a failure of collaboration or individual effort. It is a failure of system design. When information flow and decision context are not shared deliberately, the cost does not disappear. It is redistributed onto the individuals most willing or able to carry it.

Translation Is Work

In many professional environments, there is an unspoken expectation that communication will be softened, hedged, or socially cushioned before it is shared. For professionals who communicate directly and precisely, prioritizing accuracy over social lubrication, this requires constant internal editing. That editing is a form of translation, and translation draws on cognitive capacity.

This dynamic intensifies in remote environments. On video calls, professionals attuned to subtle signals spend entire meetings scanning cues, adjusting tone, managing visible presence. Even in camera-optional cultures, unspoken expectations about responsiveness and real-time participation often remain. The translation continues, just in a different register.

When translation work succeeds, it looks like ease. When it fails, the burden typically lands on the person who was translating, rather than on the mismatch between communication styles that made translation necessary.

For pattern-recognition-forward processors, this creates a compounding problem: insight that is accurate but not yet palatably packaged gets discounted or ignored. The cost of continuous translation is high. The cost of failing to translate is also high. There is no low-cost option in environments that require constant adaptation in one direction only.

Well-designed environments reduce this load by establishing explicit norms around direct communication. When clarity is treated as a legitimate style rather than a social failure, the burden of continuous translation lifts. That shift does not require anyone to abandon warmth or collegiality. It requires the organization to stop outsourcing the cost of its own communication gaps onto the people least able to pretend they don't exist.

The Cost of Being Put on the Spot

Professional culture often equates quick responses with competence. Meetings reward immediacy. Thinking out loud in linear sentences is treated as leadership.

For pattern-recognition-forward processors, this creates friction under specific conditions. When the contextual frame is intact and incoming data fits cleanly within it, response is not the problem. The problem arises when the frame is incomplete, when data doesn’t resolve cleanly, or when synthesis hasn’t yet cohered. In those moments, being put on the spot forces premature articulation, conclusions offered before the model is ready. The result frequently looks like uncertainty in the moment and produces more accurate analysis thirty minutes later, after the meeting has ended and the decision has already been made.

The pattern this creates is predictable. Capable professionals appear slower in the moment while later carrying the consequences of decisions made before context had fully cohered. Those consequences surface as rework, clarification, risk mitigation, or relationship repair, absorbed by the same people who flagged the issues early. The system moves fast. The cleanup lingers.

Normalizing alternatives distributes the cost more fairly and produces better outcomes: “I’ll follow up in writing,” or “give me a chance to think about this before we decide.” Most organizations have simply never established these as legitimate options.

When Regulation Becomes Invisible Labor

Work culture often treats emotional neutrality as professionalism. Visible responses are expected to stay out of sight.

For many pattern-recognition-forward professionals, and disproportionately for neurodivergent ones, emotional regulation under sustained environmental strain is not a background process. It is active work, drawing from the same finite cognitive reserves needed for complex thinking. When the environment itself is generating constant low-level threat signals, ambiguity, inconsistency, fragmented information, the regulatory demand never fully subsides.

For those with ADHD-forward profiles, the regulatory demand operates through a different mechanism, the continuous effort of managing attention and activation in environments that provide no external structure to borrow from, but it draws from the same finite reserves.

When emotional regulation is treated as a character trait rather than a form of work, its cost disappears from view. People absorb it privately, often interpreting reduced capacity as personal failure rather than load. Internal confidence erodes long before performance visibly changes, which means the degradation is well underway before anyone notices.

Why Rest Alone Doesn’t Fix This

Standard burnout models assume that rest and workload reduction are sufficient for recovery. When strain is primarily volumetric, this is often true.

When strain arises from sustained environmental mismatch, recovery follows a different trajectory. The issue is not depleted energy in isolation. It is ongoing cognitive and regulatory demand generated by unclear expectations, fragmented information, inconsistent norms, and effortful translation. Rest may reduce acute exhaustion. Capacity does not reliably return unless the environment itself changes.

Without adjustments to structure, communication practices, and decision expectations, the same conditions that generated the strain remain in place. The nervous system continues to anticipate interruption and misalignment. Regulation never fully downshifts.

For gestalt processors, there is an additional mechanism that standard burnout models do not account for. Unresolved loops, open questions, incomplete processes, decisions that were never finalized, do not sit quietly in the background. The processing architecture continues running against them, looking for resolution that does not come. When loops stack, the drain is continuous and compounding. Rest reduces exhaustion but does not close loops. Only resolution does.

For gestalt processors, the loops that matter most are not peripheral. They are the ones that intersect directly with the contextual frame the work depends on: open decisions that affect scope, unresolved questions that sit at the boundary of what is known and what needs to be known next. These are not background noise. They are load-bearing gaps. Bottom-up processors can often continue executing on available inputs while other things remain open. Gestalt processors cannot, because the unresolved loop is inside the architecture they are building from. Closing the right loops at the right time is not administrative courtesy. It is a functional requirement.

Environments and managers that understand this treat information transparency and loop closure as an active responsibility: decisions get made and communicated, open questions get answered or explicitly deferred; incomplete processes get named and tracked in common. When that structure is absent, the cost does not wait. It runs.

What gets labeled disengagement or withdrawal is often a protective response: the nervous system enforcing limits that the environment failed to establish. From the outside it can look like reduced participation, slower responsiveness, or narrowing focus. It is frequently an attempt to preserve enough capacity to keep functioning at all.

In other cases, the protective response surfaces differently, as increased urgency, higher signaling volume, or intensified attempts to close information gaps and restore coherence. This is often read as overreaction or emotional volatility. Structurally, it is usually an effort to compensate for missing inputs before the consequences become irreversible.

Both responses are rational. Neither is the problem. The design is.

What Better Design Actually Looks Like

None of what follows is theoretical. These practices exist in organizations right now, not because anyone implemented a formal program, but because certain leaders simply operate this way. Decisions get communicated. Questions get answered. Loops get closed. The work is predictable enough that people can think, even in environments where conditions shift frequently and predictability feels aspirational.

This is not hierarchy. It is not bureaucracy. It is not surveillance or micromanagement. It is the opposite: when the environment holds, people need less direction, less reassurance, less repair. The work runs cleaner and so do the people doing it. That is not a high bar. It is a leadership approach, and it is available to anyone willing to adopt it.

Sustainability improves when the following are treated as baseline operating norms rather than individual accommodations: clear and consistent expectations; predictable meeting windows; advance agendas and follow-up documentation; protected focus time; camera-optional norms without social penalty; and organization-wide clarity about goals, priorities, and how decisions are made and revisited.

These practices reduce ambiguity. They make good decisions repeatable. They allow people to spend cognitive capacity on the work itself rather than on inferring what the work is supposed to be.

The benefits are not limited to neurodivergent professionals, or to pattern-recognition-forward processors, or to any particular cognitive style. They accrue across teams. Better signal reaches decision-makers faster. Fewer problems get solved twice. The people most attuned to risk stay oriented long enough to flag it.

Most importantly, none of this should require disability disclosure. When work is designed well, people do not have to explain their processing styles, justify their needs, or trade privacy for access. The benefits are structural, which means they are available to everyone.

When systems change, capacity changes with them. When they don’t, the people carrying the load eventually have to make a different choice, and organizations rarely see it coming, because those people were the ones who would have.

A Note from the Author

I am a twice-exceptional CPA, autistic and gifted, with more than thirty years of experience in accounting, financial operations, and cross-functional systems thinking across organizations of varying size and structure.

I was identified late, which means I spent most of those decades operating inside these systems successfully, though not without personal cost, without the language to name what was happening.

I wrote this because the analysis demanded to be written, and because I have standing to write it. Not despite the experience of being a high-precision thinker in environments that were not designed to support that kind of thinking, but because of it. The costs named here are not theoretical. I have carried them, and I have watched others carry them without knowing what they were carrying or why.

That matters to me personally. Discourse on masking often misses these mechanisms entirely, which means burnout and nervous system collapse can become confusing even to the gestalt processor professionals experiencing them. Without language for what's actually happening, the harm compounds in silence.

I am writing this, and doing this work, because I want fewer people to get that far without understanding why. The earlier organizations and individuals recognize what is actually being asked of gestalt processor professionals, the more of that damage becomes preventable.

People like me deserve workplaces that do not require us to disappear or carry invisible cognitive load in order to be employed. That is not a small ask. It is the baseline condition for doing the work we are actually capable of doing. And when those conditions exist, the work we are capable of doing tends to be considerable.

Gestalt processor professionals are not a liability to be managed. We are an asset that most organizations have never learned to provision correctly. And we are human beings who deserve protection from systemic harm.

This piece is the first in a series. A companion post with key takeaways and a solutions-focused follow-up will both publish next week.

If you are a leader who recognized your organization in these pages, those pieces are for you.

If this piece resonated, I’d love to hear from you in the comments or by message.

Once a month, I publish an essay that shows how I see business and systems-level challenges. These pieces are different from my twice-weekly writing. They’re written for people who need someone who notices what others miss, whether that’s in a controller role, a project engagement, or something longer-term and advisory.

I’m currently operating on two tracks: seeking remote employment in senior accounting and finance roles and building an independent practice for founders and organizations who want structural clarity, not just clean books. If this resonates and you think we should work together, reach out.

Photo by Allison Saeng for Unsplash+

I am learning how to care for precision.

Not precision as perfectionism or rigidity, but precision as an instrument that detects misalignment before it becomes visible. My nervous system is not optimized for endurance through distortion. It is optimized for early detection. It registers when ethical load is unevenly distributed, when harm is quietly being absorbed so a structure can keep functioning, when language has stopped mapping reality.

This does not arrive as an abstract concern. It arrives like a violin protesting misalignment—a sudden squeal or bow chatter that hits the nervous system before thought intervenes. My spine wobbles. I swallow hard. My eyes close involuntarily. The body tightens because something structural is off, long before an obvious failure appears.

For a long time, I believed my sensitivity was the problem. That belief was reinforced in certain environments: when I struggled to move on, or when events lingered in my body longer than seemed reasonable. I saw it as a failure to regulate.

I see now that this was a category error. The sensitivity was never the issue. The issue was that neither I nor the systems around me understood the instrument I was actually playing.

Stewardship as Practice

Stewardship begins with recognizing what you’re actually holding. In my case, that’s a diagnostic capacity that functions whether I want it to or not. It sees who is carrying ambiguity and who is being asked to override their own signals to keep things running smoothly. It notices when processes depend on memory, vigilance, or informal workarounds. It registers the gap between what a system claims to do and what it actually requires of people.

This has shown up in most environments I've worked in — sometimes as design problems that could be fixed, sometimes as capacity constraints that needed acknowledgment. The accounting department where month-end close was “on time” but only because two people were working unpaid overtime and a third had built a shadow tracking system in their personal spreadsheet. The executive team presentation where the numbers were accurate, but the narrative required ignoring what the trend lines were actually saying. The founder who asked for help pricing a product, but what they actually needed was someone to name that their cost structure couldn’t support the business model they’d committed to.

In systems terms, this kind of detection identifies where good outcomes require constant compensation. Once those points are visible, the work is not about fixing people. It is about redesigning systems so coherence doesn’t depend on heroics.

That’s the work I’m interested in. Not just implementing processes or cleaning up messes—though I do both—but working with people who want their structures to actually hold.

The Hypocrisy Alarm

I have a powerful hypocrisy alarm, and it has made me inconvenient to work with in a few specific environments.

This is not about literalism or verbal missteps. I have no issue with mixed registers. I can navigate a conversation where enthusiasm arrives as “wow, girl!” and analysis lands as “look at your balance sheet.” I allow for clumsiness, growth, and the gap between what people mean and what they can yet enact.

The alarm sounds only when there is a structural decoupling between stated values and lived behavior. It sounds when a company markets an onboarding tool as “rigorously tested” while declining to use it internally. That is not a marketing pivot. It is an ethical displacement. The company is transferring unvalidated risk onto the customer while presenting certainty it has not earned.

This is often dismissed with phrases like “that’s just marketing” or “everyone overpromises,” as if naming the practice dissolves its impact. It does not. Those statements shift attention away from the actual issue: not whether overpromising is common, but where the cost of that overpromise lands. Normalization does not neutralize harm. It merely obscures responsibility.

My system registers this as unstable terrain not because harm is proven, but because language is no longer mapping reality. It is the sound of a string being bowed at the wrong angle—jarring, unavoidable, and diagnostic.

In an accounting context, this shows up constantly. The CFO who wants “aggressive but defensible” revenue recognition. The founder who describes their burn rate as “sustainable” while making payroll from personal credit cards. The controller who says controls are “adequate” while knowing three people have admin access they shouldn’t have and nobody’s reconciling petty cash.

These aren’t always ethical failures. Sometimes they’re capacity failures. The person knows the gap exists but doesn’t have resources to close it. But the gap still exists, and someone is absorbing the cost of maintaining the fiction that it doesn’t.

I won’t participate in that absorption anymore. When I work with someone, they get structural truth even when it’s inconvenient. That’s the filter. If you want someone who will make the numbers say what you need them to say, I’m the wrong person. If you want someone who will tell you what the numbers are actually saying—and help you build systems that can handle that truth—we should talk.

Challenge as Information

One clarification matters here. My instrument is not opposed to challenge. It responds well to rigor, disagreement, and being proven wrong when the evidence warrants it. I am not threatened by critique, nor do I require affirmation to remain oriented.

What I cannot abide is challenge that is performative, defensive, or structurally constrained.

I have seen what it looks like when systems treat challenge as information and allow it to change direction. Those experiences are numerous, formative, and real. In a handful of the systems I have challenged, however, disagreement is welcomed only in theory. The appearance of openness is preserved while the conditions required for genuine challenge are quietly removed.

When that happens, challenge stops functioning as information and starts functioning as risk. At that point, my signals become inconvenient not due to inaccuracy, but because they would require structural change.

This reframes a lifetime of intermittent, but confusing feedback that I was “complicated” or “oppositional.” The issue was never my resistance to challenge. It was my refusal to participate in systems that require coherence to be asserted rather than tested.

This matters for anyone considering working with me. I will tell you what I’m seeing. I will update that assessment when new information changes the picture. I will not soften structural problems to make them more palatable. And I will not stay in environments where my diagnostic capacity is treated as a liability rather than a resource.

Truth and Coherence

Because I come from neurodivergent communities that rightly prioritize lived experience over institutional authority, I want to be precise about truth. Truth is what holds under contact with reality. It is what remains consistent across time, behavior, and consequence.

Lived experience is crucial here not because it is infallible, but because it is where impact shows up first. Bodies register strain, confusion, and misalignment before institutions do. Truth that cannot support human thriving is not neutral. It is extractive.

So, when I say something is not true, I am naming a coherence failure. I am identifying a place where maintaining the official story requires ongoing compensation from human nervous systems. Where patterns cannot be challenged, tested, or refined without penalty, the system has already failed its own truth claims.

This is why certain events did not just hurt; they forced a recalibration of the map itself. When principles I organized my life around turned out not to be load-bearing, the injury was biological. It was ethical reconstruction—a refusal to live inside a model that no longer produced truth.

In financial and operational work, this distinction matters. A budget that “works on paper” but requires three people to quietly subsidize it with unpaid labor is not actually working. A process that’s “documented” but nobody follows because it doesn’t match how the work actually happens is not actually functioning. A control environment that “passes audit” but depends on one person’s vigilance is not actually controlled.

The work I want to do is about making those gaps visible and building structures that close them. Not through surveillance or rigidity, but through design that accounts for how humans actually work.

What I’m Building

I am building trust the long way, through clarity and a consistent signal of coherence that seeks resonance rather than market share. I am not trying to persuade anyone. I am trying to be found by people who are already looking for what I offer.

That means I work differently than most people in accounting and advisory roles. I don’t do performative marketing. I don’t send AI-generated follow-ups. I don’t promise certainty I haven’t earned. When communication is treated as a task rather than a relationship, coherence degrades. The cost doesn’t disappear; it’s simply no longer carried by the sender.

I won’t build my work on that transfer.

What I am interested in now is stewardship. Of my own instrument, yes, but also of the environments I choose to participate in. A fail-safe life is one with layers that absorb error before it reaches the core. Structural clarity. Temporal slack. Relational integrity. Ethical alignment that does not require constant self-betrayal.

This shows up practically in the work I take on. I am looking for people who want to be ready, not people I need to convince. Founders who sense something is structurally off and want help seeing it clearly. Controllers and finance leaders who know their systems are held together with informal workarounds and want to build something that actually holds. Organizations that are willing to reorganize when the diagnosis shows reorganization is what’s needed.

I do traditional accounting work—month-end close, reconciliations, reporting, financial modeling, systems implementation. I also do diagnostic work that sits between accounting and operations, finance and strategy. I can step into an environment, map how the pieces interact, and tell you where the load is landing and what that’s costing you.

If you are already in motion and want skilled partnership on equal footing, we should talk. If you need someone to validate decisions you’ve already made or smooth over structural problems with better messaging, I am not the right person.

I am not trying to be less sensitive. I am learning how to care for precision—and to work only in environments where that precision is a resource, not a liability.

Chris Stephens is a Wisconsin CPA with over 30 years of experience in accounting, financial operations, and systems-level thinking. She is currently seeking part-time or full-time employment in remote senior accounting and controller roles while building an independent practice serving founders and organizations who want structural clarity. You can reach her on LinkedIn.

Photo by Luke Moss on Unsplash

For a long time, I couldn’t work in any sustained way without paying a steep internal cost. I could still think. I could still see patterns. But the conditions required to translate that thinking into something usable were either absent or actively undermined. So, I stepped back. Not to disappear, but to let coherence return.

Something has shifted.

Not in the way productivity culture likes to celebrate. My capacity isn’t endless, and I’m not interested in pretending it is. But there are kinds of work that have become possible again. Not because I’ve hardened or learned to override my limits, but because I’ve stopped negotiating with them.

The work I can do well now has a particular shape.

It happens when there is time to prepare and room to think. When problems are allowed to be understood before they’re solved. When complexity isn’t treated as a personal failure, but as a property of the system itself. I do my best work in environments that value shared reality over performance, and clarity over speed.

What’s come back online for me is the ability to sit with ambiguity without rushing to collapse it. To trace second- and third-order effects. To notice where a structure is leaking pressure onto people and where a small redesign could relieve it. This kind of work doesn’t look dramatic from the outside. It often looks slower than it is. But it tends to last.

I’m especially alive to problems where the surface narrative doesn’t match the lived experience underneath. Where intentions are good, outcomes are fragile, and everyone is compensating without naming it. Those are the places where my pattern recognition is most useful, and where careful translation can change not just decisions, but the conditions under which future decisions are made.

There are also kinds of work I’m no longer available for.

I’m not available for urgency that exists to avoid accountability. I’m not available for roles that require me to hold emotional or structural risk that isn’t mine. I’m not available to be the stabilizing force in systems that refuse to stabilize themselves. Naming this isn’t bitterness. It’s maintenance.

I’m learning to treat my capacity as an ethical constraint. When I work within it, the quality of my thinking improves, and the impact of the work deepens. When I don’t, everyone loses, even if it looks like success for a while.

I’m sharing this as the first in what I expect will be an occasional practice of naming how I’m orienting toward my work. Not as a pitch, and not as a promise, but as a way of keeping the field honest. This is me saying where I’m standing now, and what kinds of collaboration can meet me here.

If this resonates, it will likely be obvious why. And if it doesn’t, that clarity matters too.