Navigating Stuck OD Interventions: My Approach

Organizational Development is not an exact science. Mais non! Maintaining the momentum of an OD intervention can feel like navigating a twisted labyrinth or running uphill in the heat—sometimes we gain traction, only to falter unexpectedly or even regress to square one. Often things get worse before they get better. This is a truth that OD practitioners avoid.

Drawing from my broad experience, I want to share some strategies I use—and recommend to those I mentor—when facing these challenges of projects that are stuck.

1. Embrace Multi-Directional Focus

Instead of fixating on singular goals, diversify your targets. See what moves, in any direction. Flexibility  allows you to leverage existing resources and adapt to the unpredictable nature of organizations. The ability to pivot quickly has often turned stagnation into opportunity.

2. Adopt the “Stuck in a Snowbank” Strategy

Inspired by my winter driving lessons in Quebec, when often faced with being stuck in a snowbank on rue Decarie, it is useful to adapt different ways of driving.  One can rock a vehicle out of snow back and forth with back and forth movement. In OD, try to consider revisiting your mandate—broadening or narrowing your focus as needed. This iterative movement—pushing forward and backward & to the side, allowing for thin ice and spinning wheels as inevitable, and then advancing again—can create the breakthrough needed for real change.

3. Uncover Hidden Agendas

Ask yourself: who benefits from the stagnation? Whether it’s a colleague in HR vying for a vendor switch or a CFO aiming to cut costs, identifying these underlying motivations is crucial. A knack for uncovering these dynamics has consistently led to more effective interventions.

4. Prioritize Organizational Success Over Personal Gain

At the heart of OD is the success of the organization, not personal accolades. If your drive for change is rooted in self-interest in YOUR success, you may be on the wrong path. It’s the client who needs to succeed, not you. Looking bad from time to time is nothing to fear. An OD consultant often looks like shit when momentum is lost.

My commitment to face obstacles without fear and with creative strategies has also fostered lasting relationships…by dint of not giving up.

In the world of OD, challenges are inevitable. However, with the strategies, overcoming these challenges is what the profession is all about.

Share Button

Hiring Big-Company Managers to Scale a Small Company? Read This First.

Small companies often hire managers from large organizations to help them scale:
more process, repeatability, clearer product roadmaps, and better control.

On paper, it makes perfect sense.
In reality, it often disappoints.

Why?

Big-company managers grow up insulated from the market. Layers of structure, policy, and hierarchy create “padding” between individual roles and real commercial pressure. Problems are explained in dashboards and PowerPoint decks. Alignment matters more than ownership. Policies often replace judgment.

Small companies are the opposite.
The market is loud. Driving in fog is the norm. Results are often personal.

That culture shock alone can derail even very capable leaders.

But the problem cuts both ways.

Many small companies say they want to scale, yet resist what scaling actually requires. Process changes power dynamics. Routinization replaces heroes with systems. What fueled early success can quietly block the next phase of growth.

That’s why this transition so often fails.

What I’ve learned supporting these hires as a consultant:

• Don’t hire anyone who has never worked in a small company — even once
• Test rigorously for comfort with ambiguity, not just experience
• Early, visible action often beats slow, cautious “integration”
• Intensive weekly feedback in the first months is non-negotiable
• Define what “success” looks like within the first 30 days — jointly new hire and manager

Hiring big-company talent can accelerate growth.
But without intentional design, it usually creates friction, frustration, and false expectations.

Scaling is not about importing people. It’s about slow and painful mutual adjustment.

Share Button

Is the emphasis on planning a quirk?

In the Western world, most organizational development consultants take planning for granted. Whether it’s a detailed master plan, an MS Project file, or a simple Excel spreadsheet, having a plan is seen as basic professional practice. Plans define deliverables, clarify roles and responsibilities, and set timelines.

At first glance, the value of planning seems obvious. It brings order, focus, and direction. One would expect everyone to agree on its importance. Yet that assumption does not always hold.

