One of the quickest ways for a new leader to get into trouble is to arrive with all the answers. I’ve noticed it when working with new leaders or with people transitioning into a new role or department.
You step into the role because someone believes you can lead. The organization may need to grow, change direction, or finally address problems that have been ignored for too long.
Long before the first day, most leaders are already thinking about what they would do differently. Experience brings ideas, instincts and, in some cases, a pretty clear plan for what should happen next.
Then you get the keys, and the natural instinct is to start driving. I’ve learned that’s usually when a leader needs to be careful.
A new leader doesn’t just inherit an organization. You inherit its history. Relationships existed long before you arrived. So did traditions, loyalties, disappointments, unwritten rules, expectations. People remember things they’re proud of, promises that weren’t kept, and decisions they still don’t understand. Some of those experiences may involve people who aren’t even there anymore.
The org chart can change overnight. Culture doesn’t. Over the years, when I’ve stepped into an existing organization or leadership situation, I’ve learned to do some version of a cultural audit. Nothing particularly complicated or formal. It starts with listening, watching, and asking good questions.
I want to know who people trust regardless of title, what gets celebrated, and what gets tolerated. The stories people tell about the organization’s best and worst days reveal a lot. So does understanding where trust has been built, where it has been broken, and what people are afraid of losing.
One of my favorite questions is some version of, “What does everybody here know, but nobody says out loud?” The answer can tell you more about an organization than the strategic plan.
It can also keep you from fighting old fights. Every organization has them. Departments may have spent years blaming each other. People may still resent decisions made long ago. Current relationships can be shaped by history the new leader knows nothing about.
That’s why I’m particularly careful when someone is eager to tell me who the problem people are. They may be right, but every story sounds convincing when you’ve only heard one side of it.
It’s surprisingly easy to inherit someone else’s conflict before you understand what actually happened. What looks like today’s problem may really be yesterday’s war.
That doesn’t mean a leader should be timid or spend months studying the organization while everyone waits for something to happen. Some situations require immediate action. If people are being mistreated, money is being mishandled, or the organization is in danger, leadership requires you to move.
But let’s be honest – most decisions aren’t emergencies. You usually have enough time to understand what you’re looking at before deciding what to do about it.
That can be especially difficult for experienced leaders. After you’ve led long enough, you recognize patterns faster. That experience is valuable, but it can also make you too certain that you’ve seen this problem before.
Sometimes you have. Other times, two organizations can have the same symptoms for completely different reasons. Experience should make us wiser without making us less curious. That curiosity also means noticing what’s working.
New leaders naturally see problems, particularly when fixing those problems is part of why they were hired. But if you enter looking only for what’s broken, you can damage something valuable before you understand why it matters.
The people carrying the culture may not have impressive titles. A tradition that looks inefficient from the outside may have deep meaning. Even a process that needs to change may have been created for a good reason. The previous leader probably got some things right, too. Honor that.
Acknowledging what came before you doesn’t diminish your leadership. People are paying attention to how you talk about what they helped build. If you suggest everything before you was wrong, longtime employees may hear something you never intended to say: You were part of the problem, too.
None of this means preserving everything you inherit. Leadership requires change. The question is why you’re changing it. There’s a difference between changing something because you understand what the organization needs, and changing it because you want everyone to know there’s a new leader in town.
I’ve probably been guilty of the second more times than I’d like to admit. There is pressure in a new role to establish yourself and prove the organization made the right choice. Under that pressure, activity can easily be mistaken for progress.
Sometimes the stronger move is resisting the need to immediately put your fingerprints on everything. Listen first. Learn the history. Understand the people. Figure out what should be protected and what needs to change. Then lead with conviction. That’s not slow leadership. It’s informed leadership.
Before you take an organization somewhere new, understand what you’re inheriting. The keys may be yours now. But the story started long before you arrived.
