Imad's Blog

When companies talk about change, the conversation often focuses on the new system, new process, new structure, or new strategy.

But there is another part of change that can be much harder: how people work together.

A company can have a good plan and the right technology and still struggle if teams do not communicate, departments work against each other, employees do not feel heard, or knowledge is not shared.

This is where I think managers need to pay attention to the human side of change.

Start With How the Team Works

When a team is struggling, the problem is not always the people on the team.

Sometimes it is how they work together.

Maybe one person controls every meeting. Maybe nobody wants to challenge the manager. Maybe responsibilities are unclear. Or maybe meetings end with a lot of discussion but no decisions.

Before changing the team, it helps to look at the process.

• How are decisions being made?
• Are people comfortable speaking up?
• Does everyone understand the goal?
• Do people know what they are responsible for?

Sometimes simply helping a team see these patterns can lead to improvement.

Give Feedback When It Matters

Feedback is another simple idea that is often handled poorly.

If there is a problem today, waiting six months to discuss it during an annual review does not help much.

Feedback works better when it is given close to the situation. It should also be clear enough that the person receiving it understands what happened and what could be done differently.

Managers should also make sure communication went both ways.

Instead of assuming someone understood, ask them what they took away from the conversation.

That small step can prevent a lot of misunderstandings.

Conflict Is Not Always a Bad Thing

Most managers would probably prefer less conflict at work.

But disagreement itself is not necessarily bad.

Someone questioning a process may be pointing out a real problem. Two departments arguing about responsibilities may expose an issue that has never been clearly addressed.

The goal should not always be to eliminate conflict.

The goal should be to understand why the conflict exists and what we can learn from it.

When emotions get too high, a neutral person may need to help both sides talk through the issue. That person should not pick a side. Their job is to help everyone understand the problem and work toward a solution.

Departments Can Have the Same Problem

The same issues that happen between two employees can happen between entire departments.

Anyone who has worked in an organization long enough has probably seen some version of:

• Sales vs. Operations
• IT vs. users
• Finance vs. everyone

Each group sees the business from a different point of view.

IT may be worried about security while an employee is worried about getting their work done. Finance may want tighter controls while Operations wants fewer steps.

Neither side is automatically wrong.

Good organizational change creates a way for those groups to understand each other's needs instead of simply defending their own.

Get the Right People in the Room

For larger changes, getting people together can be useful, but simply scheduling a meeting is not enough.

Who participates matters.

If every person in the room has the same job, reports to the same manager, or thinks about the problem the same way, you probably won't learn much.

Bring different perspectives together.

Leadership, managers, employees, and people from different departments may see completely different parts of the same problem.

Leaders also have to be willing to listen.

If employees believe management will argue with every criticism, they will eventually stop talking.

Don't Let Knowledge Walk Out the Door

Another part of organizational change that I think gets overlooked is knowledge.

Most organizations have at least one person everyone goes to because:

They know how that works.

That becomes a problem when that person leaves.

Important knowledge should belong to the organization, not just one employee.

Documentation, training, SOPs, shared systems, and knowledge bases are not exciting, but they can make a major difference.

A strong organization should be able to learn from its employees and keep that knowledge available for the next person.

Change the Plan When You Learn Something

Organizations also need to be willing to adjust.

A strategy can make perfect sense when it is created and make much less sense a year later.

Markets change. Technology changes. Customers change. Employees find problems that leadership did not expect.

Changing direction after learning something new does not necessarily mean the original plan failed.

Sometimes it means the organization is learning.

People Are Part of the System

One thing I continue to see in IT and management is that problems rarely exist in isolation.

People, processes, departments, technology, and leadership all affect each other.

That is why organizational change cannot only be about implementing something new.

Managers also need to ask:

• How are people working together?
• Where is communication breaking down?
• What conflicts are telling us something?
• Are we sharing what we learn?
• Are we willing to adjust?

Sometimes improving those things can have as much impact as the new system or process we originally thought would solve the problem.