The people resisting the change may be seeing work the plan has omitted.

A proposal can promise a gain while leaving someone else to carry a new burden. A faster output may require more review. A new platform may make old expertise difficult to apply. A prototype may create expectations the operating team cannot yet support.

Resistance can contain useful information about those consequences.

The leadership task is to make that information examinable and connect it with the opportunity the change offers.

Ask what changes for the person doing the work.

Adoption is more than learning controls. It can change how people demonstrate competence, where they find confidence, whose judgment is consulted, and what they are expected to explain.

These changes affect enthusiastic participants too. Someone who sees a dramatic gain may not yet see the surrounding work needed to make it useful.

A conversation becomes more productive when people can examine a specific task, artifact, or proposed workflow rather than defend a general attitude toward technology.

Use the skeptical expertise.

An experienced person may recognize a failure mode the demonstration avoided. The group needs a way to understand why it matters and what observation would help resolve the concern.

Howard Pearlmutter can connect that discussion with technical reality. He has built systems, investigated difficult behavior, taught advanced professionals, and worked across organizational roles. The conversation can follow the concern into architecture or implementation when necessary.

At Telos Alliance, his engagement included skeptics alongside developers, managers, product colleagues, and executives. John Schur recognized his attention to concerns and a careful path forward. Practical prototypes also gave the discussion working foundations. See the Telos case.

Make learning part of the transition.

In earlier green-logistics work, Howard trained and mentored a team with a COBOL-era background into enterprise Java technologies. Their existing knowledge was a resource to connect with new tools and architecture.

That is a useful model for adoption: preserve what experienced people know while expanding what they can do.

It can involve shared mental models, mentoring around actual tasks, technical transfer, or a working session where different roles examine the same artifact.

Choose a testable point of disagreement.

Ask each group which part of the proposed change matters most to its work. Identify where the accounts differ. Then choose a question the group can examine through a demonstration, prototype, review, or bounded experiment.

Explore technical judgment, mentoring, and working sessions. The aim is a more workable change that benefits from the people who understand its consequences.