Most organizations still talk about relationships as if they were a cultural side topic. Important, yes — but somehow separate from “real” business metrics like cost, speed, risk, or profit. Nice to have, but not relevant.

That separation is the blind spot.

What the OrgIQ work — and especially the Network Costs paper — makes very clear is this: relationship quality is not soft at all. It behaves like a tax (or a multiplier) on every single hour of work inside an organization. And like any tax, it can be estimated, modeled, and improved.

This post extracts the core ideas and calculations from the paper and translates them into a form that gives you a solid intuition for why this matters and what it brings, even without diving into the full technical depth.

Organizations don’t run on boxes — they run on networks

Formally, organizations are drawn as org charts. Informally, they operate as networks.

Every decision, handover, escalation, workaround, innovation, or failure flows through relationships between people. Those relationships form a network whose quality determines how fast, how cleanly, and how reliably work moves.

Empirical research has shown this for years:

• Only 15–30% of real communication follows formal reporting lines.
• 60–90% of performance differences between comparable teams are explained by communication patterns, not expertise or hierarchy.
• Psychological safety is a stronger predictor of team performance than individual skill.

In short: hierarchy gives direction, networks do the work.

The invisible cost of bad networks

Poor relationship quality doesn’t just feel unpleasant. It produces very concrete economic effects. The paper groups them into three categories:

1. Real losses (direct costs)
   Rework, friction, misunderstandings, duplicate work, slow decisions, escalations.
   Studies consistently show 15–30% of working time is lost here in knowledge organizations.
2. Opportunity costs (lost value)
   Late product launches, missed deals, slow reactions to market changes, innovations that never leave PowerPoint. These costs are usually larger than the direct losses — and rarely tracked.
3. Lost upside (missing gains)
   Good networks don’t just reduce loss; they actively generate value: faster execution, better decisions, higher innovation rates, lower fluctuation, and more resilient transformations.

Most organizations only see the tip of this iceberg — and even that vaguely.

Why size makes everything worse (or better)

One of the most important insights in the OrgIQ model is this: size itself is not the problem.

Size amplifies whatever relationship quality is already there.

• In large organizations with poor relationships, network costs grow exponentially. Friction explodes, silos harden, bottlenecks multiply.
• In large organizations with good relationships, costs grow much more linearly. Lateral connections absorb complexity, and the system approaches a realistic efficiency minimum.

That’s why “we’re too big” is usually a misdiagnosis. The real issue is scaling without scaling relationship quality.

Relationship quality as a measurable variable

OrgIQ uses a deliberately simple but powerful abstraction: relationship quality on a scale from 1 to 10.

This single variable acts as a proxy for:

• friction and rework,
• information quality,
• trust and psychological safety,
• willingness to collaborate,
• and the emotional state of the system.

Empirically, the model maps these levels to friction ranges:

• 8–10 → ~5–10% friction
• 6–7 → ~10–20% friction
• 4–5 → ~20–35% friction
• 1–3 → ~35–60% friction

This is not arbitrary. It aligns closely with findings from MIT, McKinsey, Gartner, Google, and network research.

The three-step calculation logic

The paper introduces a pragmatic three-level approach.

1. Executive rough estimate

For a first sanity check, only a few inputs are needed:

• number of FTE,
• average cost per FTE,
• estimated friction (10–50%),
• silo factor (1.0–1.3),
• bottleneck factor (1.0–1.3).

Formula:
Annual loss = FTE × cost/FTE × friction × silo factor × bottleneck factor

This alone often reveals losses in the tens of millions, even for mid-sized companies.

2. Precise baseline (OrgIQ)

The baseline refines this into five interacting components:

1. Relationship quality (minimum, not average)
   Because emotionally, the minimum dominates experience and behavior.
2. Variance of relationship quality
   High variance = silos. This is one of the strongest early warning indicators.
3. Critical roles and bottlenecks
   Typically 3–7% of people disproportionately affect flow. If isolated or overloaded, costs multiply.
