3 July 2025
The Real Job of a Project Manager
Most people think a project manager keeps things on track. But in reality, the best project managers ask the hard questions before anyone else does. They don’t just manage timelines—they shape direction, challenge assumptions, and create clarity where there was none.
Piyorot Piyachan
CEO of Mutrack
I’m Here For a Reason, to Fill the Gaps Others Overlook.
The title "Project Manager" carries a sense of grandeur. A manager—someone in charge, someone knowledgeable, someone who determines the course, someone everyone depends on. But in reality, it's not always like that.
"Project Manager" also carries a sense of isolation (because there is no one else), powerlessness (because no one works under me), lack of knowledge (in technical matters), and a duty-bound existence (because I have never once set the final deadline myself). This is the reality, every single time.
In normal settings and situations, the project manager is invisible. Why? Because in the typical definition, this person is only responsible for writing plans, following up tasks, organizing meetings, sending and replying to emails, taking notes, and handling complaints no one else wants to own. In this kind of situation, if everyone communicates well, understands each other, works together as a team, upholds standards, and behaves professionally, I should be completely invisible.
Even in 2025, this "normal situation" rarely happens. Teams don't want to be teams. People avoid communication. And there's always work no one wants to do. That’s why I am so desperately needed. So much so that if I’m not in the equation, nothing moves forward. If I don’t show up, there is no team. If I don’t intervene, conflicts grow. But every time I stop and reflect with honesty, I ask: Why am I here, really?
Everyone else at the table or on the Zoom call can answer this easily:
1
"I'm a dev, so I write code."
2
"I'm QA, I test things."
3
"We're product, so we define requirements."
4
"I'm DevOps, I handle cloud infrastructure."
But what about me? What do I do? Where is the value I bring? Planning, following up, organizing, note-taking, and doing the things no one else wants to do? Do these activities require special skills? Are there things I can do that others can't? Answering without bias: No.
Anyone who knows Excel can make a plan. Anyone who understands Jira can follow up in Slack. And everyone can write an email. Even the most unwanted tasks—if someone must do them, they will. Again, honestly, anyone can do this job.
So what am I doing here? In this meeting? When I look closely, I am easily replaceable—until I understand one of the most important principles:
When Breadth Matters More Than Depth
While most believe a project manager should dive deep into every detail, draw comprehensive Gantt charts, send out 20 emails a day to coordinate 50 tasks, or respond to every chat within five minutes—that is the fastest path to becoming someone easily replaced. Deep, detailed, and instant.
But if we want to be better, to bring more value, to elevate the standard of "Project Manager," we must do the opposite. We must learn to focus on being broad, forward-looking, and grounded.
Believe it or not, 95% of people in the team are trained to focus on depth, detail, and immediacy. The word "focus" is commonly defined to mean narrow, now, and self-oriented:
1
"This is my task and I know every detail."
2
"This is my current issue and I need to solve it by Wednesday."
3
"This is my deadline and I’m fighting other teams to prove who’s the bottleneck."
Everyone is diving into details, staring at Jira tasks, Notion boards, Excel trackers, or whatever tools they use. Everyone is deep into writing requirements, arguing over test cases, rescheduling sprints, assigning owners, moving deadlines, and reorganizing lanes.
If we, as project managers, are merely listeners, note-takers, followers, or mediators, we’re being sucked into the vortex of depth, detail, and urgency. But if we listen and then ask the kind of question that makes everyone stop talking, if we observe and then pose a question no one is prepared to answer, we are fulfilling our true role.
Because our questions are broad, long-term, and steady. They require synthesis of thoughts that people aren’t trained to do. They provoke thinking in ways teams rarely expect.
We don’t create value by knowing more. We create value by stepping back to see what others can’t. It’s a rare skill. A difficult one to master. And it requires a kind of quiet courage that’s hard to find in this day and age.
Because we see what others don’t, we earn our seat in that room. We become valued not because we know more technical details, but because we ask better questions, capture insights more clearly, and dare to challenge assumptions the team has long held without question.
What’s the Objective?
"Before we talk about anything else, can someone please tell me—what is the objective of this project?"
We must ask this question every time a project kicks off. It sounds simple, direct. But in our experience, it’s the question that generates the most silence in any room. And that silence? That’s the sign we’re looking for.
Because if the team can’t answer this, then the plan has no true destination.
When a Simple Question Becomes a Trap
Picture a typical kick-off meeting. Everyone's present: devs, QA, product manager, perhaps even an executive dropping in. Everyone expects the usual questions:
1
Who is doing what?
2
What’s the deadline?
3
What’s the definition of done?
4
Which tools will we use to track progress?
But those are not the right starting points. And that’s not the kind of project manager we want to be. So we ask again—clearly, calmly:
"What is the objective of this project?"
The Dangerous Vagueness
"Uhh… to build a new system." "To serve a new segment of customers." "To improve performance." "To deliver according to the roadmap." "Because the board wants it."
These answers sound logical but they aren’t objectives. They are expected outcomes, or politically safe responses. Words like "improve," "add," or "support" lack direction, scope, and measurable anchors.
If we can easily answer when a project will end but can’t answer why it began, we are already in trouble.
Unclear objectives lead to vague scopes, competing priorities, bloated expectations, and exhausting misalignment. And when we reflect with professional honesty, we must ask: will we really let this happen and say nothing?
If our objective is unclear, we are working in the dark—no matter how solid the requirements seem or how capable the team is. The same problems always return:
1
Scope expands endlessly to please every stakeholder.
2
Everyone believes their work is "top priority."
3
The team overcommits because no one dares to cut.
4
Meetings become more frequent, yet no one knows what we're actually trying to achieve.
That’s why we ask the question early. Not to delay, but to protect the project.
Freeze the Details
Why don’t people answer this question?
Because the real answers aren’t pretty. Sometimes it’s "because leadership said so." Sometimes it’s "because we inherited half-baked work." Sometimes it's just "no one was brave enough to cancel it."
And many times, the objective doesn’t exist yet. Because the real conversation hasn’t happened: What problem are we solving? For whom?
The danger isn’t in having no answer. The danger is pretending we do.
So we must pause everything—before timelines, sprints, phases, milestones, Jira boards, Slack channels, email threads, and weekly status meetings. We stop, not to slow things down, but to give the project a chance to go somewhere meaningful.
Because if we skip this now, we’ll revisit it again in a month. And the next. And by then, it will no longer be a question—it will be frustration, blame, and burnout.
The Courage to Ask
Anyone can run a kickoff meeting. Anyone can assign tasks, write in Notion, or summarize in an email. Anyone can chase a partner or file a request.
But the harder job, the real job of a project manager, is asking the right question at the right time—the kind of question that silences a room and wakes people up.
The real job of a project manager isn’t managing tasks—it’s creating clarity, asking the right questions, and guiding the team toward a meaningful objective. 🐦
We know that objectives are rarely placed neatly on the table. They aren’t written on the first slide. They don’t sit clearly in one person’s head. They’re often scattered across half-sentences, vague comments, or hidden in silence.
That’s why we help teams uncover them—not with instructions, but with questions.
We don’t ask: "Who is doing what?" We ask: "If this project truly succeeds, what changes for the user?"
We don’t ask: "When is the release date?" We ask: "What must not be missing if we’re to call this a success?"
We don’t begin with: "How many weeks for testing?" We ask: "What if we finish the project and no one uses it—is that still a success?"
We don’t just ask: "Which sprint is this feature in?" We ask: "How does this align with our team or company’s long-term direction?"
We’re not here to answer everything, but to ask what no one else is asking. We ask not to extract answers, but to create space for shared understanding to emerge. And when someone finally says something that resonates, we catch it, shape it, clarify it—until everyone sees the same thing, clearly.
Because sometimes, the objective was there all along. Just waiting to be spoken aloud.
This Is the Real Job of a Project Manager
We’re not here just to deliver projects. We’re here to give them meaning, direction, and clarity.
In the early days of a project, we may not be the smartest or the loudest in the room. We’re not the ones who make the final decisions, write the most code, or design the best interfaces.
But what we must bring is courage. The courage to think differently. Ask differently. Act differently. And respond differently.
The courage to stay still when others want to rush. To ask when others want to skip. To speak when silence feels safer.
Because if we are brave enough to see what others don’t, and to say what others won’t—we help the team reach places they’ve never reached before.
Not by keeping the project on track. But by making sure the track leads somewhere that matters.
And in a world where anyone can run a meeting or send a follow-up, we become irreplaceable—because we choose to see, to ask, and to stand where others don’t.
Continue Reading
15 January 2025
Piyorot Piyachan
CEO of Mutrack
26 September 2024
Piyorot Piyachan
CEO of Mutrack
20 August 2024
Piyorot Piyachan
CEO of Mutrack