One of the biggest risks in any D365 implementation is silence. When employees stop speaking up, you lose the insights that help you catch problems early, refine processes, and build a system people will actually use.
I hear versions of this complaint all the time: “I’m not going to say anything because no one listens anyway.”
Is it true? Maybe. Maybe not. But if people believe it, you’ve got a problem. And in a D365 project, that problem turns into rework, resistance, and a system that never reaches its potential.
Proven strategies you can implement now
You want to know what’s not working. You want ideas that make the system better. To get that, you need a deliberate strategy that encourages people to speak up. Here are six ways to make that happen.
1. Ask for suggestions constantly
An “open door policy” won’t get you the input you need. You have to ask for it.
Ask in project meetings. Ask during design sessions. Ask during one‑on‑ones. Ask when you’re reviewing test results.
A simple prompt works:
“You’re close to the work. What’s not going to fly once we go live?”
When you ask regularly, people start to believe you actually want to hear from them.
2. Thank people who speak up
When someone brings you a concern or idea, stop and listen.
Even if the idea isn’t great, thank them for raising it.
“I’m glad you brought this up. We can only fix what we know about.”
That moment matters. It reinforces that speaking up is valued, not risky.
3. Don’t punish the messenger
D365 projects surface bad news. Broken processes. Missing data. Confusing screens. Gaps in training.
When someone brings you something unpleasant, your reaction determines whether they’ll ever do it again.
Stay calm. Stay appreciative. If you want people to keep you informed, treat bad news the same way you treat good news.
4. Give credit when employee input leads to change
Many improvements in a D365 project come from frontline observations. When that input leads to a fix, say so.
“We wouldn’t have caught this without the feedback from the warehouse team. Thanks to Maria and Devon for flagging it early.”
Public credit builds trust. It also encourages others to speak up.
5. Don’t require people to bring solutions with their problems
The old rule “don’t bring me a problem unless you have a solution” is terrible for D365 work.
Some people are great at spotting issues. Others are great at solving them. You need both.
If you make people feel like they must solve everything themselves, they’ll stop reporting what they see. And that’s how small issues turn into big failures at go‑live.
6. Explain why you reject ideas
You won’t use every suggestion. That’s normal.
What matters is explaining why. People can handle “no” if they understand the reasoning.
When you close the loop, even on rejected ideas, people stay engaged. When you don’t, they assume you ignored them.
Great D365 Teams Speak Up
Successful D365 projects depend on honest input. You need people to identify problems early, share what’s confusing, and offer ideas that make the system better.
They’ll only do that if they believe you appreciate their contributions and take them seriously. These six strategies help you build that environment.
If you want help creating a communication plan or feedback system for your D365 project, I can help you build one that actually works.
