Rep. Tom Kean returns to Congress, says depression is why he went missing for months - NPR

Last week, Representative Tom Kean returned to the U. S. Capitol after a four-month absence, publicly disclosing that he had been diagnosed with depression. The news-carried by NPR, the New York Times, and other outlets-was met with a mix of sympathy and scrutiny. For those of us who work in high-pressure, always-on environments, the story hit close to home. If a sitting congressman can vanish for months under the weight of mental illness, what does that say about the culture we've built in tech? This isn't a political opinion piece; it's a reflection on the cost of silence, the normalization of burnout. And the hard truth that even the most visible leaders can crumble when we treat mental health as an afterthought.

The article "Rep. Tom Kean returns to Congress, says depression is why he went missing for months - NPR" broke just as many of us were returning from the winter reset-a time when we ask ourselves whether the sprint is sustainable. Kean's story is uniquely relatable to engineers - product managers. And technical leaders who have experienced the slow creep of exhaustion, the withdrawal from Slack channels, the missed stand-ups that turn into missed weeks. In this post, I want to examine Kean's disclosure through a technical lens: what his prolonged absence reveals about the structure of high-stakes work, how we can build systems that support mental well-being. And why the tech industry-despite all its talk of "wellness perks"-still has a long way to go.

The Hidden Toll of High-Stakes Environments on Mental Health

Pressure is a feature, not a bug, in many engineering organizations. Deadlines, on-call rotations. And the constant threat of a production outage create an environment where stress is normalized. In congressional terms, Kean faced a similar dynamic: votes, hearings. And the ever-present media cycle. Yet the difference is that software teams often lack the institutional support that a member of Congress might theoretically receive. A 2022 survey by the CDC's Workplace Health Promotion program found that only 12% of U. S companies offer full mental health benefits that include counseling, flexible time,, and and management training

When Kean disappeared, the public reaction ranged from conspiracy theories to outright dismissiveness. Tech workers who "ghost" their teams for weeks or months often face similar judgment-stereotypes of "coasting" or "lazy" engineers. But the reality is that depression can hijack executive function, making it impossible to respond to emails, write code. Or even get out of bed. As a senior engineer once told me, "I'd stare at a blinking cursor for hours. The code was there, but the will to type wasn't. " This is not a leadership failure; it's a human one.

What the "Missing Months" Can Teach Us About Technical Burnout

Kean's four-month absence is unusual by political standards, but in tech, it's alarmingly common for employees to take extended mental health leaves-often without telling anyone the real reason. A 2024 study by the National Alliance on Mental Illness (NAMI) revealed that 60% of tech workers have considered leaving their jobs due to burnout, and 40% did not feel safe disclosing a mental health condition to their manager. The stigma is compounded by the industry's fetish for productivity-lines of code shipped, tickets closed, uptime percentages.

The lessons here are structural, not personal. When Kean returned, he did not present a six-step recovery plan, and he simply said, "I needed help" That admission-raw and incomplete-is more useful than any template for a "return-to-office mental health policy. " It forces us to ask: what does it mean to build organizations that can absorb someone's temporary incapacity without penalizing them for life? In software engineering, we design for fault tolerance, graceful degradation, and redundancy. Why not design our teams the same way,

From Congress to Code: Shared Patterns of Isolation and Overwork

While the contexts differ, the patterns are eerily similar? Both members of Congress and software engineers operate in environments that reward presenteeism-showing up - staying late, being visible. For remote engineers, this often manifests as Slack activity anxiety: the fear that if you aren't responding within minutes, you will be perceived as disengaged. Kean, by his own account, stopped showing up to votes and committee meetings. The irony is that his "disappearance" might have been his first truly healthy act-a forced disconnection from a toxic system.

