The Same Disease, Different Symptoms

Two articles crossed our desk this week that most executives will read as separate problems. CIO Magazine reports that return-to-office mandates are driving away top IT talent, with workers facing RTO requirements two to three times more likely to job hunt. Fortune warns that AI is eliminating entry-level positions, creating what author Patrick Hopkins calls a “lost generation” of knowledge workers who will be technically employed but unprepared to lead.

Both diagnoses are correct. Both miss what’s actually happening.

We’re not watching two workforce crises unfold. We’re watching one crisis manifest in two ways: organizations systematically dismantling the relationship infrastructure that makes them effective.

What Both Articles Get Right

The CIO piece includes a line from Lena McDearmid of Wryver that deserves attention: “Presence alone doesn’t create value. Purpose does.” She also notes something our research confirms—teams sitting next to each other can collaborate poorly when decisions are unclear, or leaders equate visibility with progress. The article’s core argument holds: measuring badge swipes rather than outcomes erodes trust quickly, especially among teams that have proven they can deliver remotely for years.

The Fortune piece makes an equally important point through what it calls a “delayed feedback problem.” When companies automate entry-level work, the immediate efficiency gains mask longer-term consequences that won’t become apparent until knowledge gaps emerge during complex challenges. This is systems thinking applied correctly. The apprentice stage exists because judgment, relationship skills, and the ability to deal with unexpected problems can’t be downloaded. They develop through practice, mistake-making, and mentorship.

Both articles also share an unspoken premise worth naming: organizations are relationship systems, not just production systems. When McDearmid says onboarding and mentoring early-career technologists work better in person, she’s describing relationship formation. When Hopkins argues that EQ, trust-building, and team collaboration are “the secret sauce of how good business gets done,” he’s making the same claim.

What Both Articles Miss

Neither article offers a systematic framework for what to do instead. And that’s where most organizational thinking falls apart—not in diagnosing problems, but in implementing solutions.

Consider the RTO debate. McDearmid suggests that executives ask, “What types of work are better when employees are together?” and plan intentionally for those scenarios. Sound advice. But how does an organization actually build that intentionality into daily practice? What specific behaviors change? How do we know if the intentional gatherings are working before we see turnover numbers twelve months later?

Or take the entry-level development question. Hopkins argues companies should take a long-term planning perspective and recognize the human capital they’ll need in five years. True. But what does that look like operationally? When quarterly earnings pressure collides with a recommendation to keep hiring junior staff who won’t be 100% productive for eighteen months, which one wins? We already know the answer.

The missing piece in both articles is implementation science—the systematic study of how we translate good ideas into sustained organizational practice.

Thanks for reading Lead from the Front! This post is public; please feel free to share the knowledge.

A Different Diagnosis

Both crises trace to the same root: a gap between what organizations say they value and what their systems actually reward. We call this theory-in-use versus espoused theory, following the original research of Chris Argyris and Donald Schön.

Organizations say collaboration matters, then measure individual badge swipes. Organizations say people are their greatest asset, then eliminate the developmental roles where future leaders form. The contradiction isn’t hypocrisy—it’s structural. The incentives, metrics, and time horizons built into most business systems actively undermine relationship-building, even when leaders genuinely believe relationships matter.

This makes both problems cultural, not operational. And research consistently shows that cultural problems require evolutionary solutions—small, consistent interventions over extended timeframes—rather than revolutionary mandates. Meta-analyses by Cameron and Quinn found that evolutionary cultural change succeeds 79% of the time versus 30% for revolutionary approaches.

What Would Actually Work

Start with theory-in-use audits. Map the gap between stated values and actual behaviors. If the organization says flexibility matters but tracks office presence, that gap becomes visible. If the organization says development matters but hasn’t hired a junior cohort in three years, that gap becomes visible. Visibility precedes accountability.

Implement leading indicators that predict outcomes before a crisis hits. Connection quality—measured through genuine check-in depth, not calendar frequency—predicts turnover. Psychological safety—measured through disagreement frequency in meetings—predicts innovation. Manager coaching conversations—tracked simply by counting developmental discussions—predict team performance. These metrics give organizations 6-12 months’ warning before lagging indicators (turnover, pipeline gaps, knowledge loss) appear.

Design for progressive challenge, not presence. The CIO article notes that in-person work is valuable for onboarding, mentoring, architecture reviews, and incident response. Those are high-bandwidth, relationship-building moments. Build a rhythm around them rather than mandating daily attendance. Structured off-sites monthly, war-room collaboration during critical projects, deliberate pairing of junior and senior staff for specific challenges—each of these creates a purpose-driven presence without the trust erosion of blanket mandates.

Treat entry-level development as infrastructure, not expense. Hopkins cites a Stanford study showing a 13% decline in employment among workers aged 22-25 in AI-exposed occupations. Organizations making these cuts are harvesting their seed corn. The solution isn’t to avoid AI—that’s neither possible nor desirable. The solution is to redesign entry-level work around what AI can’t do: relationship formation, judgment under ambiguity, navigating organizational complexity, and learning when and how to question the systems everyone else takes for granted.

This means longer developmental arcs with deliberate mentorship structures. Our research suggests 18-24 months as the minimum timeline for sustained behavioral change in complex skills. The modern assumption that you can compress human development into a three-day training program or eliminate it entirely through automation ignores everything we know about how capability actually forms.

The Uncomfortable Truth

Both articles are written for executives who want to know what policy to set. RTO or remote? Hire juniors or automate? That framing misses the point.

The question isn’t which policy is correct. The question is whether organizational systems support or undermine the relationships that make any policy work. An organization with a strong connectivity infrastructure can succeed with RTO or remote work. An organization without it will struggle either way. An organization that invests in developmental relationships will build its future leadership regardless of how much AI it adopts. An organization that doesn’t will hollow itself out regardless of hiring policy.

We’re not facing a workforce crisis. We’re facing a crisis in relationship infrastructure. The symptoms are everywhere. The cause is the same. And the solution requires changing what we measure, what we reward, and what we’re willing to invest in over time horizons longer than the next earnings call.

Sources

Boyagi, A. (2025, January). Work-from-office mandate? Expect top talent turnover, culture rot. CIO. https://www.cio.com/article/4119562/work-from-office-mandate-expect-top-talent-turnover-culture-rot.html

Hopkins, P.E. (2026, January 27). Coming soon: a lost generation of employee talent? Fortune. https://fortune.com/2026/01/27/lost-generation-of-employee-talent-ai-gen-z-hiring-nightmare/