Beyond the Code: Why Compassionate Leadership Is Tech’s Most Underrated Tool

If you work in software, product, or engineering leadership, your calendar is likely dominated by sprint planning, roadmap reviews, JIRA backlogs, and performance metrics. We optimize for speed, scale, and efficiency.

Yet behind the dashboards, teams are burning out. Layoffs, organizational restructuring, and the relentless pressure of AI transformation have left tech professionals feeling exhausted, isolated, and uncertain about their futures.

Recently, I sat down with Jennifer Anderson, a Gallup-certified strengths coach with nearly twenty years of executive coaching experience and author of Call for Compassion. We discussed why leading without compassion is a dead end in tech, and how bringing human connection back into engineering organizations actually drives accountability and performance.

The Story Behind “Call for Compassion”

Jen's impetus for writing the book began in 2021. While conducting coaching sessions over Zoom, she was working with a senior tech leader in India who oversaw a 450-person organization during the catastrophic second wave of the pandemic.

During one call, this stoic, reliable leader broke down in tears. He had lost team members and family members, and he was completely depleted.

Jen did not jump in with quick-fix advice or platitudes. Instead, she stayed quiet, held space, and let him process his grief.

"I couldn't fix it," Jen recalled. "I just leaned into: 'I as a human see you as a human. Tell me more.' Compassion has been here since the beginning of time. Long before Slack, email, or JIRA, compassion was the original tool we used to connect."

The Bike Restoration Parable: Fixing Tech Teams Without Starting Over

On the cover of Jen's book is a vintage bicycle, which anchors the core parable of the story.

An eight-year-old boy celebrates his birthday and eagerly expects his father to drive him to the local bike shop for a brand-new bike. Instead, his dad drives past the store and heads straight into a junkyard. Together, they pull out an old, rusted frame and spend weeks restoring it, cleaning the rust, oiling the chain, repainting the metal, and tightening the pedals.

In tech, when teams face friction or codebases get messy, the immediate impulse is often to throw everything out, rewrite the architecture, or replace team members.

Jen's parable challenges that reflex: Before you declare a team or a process hopeless, ask if it can be restored. By cleaning off the rust, applying the oil of compassion, and realigning expectations, you can restore high function and trust without burning down the house.

Why Clarity Is Compassion in Engineering Management

A common objection among engineering managers is that compassion makes leadership "soft." Leaders worry that being empathetic means tolerating missed deadlines or avoiding difficult feedback.

Jen flips that premise entirely: True compassion requires radical clarity.

If you lead a team, can your engineers clearly articulate:

  1. The Vision: Where is the company heading?

  2. The Mission: What specific problem are we solving right now?

  3. The Values: How do we treat each other while building?

  4. The Goals: What are the measurable objectives for the quarter, the project, and the individual?

"If your team doesn't know those four things, that is not compassionate," Jen explains. "How can you hold someone accountable to an expectation they don't even know exists? Clarity allows you to hold high standards because everyone understands the field they are playing on."

This philosophy applies directly to 1:1 meetings. Jen adamantly insists that 1:1 meetings are not status updates. Status updates belong in JIRA, Linear, or asynchronous Slack channels. A 1:1 meeting belongs to the human, a dedicated space to discuss career goals, challenges, workload, and well-being.

Intrinsic Motivation in the COMPASSION Framework

In Call for Compassion, Jen outlines a 10-trait backronym: Communication, Open-mindedness, Motivation, Pulse, Attitude, Smile, Sensitivity, Intention, Optimism, and Never-ending compassion.

Among these traits, Motivation is especially transformative for tech teams. Moving past superficial compensation, what truly drives each person?

  • For some engineers, it is deep technical mastery (learning complex new stacks).

  • For others, it is human impact (mentoring junior engineers, improving user workflows).

  • For leaders like Jen, it is calendar autonomy (the freedom to protect their time).

When managers take time to understand these intrinsic drivers, they can align assignments with what actually energizes people, reducing turnover and unlocking discretionary effort.

Managing AI Burnout with the 10-Minute "Kindergarten Reset"

As the conversation shifted to the AI wave, Jen shared a fascinating historical parallel: the introduction of the domestic washing machine.

While washing machines promised instant efficiency, sociological studies showed that many women experienced unexpected isolation because they lost the daily community of washing clothes together by the river. Similarly, email replaced the fax machine with promises of speed, but created an overwhelming deluge of inbox noise.

AI is another technological leap that brings both efficiency and human disruption. Rather than panicking, Jen advises leaders to meet AI with curiosity rather than cynicism, while setting firm boundaries to prevent burnout.

Her practical prescription for every busy tech leader? The Kindergarten Reset.

Remember when kindergarten teachers paused the day, handed out cartons of milk, and had everyone rest on a carpet square? Adults need that same recovery.

Before rushing into your next high-stakes presentation or performance review, give yourself a 10 to 15-minute screen-free break. Walk away from your desk, hydrate, step outside, and check in with your physical body. When you normalize pausing, you model the exact psychological safety your team needs to thrive.

Next
Next

Proving vs. Improving: How to Build a Growth Mindset in Tech