vvvvvvvv

Personal reflections from my PM certification journey

Why I'm Writing This

I'm documenting my journey into project management—not just to remember what I learned, but to track how my understanding evolves. These are my personal takeaways, the "aha" moments, and the concepts I want to revisit as I grow in this field.

Career Paths: More Options Than I Realized

One thing that surprised me: "Project Manager" isn't the only path forward. The skills I'm learning apply to so many roles I hadn't considered:

Operations Manager
Program Coordinator
Project Analyst
Scrum Master
Even Product Owner roles

My takeaway: I need to read job descriptions, not just titles. If I see phrases like "coordinate resources," "manage stakeholders," or "monitor project execution"—that's a PM role, whatever they call it.

Note to self: When job hunting, search for skills I'm building (coordination, stakeholder management, process improvement) rather than just "project manager."

The Four Core Skills I'm Focusing On

After going through the material, four skills keep coming up. These feel like the foundation:

1. Enabling Decision-Making

I'm not the sole decision-maker—I'm the person who gathers the right information so the team can decide quickly and confidently. It's about removing ambiguity and presenting options clearly.

2. Communication & Escalation

This one's huge. I need to get comfortable with:

Documenting plans and changes
Sending regular status updates (even when there's "nothing new")
Knowing when to escalate issues before they become crises

Reminder: Over-communication beats under-communication every time.

3. Flexibility

Plans will change. Always. My job isn't to prevent change—it's to adapt smoothly and help my team stay focused when things shift.

4. Organization

Track everything. Use spreadsheets, project trackers, whatever works. Nothing should slip through the cracks because I wasn't organized enough.

What Value Do I Actually Bring?

This was important for me to understand. As a PM, my value isn't just in checking boxes—it's in:

Focusing on the customer:
Ask "why" repeatedly until I understand their real problem, not just what they're asking for. Their stated request isn't always the actual need.

Building great teams:
Match skills to tasks. Empower people to make decisions. Make sure everyone feels valued and knows how their work connects to the bigger picture.

Fostering relationships:
Check in daily. Communicate the big picture. Help team members see their impact on the final goal.

Breaking down barriers:
Remove obstacles. Advocate for resources. Challenge "we've always done it this way" thinking.

My reflection: The interpersonal stuff matters just as much as the technical project management skills. Maybe more.

Working with Cross-Functional Teams

This is where it gets real. I'll be coordinating people from different departments, with different expertise, working toward one shared goal.

What I need to remember:

Clarify goals clearly - Make sure everyone understands their role and the common objective
Get the right skills - Ensure the team has what's needed to succeed
Measure progress visibly - Show the team how much they've accomplished
Recognize all contributions - Especially the ones that get overlooked (like finance securing funding, not just the engineer solving the problem)

Note: T-shaped professionals = people who collaborate across functions while contributing their specific expertise. That's the team I want to build.

Job Search Buzzwords I Should Use

When updating my resume or searching for roles, these terms matter:

Coordination & stakeholder management
Leadership & team building
Risk assessment & mitigation
Process improvement & development
Budget monitoring & resource allocation
Strategic planning & execution

Important insight: I already have PM experience from past roles, even if they weren't titled "Project Manager." That teaching role? Curriculum design = project planning. Managing a classroom = resource management. Leading a student group = coordinating a cross-functional team.

The Roles and Responsibilities

Here's what I'll actually be doing day-to-day:

Planning & Organizing:

Using productivity tools and creating processes
Developing timelines, schedules, and documentation
Maintaining project documents throughout the lifecycle

Budgeting & Controlling Costs:

Monitoring the budget
Tracking issues and risks as they arise
Managing quality by mitigating problems
Removing barriers to progress

Managing Tasks:

Tracking what needs to be accomplished and by when
Keeping the team's workload balanced
Demonstrating progress to stakeholders

The Interpersonal Side:

Teaching and mentoring team members
Building relationships with everyone (team, stakeholders, vendors)
Controlling change while protecting the team from constant rework
Empowering the team to make decisions
Communicating status and concerns clearly

My realization: The interpersonal responsibilities are just as critical as scheduling and budgeting. Maybe more so.

What I'm Taking Forward

As I continue this journey, here's what I'm keeping front of mind:

Network intentionally - Connections matter in PM roles
Stay flexible with change - It's constant, so embrace it
Communication solves most problems - Before they escalate
Read job descriptions carefully - My skills apply to more roles than I think
Trust the process - I have more relevant experience than I realize

The best project managers don't just manage tasks—they build trust, remove friction, and help teams do their best work.

That's the PM I want to become.

These notes will evolve as I learn more. This is just the beginning.