4. Organizational maturity
   Ability to handle conflict, clarity of roles, decision logic. Acts as a stabilizer or amplifier.
5. Psychological state
   Stress, insecurity, and overload directly distort communication and decision quality.

All five factors are combined multiplicatively into a single annual cost figure.

A realistic example from the paper:

• 600 FTE × €75k
• medium relationship quality,
• high variance (silos),
• one strong bottleneck,
• tense psychological state

→ ~€18 million per year in network-related costs. Not from incompetence — from relationships.

3. Measuring improvement over time

Once the baseline exists, improvement becomes financially visible.

Even small shifts in relationship quality translate directly into value. The model computes monthly gains based on reduced friction — turning “culture work” into measurable ROI.

In one transformation case, improving network quality accelerated execution by ~40%, generating €12–15 million in additional value over three years.

Innovation and adaptation are network effects

The most underestimated part of the model is the positive side.

Innovation doesn’t come from individual brilliance alone. It emerges at network intersections, where trust allows unfinished thoughts to be shared and combined. Poor relationships suppress exactly those connections.

Similarly, adaptation is not a change program. It’s real-time social coordination. Organizations adapt when people feel safe enough to speak, challenge, and realign quickly.

Empirically:

• Strong networks produce 2–5× more valuable ideas.
• High-trust organizations transform 2–3× faster.
• Poor relationships can push innovation output below baseline — into net negative territory.

Both effects depend on the same foundation: relationship quality.

The core takeaway

The central thesis of the paper is simple, but far-reaching:

Poor relationship quality acts like a tax on every hour of work.

Good relationship quality is a structural multiplier.

Once this is understood, relationship quality stops being a “soft” topic. It becomes one of the most powerful economic levers available to modern organizations.

OrgIQ’s contribution is not just the insight — it’s making this lever visible, quantifiable, and actionable.

And once you see the numbers, it becomes very hard to unsee them.

Further reading:
OrgIQ White Paper “Kosten/Nutzen von Beziehungs-Qualität” (CC BY-SA)

Der Beitrag Relationship Quality As a Hard Economic Factor erschien zuerst auf OrgIQ.

I’ve been thinking about meetings for a long time. Not because I enjoy thinking about them, but because they keep getting in the way. And the longer I watch organizations, the clearer one thing becomes: meetings are rarely the problem people think they are. They’re a symptom.

Here’s the core idea, stripped down as far as I can get it:

Meetings are a surrogate for collaboration.

They appear when real collaboration isn’t possible yet.

And no, this is usually not a conscious choice. Nobody wakes up in the morning and thinks, “Let’s avoid collaboration and replace it with meetings.” It happens subconsciously, almost automatically, as a system response to low trust, weak relationships, and a lack of shared inner state.

When collaboration actually works

I stumbled across it by chance. We had restructured our team: self-organization, smart and trust. All the practical, human, and productive things. Becoming faster. More focus. More collaboration.

And suddenly we look at our calendars and realize: the meetings have disappeared. Almost all of them. (And as the self-organization was killed again by new management, first thing was meetings came back.)

When collaboration actually works, people don’t need to talk about it. They just work together. Decisions are made while doing the work. Code gets written, designs evolve, strategies become clearer, problems get solved. Sometimes two people are involved, sometimes five, sometimes more. But nobody feels the need to put a label on it.

Interestingly, we rarely call that a meeting. We call it work. Because …

The focus is the outcome.

Meetings start to appear when this kind of working together isn’t safe, isn’t trusted, or isn’t possible. When people don’t dare to decide. When responsibility is unclear. When relationships are too thin to carry disagreement. Then collaboration gets enforced. It gets scheduled. It gets framed. And the moment you enforce something that should be voluntary, resistance appears. Quiet resistance, usually. Fatigue. Cynicism. Calendar battles.

The strange disappearance of meetings

There’s a strange dynamic here that many people miss: as collaboration capability grows, meetings disappear. Not because someone banned them, not because of a new policy, but because they’re no longer needed.

