If I could go back and talk to myself before becoming a project manager, there are a few things I would make painfully clear.
I’ve worked as an IT project manager for over eight years, managed projects ranging from $100,000 to $40 million, and earned over $300,000 in a single year, all while working remotely from places like Mexico, Peru, and Argentina.
I’ve seen the good, the bad, and the ugly.
This article breaks down the seven lessons I wish I had understood from day one — the realities of project management that most people only learn the hard way.
1. A Project Manager’s Job Exists Because There Is No Clarity
This might surprise you, but project managers are not hired into well-oiled machines.
They’re hired into chaos.
If you think a project already has:
-
Clear processes
-
Defined roles
-
Locked budgets
-
Established timelines
…you’re mistaken.
Most of the time, leadership only knows one thing:
“We need to do X.”
And X could be anything:
-
Launch a new application
-
Upgrade servers
-
Improve internal processes
-
Roll out new hardware
Your value as a project manager comes from making sense of everything quickly.
That means:
-
Organizing work on paper or in Excel
-
Thinking through what actually needs to happen
-
Executing tasks so progress begins
-
Tracking status so nothing slips
You will juggle dozens of moving parts at once:
-
Hiring resources
-
Notifying security teams
-
Managing vendors and contracts
-
Requesting budget changes
-
Ordering hardware
-
Updating stakeholders
If even one thing falls through, the project can fail.
That’s the job.
2. No One Has the Right Answer — You’re Expected to Figure It Out
One of the hardest early lessons I learned was this:
There is no one you can go to for the “correct” next step.
On one of my first major projects at a large bank, I was managing a massive Windows 7 to Windows 10 upgrade across hundreds of branches in the U.S. and Canada.
I asked my portfolio manager a simple question:
“Is there a tool we can use to automatically communicate installation dates to all branch managers?”
The answer?
“No. You’ll have to email or call them.”
That was it.
So I figured it out.
I built an automated email system using Excel macros and VBA.
The lesson was clear:
-
The company hadn’t done this before
-
The process didn’t exist
-
And I was still expected to move forward
If you rely on others to tell you exactly what to do, you will struggle as a project manager.
PMs must be self-starters and relentless problem solvers.
3. Tools and Technical Skills Are a Small Part of the Job
Before becoming a PM, I obsessed over tools:
-
MS Project
-
Excel
-
SharePoint
-
Jira
What I learned quickly was this:
In an eight-hour day, I might spend one hour in tools.
The other seven hours were spent:
-
In meetings
-
Writing updates
-
Following up
-
Communicating
-
Solving problems
Over 85% of the job is non-technical.
Yes, learn the tools.
But your success as a PM depends far more on:
-
Communication
-
Leadership
-
Organization
-
Time management
These are the skills that actually move the needle.
4. Authority Is Not Given — It’s Earned
I used to think that having the title Project Manager meant people would listen to me.
They didn’t.
The people on your project usually:
-
Don’t report to you
-
Have their own managers
-
Are more senior or more technical
You cannot order people around.
You must earn respect.
On a medical device project, I had to work with a 30-year company veteran who had built many of the internal systems we needed to upgrade. I had no industry knowledge and no validation background.
What changed everything was this:
-
I learned the quality and validation processes
-
I involved the right teams
-
I spoke their language
That showed I wasn’t just assigning tasks — I was invested.
The fastest way to earn authority is genuine curiosity and effort.
5. Projects Are Political (Whether You Like It or Not)
Projects are almost never universally supported.
Stakeholders have:
-
Competing incentives
-
Conflicting priorities
-
Different opinions
On one project, IT wanted to upgrade a 25-year-old legacy system. Engineering didn’t support it at all — they wanted to replace the system entirely in a few years.
As the PM, I had to:
-
Navigate resistance
-
Manage narratives
-
Address concerns from both sides
-
Continuously reinforce the why
If you’re not politically aware, you lose control of your project.
Being a PM means being politically savvy, not naïve.
6. You Are Always in the Hot Seat
Here’s a reality check:
If something goes wrong, it’s on you.
Leadership will not ask your team what happened.
They will ask you.
Early in my career, a shipment wasn’t sent to a branch. The technician showed up and couldn’t do the install. Money was wasted. Time was wasted.
When asked what happened, I blamed a coordinator.
That was a mistake.
The sponsor didn’t care.
The expectation was that I ensured everything was done.
From that moment on, I assumed complete ownership of outcomes — good or bad.
That’s the job.
7. Impostor Syndrome Never Fully Goes Away
Even after eight years, every new project still feels uncomfortable.
New industry.
New people.
New systems.
New regulations.
The feeling never disappears.
What changes is your confidence in your ability to:
-
Figure things out
-
Create clarity
-
Move forward anyway
Discomfort is normal.
If a project doesn’t scare you a little, you’re probably not growing.
As the quote says:
“A ship in harbor is safe — but that’s not what ships are built for.”
Would I Still Choose This Career?
Absolutely.
The pay.
The flexibility.
The remote opportunities.
The satisfaction of delivering real outcomes.
The challenges are real — but the rewards far outweigh them.
Project management isn’t easy.
But if you enjoy problem-solving, responsibility, and growth, it’s one of the most rewarding careers you can build.
