AssignArch
Project Management2024-03-08

Clear Communication | Get Your Team Aligned with Three Elements: Who, When, Task

How does a PM avoid communication gaps? This article lays out a three-part formula for clear communication — Who completes What by When — and breaks down acceptance criteria and emotional management in the field.

Clear communication is the PM's habit of explicitly naming three things — who, by when, and what task — so the team is on the same page and gaps don't appear.

Communication is a PM's day job. It's also the biggest chunk of the work.

But getting to clear communication takes real effort.

It demands deliberate guidance from the PM — confirming the other side's needs again and again, making sure both parties actually understand the same thing.

This article is written from a PM's point of view, but the application isn't limited to PMs. Anyone who has to coordinate resources or manage uncertainty can use it.

What's the PM's formula for clear communication?

Here's a formula I use:

"Who" completes "Task" by "When".

All three elements are non-negotiable. Drop "Who," and nobody feels accountable. Drop "When," and the work slides indefinitely. Drop "completion standard for the Task," and whatever gets delivered won't pass review.

"Who": How do you assign a task to a clear owner?

The "Who" has to be one specific person.

If two people in the office have similar responsibilities, and you don't explicitly say which one, both will likely "not feel" it's their job.

For example, I often hear professors say, "Just hand this to the office to handle!"

This happens to me all the time in academia: the college office? The institute office? The department office?

You have to make sure the task is actually "delivered" to the right person.

Even if it feels petty, don't test human nature — finish the communication properly.

"When": Why should a PM communicate in hours?

For time, I recommend using hours as the unit.

In other words, the completion time should be "anchored in hours".

For example:

  1. Please send the document by next Friday at 5pm
  2. Gather the team for a stand-up at 10:30am on 10/24
  3. I can stay late and get this resolved by tonight 8pm

PMs in different industries have different senses of project time:

  1. Some work in days, like construction
  2. Some work in shifts, like logistics or manufacturing
  3. Some work in hours, like software development or web design

There are different time sensibilities, but for me, "hour-based" communication is the safest.

"Task": How do acceptance criteria prevent communication gaps?

Tasks are usually where things go wrong.

Because the task's "completion standard" often isn't communicated upfront.

Anything that doesn't meet the "completion standard" can't pass review and has to be returned — but this step gets skipped all the time.

Here's a case I run into constantly:

  1. Engineer A finishes writing the code and hands it off to Engineer B
  2. Engineer B can't run Engineer A's code
  3. Engineer A thinks the code is fine and B must have set things up wrong

The completion standard: the next person can run it. It has to actually hand off cleanly to count as done.

The goal of clear communication: alignment

Alignment sounds simple, but it's hard in practice.

I often use this example in class: "fantasy."

When we set out to make a fantasy-style game, what does each person picture?

Wuxia and immortal swords? Unicorns? A magic world? Faeries?

Everyone imagines something different when they hear "fantasy."

PMs use a lot of vocabulary, and that vocabulary is also shaped by the client's habits.

When you talk to the team, words easily fall short on precision.

So my recommendation is: focus on "concrete acceptance criteria."

  1. The code "runs successfully on my machine"
  2. The design file "can be exported as a print-ready version"
  3. The copy "contains no typos"

Key point: the acceptance criteria has to be an "objective, testable condition," not "feels right."

Clear communication isn't only the PM's job

Communication is the whole team's job. It's not the PM's alone.

The Making of a Manager puts it this way:

A manager's job is to improve the team's overall output.

If a designer tells me, "This will be ready next week," I'd ask:

  1. Which day next week?
  2. Will it be ready by end of business that day?
  3. Did you factor in the design director's review time?
  4. Does "ready" mean the engineer can start working on it directly?

A PM uses questions to push others to reflect and sharpen their own communication.

A PM has to actively "raise everyone's communication precision".

Don't just run around in circles, and don't act as the message relay either.

If they have communication problems with each other, you won't even know about it!

Key point: A PM's job is to improve the project's overall output.

A great PM teaches the team to communicate effectively.

People have their own specialties, and sometimes designers and engineers need to sync 1-on-1.

Managing emotions in communication

Communication can get tense — sometimes even scary.

I've had a boss send me to push back hard on a downstream vendor while he himself stayed out of it.

PMs face all kinds of situations:

  1. The client wants changes, and the engineer is already past patience
  2. The design proposal got rejected multiple times — how do you tell the broken-down designer?
  3. The project is behind, and the boss orders the PM to apologize to the client

Yes, I've been through all of these.

My only advice for fellow PMs:

  • Don't fear conflict — state the facts calmly
  • Say what needs to be said. Some things won't be understood unless spoken
  • Use yes/no questions to converge on the issue — you'll find the root cause faster

In the end, when an apology is in order, just apologize. Don't carry guilt or feel like you were wrong.

Your job is "communication." All you need to focus on is getting the message across clearly.

How do you make clear communication second nature as a PM?

Clear communication is the foundation of project success.

The PM's job is to make sure every task has "a named owner," "an on-time finish," and "meets the standard."

But remember: communication is the team's shared responsibility — not just the PM's. Helping the team understand this is also part of the PM's job.

Next time you assign a task, force yourself to say all three things in one breath: who, by when, completion standard.

Raise the bar gradually, and the team will naturally adjust and follow.

FAQ

Q: My team isn't familiar with this formula — won't it feel mechanical to communicate this way every time? A: It feels clunky at first. After 3-5 projects, it becomes muscle memory. When a colleague asks, "When do you need this?" you'll instinctively ask back, "What time can you deliver?"

Q: What if the client refuses to commit to a specific time? A: Use the "option question" method — "Would you prefer to see the first version by Friday this week, or by Tuesday next week?" Forcing the client to choose between two times you've offered gets you an answer ten times faster than an open-ended question.

Q: How detailed should the completion standard be? A: Simple test: the next person picking up the work should be able to start without asking you anything. If they have to come back and ask before they can move forward, the standard isn't detailed enough.

Q: Can I still communicate if I'm missing one of the three elements — who, when, or task? A: You can still talk, but there will be a gap. The one I trip over most is missing the "completion standard" — everyone thinks they're done, then the PM reviews and finds out it's not. Of the three elements, completion standard is the easiest to gloss over and the most likely to blow up.