Skip to main content

Command Palette

Search for a command to run...

Early in my project management career, I thought my job was to keep people on schedule.

Why influence matters more than authority in project management

Updated
3 min read
Early in my project management career, I thought my job was to keep people on schedule.
A
I help organizations deliver complex programs across healthcare, government, and higher education. PMP-certified leader focused on PMO, modernization, Agile delivery, and program recovery. Sharing lessons from 13+ years leading enterprise initiatives.

I had a project plan.

I had status reports.

I had meeting agendas.

I had action-item trackers.

What I didn't have was authority.

The realization hit during a cross-functional initiative involving multiple departments, competing priorities, and a delivery deadline that wasn't moving.

A critical dependency was overdue.

I followed up.

Nothing happened.

I escalated.

Still nothing happened.

I scheduled another meeting.

Everyone attended. Everyone agreed. Nobody moved.

That's when I learned a lesson that no certification course had taught me:

Project managers are often responsible for delivery without having direct authority over the people doing the work.

Nobody on the project reported to me.

I couldn't change performance reviews.

I couldn't approve raises.

I couldn't reassign resources.

Yet leadership still expected progress updates from me.

For a while, I thought the answer was better process.

More tracking.

More documentation.

More meetings.

More reminders.

It wasn't.

The real problem was that I was trying to manage people when my actual job was to create alignment.

Once I understood that difference, everything changed.

Instead of asking, "Why isn't this getting done?" I started asking:

  • Does everyone understand why this work matters?

  • Does everyone agree on the priority?

  • Is there a hidden dependency blocking progress?

  • Are we solving the right problem?

  • What happens if we miss this deadline?

Those conversations produced more progress than any status report ever did.

Over the next several years, working across healthcare, higher education, and government programs, I saw the same pattern repeatedly.

The projects that struggled weren't usually suffering from poor schedules.

They were suffering from poor alignment.

People had different assumptions.

Different priorities.

Different definitions of success.

Different interpretations of urgency.

No project plan can solve that.

Only leadership can.

And leadership becomes most visible when authority is absent.

That's why I often tell aspiring Project Managers and Scrum Masters something that surprises them:

Your ability to influence people will matter more than your ability to manage tasks.

Tools can organize work.

Frameworks can structure delivery.

Certifications can teach methodology.

But none of them can create trust.

Trust comes from consistency.

Trust comes from understanding the business.

Trust comes from helping people solve problems rather than simply reminding them about deadlines.

Over time, I stopped viewing project management as schedule management.

I started viewing it as clarity management.

The most effective PMs I've worked with were not the ones who controlled the room.

They were the ones who reduced ambiguity.

They aligned stakeholders.

They facilitated decisions.

They surfaced risks early.

And they helped people move toward a common goal without forcing them to do so.

That is the part of project management that rarely appears in training materials.

And in my experience, it's the part that matters most.


More from Asif

I write about enterprise program delivery, governance at scale, and how to finish what you start.

More articles: asifsheraz.com/#writing

Case studies: asifsheraz.com/#services

Schedule a call: asifsheraz.com/#contact

PMP® Certified | 13+ Years | $52M+ Delivered

#ProgramManagement #Leadership #ProjectManagement #TeamLeadership #Influence