A new series is coming but this time not overloading like before. Just 10 posts for it.
The theme? Project management.
Until now, I’ve written and reflected on all sorts of different topics.
This time, I thought I’d write about something related to my earlier work, my profession. I want to share the experience. Maybe I can help some people turn back before it’s too late. At least, I can get them familiar with the language of project management.
Of course, I’m not going to share textbook definitions here.
Instead, I’ll bring in examples from real life. I’ll discuss skills and lessons that we can apply both in daily life and in project management itself.
In short: this is meant for everyone — so don’t run away just because it says “project management”!
What is a Project Manager?
At the most basic level, project management is about time, budget, scope… and COMMUNICATION.
But here’s the best definition I’ve ever heard — during an interview at one of the richest tech companies in the world, the interviewer described it perfectly:
👉 Professional Babysitting.
And honestly, there’s no better description.
You’re caring for a baby — trying to provide the best environment while constantly monitoring so they don’t bump their head, fall out a window, or get crushed.
You’re responsible for ensuring they grow safely and eventually stand on their own.
So if I were a boss, I’d prefer hiring a mother as a project manager!
In tech companies, project managers often get a bad reputation:
The annoying ones who constantly ask “Is it done yet?” or “When will it be done?” — acting as if they’re doing all the work themselves while never writing a single line of code or assembling a single component.
This creates tension, especially when the PM isn’t really embedded in the team.
Good, bad, and mediocre PMs are distinguished right here: at the human level.
A good PM must tailor their communication to each person.
They must understand people emotionally and frame their requests accordingly.
Even when a project is in trouble, they should avoid showing panic — much like how a parent who appears scared will cause their child to feel insecure.
And above all, a PM should never let on that they don’t know something.
They must ask even “stupid” questions — because trust and credibility aren’t handed to you: they’re earned.
Is Project Management Necessary?
Sometimes I think project management is unnecessary — but at the same time, it’s absolutely vital.
Contrary to what many believe, it’s not just a role where people sit around talking.
It requires a lot of skill — and communication is at the top of the list.
Because working with people is often much harder than launching rockets!
How I Got Here
In high school, the one thing I was certain about was that I didn’t want to deal with people.
So I ruled out social sciences, dentistry, medicine — my goal was to be an electronics engineer, focused on the science itself.
Well… that wish backfired, because even now I’m still trying to reach that goal!
I even pursued a master’s degree and was close to my goal… only to find myself suddenly working as a project manager in an industry I swore I’d never touch.
In that factory, the biggest challenges for me were the language barrier and my dislike for the industry itself.
But I tried to make the most of it.
Eventually, I tried to “return to my roots” by designing things and creating products that could generate profit.
And then — ironically — I got laid off because I wasn’t managing enough projects.
Project Management Methods in Context
Factory work was pure Waterfall:
You don’t move on until one task is fully complete.
That’s where I really learned what project management means:
- Managing crying stakeholders
- Pleasing customers and colleagues
- Addressing logistical hiccups
- Keeping things on track — all without blowing everything up.
After that, I promised myself I’d go back to being an engineer — but sure enough, the next company said:
“You’re an engineer, but you have project management experience — could you help with that too?”
Of course… and soon, organizational changes led me right back into being a full-time PM.
This time, it was a different environment: software and hardware development, not Waterfall but Agile —
basically, a “professional” version of “we’ll figure it out later”
The 5 Phases of Project Management (and Life)
There are five key stages to every project:
1️⃣ Initiation
2️⃣ Planning
3️⃣ Execution
4️⃣ Monitoring/Control
5️⃣ Closure
And then… celebration.
These stages apply to everything:
Whether you’re studying for an exam, raising a child, doing chores, or organizing a gathering with friends.
Initiation: The Most Important Phase
The Initiation phase is all about defining what you’re doing and why — who’s doing it, with what, for whom — and managing expectations properly.
Sadly, this phase is often overlooked.
Planning
Whether you’re running Waterfall, Agile, or some hybrid, planning is about:
- Understanding expectations
- Knowing your resources
- Defining requirements clearly
- Creating realistic work packages
- Identifying risks early
- Preparing mitigation plans
- Creating a solid schedule
Without this, it’s like raising a child without preparation:
You’ll exhaust yourself and things won’t go well.
Communication: The Core of Project Management
Sometimes I wish AI would just take all our jobs so we could finally relax.
Other times, I find myself laughing in the middle of meetings thinking, “We act like we’re saving the world, but this is all just noise.”
In my opinion, communication is the single most important part of project management.
It’s astonishing how much time gets wasted discussing issues that could have been resolved with a simple five-minute email.
Many people, even highly experienced ones, struggle to communicate clearly — they don’t articulate themselves, they don’t even realize they’ve completed tasks.
The PM must ask clear questions, clarify uncertainties immediately, and ensure everyone is aligned.
Execution and Monitoring
Execution is where things “should” go smoothly — until they don’t.
That’s why monitoring and control are essential:
- Regular check-ins
- Close follow-up on tasks
- Early detection of problems
Like changing a baby’s diaper before a rash develops, you must act before issues escalate.
Closure
Long projects often create emotional attachments.
Teams may struggle to “let go” — or worse, a poorly defined scope leads to endless requests and tweaks.
Closure requires a clear endpoint.
It’s essential to review:
- What was supposed to be done?
- What was actually done?
- Is everyone satisfied?
- Can we finally say goodbye?
Without this, time and money slip away endlessly.
Conclusion: Lessons Beyond Projects
If people took themselves and their titles less seriously, communication would be easier — and drama would fade.
In such a world, we might not even need project managers.
In theory, machines could manage initiation, planning, tracking, documentation, requirements, resources, and design.
The need for a project manager often exists simply because of human drama.
In the end, project management can feel like a “bullshit job.”
If you’re not deeply involved in the technical work, it might seem silly from the outside. That’s why I escaped from it and became a software engineer.
But the upside is this:
While the team is struggling to deliver, you might get to leave on time and enjoy life.
Still, a good PM should be able to motivate the team, even when enjoying that luxury.
Because if you act like a slave driver, your “team” might just rise up and strangle you!
bahadirhancicek 
Leave a comment