Through my work, I’ve learned that planning carries very different meanings for different people. Some view plans as an illusion of control—tools used by those who believe they can fully manage their environment. Others see plans as barriers to creativity, arguing that real change comes from ingenuity and improvisation, not rigid frameworks. There are also those who feel that planning is more about control than about actually getting things done.

A client in Egypt once taught me an Arabic saying that captures this mindset perfectly:
“Isal el rafik kabl el tariq”Ask who you will travel with, not which road you will take.

Many people I work with see planning not as a help, but as an unhealthy fixation.

Because I am personally disciplined and naturally inclined to plan, these ideas were difficult for me to accept at first. But once I did, the impact was immediate. Collaboration improved dramatically in places like India, Taiwan, Israel, Thailand, and Indonesia.

By acknowledging different assumptions about planning—especially when working with Germans, Americans, Brits, and Dutch alongside cultures that value planning less—I was able to adapt my approach and achieve far better results.

Bottom line, some cultures assume that they have more control of the universe. These cultures PLAN how to take the reins into their own hands. Other cultures assume that the world is chaotic and impossible to control, thus the need to improvise and adapt as we march along.

Share Button

When “Dialogue” Kills Performance: A Cross-Cultural Leadership Failure

When a manager imposes a single communication style on cultures that value either face-saving or extreme directness, the outcome is often fatal.

The vessel of communication must fit the audience.
This is not a matter of “training people to be open and authentic.”
It’s about cultural intelligence, not good intentions.

Here’s a real illustration.


Harry Foreman, SVP APAC+ & ME+, brought together his two divisions at the Centara Grand at CentralWorld, Bangkok, for a three-day sales conference. The objective was clear:
drive strict adherence to the product roadmap and stop client-driven customization.

Harry — sweating like only a farang can sweat despite air-conditioning set to 75°F — opened with a request:

“Please listen first. Then we will have an open dialogue, not debate.”

He launched into a 33-slide presentation explaining why:

  • the roadmap must be respected

  • no deviations would be allowed

  • customers must wait 17 months for the next major release

  • sales must “manage customer expectations” and “dig in our heels”

Then came the invitation:

“OK guys — discussion. Who’s first?”


Takahashi (Japan) spoke first.
She thanked Harry warmly and added:

“And I thank Foreman-san in advance for even more tools and details for M (key customer).”

Message received by Harry: full alignment, missing the “even more” subtle clue.
Message received by everyone else: total evasion.


KT (India) began explaining how the Indian market requires cheap, heavily customized solutions that ultimately pay off through volume.

Harry interrupted:

“Are you debating?”

KT immediately replied:

“We are in full agreement, Sir.”


Dov (“Bear”), Israel, didn’t bother with diplomacy:

“This won’t fly. I don’t care if you call it a debate or a watermelon — with all my love for you, Harry, you’re way off.”

Harry smiled:

“I guess we all know Dov’s style. Please, guys — no debate.”


Som (Thailand) sat quietly, smiling.
As the best-performing country manager in the division, Harry pressed her:

“Khun Som, please — speak up.”

Wearing a bright orange outfit (a linguistic irony in Thai since Som means orange), Som smiled — the smile of embarrassment:

“I am tsua that market forces cannot be changed. And we also know Khun Harry is very senior. I am tsua we all know what to do. Thank you, Harry.”

Her thick accent ensured that no one really understood her — but Harry thanked her for the “positive input.”


At lunch, bets were already being placed on how long Harry would last.

Som was the most adamant:

“Why corporate always send their shit managers here to talk bla bla?”


The Lesson

What failed here was not strategy.
What failed was cross-cultural leadership. It is absurd to expect everyone to understand the same thing about “dialogue” especially after a senior manager has given his marching orders, except for cultures where management direction is merely a suggestion. “Dialogue” means radically different things across cultures:

  • In Japan and Thailand, it protects hierarchy and harmony via subtleness

  • In Israel, it is debate

  • In India, agreement may mean temporary compliance

Treating communication style as universal is a management illusion — and a costly one.


Why I Share This

