How to see the system behind the people
Eric Connelly · April 1, 2026
You like to decide and act. Fast, clear, efficient. Very useful when there is a crisis or when people are new.
You like to share what you know. You explain, give context, tell stories. Very useful for building knowledge over time.
You look at the bigger picture before acting. You ask questions, understand the situation, then decide. Very useful when things are complex.
Organization development consultant. 20+ years working with leaders in the US and Europe. Master's in Organization Development, American University (Washington DC). Engineering background before that.
Based here in Burgundy. American. I help organizations understand what is really happening under the surface.
"Jean doesn't communicate well with the other team."
"There is no meeting, no shared tool, no process for the two teams to talk. The structure makes communication difficult."
"The project is late because people are not motivated."
"People report to department heads, not the project manager. Promotions come from department work, not project work. The reward system does not support the project."
Six places to look when something is not working. A diagnostic tool for organizations.
What is our mission? Does everyone agree?
How do we divide the work? Does it fit what we need?
How do people work together? How is conflict handled?
Is someone keeping all the boxes in balance?
Do incentives match what we need people to do?
Do we have the right meetings, processes, and tools?
Your school, a part-time job, a sports club, a restaurant you worked at. Any organization.
Go through the six boxes. Where is the organization strong? Where is it weak? Which box causes the most problems?
Be ready to tell the class: "We looked at [organization]. The biggest problem is in the [box] because..."
"How do we divide up the work? Does the structure fit what we need to do?"
By function: departments of specialists (engineering, production, sales). By project: teams built around one output. Matrix: a mix of both - people have two bosses.
Work falls between departments. Nobody owns the problem. Decisions go up the hierarchy and come back slowly. The structure was designed for a different challenge.
Functional structure = deep expertise but slow coordination. Project structure = fast coordination but you lose expertise. Every structure solves one problem and creates another.
The case you are about to read is exactly this problem: a functional company that needs to run a cross-department project. How should they organize it?
"How do people and departments work together? How is conflict managed?"
Some conflict is healthy - it means people care about different things. The question is not "how do we avoid conflict?" but "how does the organization handle it?"
When a project manager needs work from people in another department, who decides? The project manager or the department head? This tension is at the heart of most organizational conflict.
When two people in your group disagree about the approach, what happens? Does the strongest personality win? Does someone mediate? Does the teacher step in? That is the relationship system.
One character says: "Nobody's going to come into my department and tell my people what to do." How would you manage that relationship if you were the project manager?
"Do the incentives match what we actually need people to do?"
Rewards include salary, but also promotions, recognition, interesting work, and learning. People do what gets rewarded - not what the company says it values.
If you want teamwork but promote individuals, people will work alone. If you want innovation but punish failure, people will play safe. The reward system shapes behavior more than any speech.
A teacher says "collaboration is important" but gives individual grades. What do students actually do? They work alone. The reward system wins every time.
Engineers get promotions from their department heads, not the project manager. So when the project needs extra effort, who do they prioritize?
A defense electronics company has won a big government contract. They need to build an advanced spy system called "Spyeye."
The problem: four different departments need to work together. The President must decide how to organize the project.
If Atlas goes over budget, the extra cost comes from their profit - dollar for dollar.
If they deliver late: $20,000 penalty per day.
If the system does not meet requirements: penalties up to $8 million.
But if they do it well: bonus for beating the budget.
President Skillton needs your recommendation. Each option solves one problem but creates another.
The Receiver Department manages the whole project. Other departments provide support. Everything stays in the normal hierarchy.
Led by Datson (55, department head, 25 years)
A cross-department coordination team. Workers stay in their departments. The project office gives guidance but cannot directly control people.
Led by Saunderson (45, delivered a similar project)
Pull people out of their departments. Create a new team just for Spyeye. The manager has full authority. Everyone works together in one place.
Leader: to be decided
Your group has one alternative. Focus on 3 boxes that matter most. Prepare a 3-minute pitch to President Skillton.
3 minutes per group. Convince the President.
What is your recommendation and why?
Which 3 boxes did you focus on?
Every option has problems. Show you see them.
While listening: find the one weakness they missed.
This case is from the 1970s. These exact problems exist in every company you will work for.
Every way of organizing solves one problem and creates a new one. When you see a recurring problem, look at the structure before blaming people.
In many jobs you will manage people who do not report to you. Or you will report to two bosses. This is normal. It requires influence, not just authority.
Most companies use some version of the matrix. Understanding this tension gives you a big advantage on day one.
Next time something goes wrong at work, before you blame someone, ask: what about the structure made this result likely?
When there is a problem, check which of the six boxes it lives in.
The official chart shows reporting lines. Draw how work actually flows. Compare.
These frameworks work in any language and any country. You practiced them today in English.