For some people, that thought is unsettling. Meetings give structure, visibility, and a sense of being involved. For others, it sounds like a dream come true. Both reactions are worth paying attention to.

Why most meetings don’t feel like work

If you look closely at most meetings, you’ll notice something else. Very few of them are actually about getting work done. They’re about opinions. About alignment. About positioning. Maybe importance. About making sure nothing bad happens. Sometimes about making sure someone important is present.

Importance is something different than meaning.

Again, this isn’t a moral judgment. It’s a structural one.

When people come together and genuinely produce something — a decision, a piece of software, a design, a plan that actually changes behavior — we usually don’t experience that as a meeting. It feels completely different. Lighter. More focused. More alive.

In a collaborative environment, this becomes normal. The focus shifts from “Who needs to be involved?” to a much more uncomfortable question: What is the simplest possible way to get this done well?

That question cuts deep.

Intelligence is mostly about avoidance

At a system level, intelligence is mostly about avoidance. Avoiding unnecessary steps. Avoiding friction. Avoiding waste. “Maximize the work not done” sounds provocative, but it’s really about respect — for energy, attention, and time.

And one of the biggest sources of waste in organizations is ego.

This is uncomfortable to say, but hard to ignore once you see it. Ego loves meetings. Meetings create stages. Stages create hierarchy. Hierarchy creates importance. And importance can feel very good, especially when something else is missing.

Since Henry Ford, we haven’t changed that much in how we organize work. Not because we couldn’t do better, but because the pyramid still works surprisingly well as a compensation. If someone feels empty inside, standing a bit higher up can feel like meaning. It’s not the real thing, but it works — for a while.

As long as we’re busy.
As long as we’re distracted.
As long as we don’t listen too closely.

Importance is not meaning

There’s usually a moment later in life when this compensation stops working. Health changes. Time becomes limited. And a question appears that can’t be postponed anymore: Was this really what all that effort was for?

That’s a hard moment to realize that importance was never meaning. It was a substitute.

Meaning comes from only two places: being part of something larger than yourself, and being in real relationships. No meeting can replace that.

A simple experiment

If you want to play with this idea, try a simple experiment. Just observe your next few workdays with a slightly different lens. Where do you see politics instead of progress? Where do you see bottlenecks created by “importance”? Where do signatures, approvals, or meetings exist mainly to confirm status rather than to move something forward?

And, gently, where do you notice the same patterns in yourself?

This isn’t about guilt. It’s about clarity. Because once you see it, you have a choice. You can keep trading meaning for importance — or you can start letting go.

No more meetings — as a consequence

So no, this isn’t a call to ban meetings. It’s something much simpler, and much harder.

When collaboration grows, meetings fade. When trust deepens, calendars clear. When people start working together for real, enforced togetherness becomes unnecessary.

No more meetings — not as a rule, but as a consequence.

And for many organizations, that wouldn’t just save an absurd amount of money. It would make work feel human again.

Der Beitrag No More Meetings erschien zuerst auf OrgIQ.

Actually it may be fine for managers, but it shows a lack of leadership.

To be more productive and happy, decisions must be made, where the competence is. And already the Steve Jobs mentioned in his early years that “the doers are also the thinkers”.

When I talk about decision here, I mean the operational stuff. Everything along the purpose of the organization is fine.

Leadership is about ensuring that everyone at any given time, will decide in the right direction. We will always have a variance in the how and what we do. And it’s an tremendous – and not very reasonable – effort to control this. But if you are clear about your purpose, you will easily get all the people working in the right direction.

As long as I make the decisions and signatures myself, I create a bottleneck and live a means of control.

And yes, we need to give the people some tools and rules to play by. Never should a single element of the system be able to endanger the whole system. But that’s the fun part: organic systems are build this way. We just need to keep them in a state that enables survival.

We build trust and happiness this way.

And we refocus on the strengths that build our success in the first place.

Der Beitrag Why Management Shouldn’t Make (Operational) Decisions erschien zuerst auf OrgIQ.