Stepping into a project management role for the first time can feel overwhelming. You’re expected to deliver outcomes, manage people, tame risks, satisfy stakeholders, and somehow stay on time and under budget, usually with limited authority and imperfect information.
After 15+ years of managing projects across industries, I’ve collected principles of working some of which I offer below as practical advice to new PMs.
1. Your Job is Clarity, Not Control
Too many new PMs jump into schedules, Gantt charts, and status updates without deeply understanding what the project is supposed to deliver and why. Don’t move until you’ve understood:
Project objectives (measurable and agreed upon)
Key deliverables
Stakeholder expectations
Non-negotiables (time, scope, budget, quality constraints)
If these aren’t clear, you’re job is to get clarity on them that your stakeholders and team members agree upon.
2. Stakeholder Management Is Most of the Work
Project management is less about tasks and more about people. Map your stakeholders:
Who has power?
Who has interest?
Who can or is damaging your project quietly by disengagement?
Create a stakeholder influence grid even if it's a mental accounting exercise and not formally written down so that you can maintain regular engagement. Learn to listen more than you speak.
3. Your Timeline Is a Wish Until You Build It From the Bottom Up
Top-down deadlines are common (“We need this live by Q3”). That’s fine. But never build your real plan based solely on those dates. Instead:
Work breakdown structure (WBS) first
Estimate effort with the team
Use of three-point estimates (optimistic, likely, pessimistic) or Base Case / Best Case helps when there is disagreement on a single timeline estimate
Factor in risk and dependencies
Push back when the math doesn’t work.
4. Never Confuse Progress with Movement
Checking off tasks feels good. But a project can be 90% done on paper and 0% useful in reality. Focus on deliverables that produce value, not activity. Insist on:
Demos or deliverables instead of updates
Working features over reports
Outcome over output
5. The Project Plan is a Living Document
Plans break. If you treat your schedule as untouchable, you’ll either lie to yourself or lose control. Instead:
Re-baseline intelligently after major shifts
Update risks regularly
Track actuals and learn from variance
Adaptability is a must since change is certain.
6. You Must Learn to Say “No”—Diplomatically
You’re job is find options when facing choices and guide the team to the best decision. You can’t grant every wish. Saying “yes” to everything guarantees failure. Every choice has trade-offs and your job is to help illuminate those:
“We can do X by the deadline, or Y with better quality, but not both.”
“Adding that feature will require us to deprioritize something else. What would you suggest?”
This forces decision-makers to own the consequences.
7. Documentation Is Not Bureaucracy—It’s Insurance
You’ll encounter scope creep, finger-pointing, and selective memory. A written trail protects you and your team from future misunderstandings and disagreements on historical decisions. At minimum:
Clear meeting minutes with action items
Change request logs
Decision records
Assumption lists
Store them somewhere accessible and version-controlled.
8. Build Redundancy Into Everything
People get sick or go on vacation. Vendors ghost you. Simple tasks can be delayed as resources become constrained. Build in:
Buffer time
Backups for key roles
Alternate suppliers or tech options
Contingency plans for every major risk
Your job isn’t to avoid all problems—it’s to absorb them with minimal damage.
9. The Best Tool Is the One Your Team Actually Uses
You can spend weeks customizing your favorite project management or communication software tool. None of that matters if your team ignores them. Choose tools based on:
Team habits
Integration with existing workflows
Ease of use
Don’t worship tools—use them as means, not ends.
10. Your Success Metric is Delivery, Not Busy-ness
You will attend a mountain of meetings, process hundreds of emails, and deal with dozens of blockers. But your job is not to look busy. Your job is to:
Deliver value
Hit key milestones
Resolve impediments
Keep the team moving
Busy-ness is not impact. Don't confuse the two.
Final Thought
Project management is less about managing projects and more about managing reality—in all its messy, political, shifting landscape. Learn to navigate ambiguity. Develop a bias for communication. Stay calm when others panic.
And most importantly: never assume the project is on track just because no one is complaining.
Posts
No comments:
Post a Comment