You Can't Lead People You Never Take Time to Know

You can know every performance metric your employee has and still know absolutely nothing about what makes them tick.

Think about that for a second.

We spend hours reviewing performance reports, setting goals, measuring productivity, and evaluating whether someone is meeting expectations. But how often do we actually take the time to understand the person behind those numbers?

Throughout my career in education, operations, and sales leadership, one thing has become increasingly clear to me: you can't effectively lead someone you haven't taken the time to understand.

And no, I'm not talking about becoming everyone's best friend.

I'm talking about understanding what motivates people, what challenges them, and what they need from leadership to be successful.

People Aren't All Motivated by the Same Things

Here's something that seems obvious but gets overlooked constantly.

Not everyone is motivated by money. Not everyone wants recognition in front of the entire team. Not everyone thrives under pressure, and not everyone responds well to the same coaching style.

Some employees want opportunities to grow. Others value stability. Some appreciate direct feedback, while others need time to process information before having a productive conversation.

Yet organizations frequently approach leadership as if every employee came with the same instruction manual.

Set the expectations. Establish the metrics. Evaluate the results.

Done.

Except people don't work that way.

A leader who understands what motivates each person can make better decisions about how to support them. That doesn't mean lowering expectations or creating different standards for everyone.

It means recognizing that consistent expectations don't require identical leadership approaches.

Performance Numbers Don't Tell the Whole Story

I believe in accountability. I've spent plenty of time working with performance metrics, dashboards, and organizational goals.

Numbers matter.

But numbers don't always explain why something is happening.

Imagine an employee who has consistently performed well suddenly begins missing deadlines.

One approach is to immediately address the missed deadlines, document the performance decline, and demand improvement.

Sometimes that's necessary.

But what if something changed in the employee's workload? What if priorities became unclear? What if a process that previously worked is now creating unnecessary obstacles?

And yes, sometimes personal circumstances affect professional performance.

A leader doesn't need to know every detail of someone's personal life. Employees deserve privacy.

But there's a difference between respecting boundaries and never bothering to ask whether someone has the resources and support they need.

Accountability tells us what needs to improve. Understanding helps us determine how to improve it.

We need both.

The Five-Minute Conversation That Never Happens

One of the simplest leadership tools doesn't require software, a committee, or a new initiative.

It's a conversation.

Not another meeting where leadership does all the talking.

A real conversation.

Ask an employee what's working well. Ask what's making their job harder than it needs to be. Ask whether there's something they wish leadership understood about their responsibilities.

Then do something that can be surprisingly difficult.

Listen.

Don't immediately defend the current process. Don't explain why things have always been done a certain way.

Just listen.

You might discover a problem that's been costing your organization time for months. You might identify an employee who wants additional responsibility. Or you might learn that a small change could remove a daily frustration.

Of course, not every suggestion can be implemented.

But employees are much more likely to share useful information when they believe leadership genuinely wants to hear it.

Relationships Don't Replace Accountability

I want to be clear about something.

Getting to know your employees doesn't mean avoiding difficult conversations.

In fact, I believe strong professional relationships can make those conversations more productive.

When employees understand that feedback is intended to help them improve rather than simply criticize them, they're more likely to engage with it.

That doesn't eliminate disagreements. It doesn't guarantee everyone will respond positively.

But it creates a foundation of trust.

And trust matters when decisions are difficult, resources are limited, or expectations need to change.

Leaders should be approachable without being inconsistent. Supportive without ignoring problems. Understanding without abandoning standards.

That's not always easy.

But leadership was never supposed to be easy.

Make Time Before There's a Problem

Here's where I think organizations get things backward.

We often make time for employees when something goes wrong.

A missed deadline. A complaint. A performance concern. A resignation.

Suddenly, there's time for a meeting.

What if we invested some of that time before problems developed?

What if regular conversations were part of how we led people instead of something reserved for performance reviews?

You don't need an elaborate program.

You need consistency, genuine curiosity, and the willingness to follow through when someone raises a legitimate concern.

Because the people doing the work often understand the obstacles better than the people reviewing the reports.

Final Thought

You can manage tasks without knowing people.

You can measure performance without understanding motivation.

You can even achieve short-term results through policies, pressure, and accountability alone.

But if your goal is to build a team that trusts leadership, solves problems, and wants to contribute to something bigger than a checklist, relationships matter.

The best leaders don't just know what their employees do. They take the time to understand what helps them succeed.

So here's my question:

When was the last time you had a conversation with an employee that wasn't about what they needed to get done?

When was the last time you had a conversation with an employee that wasn't about what they needed to get done?