A Project Manager's Most Valuable Skill

I was 21 years old, working on a new project with another designer. Just another day at the office, early in the morning, when my manager came to my desk.

We started talking about the project, discussing a few changes and brainstorming solutions to some issues. While we were chatting, I noticed that he often glanced at the other designer, who wasn't part of our conversation.

What was he looking for? Was he checking if the designer was working? Was he concerned about something I didn't know?

He eventually turned to me and said, "Work on some ideas. We'll continue later."

Then he looked at the other designer and called her into a quick meeting.

Twenty to thirty minutes later, she went home, and he returned to chat with me.

"She was having some serious personal issues, so I sent her home for today and tomorrow. She might need more time, but I'll check again in two days."

I had no idea she was going through anything. It looked like a normal day to me.

He then explained something I'll never forget:

"Being a manager is 10% technical and 90% psychology."

Psychology at work

The ability to recognize when someone is having a bad day or feeling inspired helps you adapt your plans.

People won't always tell you what's going on in their personal lives, but sometimes you can notice it in their behavior. And it affects their work. If you ignore it for too long, it can eventually affect the entire team.

Imagine someone spending five days completely unfocused. Every task takes twice as long and probably contains more mistakes. Giving that person one or two days to rest could make a huge difference in their focus and productivity afterward.

Of course, this doesn't mean giving people a day off every time something goes wrong. Sometimes all they need is a five-minute break, a quick conversation to help them solve a problem, or a little encouragement to regain confidence in their ability to handle a challenge.

Paying attention to people's behavior can also reveal things that might otherwise go unnoticed:

• People who want to leave the company and are just waiting to find another job.
• People with great ideas who are too shy to share them with the team.
• Problem solvers who rarely speak during meetings.
• People who are there just for the money and have little interest in the problem or the team.

You won't know all these things just by looking at someone. But paying attention gives you a reason to ask questions, start conversations, and understand what's really going on.

There are plenty of managers who use tools they learned in management school:

• Team-building games.
• Brainstorming sessions.
• Pizza days or even beer to make everybody happy.

There's nothing wrong with these activities. The problem is assuming they will solve every team's problems.

Using tools is very different from understanding people's behavior. I rarely see these activities used at the right time or for the right reasons.

The team participates and pretends to enjoy it, but behind the scenes, everybody is thinking, "What a waste of time."

A team-building activity won't fix a lack of trust. A pizza day won't solve a problem with management. And another brainstorming session won't help someone who's afraid to share their ideas.

Sometimes, the problem isn't the tool. It's that the manager doesn't understand what the team actually needs.

Learning to read people

There's an important distinction between understanding who a person is and how that person is feeling.

Someone may be creative and technically skilled but rarely speak during meetings. Are they shy? Are they uncomfortable around certain people? Or do they simply have nothing to add at that moment?

You can't assume the answer. You need to get to know the person.

I once had a great designer on my team who only discussed ideas in the office, sitting in front of his computer. Everywhere else, he was quiet.

I started visiting his desk before meetings to collect his ideas beforehand. During the meeting, when the time was right, I'd bring him into the conversation.

"Hey, you mentioned a good idea to me earlier. Can you explain it?"

Even a short explanation was enough. I could help elaborate on the idea afterward.

The goal was to help him build confidence.

A few months later, I didn't need to invite him to speak anymore. He started sharing his opinions on his own.

I realized he wasn't necessarily shy. He just lacked the confidence to speak in front of other managers.

When I became a manager for the first time, understanding people's behavior became one of my top priorities.

It's not about making people like you. It's about making people trust you.

Think about a psychologist. You don't necessarily need to like them, but you need to trust them enough to feel comfortable sharing your problems.

The same principle applies to management. People need to feel comfortable telling you when something isn't working, when they disagree with a decision, or when they're struggling with a task.

Without that trust, you'll only see what people are willing to show you.

I once worked at a company where most employees liked their team but hated the company's owner.

Every time the owner entered the office, I could see a shift in everyone's behavior. The owner micromanaged people and constantly overstepped boundaries, not just with my team.

I managed to reduce some of the problems after a few conversations and by introducing new dashboards to improve visibility into the work. But it wasn't enough.

A few weeks later, two designers left the team.

I had recognized the problem, but the solution was beyond my control.

Without understanding their behavior, I could have blamed the designers:

• They weren't professional enough.
• They kept jumping from job to job looking for more money.
• They weren't loyal to the company.

But understanding the root cause answered the questions that mattered: Why did they quit? Why were they unhappy with the company?

I knew the answers.

And sometimes, knowing the answer doesn't mean you have the power to change it. But it does help you avoid blaming the wrong people.

Behavior over technical skills

Understanding people also helps when building your team.

I don't remember where I heard this, or if it was just a conclusion I reached myself, but I've always liked this advice:

"Hire for attitude, train for skills."

Technical skills matter, of course. But skills can often be taught. Changing someone's attitude toward learning, collaboration, or feedback is much harder.

If you've ever tried to change a habit, you probably know what I mean.

We've all had a coworker who was difficult to work with but extremely skilled at something the company needed. On the other hand, we've also worked with someone who didn't know much about a particular subject but was always eager to learn and easy to teach.

Which person would you rather have on your team?

The answer depends on the role and the situation, but technical skills shouldn't be the only thing you evaluate.

Behavior is also one of the first things you can observe when someone joins your company.

A new hire who never asks questions might be a red flag. But what does that actually mean?

Are they not interested in learning? Are they afraid of looking inexperienced? Or is the team ignoring them and not creating opportunities for them to ask questions?

Each situation requires a different response.

That's why observing behavior is only the first step. You still need to understand what's behind it before deciding what to do.

Managing change

As a production engineer, I implemented many changes in the companies I worked for. The biggest challenge was always getting buy-in from the team on the shop floor.

I always tried to maintain a good relationship with everyone in the company. When introducing a change, I had to look at it from their perspective.

Imagine introducing time tracking in a manufacturing environment. People might immediately think:

"They want to micromanage us."

"They want to know how many minutes we're working."

"They'll fire whoever isn't delivering enough."

These were valid fears, and they were things I actually heard throughout my career.

Because I understood what people were afraid of, I knew how to talk to them about the changes. I could explain the reasons behind them, address their concerns, and help them understand what would change and why.

This is where understanding people's behavior makes a real difference. You can have a perfectly reasonable improvement, but if the team sees it as a threat, getting them on board will be much harder.

There's one important rule I always follow: Never lie.

If a director above you wants to track time for the wrong reasons and you promise the team something else, you won't lose the director's trust. You'll lose the team's.

Once people stop trusting you, even a good change becomes harder to implement.

You don't need everyone to agree with every decision. But people deserve an honest explanation, and they need to know you're not hiding the truth from them.

So, what's a project manager's most valuable skill?

Leadership, time management, risk management, and stakeholder management are all important. But there's something that connects them all: understanding people.

You can have the best project plan, the best tools, and the most talented team. But if you don't understand the people you're working with, you'll eventually run into problems that no dashboard or methodology can solve.

You don't need to be a psychologist. You don't need to know what everyone is thinking, either.

Start by paying attention. Notice changes in behavior. Ask questions instead of making assumptions. Give people the space to speak, and make it safe for them to tell you when something is wrong.

Sometimes, the most valuable thing you can do as a project manager isn't to solve a technical problem or reorganize a schedule.

It's to notice that something is wrong before it becomes a bigger problem.