Skip to main content

From dependence to independence, to interdependence

Last week I was listening to an Coaching For Leaders podcast when Stephen M. R. Covey was the guest. Stephen is a bestselling author and former CEO Covey Leadership Center.


Stephen is also the son of Dr. Stephen R. Covey’s, author of the well known 7 habits of highly effective people book. When asked about a key lesson from his father, Stephen talks about the evolution from dependence to independence to interdependence. Having never read the book, I though it would a good idea to

a) Put the book on my reading list.

b) Already dive in a little bit more into this topic.

What did I learn?

The basic idea is that personal and professional growth can be seen as a journey through three stages: dependence, independence, and interdependence. Each stage represents a significant transformation in how we relate to ourselves, others, and the world.

 


Dependence: The starting point

Dependence is where we all begin. As children, we rely on our parents to meet our basic needs and guide our decisions. In the professional world, dependence can be seen in those who require constant supervision or direction. At this stage, we look to others for approval, solutions, and validation.

This doesn’t mean that dependence is something bad—it’s a natural phase of learning and development. However, staying in this phase too long can stifle growth and create unhealthy dynamics, such as a lack of accountability or over-reliance on authority figures.

Independence: The empowerment phase

The next stage, independence, is often celebrated as the hallmark of success. Independence is characterized by self-reliance, the ability to make decisions, and the confidence to act without needing constant guidance. It’s the phase where we take ownership of our lives and careers.

In the workplace, independence is evident in employees who manage their tasks effectively, take initiative, and solve problems autonomously. It is also the stage where leaders empower themselves to step away from micromanagement and trust their teams to deliver.

However, independence has its limitations. While it fosters self-sufficiency, it can lead to isolation or a lack of collaboration. Highly independent individuals may struggle to delegate, collaborate, or leverage the strengths of others.

Interdependence: The ultimate goal

The final stage, interdependence, is where the real magic happens. Interdependence recognizes that no one succeeds in isolation and that collaboration creates exponential value.

It’s not about losing your independence—it’s about combining your strengths with others to achieve something greater.

In personal growth, interdependence means forming meaningful relationships where support flows both ways. In professional settings, it translates to high-performing teams that trust each other, communicate effectively, and share responsibility for outcomes.

Interdependence is the cornerstone of thriving organizations. It’s seen in cross-functional collaboration, shared leadership models, and cultures that prioritize collective success over individual glory.

My takeaway

The key to growth, both personally and professionally, lies in mastering interdependence. As a leader, it’s essential to embody both tenacity and humility—the tenacity to lead as you were once led and the humility to serve as you were once served. While independence often develops naturally, interdependence demands deliberate effort, insight, courage, and humility. Independence can drive change, but only interdependence can drive true transformation.

More information

The 7 Habits of Highly Effective People – Wikipedia

The Beliefs of Inspirational Leaders – Coaching for Leaders

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,...