Remember when you were a kid and played tag? You ran around breathless, slapping your buddy on the arm and yelling, “Tag! You’re it!” Then you sprinted away laughing before they could tag you back. It’s a fun game when you’re 8.
Absolute dumpster fire when you’re running a project worth millions, leading teams of adults who allegedly have professional titles, and the stakes aren’t recess-level; they’re career-level.
Yet somehow, in boardrooms and Teams calls across the world, project managers are playing that exact game. Tag. You’re it. No clarity. No ownership. No accountability. No consequences.
Everyone thinks someone else owns the work. Everyone assumes someone else will run it to ground. Everyone believes “they” know what’s happening.
Meanwhile, deliverables slip, communication breaks down, and the project starts bleeding time, money, morale, and credibility (while the PM stands there confused, frustrated, and helpless). At some point, he yells, “But I told them to handle it!”
Yeah. You tagged them. You didn’t lead them. You didn’t hold them accountable. You didn’t assign ownership and consequences. And you sure as hell didn’t follow through with clarity, expectations, and structure.
That’s the problem. Most PMs think accountability is telling someone to do a thing.
No. Accountability is ensuring the thing gets done, to the standard, on the timeline, and with visibility.
Anything less? You’re not leading. You’re playing tag. And tag doesn’t ship deliverables. So stop pretending that “assigning” = accountability. Handing a task to someone isn’t leadership: that’s administration.
Here’s the no-BS truth: If you’re not ensuring clarity, alignment, constraints, timeline, and consequences, then no one has ownership, and nothing is truly assigned.
Work isn’t real just because you wrote a name next to a bullet point. A deliverable isn’t owned because it appears in Jira or Smartsheet. Saying “John’s got it” isn’t project management. It’s wishful thinking disguised as delegation.
And let me be even more direct: most PMs don’t actually assign work. They announce names and hope.
But, hope is not a project management strategy. “But They Said They’d Do It…” Cool story. Did you get: Clear acceptance? Timeline and checkpoint agreement? Documented responsibility? Defined success criteria? Agreement on resources and constraints? Alignment with their manager if needed? Confirmation they understood and committed?
Or did you just say the name and move on? If the latter, congratulations, you’ve set your project up for confusion and blame.
This is where people get fired. This is where budgets explode. This is where relationships sour and trust dies.
Assumptions kill projects. Silence kills projects. Soft-spoken, passive, fragile PMing kills projects.
Your job is not to assign. Your job is to ensure execution.
Big difference.
Let’s get uncomfortable for a second. Many PMs avoid accountability conversations because they’re terrified of confrontation. They want to be liked. They want to be seen as a “team player.” They don’t want to upset anyone.
So they keep things soft: “I think you’re working on this, right?” “Hey just circling back…” “Quick check-in on that thing…” “Just following up…”
Just. Circling. Back. Death by 1,000 soft emails.
Meanwhile, the stakeholders with real power (the leaders who actually deliver results), look at PMs like that and see what?
Weakness. Uncertainty. Lack of command.
You don’t have to be a tyrant. But you do have to be a leader.
Leadership means clarity. Leadership means standards. Leadership means accountability. Leadership means being willing to say:
“You committed. You didn’t deliver. Let’s talk about why and how we fix it.”
If that scares you, this field will eat you alive.
Effective accountability has five components:
1. Clear Owner: Not a team. Not a function. Not “the engineering group.” A name. A person. A single throat to choke (KIDDING).
2. Defined Outcome: Not “move project forward.” What does done look like? How is it measured? What does success mean?
3. Deadline & Checkpoints: Not “ASAP.” Specific dates. Specific times. Specific touchpoints. Checkpoints are not micromanagement; they are leadership insurance.
4. Real Consequences: Not anger. Not blame. Not embarrassment. Just truth: “If you miss this, the project slips 17 days, costs increase, executive trust erodes.” Consequences = impact visibility.
5. Documented & Visible: If it isn’t documented, it didn’t happen. If it’s not visible, it’s not accountable. Write it. Track it. Show it. RACI exists for a reason, and most PMs bastardize it.
“Shared Ownership” is corporate talk for zero ownership. Shared responsibility sounds nice on paper.
But here’s the reality: When everyone owns it, no one owns it.
Shared accountability works only when: One person is ultimately responsible. Everyone knows their specific slice. Dependencies, expectations, and handoffs are explicit. Escalation paths are defined
Otherwise it becomes: “I thought they were doing it.” “No, I thought you were.” “We assumed Bob had the lead.” “Wasn’t this the PM’s job?” “I didn’t see that email.”
Classic corporate clown show.
Your job is to kill ambiguity. Because ambiguity kills execution.
Your project isn’t a suggestion. People aren’t doing you a favor by delivering work.
This isn’t extracurricular volunteering.
Your project affects: Money. Time. Headcount. Market share. Customer trust. Operational stability. Team careers
Nothing about that is soft. So stop acting like it is.
Set the tone: “This is mission-critical. You own this piece. You report progress on X date. If barriers show up, escalate immediately. Our job is to win as a team, not pretend work is happening.”
That’s leadership.
Weak PMs believe escalation = tattling. Wrong. Escalation means protecting the mission. You’re not escalating because you’re mad; you’re escalating because there is an impact that requires leadership resolution.
Strong PMs escalate early, clearly, and professionally: “We’re blocked on X. This impacts delivery by Y. I need support on Z by Friday to maintain schedule.”
If you escalate with data (not emotion), you stay professional and in command.
If you avoid escalation because you’re scared? You’re not managing risk. You’re creating it.
Your meetings reveal your leadership. Here’s a litmus test.
If your meetings sound like: “So who’s doing this?” “Anyone want to take this on?” “Does someone want to volunteer?” “Let’s circle back later.” “Okay team, let’s keep pushing!”
You’re not running a project, you’re running a pep rally. Rallies don’t deliver. Execution does.
Strong project meetings end with: Person assigned. Deliverable named. Standard defined. Deadline set. Checkpoint established. Documented in real-time.
If someone leaves unclear, that’s on you.
Accountability isn’t barking orders. Accountability is clarity, structure, and respect.
It sounds like: “I want you to succeed. That means we need crystal-clear expectations so you’re supported and we deliver together.”
It sounds like: “What do you need to meet this deadline?”
It sounds like: “If risk shows up, surface it immediately so we can address it before it grows.”
It sounds like leadership, not dictatorship.
And heaven help the PM who confuses confrontation with leadership, or worse, thinks avoiding it is kindness. Avoidance is self-protection, not team protection.
Tag feels like teamwork. It feels collaborative. It feels polite and friendly.
But it’s chaos in disguise.
Tag is when teams say: “Let’s not assign specific owners, we’ll all work together.” “Let’s keep this flexible.” “We’re all accountable.” “Let’s not push too hard.”
Translation? Let’s not lead. Let’s not own. Let’s not be uncomfortable. Let’s not risk conflict.
If you are building a project plan based on comfort, consensus, and friendliness…
You’re building your own coffin.
People don’t want micromanagement, but they don’t want ambiguity either.
Most professionals (the good ones anyway) want: Clarity. Prioritization. Definition of success. Support. Visibility. Feedback. Trust.
They want to win.
Your job is to set the conditions for victory. Not avoid discomfort. Not play tag. Not “hope it works out.”
You are the conductor. You set rhythm. You set pace. You set standards.
If you don’t, the project will, and it won’t be pretty.
Stop running projects like recess. This is not tag. This is execution.
Leaders don’t tap and run. Leaders assign with clarity. Leaders align people and purpose. Leaders hold the line. Leaders enforce discipline. Leaders support and remove obstacles. Leaders say hard things when needed. Leaders own outcomes.
If the work fails, it’s on you to fix, not blame. If people don’t deliver, it’s on you to lead better. If the team is confused, it’s on you to create clarity.
That’s the job. Not tag. Leadership.
If you’re reading this and thinking: “Damn, that’s me. I’ve been playing tag.”
Good. The first step is admitting you have a problem, right. Awareness is step one. Responsibility is step two. Action is step three.
This week, do three things: Assign one deliverable with absolute clarity. Set a checkpoint and follow through. Escalate one blocker like a leader, not a passenger.
Stop hoping projects work. Start making them work. Tag is for playgrounds. Projects are for professionals.
And you (if you choose to lead) are it.
Stay dangerous. Stay disciplined. Execute relentlessly.
