DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. Data
  4. The Organizational Debt Cycle

The Organizational Debt Cycle

Michael Sahota user avatar by
Michael Sahota
·
Feb. 08, 15 · Interview
Like (0)
Save
Tweet
Share
8.25K Views

Join the DZone community and get the full member experience.

Join For Free

Many consider the modern workplace inhumane and uninhabitable. People are not fully engaged. It is killing our bottom lines. It is putting our organizations at risk. With our prevailing management system we have created a vast organizational debt that inhibits growth and performance.

We define organizational debt as the baggage that prevents people from delivering astonishing results. The diagram below shows the key problems that impact each human being and ultimately the effectiveness of our whole organization.

Joint post with Olaf Lewitz.

Organizational Debt Cycle

This is how the organizational debt cycle works:

Organizational Debt Cyle

We learn not to trust people we don’t know well, so our first principle is not to trust anyone. We act as if we’re afraid and sometimes we are. We want to be safe, avoid to be noticed, avoid to stand out. The more we cover our *ss, the less we connect. The less we connect, the more we feel alone… and can’t build any trust. The cycle continues.

The cycle works the other way, too: We start being afraid, not trusting people, feeling alone, so we make sure we don’t get hurt…

Impact

There is a direct connection between each of these problems and our organization’s effectiveness. For example:

  • No trust → I will try to do this myself rather than cooperate with you. I don’t believe in my leaders.
  • Fear → I will not ask for help when I need it. I will not take any risks that might improve things.
  • Cover your *ss → I will not report important information. I will not speak up to avoid disaster.
  • Alone → I will disengage. I will be powerless and not valued.

Henry Ford reportedly said that “every pair of hands comes with its own brain”. Many people got used to leave their brain at the door when they came to work. In many organisations people additionally leave their hearts outside. We don’t fully show up at work.
Prominent words like “work-life-balance” only make sense if we leave our life outside when we go to work. This cycle describes how we do that and why we keep doing it. We don’t feel we have a choice.

How We Create Organizational Debt

In organizations we create structures to support it:

  • RACI matrices have single responsibilities → alone
  • Performance reviews → fear
  • Reports are expected to match plans → cover your *ss
  • Don’t rock the boat → cover your ass
  • Gap between what we say and do → Trust no one

As leaders, we may unwittingly create or support an organizational culture where mistrust and fear impair performance.

How to Use this Model

The purpose of this model is to create awareness. When we choose to acknowledge and accept what is actually going on, then new behaviours and choices automatically emerge. Once we decide that we no longer wish to operate in this cycle, we may then ask, “What do we wish for ourselves?”

Trust (business) Management system Brain (computer virus) Diagram POST (HTTP) Build (game engine) Connection (dance)

Published at DZone with permission of Michael Sahota, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • SAST: How Code Analysis Tools Look for Security Flaws
  • How To Generate Code Coverage Report Using JaCoCo-Maven Plugin
  • Top Authentication Trends to Watch Out for in 2023
  • PHP vs React

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: