Tasks Keep Getting Misunderstood? The Key to Downward Communication Isn't Clarity—It's Making People Able to Act

"This is ridiculous. I've explained it three times. How can they still get it wrong?"

Many first-time managers have complaints like this.

But over time, you realize the problem isn't the other person's poor comprehension. It's that our way of speaking doesn't match their state. We're used to expressing things from our own position, but we forget to consider whether what we say lands in their ears as a signal they can act on immediately.

This article is about how to communicate downward so the other person can understand, can act, and gets clearer as they go.

Starting with how to do it matters more than emphasizing doing it well

We often say things like: "This copy isn't compelling enough," "The logic feels a bit messy," or "Why don't you smooth out this flow?"

These statements aren't wrong, but they're useless to a new colleague.

They'll think: "What does 'compelling' mean? Add data? Add metaphors? Change the tone? Or rewrite the whole thing?"

"Which part of the flow is rough? Is it an interaction problem or an information architecture problem?"

We're expressing feelings, but they need direction.

So the first step in assigning a task isn't pointing out the problem. It's telling them where to start.

For example, instead of saying the flow isn't smooth, say:

In the last version, users dropped off heavily at step two. For this version, we want to combine two clicks into one screen. Focus on optimizing that part of the path.

It sounds like a small difference, but the execution results are worlds apart.

When we're too abstract, the other person can only guess

"Smoother," "not disjointed"—we may be used to these words, but a new colleague has no idea where to begin.

They can't tell which step is rough, or whether "disjointed" means a page transition problem or a user behavior problem.

Even more common is this scenario:

We say: "The flow isn't clear enough."

They revise it. We say: "It doesn't look much different."

They revise again. We say: "You still haven't captured the key point."

After three rounds, it still doesn't pass. We think they're not capable. They think you didn't explain clearly.

The root cause isn't the work itself. It's that our communication style hasn't helped them build a judgment framework.

So when assigning a task, using 5W2H to make it concrete can greatly reduce misunderstandings.

For example:

What: Optimize the registration flow for Product A (What exactly needs to be done?)

Why: Current drop-off rate exceeds 20%, conversion is low (What value does this task have for the outcome or goal?)

Who: You'll work with Designer B, with support from Developer C (Who is responsible? Are there other collaborators?)

When: Demo expected by next Tuesday (What's the latest delivery date? Are there intermediate checkpoints?)

Where: Focus on optimizing the interaction in the first two steps (What is the deliverable? Is there a collaboration space or file?)

How: Reference competitors X and Y to reduce clicks (What approach is recommended? Are there templates or processes to follow?)

How much: Keep costs within the existing framework, no additional development resources (What are the standards, scope, and expected workload?)

After hearing this, most people won't feel lost.

Don't be afraid of being wordy. What's scary is being vague

Some managers worry that explaining too much feels like micromanaging, as if they don't trust the person.

But the real problem isn't saying too much. It's saying too little of substance.

A practical suggestion: break the task into two parts when you explain it—

One part is what you hope to achieve in the end (so they know your expectations)
One part is how they can start (so they know how to take the first step)

For example, if you want a more concise landing page copy.

You could say:

This version has too many paragraphs, which makes people bounce. We want this screen to communicate the main feature within 10 seconds. You could try opening with a punchy one-liner that directly states the product's value, then add a user conversion stat.

It's not giving the answer directly, but giving direction and a starting point.

Hearing and internalizing are two different things

There's another scenario: we explain, they nod, but the final deliverable still misses the mark.

That's because they understood the literal meaning but didn't form an internal understanding.

A particularly useful practice is to ask them, before they start, to restate in their own words what they understand the key points of the task to be.

This isn't about distrust. It's about making sure you're on the same wavelength.

For example:

What's your understanding of what I just said? What do you think the core goal of this page is? How do you plan to start?

These questions can help uncover misunderstandings and also help them sort out their own thinking.

Assigning a task isn't a one-time explanation. It's about continuously building mutual trust

Experienced managers provide feedback throughout the task.

And that feedback isn't "you're wrong." It's "there's something here you might not have noticed," or "we could try a different approach."

For example, a new colleague writes a user segmentation logic but uses an unstable field.

We might be tempted to say: "This won't be stable. It'll break when you rerun it."

But a better way might be:

We've used this field before, but the problem is it's unstable in edge cases. You could try using Field X as the primary key. It'll be more stable for downstream analysis.

This expresses expectations while protecting the relationship.

The core of downward communication isn't what you say. It's whether they feel you're helping them do better.

A short closing note

Many people think managing is hard because the other person is too green or not proactive enough.

But real management is helping someone go from not understanding how you think to knowing what they should do.

From delivering what you asked for to delivering what you actually want.

This isn't a matter of talent. It's a matter of communication style.

If we're willing to think one more step and ask one more question, we'll gradually find:

The more clearly we explain, the more clearly the people we manage will progress.