I’ve spent years working across Asia, the Middle East, Europe, and the U.S., helping leaders and organizations avoid exactly this kind of failure.

Strategy doesn’t fail in PowerPoint.
It fails in the room, when culture is ignored.

If you manage global teams and still believe that “open dialogue” means the same thing everywhere — this story should make you uncomfortable.

And it should.

Share Button

Why I Find Communicating with Americans Harder Than with Asians reframed through years of global experience)

After nearly 1,500 hours working across Asia, I learned a counterintuitive truth: communication is not about clarity alone—it’s about context, restraint, and cultural intelligence. These were not easy lessons. In fact, they were among the hardest I’ve ever learned.

Some of my most influential teachers were not in classrooms:

  • Khun Som in Bangkok taught me how much can be communicated through evasion—and how silence can speak volumes.

  • Miyazaki in Osaka showed me that in certain cultures, giving the right answer takes years, and until then, silence is wisdom, not avoidance.

  • Emma in Malaysia and Felipe in the Philippines taught me that some topics are best left untouched—so that communication itself can continue.

  • Ji in Shanghai helped me understand how what we label as “lying” can, in context, be a deeper form of truth-telling.

  • Igor in Moscow made it clear that when the arguing stops, the relationship—not the debate—has ended.

Across Asia, something remarkable happened: people understood how different I was—and never tried to change me. We didn’t communicate despite our differences; we thrived because of them.

My frustration begins elsewhere.

When communicating with some Americans (not all), I often sense an expectation to conform: to speak the same way, think the same way, value the same forms of directness. At times it feels as though the message is: be like us, and then we can communicate. I am acutely aware of this, perhaps because although I was born in North America, and have lived in the Middle East for 56 years. I sound like a North American, but when you scratch a bit, accent aside,  my roots are not that evident.

Perhaps that’s just my perception in talking with Americans—but it often feels as if true dialogue is postponed until one has “outgrown” their cultural instincts.

Organizational development consultants must practice humility. The world is not populated by one communication style. It is full of Soms, Miyazakis, Allons, Pierres, and Hans—many of whom find the efficiency, sterility, hyper-directness, and occasional face-losing tendencies of U.S. communication deeply uncomfortable.

Alignment comes from learning to sit down with a certain amount of discomfort—and listen anyway.

Share Button

How leaders systematically teach people not to care

No one wakes up intending to build an apathetic organization.
Yet many leaders do exactly that — methodically, predictably, and at scale.

Here’s the playbook.

Tell people they can work from home as much as they want, as long as the job gets done.
Then act surprised when work becomes a contract, not a commitment.

Eliminate wasteful  meetings — especially those unstructured conversations where people talk, wander, and connect.
Call it efficiency. What you’re actually cutting is trust.

Replace real conversations with WhatsApp, Slack, and chat threads.
Now everything is urgent, nothing is important, and no one feels heard.

Normalize checking phones while talking to one another.
You’ve just taught people that attention is optional and respect is negotiable.

Set aggressively unrealistic goals “to bring out the best.”
Add wellness programs to manage the damage.
This isn’t balance — it’s gaslighting.

Give the same task to multiple people and see who performs best.
You won’t get excellence. You’ll get internal competition and silent resentment.

Automate HR, travel, and logistics through global shared services.
Congratulations — support is now efficient, anonymous, and emotionally vacant.

Promote work–life balance — except for clients, boards, executives, and financial crises.
In other words: balance applies until power speaks.

Hire in kitchens and parking lots to prove your DEI credentials.
When symbolism replaces content, cynicism follows.

Never bend on compensation because “the system must be protected.”
The system survives. Loyalty does not.

Run difficult messages through PR until they’re smooth, safe, and empty.
People stop listening when they stop believing.

Acquire innovative companies and put them under middle management supervision.
That’s not integration. That’s suffocation.

None of these decisions are accidents.
They are choices.

And the message they send is crystal clear:

“Deliver results. Don’t expect meaning. Don’t expect fairness. And above all — don’t care too much.”

