The Relationship Debt Organizations Don't Know They're Carrying
- Coach Kenn
- Aug 15
- 10 min read
Behavioral Theories & Concepts™
The Workplace Series
Volume 1 | Issue 3
By Kenn Wayne Published by Kennology Theory Coaching Group
Organizations know how to calculate debt. Entire departments are dedicated to calculating that as well as risk, but for this article, we will stay focused on debt as in financial, technical, operational, and staffing debt.
We understand what happens when maintenance is deferred, systems are neglected, positions remain vacant, or financial obligations compound.
Eventually, somebody pays. But there is another form of debt accumulating inside organizations every day that goes unnoticed, and that does not appear on a balance sheet.
Your highly qualified finance team cannot calculate it. The HRIS group probably cannot measure it. And your annual engagement survey may show you the symptoms without ever identifying the source.
It's something we here at Kennology Theory Coaching like to call Relationship Debt™.
Relationship Debt™ is the accumulated cost of unresolved experiences between people and the organization, and between the people inside it. It forms when something happens, the business moves forward, but the relationship does not.
More specifically: Relationship Debt™ begins when the organization considers an issue closed, but the people involved are still carrying it.
The operational issue was closed. The relational issue remained open.
The business moved on. The relationship didn't. And like most debt, ignoring it does not make it disappear. Actually, it compounds.
The Meeting Ended. The Experience Didn't.
This is where I believe organizations misunderstand human behavior.
Businesses are built to move on to:
The next meeting.
Next quarter.
The next leader.
Next restructuring.
Next initiative.
The next employee.
People don't process experiences that way, so consider what this looks like inside an actual organization. A restructuring happens. The new organizational chart is published. Roles are reassigned. Leadership holds a town hall. Everyone is told where they report Monday morning.
Operationally, the restructuring is complete. But nobody addresses how the restructuring happened, what people lost, what promises changed, or why some employees no longer trust the people making the decisions.
The organization moved forward. The relationship didn't.
Or an employee is embarrassed by a leader during an afternoon meeting.
The meeting ends at 2:00 p.m. By 2:30, the leader is in another meeting and may never think about the interaction again.
Guess what? The employee does. Six months later, that employee rarely challenges an idea in meetings. Leadership notices the employee has become quieter. What leadership may not remember is the moment that taught the employee that speaking carried a cost.
The meeting ended, but the employee's experience and affect didn't.
By now, you should be seeing a pattern. We often mistake continuation for resolution, but they are not the same thing. People can continue working together without repairing what happened between them.
That's where the tally of relationship debt begins.
How Relationship Debt Accumulates
It rarely starts with one catastrophic event. Most debt doesn't. It accumulates through smaller transactions.
Here is an example:
Leadership asks employees for honest feedback.
Employees give it.
Nothing visibly changes.
Nobody returns to explain what was heard, what will change, what won't change, or why.
Three months later, another survey arrives.
Leadership wonders why participation has fallen.
Employees have already learned something: You asked us to speak. We spoke. Nothing happened, and it hardly ever does. That's a deposit into Relationship Debt™.
Or consider the employee passed over for a promotion.
Here is that flow:
Someone else gets the position.
The announcement is made.
The role is filled.
Operationally, the matter is finished.
But the employee receives little more than, "We decided to go in another direction."
Nobody explains where they fell short.
Nobody creates a developmental path.
Nobody has the conversation necessary to help them understand what comes next.
Months later, their effort changes.
Then leadership says: "They just aren't as engaged as they used to be."
Well, maybe, but the better question might be: What happened before their engagement changed?
Then there is the broken commitment.
A leader promises additional staffing, flexibility, a compensation review, a promotion discussion, or simply, "I'll get back to you."
Circumstances change.
The commitment isn't kept.
The business keeps moving.
The employee does too.
But something else quietly changes: what that employee believes the leader's word is worth.
That (folks) is Relationship Debt™.
None of these moments necessarily destroys a workplace. But they make deposits.
Eventually, people begin withdrawing something in return.
Trust.
Effort.
Candor.
Patience.
Collaboration.
Grace.
That withdrawal is where Relationship Debt™ starts becoming organizational cost.
The Relationship Debt Cycle™
At Kennology Theory Coaching Group, we believe there is a behavioral progression worth paying attention to: Event → Unresolved Impact → Pattern Recognition → Behavioral Protection → Organizational Cost
1. Event
Something happens.
A decision.
A conversation.
A broken commitment.
A conflict.
A leadership change.
A perceived betrayal.
A layoff.
A promotion decision.
A restructuring.
The event itself does not automatically create Relationship Debt™.
What happens afterward matters.
2. Unresolved Impact
The organization moves forward without adequately addressing what the experience created.
This does not automatically mean the employee was right, but resolution does not require agreement. A decision can be necessary, justified, and even correct while still creating relational consequences.
Consider layoffs.
Let's say that layoffs happen on a Friday. Monday morning, the remaining employees are told: "Now we need to focus on the future."
From an operational perspective, that makes sense, but some employees are still processing the loss of colleagues.
Others are wondering whether another round is coming. Some may now question decisions or assurances they previously trusted.
Leadership (being reactive vs. proactive) has moved into execution mode. The workforce may still be in interpretation mode. The business moved forward. The relationship didn't.
3. Pattern Recognition
Now the person starts watching and telling themselves a story that involves "patterns."
"This happened before."
"They always do this."
"I know how this ends."
Human beings learn from patterns. That ability protects us. But inside organizations, it also means today's decision may be interpreted through yesterday's experience.
One broken commitment may be forgiven. Three broken commitments become data.
One ignored concern may be overlooked, but repeatedly ignored concerns become a pattern, and eventually, employees stop evaluating individual events. They begin predicting outcomes.
4. Behavioral Protection
Once people believe they recognize the pattern, behavior changes.
They stop volunteering ideas.
They document everything.
They communicate less.
They take fewer risks.
They become more transactional.
They stop giving the benefit of the doubt.
They comply instead of contribute.
Or they have a moment of clarity, and they simply leave.
Leadership may call that disengagement. The employee may call it self-protection. Both may be describing the same behavior from different sides of the relationship.
5. Organizational Cost
Eventually, the behavior reaches the business in the form of collaboration slowing, conflict increasing, innovation becoming safer, and communication becoming guarded.
Managers spend more time navigating interpersonal friction, while good employees become cautious employees, and leaders begin trying to solve a performance problem that may have started as an unresolved relationship problem. That is the interest payment.
When Departments Carry Debt With Each Other
Relationship Debt™ does not exist only between leaders and employees.
Entire teams can carry it, and that plays out like this:
Two departments have a major conflict.
Maybe Operations believes Sales continually overpromises.
Sales believes Operations continually blocks deals.
Leadership solves the immediate issue.
The customer is taken care of.
The deadline is met, and everyone returns to work. But the underlying relationship between the departments is never addressed.
Now every request carries history.
Emails become longer.
More people get copied.
Simple questions sound accusatory.
Teams begin documenting conversations less for clarity and more for protection.
The original operational issue may have been solved months ago, but the organization is still paying for it. That's Relationship Debt™.
We Keep Measuring the Interest Instead of the Debt
This may be one reason organizations struggle with engagement.
Research consistently connects leadership, trust, manager behavior, employee wellbeing, and engagement. But I think there is another question underneath the numbers.
What happened before the employee stopped trusting?
That's not only a different question. It's potentially a more useful one.
When organizations see declining engagement, they often respond with another survey, leadership training, recognition program, town hall, listening session, culture initiative, or new benefit.
Some of those interventions are valuable. But imagine trying to repair a damaged financial position without first understanding the liabilities. You wouldn't.
Yet organizations routinely attempt to improve culture without understanding the relational liabilities already sitting inside it. We may be measuring the interest while ignoring the debt.
The Employee You're Calling Disengaged
Here is the harder conversation needing to happen.
What if that employee you're calling disengaged is responding exactly as your organization's history taught them to respond?
That doesn't automatically excuse their behavior. After all, employees still have responsibility.
They must communicate, remain professional, examine their own assumptions, and distinguish previous experiences from current reality.
They too must be willing to repair relationships instead of endlessly prosecuting old ones.
Since culture is everyone's responsibility, understand that employees can create Relationship Debt™ too.
An employee can repeatedly agree to something and fail to deliver.
A coworker can avoid addressing an offense directly while allowing resentment to change how they interact with the other person.
A team member can bring the behavior of a previous manager into a relationship with a new manager who has done nothing to earn the distrust.
Employees can create debt.
Peers can create debt.
Departments can create debt.
Executives can create debt.
High performers can create debt.
This is not another argument that leadership is responsible for everything that goes wrong inside an organization. They're not.
Leadership owns the environment. Employees own the experience they create inside that environment.
That said, Relationship Debt™ can travel in every direction.
Leader to employee.
Employee to leader.
Peer to peer.
Department to department.
Organization to workforce.
The responsibility may not always be equal, but the consequences are shared.
High Performers Can Be Expensive
There is another form of Relationship Debt™ organizations rarely calculate. (Hot take alert)
The high performer everyone is afraid to confront.
You know that person in your group. You know that leader. They hit the numbers. They know the business. Your customers love them, and it is believed that they are difficult to replace.
At the same time, they also mistreat their coworkers. Everyone knows it, and even leadership knows it (if they are truly reading the surveys). But because the employee produces results, leadership keeps finding reasons not to address their behavior.
The numbers still look good. The relationship balance sheet does not.
Other employees are watching, and they learn something not from the values printed on the wall, but from the behavior the organization permits. Results protect you here.
That lesson becomes your workplace culture.
Eventually, the organization may discover that the effort or revenue generated by one employee came with a cost distributed across ten others.
Turnover.
Conflict.
Reduced collaboration.
Manager time.
Loss of trust.
Good employees becoming quieter.
That's Relationship Debt™ too. Performance does not erase it.
"But We Already Apologized."
An apology can matter, and acknowledgment does matter, but it is not always repair.
Neither does a town hall, nor explaining the decision again, telling employees leadership has "heard their concerns," or waiting long enough for everyone to stop talking about what happened. Silence should never automatically be interpreted as resolution.
Sometimes people stop talking because something has been resolved. Sometimes they stop talking because they have concluded talking changes nothing. Those are two very different cultures, and they both require leadership's attention.
Repair requires more than acknowledgment.
It most times also:
Requires clarity.
Ownership.
Changed behavior.
Reset of expectations.
Another open conversation.
And sometimes repair means acknowledging that the original decision will remain unchanged while still addressing how the relationship moves forward.
In short, repair is not appeasement.
Relationship Debt Has Interest
Relationships are often discussed as though they are the soft side of business. I assure you, they're not. Relationships affect the business more than companies will acknowledge.
Every unresolved interaction does not become organizational debt. After all, human beings disagree. Managers will make unpopular decisions. Employees receive feedback they don't like,
organizations restructure, and people disappoint one another.
Healthy workplaces are not conflict-free workplaces. The issue is what happens after the conflict.
Was there clarity?
Was there ownership?
Was there conversation?
Was there behavioral change?
Were expectations reset?
Did both sides understand what happens next? Or did everyone simply return to work?
Returning to work tells us that operations resumed. It tells us very little about whether the relationship recovered.
The Relationship Debt Audit™
Instead of asking only: "Are our employees engaged?"
Organizations may need to start asking: Where are we carrying unresolved Relationship Debt™?
Where have promises been made but not kept?
Where have employees stopped raising concerns?
Which leaders produce results but leave damaged relationships behind them?
Which departments no longer trust one another?
What organizational decisions are employees still referencing months or years later?
Where has leadership explained something repeatedly but never actually repaired it?
What behavior have we normalized because addressing it would be uncomfortable?
Where are people cooperating operationally while remaining disconnected relationally?
Where have we interpreted silence as resolution?
And perhaps the most revealing question: What are people doing today because of something we failed to resolve yesterday? (We love this question for leaders and their teams)
Those questions take us beneath culture. They take us into behavior.
The Kennology Question Within The Question™
Most organizations will eventually ask: "How do we improve engagement?"
As for me, I would ask something first. What has happened here that taught people not to engage? That's your question within the question.
Even if disengagement is partially a learned response, another engagement initiative may never reach the actual problem. You cannot incentivize your way out of unresolved history, and you cannot survey your way out of broken trust. Also, companies cannot communicate their way around behavior people continue experiencing.
At some point, the debt has to be addressed.
The Future of Culture May Be Repair
Organizations spend enormous energy trying to build culture.
I wholeheartedly believe the next evolution will require organizations to become equally skilled at repairing it.
Keep in mind that:
Not every relationship can be restored.
Not every employee will be satisfied.
Not every leadership decision should be reversed.
Not every complaint means leadership was wrong.
And not every difficult workplace experience represents organizational failure.
The standard is whether organizations and the people inside them are capable of addressing what happened well enough that yesterday's unresolved experiences do not unnecessarily dictate tomorrow's behavior.
The strongest organizations will not be organizations where nothing relationally difficult happens. That organization exists only in fantasy.
The strongest organizations will be the ones capable of recognizing relational damage early, addressing it directly, resetting expectations, changing behavior when necessary, and preventing unresolved experiences from becoming institutional memory.
Remembering that organizations have memory too. We just call it culture.
And when enough unresolved experiences accumulate inside that memory, eventually somebody pays.
The employee.
The leader.
The customer.
Or the business.
In most cases, it's usually all four. No one escapes their portion of the bill.
The operational issue may be over. But if the people are still carrying it, the organization is still paying for it. That is Relationship Debt™.
And as we continue to communicate, Everything Starts With Relationship.
About Kenn Wayne
Kenn Wayne is the creator of The Kennology Theory™ and a corporate culture strategist focused on the psychology behind workplace behavior, relationships, leadership, and organizational performance.
At Kennology Theory Coaching Group, we help organizations understand the psychology behind workplace behavior so they can build scalable cultures where people thrive, leaders are equipped, relationships strengthen, and businesses grow.
Because Everything Starts With Relationship.
Comments