Organizational Change Management for PLM

Element runs the people side of PLM implementations — stakeholder alignment, champion programs, communication, training, and resistance management — as a dedicated workstream with its own named owner.

Most PLM programs assign change management to the same team building the system, where it loses every week to technical deadlines. We staff it separately, from discovery through hypercare. The full method is in our guide to organizational change management for PLM rollouts.

Talk to a consultant

Last reviewed by Element Consulting

black and white airliner turbine

The problem this solves

Your PLM implementation has a change management plan. Most do.

What it usually doesn't have is anyone whose actual job is to execute it. The workstream gets assigned to the project team — the PLM administrator, the solution architect, a senior engineer — the same people responsible for configuration, migration, and go-live.

Those deadlines are hard and their failures are visible. The people work has neither. So it slips, quietly, every week, until go-live arrives and the organization has been told about the change roughly twice.

Then adoption comes in low and everyone concludes the users resisted.

They didn't. Nobody prepared them.

Signs you need a dedicated change owner

blue circuit board

Your change management workstream is assigned to someone who also has technical deliverables

You've named champions but given them no training, talking points, or early access

Communication about the project has been a kickoff email and a training invite

Engineering is asking why you're changing something that isn't broken — and nobody has a good answer ready

A previous rollout technically succeeded but people kept working the old way

Your executive sponsor hasn't spoken about the project publicly in the last quarter

Adoption is the only metric you're reporting, and leadership doesn't seem to care about it

What we do, in order

  1. 01

    Change discovery and stakeholder analysis

    When: Discovery

    We sit in the same process workshops as the solution architect and ask five questions: how the work is done today and what goes wrong, what will be different, who is affected most, what else has to change, and what people have already heard. Then we map every group that creates, changes, approves or consumes product data (engineering, manufacturing, quality, supply chain, the shop floor, IT, occasional approvers) across executives, people managers and the people doing the work. The middle tier is the one most often skipped: managers want to know what happens to their team's throughput during the transition.

    Deliverables: case for change, change radius (where the change is broad and where it is intense), stakeholder map with influence and disposition, tier-specific engagement plan, executive sponsor talking points.

  2. 02

    Program OCM plan

    When: End of discovery

    One plan for the program, and a lighter one per release: who hears what and when, how champions are picked, how training is split by role, the readiness criteria that will feed go/no-go, the hypercare model and how adoption will be measured. It goes on the same weekly status cadence as the technical plan, so slipping people work shows up next to slipping configuration work.

    Deliverables: program OCM plan, communication calendar mapped to project milestones, escalation paths for groups that are not ready.

  3. 03

    Champions and super-users, equipped

    When: Design and CRP

    Naming champions is the easy half. Equipping them is the half that gets skipped, and a champion who can't answer a colleague's question is worse than no champion. Ours sit in the conference room pilot (CRP) sessions for their area, so they have used the system before anyone else and have seen their findings fixed or explained.

    Deliverables: champion and super-user selection criteria (at least one per site and major user group), enablement sessions, talking points and FAQ, early sandbox access, a standing channel to the project team.

  4. 04

    Communication and resistance management

    When: Build through go-live

    People need to hear what is changing, why, and what it means for them specifically, from someone they trust, more than once. We plan messages for leaders, people managers and contributors, and move each audience from awareness to understanding to commitment to adoption. Where a group pushes back (check-in discipline, the formal change process, BOM ownership and part numbering are the usual Windchill sore spots), we work that specific problem with them.

    Deliverables: audience-segmented messages tied to kickoff, design sign-off, CRP, training, go-live and hypercare; resistance assessment; barrier log with owners; targeted interventions for the groups with the most to lose.

  5. 05

    Role-based training and the readiness check

    When: CRP, UAT and the run-up to go-live

    Training is built while CRP runs, on your own parts, documents and BOMs, and split by role: designers, manufacturing engineers, change administrators, approvers and occasional viewers. Before the go/no-go meeting we run readiness sessions with each area and keep two questions apart: does the system work, and can the people in each area do the changed process on Monday?

    Deliverables: training by role, attendance and completion tracking, office hours and make-up sessions, a readiness assessment per area with owned gaps, an OCM input to the recorded go/no-go decision.

  6. 06

    Hypercare and adoption measurement tied to business metrics

    When: Hypercare and after

    With the technical architect we run hypercare: one place to report problems, defects fixed before new requests, a daily issue review, the incident trend to the sponsor, and an exit when the system is stable instead of on a fixed date. Adoption is reported separately from training attendance, against business metrics leadership already watches: cycle time, cost of poor quality, on-time delivery, scrap rate.

    Deliverables: hypercare plan and support channel, baseline capture before go-live, adoption dashboard, business-metric linkage, post-go-live measurement at 30/90/180 days.