People hear that message.
They adjust.
And then leaders ask the most dangerous question of all:

“Why is everyone disengaged?”

Share Button

What Management Hears—but Too Often Fails to Understand אָזְנַיִם לָהֶם, וְלֹא יִשְׁמָעוּ

What Management Hears—but Too Often Fails to Understand
אָזְנַיִם לָהֶם, וְלֹא יִשְׁמָעוּ

I speak three languages fluently—Hebrew, French, and English. I can read Spanish reasonably well (though I don’t speak it), and when I overhear a conversation in Arabic, I usually grasp the essence.

Russian, however, is different.

Since the large-scale immigration of Soviet Jews to Israel, Russian has been part of the soundscape of daily life—on buses, in offices, in cafés. I have heard it constantly for decades. And yet, I do not understand a single word. Not one. Despite exposure, despite familiarity, it simply does not register.

That realization led me to a broader question—one that is deeply relevant to leadership and organizational life:

What does management hear, again and again, without truly understanding?

French offers a useful distinction here. One can écouter—to listen in a technical sense—without entendre: without grasping meaning, implication, or urgency. Many leaders écoutent. Far fewer truly entendent.

Below is my attempt to articulate the messages that organizations repeatedly send upward—and that management often hears, but does not fully absorb:

  1. The timelines are unrealistically aggressive.
    Current schedules are aspirational, not analytical. They reflect hope rather than planning.

  2. Releasing this version prematurely risks reputational damage.
    Speed is not always a virtue; credibility, once lost, is difficult to regain.

  3. We cannot recruit effectively at these compensation levels.
    Entry-level salaries signal how much we truly value talent.

  4. Several key contributors are actively looking elsewhere.
    This is not noise—it is an early warning system. People are, in fact, our greatest asset.

  5. Employees from the acquisition completed a year ago are disengaging.
    Integration is not a legal event; it is a long psychological process which often fails.

  6. If frontline employees are not convinced, execution will fail.
    Decisions that are not “sold” internally rarely survive contact with reality.

  7. Diversity is not a moral luxury—it improves results.
    Heterogeneous teams consistently outperform homogeneous ones when properly led.

  8. The lack of cooperation between Units A and B is not structural.
    It is not about roles or charts—it is about trust.

  9. Trust, once damaged, is extraordinarily hard to restore.
    If leadership withholds or distorts the truth, skepticism will persist long after the facts change.

  10. After a downsizing, top performers begin to leave.
    They assume they are next—and unlike others, they have options.

These messages are not whispered. They are spoken clearly, repeatedly, and in good faith. And yet, too often, they fail to penetrate.

Which brings us back to the ancient insight from Psalms 115:6–7:

They have ears, but cannot hear;
and noses, but cannot smell.
They have hands, but cannot feel;
and feet, but cannot walk;
they cannot make a sound.

Leadership is not defined by access to information, dashboards, or briefings. It is defined by the capacity to entendre—to recognize meaning, risk, and human reality before consequences make them undeniable.

Hearing is easy.
Understanding is the work.

Share Button

The Organizational Dictionary: Deciphering Culture, Driving Clarity

Language has many uses. It can clarify, divert, focus and defocus. An organization’s genetic code (including strengths and pathologies) can be hidden via way certain words are used.

A consultant who knows how to use language to diagnose can intervene more effectively, more accurately pinpointing pathologies that otherwise would take months to unravel.

A very important tool that I use in my work is deciphering hidden meaning of the language by preparing a short dictionary of how certain terms are (mis) understood and (mis) used in the organization. I use this dictionary as a major part of my work in the high tech industry.

Case Study

When asked by the CEO if client X made payment for a recent delivery, the CFO said that payment was forthcoming after I hear from Billy, who is the paymaster of X. I learnt that forthcoming meant “no not yet”, and that “waiting for Billy” means Billy is not paying; Billy’s boss has not oked payment because of several issues that yet to have been solved. I used language as the major diagnostic tool and intervention tool in this case with excellent results.

