Leadership Starts with You: Why the Best Project Managers Lead by Example

There is no doubt that project managers need technical skills. We need to understand planning, risks, dependencies, governance, stakeholders, and sometimes even the technology behind the project. But technical knowledge is only part of what makes a good PM.

The other part is more personal. It is the willingness to step forward before asking others to do the same. It is about not simply assigning activities, but helping create the conditions for people to complete them successfully.

In other words, it is about leading by example.

Your Team Watches What You Do

A PM can talk about accountability, collaboration, transparency, and commitment. But the team will pay more attention to actions than words.

If I ask people to arrive prepared for a meeting, I need to be prepared too.

If I expect transparency about problems, I should be the first to admit when I have missed something.

If I ask the team to make an extra effort before an important deadline, I cannot disappear and wait for the final result.

This does not mean that the PM must personally complete every activity. It means being visibly committed to the same standards expected from everyone else. Leadership becomes credible when our behavior is consistent with our requests.

Understand Before You Ask

I often come back to a simple principle: I should not ask someone to do something that I am not willing to understand, try, or support.

A project manager does not need to be a software developer, legal expert, risk specialist, and business analyst at the same time. Our role is not to replace specialists.

However, we should understand what we are asking from them.

Before requesting an analysis within a very short deadline, we should understand what it involves. Before escalating a delay, we should investigate whether the problem comes from poor execution, unclear requirements, missing decisions, or an unrealistic plan.

There is a big difference between saying:

“We need this by Friday. Please find a way.” and saying: “I understand that completing this by Friday requires input from Legal and IT. I will help obtain the decisions you need.”

The first approach transfers pressure. The second creates shared responsibility.

Be the First to Step In

Projects often reach moments when everyone is waiting for someone else. Business is waiting for IT. IT is waiting for requirements. Risk is waiting for documentation. The sponsor is waiting for a recommendation.

In these situations, the PM should be the first person to step in.

Imagine that an important document is still incomplete two days before an approval meeting. The PM could simply send another reminder. Or the PM could consolidate the available content, highlight the missing information, contact the right people, and organize a short working session.

The PM is not doing everyone else’s job. The PM is removing the friction that prevents the team from completing it.

Being Available Creates Energy

Napoleon Hill wrote that we can succeed best and quickest by helping others to succeed.

I believe this principle applies perfectly to project management. When you genuinely make yourself available, people often respond with the same commitment. If you help a colleague prepare for a difficult meeting, that person will probably be more willing to support the project when a critical analysis is needed.

If you protect the team from unnecessary pressure while keeping everyone accountable, people are more likely to raise problems early instead of hiding them.

This should never become a transaction. It is about creating an environment in which collaboration becomes natural.

Availability generates trust. Trust generates openness. And openness helps the team identify problems while there is still time to solve them.

What Leading by Example Looks Like

Leading by example is usually visible in small, everyday behaviors.

1) When an activity is late

Instead of immediately asking who is responsible, start with: “What is blocking the activity, and what can I do to help?” Accountability still matters, but understanding should come before blame.

2) When the team makes a mistake

Do not distance yourself from the problem. Explain what happened, take responsibility for the project-level consequences, and help define the corrective actions. A PM who represents success but delegates failure will quickly lose credibility.

3) When the workload becomes intense

Do not ask for an extraordinary effort from a comfortable distance. Join the working sessions, clarify priorities, remove unnecessary activities, and protect the team from lower-value requests. Sometimes the best way to help is not to add more work, but to remove the work that should not be done.

4) When the project succeeds

Give visibility to the people who made the result possible. Recognize specific contributions and make the team’s work visible to senior stakeholders. The PM already has visibility because of the role. Good leaders use it to recognize others.

Being Supportive Does Not Mean Being Weak

Supporting the team does not mean accepting everything or avoiding difficult conversations.

A good PM can be supportive and demanding at the same time.

You can help someone solve a problem while still holding them accountable. You can listen to the team while still making an unpopular decision. You can admit that you do not know something while still providing direction. Saying, “I do not know, but I will help find the answer,” can create more credibility than pretending to know everything.

A Simple Question for Every PM

Before asking the team for something, I try to ask myself:

What am I personally doing to make this possible?

If I am asking for speed, am I removing unnecessary approvals?

If I am asking for quality, have I provided clear requirements and enough time?

If I am asking for transparency, do I react constructively when someone brings me bad news?

If I am asking for commitment, is my own commitment visible?

This question changes the way we approach leadership. It moves us from assigning work to enabling it. From controlling people to supporting performance. From managing a plan to helping a team deliver it.

Final Thought

The strongest project managers are not necessarily those who know every methodology or produce the most sophisticated documentation. They are the ones people want to work with again.

They are present when the project becomes difficult. They take responsibility before assigning it. They try to understand before judging. And they help others succeed without needing to be at the center of every success. Technical knowledge gives a project manager the tools to manage a project. Personal attitude gives the team a reason to follow. That may be the real difference between coordinating a group of people and leading a team.