Skip to main content

The servant leadership paradox - When org charts contradict culture

In boardrooms and mission statements across the globe, "servant leadership" has become the philosophy du jour. Leaders proudly proclaim their commitment to serving their teams, inverting the traditional power structure, and putting employees first. Yet something curious happens when you ask to see their organizational charts.

There they are—the familiar pyramids with executives perched at the top, managers in the middle, and the frontline workers—those actually creating value—relegated to the bottom or, in many cases, not represented at all.

This visual contradiction begs the question: Can an organization truly embody servant leadership when its very structure portrays the opposite relationship?

The telling power of visuals

I think that organizational charts are more than administrative tools—they're powerful symbols that communicate "how things really work around here." When leadership teams espouse servant leadership while maintaining traditional hierarchical visuals, they send mixed messages that employees instinctively decode:

We talk about serving you, but when it comes to power and decision-making, we're still on top.

These contradictory signals create cognitive dissonance. Employees notice when words and structures don't align, often resulting in cynicism about leadership's true intentions.

Beyond the inverted pyramid

You can fix this by simply inverting your org charts, placing leaders at the bottom and frontline workers at the top. While symbolically powerful, this approach often feels like a superficial fix that doesn't address underlying power dynamics.

True servant leadership requires more than flipping a visual. It demands reimagining how organizations visualize relationships, workflows, and decision-making authority altogether.

Organizations resistant to reconsidering their org charts may be revealing something profound: they haven't truly internalized servant leadership principles. The visual representation is often one of the last things to change because it reflects deeply held beliefs about power, authority, and organizational effectiveness.

When leaders insist on maintaining traditional hierarchical charts while speaking the language of servant leadership, they may be holding onto control and reluctant to relinquish authority.

Moving from contradiction to congruence

Aligning an organizations visual representation, could lead to the following benefits:

  • Increased trust - Employees see consistency between words and symbols
  • Greater engagement - Team members recognize their centrality to the organization's purpose
  • Authentic culture - Where servant leadership becomes "how we naturally operate" rather than an aspirational slogan

So, my invitation to you is to review your organizational charts and structural representations: 

Are your org charts sending the right message that reflects your leadership principles? If not, it is maybe time to create new visualizations.

The ultimate test

Perhaps the most telling indicator of servant leadership in an organization's DNA isn't the org chart itself, but how willingly leadership embraces the conversation about changing it.

Organizations with servant leadership truly embedded in their culture should welcome the opportunity to examine contradictions between their stated philosophy and their structural representations. 

Visuals matter not just as symbols, but as daily reminders of how power should flow and whom the organization ultimately serves.

The next time you hear an executive team extolling the virtues of servant leadership, ask to see their organizational chart. The response—whether defensive, dismissive, or genuinely curious—may tell you everything you need to know about how deeply servant leadership principles have truly penetrated their organization's DNA.

More information

Trust & Inspire instead of Command & Control

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...