The unique ‘patois’, where common terms take on different, often obfuscated, meanings. profoundly impact clarity, accountability, and decision-making. Unmasking via language, not be behaviour, is far less threatening & more powerful.

The Pitfalls of Ambiguity

Consider terms as ‘challenging,’ which may disguise difficult or impossible. Can we make the cost of goods product for $7000? It’s challenging. (COGS will cost $15,000)

Or ‘well-being,’ a word that can inadvertently suppress critical discussions and mask genuine mental health issues.

Case Study

After a year marked by 5 major accidents, the word “safety culture” started to appear. When I scratched at the meaning of the term, it meant more safety but no more resources to ensure safety.

This calculated ambiguity can foster complacency and hinder transparency, creating a culture of plausible deniability and scratching your bum instead of doing your work

The Consultant’s Advantage

By deciphering this coded language, we expose the underlying realities, not to threaten, but to inform. This process enables a collaborative plan to be formulated, transitioning from ambiguous phrases to a shared vocabulary that drives genuine progress. My colleague Peter Altschul has suggested that there is a good reason that these words are in use and correctly questions the value of this exercise. My experience is that there are no magic wands available to create change in organizations. Sometimes, some strategies work. Sometimes they don’t. Imho, using an organizational dictionary is an investment in clarity, ensuring that every word builds a foundation for success.

This technique is a very powerful arrow to have in your quiver, at least some of the time.

Finally, frequent words I find very useful to decipher:

Urgent-may mean the CEO asked for it. Or, pay attention to what I ask you for, because my priorities are not aligned with yours.

Complex-failure. The army spokesman said that the maneuver was complex; that is, wait for the causality report. Or the R&D hardware lead said that the new feature is challenging; that is it is beyond our capabilities, be it time, budget or bandwidth.

Deadline: This may mean what we promised the client, not what we can do.

Anyone who wants to know how to compile and use a dictionary in OD work-you are invited to ask me.

 

Share Button

On trust, power and designing for transparency

Remote and virtual teams are no longer an experiment; they are a structural reality of modern organizations. Distributed work brings clear advantages — access to global talent, continuous operations, proximity to customers — yet it also exposes organizations to persistent and often mis-diagnosed failures.

Across years of consulting with global companies and thousands of professionals, I have found that  breakdowns in remote collaboration are not generally caused by technology, individual capability, or lack goodwill of a personal nature. They are rather rooted in systemic trust failures — failures that organizations rarely name explicitly and even more rarely address directly.

This article outlines the most common trust barriers in remote and virtual teams, illustrates how they manifest in practice, and clarifies what leaders must do differently if they want distributed teams to perform rather than merely function.


The Problem with “Trust”

Trust has become one of the most overused and least operationalized words in organizational life. Leaders routinely call for it, HR programs promote it, and values statements celebrate it — yet when trust fails, no one agrees on what was violated.

The reason is simple: trust does not mean the same thing across cultures, roles, or power structures.

In many German professional environments, trust is procedural: “If you follow the process, I will trust you. However many other cultures work like this: once I trust you, I will follow the process.” Why? Trust in many relationship-oriented cultures is reciprocal and personal. A favor given creates an expectation of a favor returned. When these logics collide — as they often do in global organizations — both sides believe the other has broken trust, while neither believes they are at fault.

Until trust is made concrete and observable, it remains too vague to guide behavior in complex, distributed systems.


Three Systemic Trust Barriers in Remote Teams

1. Hidden Agendas and Power Imbalances

The most damaging trust failures in remote teams rarely involve interpersonal conflict. They involve control.

Who sets direction? Which site is strategic and which is tactical? Who gets visibility, budget, and senior leadership attention?

Over time, sites perceived as more powerful accumulate the most attractive work, greater influence, and political protection. Other sites are relegated to execution, maintenance, or “continuous engineering.” Predictably, morale declines, engagement erodes, and downsizing eventually follows.

This dynamic is not accidental. It is the natural outcome of ambiguous governance and poor design.

