Bring Change Management Into a Technology Evaluation

A product choice does not settle how people will learn a new process or who will help when work slows down. An executive sponsor might support a purchase while no one has named training, internal communication, or manager follow through. A seller who notices this gap early helps a customer make a more complete evaluation. The aim is not to run adoption work for them. The aim is to bring affected roles and practical choices into view before a project reaches launch.

Start with one plain question: “On the first day of use, what will one person do differently?” Pause after asking. Look for an answer with a role, an action, and a point in the day. “A support agent records a reason during case closeout” gives a team something concrete to examine. “People will use the system” leaves every important choice hidden. Begin with one workflow. A narrow conversation often reveals who needs preparation without turning an evaluation into a giant planning session.

In a fictional evaluation, Priya sponsors a service operations project. She says staff should find the new screens easy to learn. Her account lead asks, “Which group meets the first change during a normal Monday?” Priya names 18 support agents. They now choose a reason code from a shared spreadsheet near the end of each shift. Under the proposed process, an agent records a reason during case closeout. Priya and the lead now have a visible change rather than a broad claim about adoption.

The next question concerns review. “Who sees this work often enough to spot a poor fit before a pilot?” Priya names Mateo, the support manager. He hears questions during coaching and sees missing fields in case records. The account lead asks a second question: “Does Mateo approve this workflow, or does he provide operational input?” Priya says a director approves the process while Mateo provides input. Keep those roles separate. The director needs a concise decision. Mateo needs room to describe a busy shift, common exceptions, and places where guidance might be unclear.

Invite an affected manager with a purpose connected to a real choice. “Join our change discussion” gives little reason to accept. Priya sends Mateo a request instead: “We are mapping case closeout for a short pilot. Please review a draft process and point out a step where an agent might lose time or need guidance.” Mateo knows why his knowledge matters. Priya keeps ownership of the project. The invitation also gives Mateo a manageable assignment rather than an undefined meeting.

Ask about the first use of a workflow instead of an ideal future state. Questions such as “What happens immediately before closeout?” and “What does a manager need to notice during week one?” help the group prepare for ordinary work. Mateo explains how agents start in one screen, check a customer note in another, then close a case after a caller leaves. He wants managers to notice blank reason fields during coaching. Priya records each detail as an open design item. She does not treat an early explanation as a settled fact.

Training benefits from similar precision. Do not label training as one calendar event and move on. Ask who needs instruction, what each person needs to do afterward, and when learning fits the work. The 18 agents might practice with sample cases during a short guided session. Managers might need to review incomplete records and respond to an agent question. An operations administrator might need a decision about future reason codes. Give each audience material suited to its task. A manager should not receive an agent exercise as a default.

Communication also needs a name beside every action. “Send an announcement” hides audience, timing, and purpose. Priya decides to introduce the pilot at a Monday staff meeting. Mateo agrees to send a one page walkthrough on Tuesday. The director will explain why case reasons matter during the Wednesday feedback session. The account lead does not write a customer message or speak for Priya’s team. She helps Priya assign a sequence and expose missing decisions.

Use a pilot for learning from real work. In this fictional example, Priya chooses four agents for five business days. The director approves this scope after Mateo identifies two suitable queues. Priya schedules a feedback session for the following Wednesday before pilot work starts. Each participant brings one confusing point, one slow step, or one missing instruction. The group then decides whether to alter the workflow, revise the guide, or keep gathering input. No participant needs to promise an outcome before reviewing what happened.

Manager follow through deserves a specific routine. Mateo already holds brief coaching sessions every Thursday. Priya asks whether he will review incomplete reason fields during those sessions for the first two weeks of wider use. He agrees, provided he receives a simple view of open fields before each session. Priya assigns an operations administrator to confirm whether such a view exists and bring an answer to the next meeting. This produces a real dependency, not an unsupported promise from the account lead.

Sometimes a sponsor says no adoption work is needed because a product feels easy. Avoid an argument about product quality. Return to changed work. Ask, “Who will notice whether case closeout fits a crowded shift?” The question respects the sponsor’s view while focusing on an observable issue. If no owner appears, state the gap directly: “We have a product direction, yet no person is preparing the affected team.” A clear gap gives the sponsor a chance to assign someone or defer the decision openly.

Keep a small rollout record during evaluation. Include the affected group, first changed workflow, operational reviewer, approval owner, learning activity, communication owner, pilot scope, feedback date, and manager routine. Every entry needs a confirmed name or an open question. Do not assign people by assumption. Blank spaces remain useful because the group sees unfinished work before a launch date approaches.

Practice with a fictional sponsor who says, “Staff will work this out once we switch.” Ask for the first role affected. After a role appears, ask what action changes during an ordinary day. Then ask who should review a small pilot. Stay with those questions. Training, communication, and manager support do not need solutions in one reply. Your next goal is a named owner and a workflow suitable for a test.

Priya takes the next action on Friday afternoon. She sends Mateo a draft case closeout step and asks him to mark any moment where an agent needs guidance. Mateo replies with two questions about reason codes. Priya adds both to Wednesday’s pilot agenda, confirms the four participant group, and sends the director a request for approval of the five day pilot scope.