Analysing Conflicts

Conflict happens to all of us. It appears in families, friendships, offices, boardrooms, project groups and even harmless-looking WhatsApp groups that were originally created only to decide where everyone should meet for dinner.

Sometimes conflict arrives loudly, accompanied by raised voices, dramatic emails and sentences beginning with, “With all due respect…” At other times, it develops quietly through delayed responses, unexplained silences, changing expectations and meeting invitations that suddenly include six people we have never heard of.

Conflict can certainly bring out the worst in us. It can make sensible people defensive, impatient and strangely skilled at forwarding old emails to prove that they were right three months ago.

But conflict can also bring out the best in us. When approached thoughtfully, it forces us to listen, communicate honestly and examine situations beyond our immediate point of view. It can expose weak assumptions, unclear responsibilities and decisions that everyone had accepted simply because nobody wanted to ask an inconvenient question.

This is particularly true in consulting and business relationships.

When a Simple Project Becomes a National Mission

Every consultant who has worked towards delivering measurable results for a valued client has encountered difficulties. These may involve deliberate or unintentional scope creep, delayed feedback, internal political issues, unrealistic expectations, changing budgets or a sudden shift in priorities.

Frequently, new people also enter the client team midway through the assignment. They arrive with fresh energy, new ideas and no emotional attachment whatsoever to the work already completed.

A project that began as a simple website may gradually be expected to become a marketplace, a social network, a customer relationship system, a research platform and possibly a small digital republic—with the original budget remaining untouched.

Each additional request may appear harmless when discussed separately.

“Can we add just one more feature?”. “Could we also conduct a little additional research?”. “Would it be possible to redesign the interface once more?”

The word “little” has probably damaged more consulting budgets than inflation.

If such developments are not identified and addressed early, they can slow down a project, raise delivery costs, strain relationships or bring the assignment to an unfortunate end. Both consultant and client eventually become frustrated, although each side usually believes that the other created the problem.

Conflict Is Rarely About What It Appears to Be

On the surface, conflict may seem to be about a missed deadline, an unpaid invoice, an additional feature or disagreement over responsibility.

In reality, the visible disagreement is often only a symptom of something deeper.

A client demanding more work without approving a higher budget may be facing financial pressure. A senior executive repeatedly changing the project direction may be responding to internal politics. A new manager challenging previous decisions may simply be trying to establish authority.

A delayed approval may indicate uncertainty that nobody wishes to admit openly. It is often easier to say, “We need more analysis,” than to say, “We do not know what we want.”

The same pattern exists in social relationships. An argument between friends may appear to concern a cancelled dinner but may actually be about feeling ignored. A family dispute over money may really concern control, recognition or long-standing perceptions of fairness.

Human beings rarely enter conflict carrying only facts. We also arrive with fears, expectations, insecurities, memories and carefully rehearsed speeches.

Resolving a conflict therefore requires more than proving who is correct. In fact, proving that we are correct can sometimes be the least productive achievement available.

The real task is to understand what is happening beneath the visible disagreement.

Sitting on the Same Side of the Table

In managing successful client relationships, one principle has repeatedly proved useful: analyse the conflict carefully and approach the client with plausible solutions.

The objective should not be to defeat the client in an argument. Nor should a consultant silently agree to every request while privately preparing a nervous breakdown.

A wiser approach is to imagine that both sides are sitting on the same side of the table, looking at the problem together.

This change in perspective can transform the conversation.

Instead of saying, “The client is creating problems,” we might ask, “What has changed within the client’s environment?”. Instead of thinking, “They are asking for too much,” we could ask, “Have their business objectives changed since the project began?”

Several questions become important:

Has the scope expanded because the client has realigned its objectives?. Is there a political undercurrent influencing the new priorities?. Has a change in the client-side team altered the definition of success?. Are the new requests genuinely in the client’s best interest?. Can we find an approach that protects both the client’s objectives and our commercial interests?

These questions do not guarantee agreement. However, they allow us to move from emotional reaction to thoughtful analysis—which is usually a better place from which to send an email.

A Project That Grew New Limbs

One of my own work experiences taught me how quickly unresolved conflict can damage a promising project.

We had begun a web portal ideation and design assignment. Considerable effort had gone into defining objectives, methods and milestones. Timelines, costs and expected revenue opportunities had been discussed and consolidated. Approximately half the work had been completed, and the remainder was progressing.

At that stage, our management decided to involve additional members in the interaction circle. Their mandate was to guide the project further and improve delivery.

The intention was positive. Intentions, however, are not always accompanied by budgets.

Over the following month, the new team proposed several features, additional components and more research. Each suggestion sounded intelligent. Most suggestions also appeared essential when presented in a meeting.

Collectively, they represented nearly 50 percent more work, along with higher vendor costs and extended timelines.

Being a naturally “never-say-no” person, I initially responded with, “Of course.” The words left my mouth before the finance department inside my head had completed its calculations.

A few days later, I understood the full impact of my enthusiasm. The original schedule was no longer practical, the workload had increased considerably and the commercial viability of the project was weakening.

Resentment slowly entered the relationship. Every new call or email produced a small wave of irritation. Because the situation existed within my own organisation, I felt trapped. I wanted to deliver, but I had failed to establish limits when the additional demands first appeared.

Eventually, I faced the committee and proposed revised timelines and budgets. Unfortunately, by then, the conversation had become defensive. What should have been a discussion about changed requirements became a debate about commitment.

