← Writing

A Company Is Organized Conflict

Departments in a company follow different goals, and the people working in them have their own goals, too. Decisions taken by escalation or by vote therefore often lead to nothing. What I try to do instead is to understand what the people involved need, so that we find an action everyone can commit to.

Most of us have seen projects in which everything was planned well, the organization as well as the technology, and still nothing moved forward. Usually the reason isn’t a bad plan. The people who have to implement the plan just don’t all want the same thing.

In this article I would like to explain why this is normal, and what you can do about it.

Different Departments, Different Goals

I like to say that a company is organized conflict. This may sound cynical, but I mean it as a description of how a company is structured.

Let’s say Marketing wants reach and speed, Finance wants to control costs and plan reliably, Legal wants to keep risks small, and HR wants the organization to stay healthy so that employees stay with the company. All of these goals are legitimate, and still they quite often pull in opposite directions. This isn’t a malfunction, though. A company needs all of these views, and a large part of management (and of Enterprise Architecture) is about organizing this conflict in a productive way.

In addition, departments consist of people, and people have their own individual goals. One colleague wants to prove a point, another one wants a quieter quarter, and a third one wants the project they once proposed to become a success. If you only look at the org chart and the official goals of the departments, you’ll miss a lot of what is going on.

Two Common Ways to Solve a Conflict

When goals collide, most organizations choose one of the following two approaches:

  1. They escalate to a decision-maker. The conflict is pushed upwards until someone who is senior enough picks one side.
  2. They escalate to a committee. All stakeholders are invited, there is a vote, and the majority wins.

Both approaches lead to a decision. Yet, in both cases the people who have been overruled leave the room with little or no commitment to the result, as nobody has convinced them. In the best case they comply. In the worst case the plan gets delayed in many small ways, and afterwards it’s hard to tell where it got stuck.

This is how you end up in the situation I described at the beginning: everything has been planned well, and still nothing moves.

Understanding Enlarges the Solution Space

There’s a third approach. It takes more time at the beginning, but it saves much more time over the lifetime of an initiative: you increase the number of possible solutions until you find one which everyone involved can support.

To do this, you need to understand the people involved, and I mean the need behind the position they defend as well as the position itself. Positions often conflict with each other, while the needs behind them can be combined in many cases. Two people who argue about the same option can often both be happy with a third option, which neither of them had seen before, once you understand what each of them needs it for.

Abraham Lincoln is supposed to have said: “I don’t like this man. I must get to know him better.” I think this describes the approach quite well.

In practice this means the following:

  • Spend time with people, ideally one to one. People rarely tell you about their interests in a meeting with twelve participants.
  • Ask questions about what has been said, so that you understand what was meant. Most people tell you what they demand, and you need to find out why they demand it.
  • Look for the need behind the goal of the department and behind the personal goal. Both exist, and a good solution has to consider both.
  • Invest in empathy. The better you understand someone, the less time the whole process takes. Many people consider this the soft part of the work, but I would say it is the part which speeds things up the most.

Once you see where the needs of the people overlap, more solutions become possible. In most cases you’ll find a superordinate goal in there, which means a goal everyone considers more important than the local conflict, and an action which supports this goal and which every party can commit to. The following picture shows the idea:

Understanding enlarges the solution space Marketing Finance Legal Shared action a superordinate goal everyone can carry Each circle also carries the individual goals of its people. Understand those, not just the department’s.

An Example

I remember a case in which two people in leading roles each explained what had to be done, and their proposals excluded each other. There was no option in the middle which we could have chosen as a compromise.

After working with both of them for a while, I understood that the conflict was only partly about the proposals. For one of them it was important to be seen as the person who had set the direction. For the other one it was important that their own ideas didn’t get lost, and that everybody could agree with the result. So we started with what both proposals had in common and made this the core of the solution. Then we added the remaining parts as what the core needed in order to work. After some smaller negotiations both of them accepted the result.

Most of what the two needed had little to do with the content of their proposals, but we wouldn’t have found the solution without knowing it.

Four Steps

When I find myself in the middle of such a situation, I try to follow four steps:

  1. Understand what has been said, what was meant, and which needs are behind it, for everyone involved.
  2. Find options in the overlaps which show up once these needs are on the table.
  3. Choose one of them: a common action which serves a shared, superordinate goal.
  4. Act.

I know this looks obvious when you read it. Yet, under pressure most organizations do something else. They jump right to step three by vote or by order from above and skip the understanding part completely.

Why Does an Architect Care About This?

You might expect an Enterprise Architect to mostly care about capabilities, data flows and target pictures, so basically about boxes and lines. And yes, I do care about these things. But I’ve seen well-reasoned architectures fail because the people who had to live with them never wanted them, and I have seen rather modest plans succeed because everyone involved had a stake in them.

This is why I treat understanding people as part of the architecture work. The structure of a company consists of processes and clearly assigned responsibilities, but also of the individuals who fill the roles, and each of them has their own goals. If you design a structure for the individuals and not only for the roles, chances are much higher that it still works a year later.

Conclusion

A company needs its conflicting goals, so the conflicts won’t go away. What you can influence is how you deal with them. Escalating or voting gives you a decision quickly. But if you want people to commit to the result, I recommend spending the time to understand what they need first, and looking for an action which serves a goal all of them share.