In the tech world, we have seen high-profile cases of founders and executives taking sabbaticals after burnout (think of Satya Nadella's reflections on his son's disability or Basecamp's infamous changes to reduce stress). But rank-and-file engineers rarely have the privilege of a four-month disappearance. The typical response is to "quiet quit" or simply resign. Kean's story highlights the need for better "runbooks" for mental health crises-company policies that treat depression as a medical condition requiring accommodation, not as a character flaw.

The Role of Leadership in Destigmatizing Mental Health Struggles

Kean's decision to publicly explain his absence after returning is a leadership act. It signals to colleagues and constituents that depression isn't shameful. In tech, the equivalent would be a CTO or VP of Engineering sharing their own journey with anxiety or depression in a team all-hands. I have seen this work: a senior staff engineer at a mid-stage startup once disclosed during a retrospective that she had been on medication for depression. And the team responded not with pity but with concrete offers to redistribute work and adjust stand-up times.

Yet most executives remain silent, and a 2025 report from the World Health Organization estimates that depression and anxiety cost the global economy $1 trillion per year in lost productivity. That figure is a direct consequence of organizations that prioritize output over people. Kean's case is a reminder that vulnerability from the top is the catalyst for systemic change. Without it, even the best "mental health days" policy is just a band-aid.

Building Resilient Teams: Technical Lessons from the Kean Episode

What can engineering leaders learn from this? First, add a "bus factor" protocol that extends beyond code: every critical role should have a documented backup for operational and interpersonal tasks. Second, normalize the idea of long-term mental health leave as part of your benefits package, not just a one-off "wellness week. " Third, treat the return from leave with the same rigor as an incident postmortem-what would have prevented the crisis, and how can we adapt?

In my own experience leading a team through a member's extended depression-related leave, we found that the biggest challenge was re-onboarding. The person returned to a codebase that had moved forward, a team that had adjusted. And a calendar full of meetings they had missed. We created a "gradual return" template: two weeks of 50% capacity, no critical path items. And a dedicated buddy to catch them up on context. This isn't charity; it's risk management. Losing a senior engineer costs 6-9 months of their salary in recruitment and training, according to SHRM data,

When Work Becomes the Only Identity: The Trap of Over-Engineering Life

Kean's office did not disclose the specific triggers for his depression, but many reports mention the intense pressure of modern politics. Similarly, many engineers tie their self-worth to their velocity, their code reviews. Or their reputation on Stack Overflow. This is a dangerous monoculture. When work is the only identity, any career setback-a layoff, a failed launch, a brutal performance review-can become an existential crisis. I have seen brilliant engineers spiral after a single 1:1 where they received a "meets expectations" rating.

The antidote isn't mandatory fun or ping-pong tables it's a deliberate separation of professional identity from personal worth. This requires structural changes: shorter sprint cycles, mandatory PTO (not just "unlimited," which often leads to less time off). And performance reviews that measure impact, not hours. Kean's story should also remind us that "returning to Congress" isn't the same as "recovery. " The system that broke him is still there. The same is true for most tech companies.

What the Tech Industry Still Gets Wrong About Mental Health

Employee Assistance Programs (EAPs) are often touted as a solution. But utilization rates hover around 5%. Why? Because they're anonymous, generic, and usually limited to a handful of therapy sessions. More importantly, they do nothing to change the root causes: unrealistic deadlines, cultural pressure to be always on. And the absence of true psychological safety. Kean's case underscores the gap between having a policy and implementing a culture.

Compare this with the approach taken by companies like Buffer or GitLab, which have published explicit mental health policies including paid sabbaticals after four years, no-meeting days. And an open "mental health" Slack channel where people can share resources. But even these are outliers. The majority of tech companies-especially startups-still treat burnout as an individual failure rather than a system failure. Until we adopt the mindset that Rep. Tom Kean returns to Congress, says depression is why he went missing for months - NPR isn't a quirky news story but a textbook case study in organizational neglect, we will continue to lose our best people.

Practical Steps to Prevent the Next "Missing Months" on Your Team

• Create a clear escalation path for mental health crises. Designate a trained mental health first aider on the team, separate from HR.
• Audit your on-call rotation. Chronic sleep disruption is a known trigger for depression. And ensure fair distribution and recovery time
• Normalize "no questions asked" sick leave that covers mental health. Update your handbook to explicitly list mental health as a valid reason for sick time.
• Conduct "health sprints" quarterly. Dedicate one sprint to reducing technical debt and lowering cognitive load-no new features.
• Encourage senior leaders to share their own stories (when ready). Vulnerability from the top is the most powerful destigmatization tool.

These aren't soft suggestions; they're engineering discipline applied to human systems. If we can write automated tests to catch regressions in code, we can write policies to catch regressions in well-being. Internal link: how to build a mental health runbook for your engineering team

FAQ: Understanding Depression in High-Pressure Roles

Conclusion: The Cost of Silence is Too High

Kean's return to Congress isn't a story about politics; it's a mirror held up to every industry that glamorizes overwork. In tech, we pride ourselves on building scalable systems. But we neglect the most critical component: the humans who run them. The next time you read "Rep. Tom Kean returns to Congress, says depression is why he went missing for months - NPR," ask yourself: is your team built to absorb a long-term absence without breaking the person or the project? If not, it's time to rewrite the runbook.

I challenge every engineering leader reading this to schedule a 30-minute retrospective this week focused solely on team mental health. No ticket board, no feature roadmap-just a conversation about how we can design work that doesn't destroy us. Internal link: template for a mental health retrospective

What do you think?

If your CTO or VP announced they were taking four months off for depression, would your team adapt gracefully or fall into chaos? Share your experience in the comments.

Is it ethical for companies to track "mental health days" as a metric,? Or does that create new pressure to perform wellness?

Could open-source projects adopt a "bus factor" for contributor mental health,? And what would that look like in practice?