The project eventually reached a stage where it was called off.

The conflict ended, but no one won. The project disappeared, the work was wasted and everyone probably carried away a different explanation of what had gone wrong.

My explanation, naturally, was the most convincing to me.

The experience taught me that avoiding conflict does not eliminate it. It merely allows the conflict to grow quietly until it becomes large enough to require a committee.

Silence Is Also a Form of Communication

Another experience involved the assessment of a potential new venture.

After extensive research and several discussions, additional people entered the debate at a later stage. Eventually, the group decided not to proceed.

However, some of the people I had interviewed earlier continued contacting me about partnerships and memberships. Initially, I found it difficult to respond. The final decision was not mine alone, and I was unsure how much information I could disclose.

So, I became unresponsive.

Silence felt safer. Unfortunately, silence is rarely interpreted as “complex internal decision-making is underway.” It is more often interpreted as indifference, arrogance or avoidance.

When I eventually informed these people that the venture had been abandoned, some felt misled. Trust was damaged, and valuable relationships suffered.

Before the matter reached boiling point, I discussed it with the project sponsor. He explained that the venture remained interesting, but the group had limited patience and several other priorities required immediate funding.

The reasoning made sense internally. Yet those outside the decision-making circle had experienced only uncertainty.

This taught me an important lesson: people may accept disappointing news more easily than prolonged ambiguity. When we provide no explanation, they create their own—and their version seldom presents us as the thoughtful hero of the story.

Everyone Represents a Department

Several practical lessons emerged from these experiences.

People who can materially influence a project should ideally be involved from the beginning. When major decision-makers enter halfway through, they often reopen matters that others believed were settled.

Their roles must also be clearly defined.

A project team should not consist merely of departmental representatives guarding their respective territories.

The finance representative may wish to reduce costs. Marketing may request more features. Operations may prefer no change at all. Technology may explain why everything is more complicated than it appears.

Each department may be correct from its own perspective, while the project as a whole steadily moves towards disaster.

For example, a chief financial officer should not participate solely as a cost-cutting authority. The CFO should understand the commercial dynamics and help develop alternative financial models. The role should reflect a capital-building attitude, not merely that of an accountant whose natural response to every creative idea is to remove two zeros from the budget.

Similarly, a marketing leader should not insist on adding features simply because they look impressive. An operations manager should not oppose innovation solely because it disturbs established routines.

Every participant must balance departmental interests with the larger purpose.

There must also be one clearly recognised project leader with the authority to approve, postpone or reject changes. Without a final decision-maker, projects become democratic in the most dangerous sense: everyone can suggest, but nobody is responsible.

Conflict on the Retail Floor

The same principles apply in retail.

Imagine a menswear retailer planning to redesign a store. The sales team wants more display space. The accounts team wants lower expenditure. The inventory team wants larger storage areas. Marketing wants attractive experience zones. The tailor wants a proper consultation space, and the customer wants everything visible without having to walk more than six steps.

Each demand has merit. The conflict begins when nobody balances the competing priorities.

A successful design may require prominent displays for high-margin products, efficient storage for fast-moving inventory, disciplined spending and enough visual appeal to keep the store from resembling a warehouse with mirrors.

Conflict can also arise between a retailer and a customer.

Suppose a customer wants to return a tailored garment because the fit does not meet expectations. The retailer believes the measurements were approved and the item cannot be resold.

A defensive response would be, “You approved the measurements. Nothing can be done.”

A more thoughtful retailer would investigate. Was the measurement recorded correctly? Was the style of fit explained? Did the customer expect a slim fit while the tailor understood “comfortable” to mean that two additional relatives could fit inside the jacket?

Can the garment be altered? Can a practical solution preserve the relationship without causing an unreasonable loss?

Analysing the conflict does not mean surrendering to every customer demand. It means understanding the source of dissatisfaction before deciding how to respond.

Some Clients Are Lessons, Not Relationships

Not every conflict can or should be resolved.

Occasionally, repeated disputes reveal that a client is unreasonable, irresponsible or commercially unsuitable. A client who continually changes the scope, delays approvals, withholds payment and then demands urgency may not be worth keeping.

A detailed project proposal can prevent many misunderstandings. It should define the scope, deliverables, responsibilities, timelines, approval process, revision limits, payment terms and treatment of additional work.

Yet even the finest proposal cannot anticipate every human complication. Agreements are interpreted by people, and people are influenced by pressure, ambition, insecurity and the occasional desire to pretend that a previously approved decision was someone else’s idea.

The consultant must therefore combine contractual clarity with emotional intelligence.

Conflict Is Information

Conflict should not always be treated as a breakdown. It is also information. It tells us that expectations are misaligned, responsibilities are unclear, trust is weakening or circumstances have changed.

When recognised early, conflict allows corrections before the damage becomes permanent. Handled respectfully, it can strengthen relationships, expose hidden assumptions and improve the way future projects are structured.

The next time we face conflict with a client, colleague, customer, friend or family member, we should resist the temptation to react immediately.

We should pause, examine the people involved, understand the pressures influencing their behaviour and ask what may be happening beneath the obvious disagreement.

Then we can decide whether to clarify, negotiate, compromise, restructure or walk away.

Analysing conflict is not merely a consulting or project-management practice. It is a way of understanding human behaviour.

And in a world where every straightforward matter eventually attracts a meeting, a committee and a revised presentation, that understanding can make a world of difference.