1 GIANT STEP PLM Implementations are a recipe for disaster. You can’t turn on 15 modules of PLM over the weekend, effectively changing the way people do everything overnight, and expect them to accept it. It’s the fastest way to overwhelm users and ensure system failure.

The technical folks won’t use a system that doesn’t perfectly meet their needs and non-technical users will likely get over-whelmed and reject the system entirely. Both user types end up creating workarounds and the PLM system won’t contain reliable real-time data. Eventually the system fails because it is not the trusted source of the truth.

If you’re stuck: Stop. Pick one process and roll it out. Get feedback. Make adjustments. Wait 30, 60 or even 90 days to roll out another step. A phased implementation approach requires flexible software that doesn’t rely on one big compile-and-release event.  The benefits of a phased implementation are well worth it. It keeps users engaged, shows continuous progress and eases the learning curve for everyone involved which ultimately leads to a much more successful PLM implementation.

For tips on increasing user adoption ideas which Doug Draughn, the “Bulldog”, from Basic Research.