Leadership implication: Trust does not emerge organically here. It must be engineered through explicit decision rights, explicit allocation of strategic work, and senior leaders who actively prevent quiet marginalization.


2. Limited Transparency Across Sites

Most distributed teams exhibit what I call local loyalty. Information flows freely within a site but becomes selective — or strategic — across locations.

Why? Because information is perceived as power. Transparency is often viewed as weakness in an unspoken competition between sites.

The result is siloed knowledge, duplicated effort, hidden agendas and missed opportunities for leverage.

Leadership implication: Transparency across sites does not happen because tools exist to enable transparency. It happens when leaders explicitly reward openness, model it themselves, and make cross-site cooperation non-negotiable.


3. Tension Between Differing Competencies

Global teams are typically distributed to capitalize on different strengths:

  • U.S. sites close to markets and roadmaps
  • Israeli sites emphasizing innovation
  • Indian sites offering flexibility and scale
  • Japanese sites excelling at customer intimacy

These strengths are valuable — but without alignment they become sources of friction.

Customer-driven sites push for immediate customization. Innovation hubs push for architectural integrity. Market-facing leaders push for roadmap discipline. Each believes they are protecting the business. Each distrusts the others’ priorities.

Leadership implication: Trust improves only when leaders explicitly define how these competencies complement — rather than compete with — one another.


How Organizations Compensate for Low Trust

Interestingly, many organizations perform well despite low trust — at least in the short term. They do so by relying on compensatory mechanisms:

  1. Escalation: Issues are pushed upward until a senior leader makes a unilateral decision.
  2. Feigned trust: Polite agreement, vague commitments, and deliberately ambiguous decisions.
  3. Blame: Individuals or functions are punished instead of addressing systemic causes.
  4. Brute force: Fear, coercion, and pressure drive delivery.

These mechanisms work — temporarily. They also exhaust leaders, burn talent, and collapse under scale.


What Trust Looks Like in Practice

Through my work with organizations that have built durable trust across distance and culture, trust consistently shows up in 8 observable behaviors, including:

  1. We accurately represent one another’s views when the other party is not present.
  2. We follow through on the decisions we make together.
  3. We assume positive intent unless proven otherwise.
  4. We implement what we decide upon
  5. Decisions are made on technical/marketing/business considerations to neutralize political positioning
  6. We act reliably and honestly towards each other
  7. We avoid character assassination.
  8. We involve the relevant people in decision-making.

A Leadership Reality Check

Remote and virtual teams do not fail because individuals lack skill or motivation. They fail because organizations place individuals into trust-busting systems and then ask them to behave heroically.

Developing individual capability matters — but only within an environment that does not systematically undermine trust through power ambiguity, opacity, and misaligned incentives.

Leaders who succeed with distributed teams understand this distinction. They stop moralizing trust and start designing for it.

That, more than any tool or training, is what separates remote teams that merely survive from those that perform at scale.

Share Button

Welcome to the Organizational Zoo: A Field Guide to Office Politics

Most of us begin our careers believing that talent, motivation, and hard work will naturally lead to success. And then reality intervenes. Again and again, capable people watch opportunities slip away—not because they lack skill, but because they lack political awareness. Meanwhile, others with sharper political instincts seem to thrive, sometimes despite modest competence.

What’s missing is a systematic initiation into organizational politics.

We teach young managers processes, frameworks, and leadership ideals. What we don’t teach them is how power actually works. As a result, many learn the hard way—by getting burned. That’s a bit like learning about sex exclusively from pornography: distorted, unrealistic, and ultimately harmful. Organizational life, like real life, is messier.

This article is not a how-to manual for manipulation. It’s a guided tour of the organizational zoo—illustrating political behaviors as they are commonly practiced, both admirable and Machiavellian—so managers can at least recognize the species roaming around them.


Goal Setting: The Politics Behind the Numbers

At face value, goal setting seems simple. Managers set reasonable targets, deliver results, get rewarded—or learn from failure. Clean. Rational. Almost comforting.

In reality, goal setting is often a political negotiation disguised as a planning exercise.

