At the CLM Summit, the conversations on the surface were about AI, configuration management, digital threads, and manufacturing transformation.
Underneath all of it was the same unresolved tension.
Organizations are trying to manage increasing complexity with execution systems that were never designed for this level of operational demand. The technology is advancing. The systems underneath are not keeping pace.
One statement from the summit captured it clearly: “Complexity is not the problem. Losing control is.”
That distinction matters more than most organizations are currently treating it.
Complexity is not new. Product variation, software integration, global compliance, and customer customization these have existed for decades.
What is changing is the coordination burden required to manage all of them simultaneously, at speed, across departments that still largely operate from their own version of reality.
Engineering updates one system. Sales quotes from another. Manufacturing runs on assumptions that may no longer reflect current product configurations. Service teams execute against information that does not account for changes made after deployment.
Leadership makes strategic decisions while the data feeding those decisions is fragmented across the business.
This is not a technology problem. It is a visibility problem.
A question kept surfacing throughout the summit: “Where does your product knowledge live?” Most organizations cannot answer that cleanly.
They do not fully know where critical operational knowledge sits, who owns it, how it connects downstream, or what breaks when one variable changes. That is an operational blind spot. And blind spots do not stay contained — they compound quietly until something fails visibly.
The AI conversation at the summit reinforced this. AI is an amplifier. That works in both directions.
Healthy execution systems get faster and sharper with AI on top. Fragmented systems get more fragmented, faster. Broken processes do not get fixed through automation they get scaled with increasing complexity.
Many organizations are moving toward AI implementation before examining what they are actually automating. Process maturity is not an implementation detail. It is a precondition. The question worth asking before any automation initiative is: what level of operational health does this process need to reach before acceleration makes sense?
The human barriers at the summit were just as telling as the technical ones. Unclear data ownership. Poor adoption. Resistance to change. Weak cross-functional coordination.
These are not soft implementation challenges to manage around. They are signals about how the organization actually functions beneath the surface. Resistance has information in it. Most organizations ignore it rather than interpret it.
What I left thinking about is not which technologies organizations should adopt next.
It is whether organizations understand the execution system they are asking those technologies to operate on top of.
Faster execution without visibility creates instability. Automation without operational clarity creates failure at scale. Neither problem is solved by moving faster.
The organizations that hold their ground as complexity increases will not be the ones with the most advanced tools. They will be the ones who built something solid enough to sustain what those tools demand.
If siloed data and disconnected systems are preventing your organization from meeting market demand, that is an execution visibility problem and it is solvable.
Schedule a free strategy session with us to discuss your product knowledge and where the gaps may be costing you.
