Our managers keep pitching machine learning projects that fail to get adopted by the frontline. How should we reframe AI rollouts internally so our company actually uses them?

Question

Tyler Smith · Accepted Answer

Stop calling these initiatives AI projects or machine learning rollouts. The moment leadership announces an AI initiative, two bad things happen. First, frontline employees get defensive because they assume software is coming to replace their jobs. Second, your managers treat the technology as a glamorous novelty, spending time playing with prompts rather than fixing operational bottlenecks.

Adopt a firm rule across your leadership team: never sell AI. Pitch operational improvements that machine learning will enable, mentioning machine learning only as a footnote.

When you present a workflow change to the company or assign a quarterly Rock, frame the project around the elimination of friction. Do not say, We are rolling out a machine learning model to optimize scheduling. Say, We are redesigning our field dispatch process so our technicians stop driving forty miles between service calls and can get home an hour earlier every night.

Ground every project in your documented Core Processes. Identify the cumbersome tasks that keep employees mired in low-value busywork, such as copying data across platforms, chasing missing vendor paperwork, or drafting repetitive status emails. Announce the operational goal: eliminating ten hours of administrative drudgery per person each week so they can focus on higher-value client service.

When employees realize the software removes the exact tasks they hate doing most, resistance evaporates. Machine learning is just an engine under the hood. Your frontline does not care about the engine; they care whether the truck runs smoothly and helps them win the day.