In highly political organizations, there are usually two scripts. The official script—the budget cycle, investor presentations, strategic plans—is written for “the street”: analysts, shareholders, and senior executives who need reassurance. The real script emerges later, as deadlines approach and reality intrudes.

Politically astute managers know this. They rarely take goals at face value.

Some under-promise and over-deliver. Others under-promise, then renegotiate once expectations soften. Some quietly agree to ambitious targets to calm the CEO, only to “manage the glide path” later with carefully timed explanations. Being fully realistic upfront, paradoxically, can be the riskiest move of all—it invites pressure before there is room to maneuver.


Managing Your Boss (Without Saying “No”)

Another unspoken discipline in the zoo is managing upward.

One common tactic is unwavering support. Some managers back their boss publicly at all times—right or wrong—earning a reputation for loyalty that can be invaluable in political environments.

There is also the art of selective transparency. Sometimes your boss genuinely does not want to know certain things, especially if the knowledge could implicate them. Yet there are moments when pushing uncomfortable information upward protects you from becoming the eventual scapegoat.

Over-involving your boss can be equally strategic. Flooding them with detail clarifies obstacles without explicitly refusing instructions. Expectations are adjusted—without anyone ever saying “no.”

Disagreement, too, is rarely direct. “Yes, but…” statements, foot-dragging, and tacit coalition-building with more powerful allies are time-honored methods. And when bosses are deeply unpopular, employees may simply execute instructions literally, knowing the outcome will speak louder than dissent ever could.


Ted and the Cost of Being Honest

Consider Ted, a project manager at a company we’ll call 3Q.

3Q promises product upgrades every three quarters and almost never delivers. Yet the company outperforms competitors. The atmosphere is aggressive, employee satisfaction is low, and project managers churn at 20% annually. Still, people are paid well, and firings are rare.

Ted comes from the military. For him, a commitment is sacred. 3Q is his first exposure to civilian project management.

Faced with impossible deadlines, Ted has options. He can resist and be labeled a naysayer. He can accept commitments and pass the blame later. He can hide risks in ambiguity. He can slowly reveal problems when the organization seems “ready.” Or he can overwhelm his boss with detail until alignment is forced.

Ted chooses honesty.

“I’m a straight shooter,” he says. “This project needs five quarters.”

Ted is reassigned to a minor supply-chain project. Six months later, he leaves the company.

In the organizational zoo, truth without timing is rarely rewarded.


Coalitions, Closures, and Quiet Revenge

Now consider a different enclosure.

Paul Wight, Head of R&D, is instructed to downsize by 30% and close one of four global sites. He calls all site leaders to Denver. The tension is immediate.

Chester Man, who runs the Manchester site, believes Paul dislikes time zones, travel, and early-morning calls. Denise Thibadeau, head of the Québec site, fears her location will be targeted due to language issues and Paul’s visible impatience on calls. Both assume bias. Neither trusts Paul.

Despite mutual dislike, Denise and Chester form a tactical alliance. They jointly propose taking responsibility for a profitable legacy product and a new platform—at remarkable speed and low cost. The timeline is knowingly optimistic. The plan is to “fix it later.”

They escalate the proposal directly to Paul’s boss, a European executive, effectively bypassing him.

Meanwhile, Paul asks HR to “build trust.” The result: a cooking class and a motivational webinar about a horse that runs faster while eating less.

The outcome? Vancouver is shut down. Manchester and Québec grow by 20%. Paul “moves on to his next assignment.” Denise is promoted into his role.

Politics 1. Process 0.


The Lesson No One Likes

Organizational politics thrive on mistrust, perceived bias, cultural friction, and coalition-building. They don’t disappear during restructuring; they intensify. And they don’t reward fairness—they reward awareness.

The uncomfortable lesson is this: when everyone in the room is a potential victim, consensus is unlikely. As one crude but accurate metaphor puts it, people will never agree on who deserves a second circumcision when they themselves are candidates.

Sometimes, leadership means deciding alone.

Welcome to the zoo.

Share Button