Introduction
Over the years, I have worked with engineers, sales teams, service organizations, architects, product managers, executives and transformation leaders.
The industries have varied. The technologies have evolved dramatically. The business priorities have changed.
Yet one thing has remained surprisingly consistent.
Most transformation challenges are far less technical than they first appear.
That realization took me a long time to accept.
Because when you spend years working with PLM, engineering systems, product structures and digital transformation, it is easy to believe that technology sits at the center of the problem.
Today, I think technology is usually sitting somewhere else.
Important. Necessary. Sometimes critical. But rarely at the center.
The center is almost always people. And how effectively they work together.
Every Function Is Rational
One lesson that has stayed with me throughout my career is that most organizational behavior makes sense from the inside.
Engineering wants better product quality. Sales wants greater flexibility. Manufacturing wants stability. Service wants simplicity. Management wants predictability.
Each perspective is rational. Each perspective is defensible. Each perspective is usually based on genuine business needs.
The challenge begins when organizations assume that rational local decisions automatically create rational global outcomes.
Unfortunately, they often do not.
Many transformation problems emerge because every function is optimizing something valuable. Just not the same thing.
Nobody Wakes Up Planning to Create Complexity
Another observation is that complexity is rarely intentional.
No engineer decides to make a product difficult to support. No salesperson deliberately makes manufacturing harder. No service organization intentionally creates frustration for engineering.
Complexity accumulates gradually.
One customer request. One market adaptation. One exception. One workaround. One urgent decision.
Then another. And another.
Years later the organization discovers it is struggling with a system nobody consciously designed.
The complexity emerged from many reasonable decisions made independently.
That realization changed how I think about blame.
Because most lifecycle problems are not people problems. They are interaction problems.
Experience Often Lives in People
For years, I was fascinated by information management.
How do we structure information? How do we create traceability? How do we improve access?
Those questions remain important.
But eventually I noticed something interesting.
Many of the most important answers were not stored in systems. They were stored in people.
A senior engineer knew why a decision was made. A service technician understood a recurring customer issue. A salesperson knew which exceptions actually mattered. A product manager understood historical trade-offs.
The organization depended on knowledge that had never become explicit.
And that creates both strength and vulnerability.
Because expertise can solve problems remarkably quickly. But expertise cannot scale indefinitely.
Listening Is a Competitive Advantage
One of the most effective people I have encountered throughout my career have not necessarily been the smartest in the room. Nor the most experienced. Nor the most technically skilled.
Often they were the best listeners.
They understood something important.
Every function sees part of the truth. No function sees all of it.
Engineers understand things that executives do not. Service organizations understand things that architects do not. Customers understand things that neither group understands.
The ability to connect those perspectives is incredibly powerful. And surprisingly rare.
Many transformation failures can be traced back to people speaking. Far fewer to people listening.
The Best Organizations Are Curious
Another pattern became visible over time.
The strongest organizations tend to be deeply curious.
They are willing to challenge assumptions. They ask uncomfortable questions. They investigate problems rather than defend existing answers. They are interested in understanding. Not simply proving themselves right.
This matters because most transformation challenges are not obvious.
The first explanation is often incomplete. The visible problem is often a symptom. The root cause usually sits somewhere deeper.
Curiosity allows organizations to keep looking.
And organizations that stop looking often stop learning.
Technology Rarely Changes Culture
Many transformation programs quietly assume that new technology will create new behavior.
Sometimes it does.
More often, existing behavior adapts to the new technology.
The organization remains largely unchanged.
The system looks different. The meetings remain the same. The decision making remains the same. The accountability remains the same. The conflicts remain the same.
This is one reason cultural change is so difficult.
Technology is implemented in months. Behavior evolves over years.
The two frequently move at different speeds. And when they do, expectations become misaligned.
Trust Matters More Than Most Frameworks
If I look back at the best transformations I have experienced, one characteristic appears repeatedly.
Trust.
Trust between engineering and sales. Trust between management and operational teams. Trust between service organizations and product development. Trust that problems can be raised without punishment. Trust that information will be used constructively. Trust that decisions have coherent reasoning behind them.
Without trust, information becomes political. Knowledge becomes guarded. Collaboration becomes transactional. Decision making becomes slower.
Trust rarely appears on transformation roadmaps. Yet it influences almost everything that follows.
The Human Side of Change
One lesson that took me years to fully appreciate is that transformation is deeply personal.
People do not experience transformation as a strategy. They experience it as change.
New responsibilities. New expectations. New ways of working. New measurements. New priorities. Sometimes uncertainty. Sometimes opportunity. Sometimes both.
This means successful transformation requires more than technical excellence.
It requires empathy.
Understanding why people behave the way they do. Understanding what they fear. Understanding what they value. And understanding that resistance is often information, not opposition.
People are frequently telling us something important when they push back.
The challenge is learning how to hear it.
Why I Still Enjoy This Work
After all these years, people occasionally ask why I am still interested in transformation.
The answer is surprisingly simple.
Because every organization teaches something new.
The technology changes. The products change. The industries change.
But the underlying challenge remains fascinating.
How do people work together to create value? How do decisions move through the organization? How does knowledge become capability? How does experience become learning?
Those questions never really disappear. They simply emerge in new forms.
And every company provides a slightly different answer.
What Matters Most
If I had to summarize twenty-five years in a single observation, it would probably be this:
Most business problems are not caused by a lack of intelligence.
Organizations are already full of capable people.
The challenge is helping those capabilities work together effectively.
Helping information move. Helping knowledge move. Helping decisions move. Helping learning move.
That is where transformation becomes difficult. And that is also where it becomes meaningful.
Because organizations rarely succeed because one person has all the answers.
They succeed because many people become better at solving problems together.
Final Thoughts
When people talk about transformation, the conversation often gravitates toward strategy, systems and architecture.
Those topics matter. But I have come to believe that the most important parts are often much simpler.
Curiosity. Trust. Learning. Collaboration. Listening. Shared understanding.
These qualities rarely appear in technology roadmaps. Yet they often determine whether technology creates value.
After twenty-five years, I am probably less impressed by systems than I once was. And much more impressed by organizations that know how to learn.
But learning requires direction. Before an organization begins another transformation, leadership needs to step back from the roadmap and agree on something more fundamental.
Why should we do anything at all, and what are we
actually trying to achieve?
Without a shared answer, a transformation can become a collection of individually reasonable initiatives moving in different directions. Activity increases. Technology improves. Yet the purpose becomes harder to see.
Perhaps the most useful contribution a leadership team can make is therefore not to provide the first solution. It is to establish a common intent.
Three questions can help begin that conversation.
Start With Intent
WHY
Why should we change?
Not because a new technology is available. What constraint are we trying to remove, what opportunity are we trying to capture, or what risk can we no longer accept? If the reason is unclear, the transformation will eventually lose direction.
WHAT
What do we want to become better at?
Not which system we want to implement, but which capability we want to strengthen. Better decisions? Faster learning? More effective complexity management? Stronger coordination across the lifecycle? Technology should enable that capability, not define it.
EVIDENCE
How will we know that we succeeded?
What will genuinely be different? Which decisions will improve? Which friction will disappear? What will customers, employees or leaders experience differently? Success should be visible in outcomes, not only in completed activities.
A final reflection
Transformation should not begin with a solution. It should begin with intent. Technology, architecture and AI matter, but only after leadership understands why the organization must change and what it wants to accomplish.
Because organizations rarely fail from a lack of technology. More often, they struggle because they never established a shared understanding of what success was meant to look like.