People like to say a chain is only as strong as its weakest link. I get the idea. I have seen it play out with ropes, shoelaces, and rubber bands too. They all have weak spots.
But teamwork during a D365 implementation is a different story. The idea of a single weak link does not hold up. The person you think is slowing things down may not be the real issue at all.
In ERP projects, the so‑called weak link is almost never obvious. You might be quick to point to one person, but would that person agree. Would the rest of the project team agree? And what criteria are you using? Your view of what strong looks like may not match what the project actually needs.
Two perspectives
Here are a few examples I see all the time on D365 projects. Take a look at these potential weak links and tell me which deserve the label:
People who do the least because they don’t do their fair share
OR
People who do the most because they cover for the slackers
People who are cranky because they bring everyone down
OR
People who are sunny because they aren’t realistic
People who are loud and opinionated because they make everyone uncomfortable
OR
People who are quiet and timid because they don’t contribute their insights
People who have the least knowledge because they don’t catch on quickly enough
OR
People who have the most knowledge because they don’t examine basic assumptions
Then there are the folks who sit in the middle. They are pleasant and steady, but they do not push the project forward. In an ERP implementation, that can be its own kind of weak spot.
Whenever we try to identify the weakest link, we bring our own preferences and working styles into the judgment. On a D365 project, that is risky. The real issue is often not a person at all. It is unclear roles, missing processes, poor communication, or a lack of readiness.
When problems surface, the easy move is to blame the people who are not doing things the way we would. Instead, I look at the whole system. Everyone’s contribution, including my own, is part of the picture. That is where the real insight lives.
Capitalize on the differences
A better approach is to examine the differences on the team and figure out how to use them to strengthen the implementation. D365 projects need a mix of perspectives. Super users, end users, functional leads, and technical experts all see the system differently. That diversity becomes a strength only when we appreciate it and find creative ways to put it to work.
When we stop hunting for the weakest link and start looking at how the team fits together, we build a stronger project and a smoother path to adoption.
