The Hidden Cost of "Feedback Welcome"

"We want your feedback" might be the most expensive sentence in change communication.

Not because feedback is bad. Because most organizations can't absorb it, don't act on it, and damage credibility by asking for input they won't use.

When Feedback Requests Backfire

Asking for feedback creates three obligations:

• You have to actually listen

• You have to respond to what you heard

• You have to explain what you're doing with it

Most organizations fail at #2 and #3.

They collect input, say "thanks for sharing," and then proceed exactly as planned. People notice. They stop participating. And the next time you ask for feedback, they remember that it didn't matter last time.

Asking for feedback you can't use doesn't make you look collaborative. It makes you look performative.

The Wrong Question

"What do you think about this change?" is almost always the wrong question.

It's too broad to be actionable. It invites philosophical objections you can't address. It creates the impression that the decision is still open when it usually isn't.

Better questions target specific, addressable concerns:

• "What information do you need to prepare your team?"

• "What obstacles do you see in your area that we might not know about?"

• "What questions will your staff ask that we should be ready to answer?"

These questions acknowledge constraints while still gathering useful input. They make it clear what's fixed and what's flexible.

Feedback vs. Input

Feedback implies you might change the plan based on what you hear. Input means you're gathering information to refine how you implement.

Most change leaders want input but ask for feedback. The mismatch creates confusion and resentment.

If the core decision is made, say so. Then ask for input on execution.

If the decision is genuinely open, say that too. Then explain the criteria you'll use to decide and commit to explaining the outcome.

Don't ask open-ended questions about closed decisions.

When to Actually Ask

The best time to ask for input is when you can genuinely use it.

That's usually:

• During design, when implementation details are still flexible

• During early implementation, when you're troubleshooting specific problems

• After major milestones, when you're assessing what's working

It's not:

• After the decision is final but before announcement (creates false hope)

• During crisis moments when you need compliance, not debate (creates confusion)

• When you're trying to manufacture buy-in for something unpopular (creates cynicism)

The Credibility Question

Every feedback request either builds or burns credibility.

Before you ask, answer: "Can we actually do something with what we hear?"

If the answer is no, don't ask. If the answer is "sort of," be specific about what you can and can't address.

If the answer is yes, commit to closing the loop: explaining what you heard, what you're doing about it, and what you can't change and why.

The DANCE System includes structured approaches for gathering meaningful input without creating false expectations or burning credibility. Learn more about systematic change communication