How we work with your team

We don't replace your people. In most engagements your team still runs the change program day to day — we bring the method, train your champions, and stay accountable for the workstream so it doesn't get absorbed into technical firefighting.

Where you don't have an internal person with the standing to talk to an executive and the credibility to talk to the shop floor, we staff that role directly.

The honest version of this conversation happens early, while it's still a staffing decision — not at go-live, when it's a rescue.

Who does this work

These partners work alongside the Windchill architects delivering the technical implementation — which is the point. The two workstreams stay connected without competing for the same person's calendar.

When to bring us in

people sitting on chair in front of table

Best

During scoping, before the project plan is locked. Baseline metrics get captured, stakeholders get mapped, and champions get identified while there's still time for their input to change something.

Common

Mid-implementation, when the technical work is on track and it becomes obvious nobody has run the people side.

Still worth it

After a go-live that didn't stick. Low adoption is recoverable, but it's more expensive than preventing it — and you're now also managing the credibility damage from the first attempt.

About Element Consulting. Element Consulting is an independent PTC partner that has implemented, upgraded, integrated, and rescued PTC Windchill since 2003: 100+ PLM implementations, a senior-only team, headquartered in West Des Moines, Iowa. Managing Partner Eric Horn is a PTC Certified Windchill Implementation Practitioner. The firm works mainly in aerospace and defense, federal and national-security programs, medical devices, and industrial equipment, including ITAR-controlled and government-cloud delivery, and does not resell software.

FAQ

What is organizational change management in a PLM implementation?

The work of preparing people to actually use a new system — stakeholder alignment, champion development, communication, training, resistance management, and adoption measurement. It runs parallel to technical implementation and addresses whether the system gets used, not whether it works.

Why do PLM implementations fail even when the technology works?

Because adoption is a separate problem from configuration. The most common structural cause is that change management gets assigned to the team doing the technical build, where it loses to hard deadlines every week and never gets executed.

Can we run change management ourselves?

Often, yes — if you have someone with the standing to talk to executives and the credibility to talk to the shop floor, with real time carved out rather than a line in their objectives. Where that person doesn't exist, the honest move is to say so during staffing rather than at go-live.

When should change management start?

At scoping, before the project plan is finalized. Starting at go-live means you're managing a rollout that has already happened.

How do you measure whether change management worked?

Against business metrics leadership already watches — cycle time, cost of poor quality, on-time delivery — with a baseline captured before go-live and re-measured at 30, 90, and 180 days. Adoption percentage alone reads as overhead.

What do we get from an Element change management engagement?

A case for change and stakeholder analysis in discovery, a program OCM plan with a communication calendar tied to project milestones, an equipped network of champions and super-users, role-based training on your own data, a readiness assessment that feeds the go/no-go decision, a hypercare plan run with the technical team, and adoption measured against business metrics from a baseline taken before go-live.

Which Windchill changes do users resist most?

Check-in and check-out discipline, the formal change process (problem report, change request, change notice), BOM ownership between engineering and manufacturing, and part numbering. We settle each one in design, show the reason in the conference room pilot, and train each role on that exact moment.

Do you only do this alongside a Windchill implementation?

No. It's most effective paired with an implementation or upgrade, but we also take standalone engagements to recover adoption after a rollout that didn't stick.

40/40

Migration phases in an AI-verified Windchill 12 to 13.1 upgrade. Zero failures, zero production outage.

Read the case study

80%

Lower cost of poor quality at one manufacturer once manufacturing reviewed the data before release.

100+

PLM implementations since 2003, from new Windchill rollouts to upgrades, ERP integration and rescue.

*Results from specific engagements. Clients are named only with their permission, and your results will depend on your scope and starting point.