When does PLM customization become technical debt?
Imo - business requirement doesn’t fit the standard process perfectly, so the obvious idea here is to customize it all. But then another team needs an exception. And then another region does things differently.
A year later you have a system that technically matches the original requirements very well, but even relatively small process changes become painful. Ooops.
One principle I liked from some consult teams (e.g. C+P) approach to PLM is standard-first focus: start with what the platform already does, then customize only when there’s a real business case for doing so.
Impossible to avoid customization completely, especially in large implementations, but I think the burden of proof should almost be reversed:
not idea to blindly customize this but questioning if**** this requirement valuable enough to justify owning this customization for the next 5-10 years
Curious how you guys approach this. Where do you personally draw the line between adapting the business process and adapting the system?