Skip to content

Q&A[2026-11-17]

Data Leaders Share Ways to Build Lasting Adoption

IMInformatics MagazineNovember 17, 2026

Lasting adoption starts with less friction, clearer benefits, and tools that solve real daily problems. Experts in the field share practical ways to build trust, prove results, and help teams make new systems part of their routine. From early pilots to reliable support, these strategies turn hesitation into lasting use.

§ How this was made

The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content

Fig. 1 · Q&A · 2026-11-17

Illustration generated with AI

FKVVJHZBOKJBSAHC
In [*] · 25 contributors
FKFahad KhanDigital Marketing Manager, Ubuy Sweden

Streamline Inputs and Recruit Peer Proof

Leading data and marketing operations for about thirteen years, I treat early resistance as a workflow problem, not an attitude problem. When we introduced a new reporting process, analysts said it felt slower because they still had to gather inputs from three places. We did not insist on adoption; we removed two manual steps and created a short template that captured the decisions people actually needed. Then one respected team member demonstrated it during a live reporting cycle. Usage held after the first month because the process saved time once people reached the analysis stage. Prosci research found 63 percent of AI implementation challenges come from human factors, not technical limits.

VVVolen VulkovCo-founder, Enhancv

Expose Early Wins and Cut Friction

The new process almost always is slower at first, and pretending otherwise is the fastest way to lose people's trust. So I'd never sell it as faster. I'd show exactly where the extra time goes and what it buys later.

Resistance usually isn't about the minutes. People are good at their old way of working, and a new process makes them feel like beginners again. If you treat their complaints as stubbornness, they dig in. If you treat them as feedback, you often find the step that really is pointless, and removing it earns more goodwill than any training session.

What turns resistance into habit is the first save. Every good process catches something the old way would have missed: a mistake, a duplicate, a number that didn't add up. The moment that happens, make it visible. Share it with the team and say plainly, "This is why we added the step." One concrete catch convinces people more than any explanation of why the change is good for them.

Then lower the cost of switching. Write down the new steps where people work, not in a document they'll never open, and make it normal to ask the same question twice. People don't stick with a process because they were told to. They stick with it once it's easier to follow than to work around.

JHJens HagelFounder & Owner, kjello

Explain Risks Behind Every Safeguard

I explain the incident behind the rule, because people accept slower steps once they know what they prevent. A Hamburg sales office of an industrial group got a phishing email asking to change the bank account for someone's salary. Since then our support only accepts requests from senders on their staff list and confirms everything else by phone. It is slower than a quick reply, and the reason behind it is easy to remember.

Jens Hagel, Founder & Owner, kjello (Hamburg, Germany)

Showcase Live Outcomes and Set Dashboard Defaults

I've run a digital marketing agency for nearly a decade where every team member has to trust data dashboards over gut instinct -- that tension is real and I've lived it repeatedly.

The turning point for us wasn't training, it was a live reporting dashboard. When my team could see in real time how their inputs directly changed client outcomes, the new process stopped feeling like extra work and started feeling like proof of their own value.

The biggest mistake I see is rolling out a new data process without a quick win attached to it. When we onboarded clients into our tracking systems, we'd deliberately surface one insight fast -- something that caught a campaign problem the old method would have missed entirely -- so skeptics had a concrete reason to believe.

After that, sustained adoption becomes a culture question. We made the dashboard the default starting point for every client conversation, so skipping the process meant showing up unprepared. Peer pressure does the rest.

Reveal Results, Adapt Tools, Empower Champions

I've spent 30 years building Netsurit, so change management is something I've lived through repeatedly - both internally and with clients.

The real issue isn't the process being slower. It's that people don't yet trust the new process. When we helped Novo Nordisk automate their pharmacy restocking workflow, the team was used to handling email queries manually. The automated system felt unfamiliar at first. What shifted things was showing them a Power BI dashboard where they could see the results in real time - queries resolved in 3 minutes instead of 48 hours. Visibility into outcomes replaced skepticism with ownership.

The same thing happened with Machen McChesney. Their team had years of ingrained habits. We didn't force the new tools onto their workflow - we shaped the tools around how their people actually worked, department by department. That distinction matters enormously. When people feel heard in the transition, resistance drops fast.

My rule internally: never launch a new process without identifying at least one person per team who becomes its champion. Not a manager mandating it - a peer who genuinely finds value in it first. That peer credibility spreads adoption faster than any top-down rollout ever will.

Standardize Intake to Prevent Lost Leads

As the CEO of CI Web Group, I see this resistance constantly when transitioning teams away from fast, comfortable shortcuts like sticky notes and paper logs into structured tracking systems.

When we moved our customer intake and management into CRM platforms like HubSpot, we focused on training staff through standardized intake processes. We mapped out exactly how every lead source, inquiry, and follow-up needed to be logged to eliminate confusion.

We also applied the EOS framework to align our accountability chart, ensuring the right people were in the right seats and fully trained on the tools. Once the team experienced how structured CRM data prevented leads from falling through the cracks and eliminated daily firefighting, sustained adoption followed naturally.

SASahil AgrawalFounder, Head of Marketing, Qubit Capital

Link Daily Entry to Faster Month-End Closes

Let the new process answer the team's own complaint first. When our small accounts team switched from saving vendor bills in a folder until month-end to entering each one in the accounting software the day it arrived, it felt slower because it was. Every bill took a few minutes on a day when nobody was thinking about bills.

What changed their minds was the thing they had complained about for a year, month-end closes running into late nights. You only see the difference once a full month has gone through the new way. The second close finished days earlier, with nobody hunting for a missing bill on the last evening. How many data habits get dropped in their first month, before the data has had time to say anything?

Pilot Real Tasks and Refine Requirements

When employees find a new data process slower, I ask them to compare the complete workflow rather than just the time spent entering information. For example, adding a payment reference field may initially feel unnecessary, but it can prevent colleagues from spending time investigating unmatched invoices later. I run a small pilot using real tasks and ask employees to identify redundant fields, confusing instructions and steps that create additional work. We then simplify the process while preserving the information needed for accuracy and accountability. I also explain how the changes affect downstream teams so employees understand the purpose behind each requirement. This approach helps turn resistance into ownership because employees can influence how the process works. I've learned that sustained adoption comes from demonstrating practical value and responding to feedback, not simply requiring everyone to follow a new procedure.

LHLina Haj HussienFounder and CHO, Employee Engagement & Experience Manager, Inspire

Foster Confidence Through Pilots and Empathy

I think new processes will be successfully implemented when the employees involved understand the importance of that change. The key is to demonstrate both patience and empathy. The new process will likely slow people down at first. It's important to give employees the opportunity to feel secure in their use of the new process.

It can be beneficial to create small pilot groups to introduce new processes. It is helpful to serve as the process expert and offer guidance to employees. New processes should be designed to be flexible to accommodate the feedback provided by employees.

It is better to create a shared understanding of the positive impact the process will have on the organization over the long-term. Improving the fidelity of organizational data to support business decisions will naturally reduce the number of errors made and enhance the confidence of employees in the decisions made.

Contrast Legacy Risks With Collaborative Design

I've spent 15 years helping businesses adopt new digital systems -- CRMs, eCommerce platforms, marketing automation -- and the resistance pattern is almost always the same: the new process feels slower because people are measuring it against muscle memory, not outcomes.

The reframe that works is showing what the old way was actually costing them, not in theory, but in their own work. When we migrated clients from Shopify to WooCommerce, the team managing the store initially pushed back on the transition. Once they saw that the old platform could strip access to their entire business overnight based on a policy change, "slower setup" became a non-argument.

The other thing I've learned: early resistance usually comes from people who weren't part of the decision. When we build out a new website or catalog structure for a client, we pull in whoever manages that system day-to-day before we finalize anything. They catch friction points we'd miss, and they go from skeptics to internal champions because the solution partly belongs to them.

New processes don't feel slow forever -- they feel slow until the first time the old way would have failed you. Your job is to make that contrast visible before that failure actually happens.

JRJames RowellChief Technology Officer, Capture Expense

Deliver Immediate Payoffs and Retire Old Routes

People adopt a new data process when it removes a task they dislike within the first week, so I design the rollout around that moment rather than around training. A new process usually feels slower at first because people are learning it while keeping their old habits in reserve.

With expense management, the familiar way is often a spreadsheet and a folder of receipts. The new way asks people to photograph receipts and let software read them, which feels like an extra step until they see the claim already filled in. The approach that turns resistance into sustained use is making that payoff visible immediately, and removing the old route once the new one works, so there is no parallel system to fall back on. I also listen carefully to early complaints. Some are habit. Others point to a real gap in the product, and fixing those quickly earns more trust than any training session.

RARahul AgrawalFounder & CEO, QuickIntell

Audit Duplicate Work Before Expansion

First check whether the new process really has added work. People may be describing a design problem quite accurately.

In QuickIntell deployments, we found teams using their old process alongside the new system. We added a week-three review to identify that duplication and other workarounds. We also moved away from launching the whole platform at once toward introducing one useful workflow first.

I would ask employees to walk through a real task, including the spreadsheet or manual check they still keep on the side. Agree which old steps can safely stop and which checks must stay. Make the next rollout depend on the first workflow being usable. Asking people to tolerate two full processes indefinitely is a poor adoption plan.

CMChristy Maria JoseSenior Manager - People Ops, Skill Lake

Support Gradual Learning With Accessible Guidance

Whenever a new process is introduced, some employees may hesitate to adopt it, especially when the old way feels quicker and more familiar. I think this is quite natural. People are comfortable with what they already know, and getting used to a new routine takes time.

One thing I find important is explaining why the change is happening before expecting everyone to follow it. Employees should understand what problem the new process is solving and how it can make their work easier in the long run.

Training also makes a difference. Instead of expecting employees to learn everything at once, I would break the process into smaller steps, show them practical examples, and give them time to try it themselves. Just as importantly, I would listen to their concerns and understand where they are finding it difficult.

We use Skill Lake to organize learning activities and make relevant learning materials available to employees. This gives them a place to revisit instructions whenever they need help.

I believe people are more likely to accept a new process when they feel supported rather than pressured. Giving them time to practice, listening to their feedback, and helping them through the initial challenges can gradually turn resistance into acceptance.

Simulate Audits to Reinforce Compliance

In over 23 years leading regulatory compliance at REJIMUS, I have found that staff resist new data processes when they view them as operational drag rather than risk protection. The key is demonstrating how precise data recording directly prevents costly batch rejections and cGMP violations.

When we implement rigorous record-keeping and testing specification updates, we combine hands-on training with mock inspection simulations. Showing teams how vague data or improper analytical method references trigger immediate audit citations clarifies why every required field matters.

Sustained use happens when you establish dedicated internal compliance support and regularly evaluate the workflow to remove friction. Once employees realize structured data entry prevents agonizing quality investigations and delays later, adoption shifts from forced compliance to daily habit.

BWBen WilliamsCEO & Principal Consultant, OpsStack Solutions

Invite Feedback and Provide Practical Help

When a new process feels slower, explain what it is meant to improve and acknowledge that learning it may take time. In a major truck-route expansion I worked on, the floor team needed the right tools to handle the change, which reinforced for me that a process has to work for the people using it. Give employees a chance to point out where the new steps create friction, then address what can be improved without losing the purpose of the process. Provide practical support as people learn, and check whether the process is being used and delivering the intended results. Sustained use is more likely when employees can see that their feedback matters and the process helps them do the work.

SMSoham MehtaGrowth Lead, Jitsu

Compare Parallel Systems Before Switching

Run the new process next to the old one before you ask anyone to give the old one up.

People resist a slower process because they're asked to trust it before they've seen it work. If both run side by side for a while, nobody loses anything, and the comparison does the persuading. The new way has to win on numbers the team already cares about, not in a training session.

Jitsu is built to be adopted that way. It runs alongside Segment first: Segment forwards a copy of every event through a webhook destination, nothing on the website changes, and a team compares the two pipelines on its own traffic before turning anything off. The decision to switch happens after people have seen the data match, not before.

The other half is removing what feels slow. If the new process adds steps, cut one somewhere else at the same time, or people will route around it. A process that's slower and also unproven loses every time.

Prove Automation Through Transparent Side-by-Side Results

Building AI Local Boost taught me something counterintuitive: the resistance isn't really about the process being slower -- it's about trust. People won't adopt what they can't yet see working.

When I onboarded early clients onto our automated Google Business Profile system, their staff pushed back on letting AI handle review replies. They felt it would sound robotic and damage relationships. So instead of mandating it, I had them run it alongside their manual process for two weeks and compare outcomes side by side.

Once they could literally see the response consistency and time saved, the conversation flipped completely. They stopped asking "why should we use this?" and started asking "can we automate more?"

The real unlock is making the new process transparent enough that people can judge it fairly against the old one -- not selling them on it, just showing them the evidence in their own context.

ASAlexander SmithOperations Manager, Elite Security

Show Client Recognition to Validate Digital Reports

Security operations gave me an unusual vantage point on this exact problem. When we moved officers from handwritten shift logs to digital reporting on company-issued tablets and smartphones, the immediate feedback was that typing a report in the field felt slower than scribbling notes and handling it later.

What actually broke through the resistance wasn't training harder on the new tool--it was showing officers what we could do with the data that we simply couldn't before. When a property manager could see timestamped checkpoint logs from the previous night's patrol before their morning coffee, and started calling us to say so, officers felt the difference. The process stopped being extra work and started being proof of their professionalism.

The other thing I'd flag: don't frame the old method as wrong. Officers who had worked law enforcement for years had documentation habits that kept them reliable in the field. Acknowledging that their instincts were sound--while showing them the new process extended those instincts to the client relationship--made the conversation completely different than "this is the new way, get used to it."

Sustained use came from clients visibly responding to the reporting, not from us mandating compliance. When the output of a process earns respect from the people your team is trying to protect, adoption takes care of itself.

Answer Urgent Questions Before Demanding Effort

I co-founded SellerQI, an analytics tool for Amazon sellers, and the resistance I see most is from brand managers who have checked the same three numbers in Seller Central every morning for years. Moving them to a structured diagnosis process always feels slower at first, because it is slower at first.

What turned that around was refusing to sell the new process on accuracy. People do not adopt a method because it is more correct. They adopt it when it answers a question they already have, faster than their old habit can.

So we start with the question that keeps them up at night, usually "why did sales drop on this ASIN?" The old habit is opening the Business Report, then the Advertising console, then the inventory page, and guessing. The new process checks a fixed sequence: Featured Offer percentage, sessions, conversion rate, inventory status, suppressed or stranded listings, then ad spend. The first time it points to a lost Featured Offer or a listing suppression the manager would have missed, the process sells itself.

Two practical rules help. First, run the new process alongside the old one for a few weeks instead of replacing it on day one, so nobody feels their judgement is being taken away. Second, cut every step that does not change a decision. If a check has never altered what someone did next, it goes.

Early resistance is usually a sign the new process asks for effort before it gives anything back. Flip that order and adoption follows.

Use Inputs to Drive Visible Decisions

I've dealt with this at Refresh Digital Strategy and Icebox, where bad data turns into either bad marketing decisions or messy rental logistics. My rule is: don't sell the process, sell the decision it makes possible.

At Refresh, we had teams tag work by location, service, and channel so we could see which multi-location campaigns needed SEO, content, or social support. It felt slower at first, so we cut any field that didn't change a real decision.

At Icebox, intake details like rental duration, unit size, delivery location, and power availability matter because our trailers need the right setup, like a 110-volt, 20-amp dedicated circuit or generator. When the team saw that cleaner intake meant fewer back-and-forth calls before delivery, the process stopped feeling like admin work.

The shift happens when you review the new data in front of the team and use it to make actual calls. If people enter data and it disappears into a spreadsheet nobody mentions again, adoption dies fast.

VRVishnuvardhan Reddy KaithapuramSoftware Development Engineer, Amazon

Build Trust With Reliable Checks and Maintenance

When a new data process feels slower at first, I do not try to win people over with a presentation about the process. I start by finding the one part of their current work that is actually painful, and I make the new process better at that one thing first. People will put up with extra steps if the result they care about gets easier to trust or easier to find.

In my work building and maintaining data pipelines at Amazon Advertising, that usually means showing the work, not describing it. When I built the Insight Ingestion Orchestration Service from scratch, the point was not to add another tool for teams to learn. It was to bring ingestion, checking, and delivery into one place so teams did not have to chase down where a number came from. When a team can see the checks that ran, where the data came from, and what changed, they start to use the new process because it answers their own questions faster, even if the first few runs take longer to learn.

I also keep the old way available for a short, clear period, and I say in advance when it will end. That matters. If people feel forced to switch overnight, they resist. If they can run both ways for a while and compare the results side by side, they can see for themselves whether the new process is catching problems the old one missed. I have found that comparison does more than any training session. It turns a debate about speed into a conversation about accuracy.

Another thing that helps is removing work, not adding it. If a new process asks for extra manual checks, it will fail. If it automates a check people used to do by hand, or if it gives them a clear error message instead of a silent failure, they notice the difference right away. I try to make the first version of a process do one useful thing well, rather than asking people to learn a full new system at once.

Sustained use comes from support after the switch, not from the launch. When something breaks, I want people to get a clear answer quickly, and I want the fix to be visible so they know the process is being maintained. Over time, that builds trust in a way that a rollout plan cannot. People keep using a process when it keeps working, when it saves them from rework, and when they know who to talk to if it does not. Slower at first is fine if the process is more reliable. Teams will adopt a slower process that they trust. They will not keep using a faster one that leaves them guessing.

DGDaniel GohChief Marketing Officer, RankAISearch

Measure Bottlenecks and Automate Manual Tags

When I moved an admin task at TradingFXVPS from copy-pasting between emails and a spreadsheet to a fully data-driven process, the team felt it had slowed down. I spent a week with two team members timing out the original process and the new one, and their feeling was half right. The new process was on average faster than the old, but one step in particular - manual tagging of records - added significant friction. Writing a very small Python script with an AI step to tag records for them to verify was far faster than the original, and the old spreadsheet was never opened again. The team at TradingFXVPS is very small and this was one process, so I wouldn't claim this to work in all situations, but the key to overcoming resistance to change is to identify the one bottleneck in the current process and fix that step, not attempts to energize the team as a whole. I also ensure that I am only changing one thing at a time and that I document what I have done. If you change 10 things at once, you have no idea what has helped, and soon everyone will be tired.

XBXavier BerknessPresident & CTO, PERC Engage

Phase Rollouts and Set a Firm Sunset

Large data rollouts create resistance because employees absorb new rules, screens, and accountability at once. A phased introduction works when each phase removes a specific pain. Start with information needed to prevent the costliest handoff failure, then add fields after that habit is stable. I have seen enthusiasm return when staff realize the rollout is not an endless expansion of administrative work.

The key is to preserve a clear sunset for the old method. Running two systems indefinitely teaches employees that the new process is optional. Set a short overlap, identify the decision date, and provide a reliable way to resolve exceptions before retiring the familiar workaround.

ACAmanda CrookshanksGeneral Manager, Reineke Ford Inc.

Map Rework and Let Peers Coach

I've had to do this as Director of Digital Retail across 12 stores and now as a GM, especially when moving teams from "I know where my notes are" to consistent CRM, finance, and digital retail processes. The mistake is trying to win with a policy memo; you win by making the new process solve a pain they already feel.

One example: when a sales or BDC team felt entering better customer data slowed them down, I would sit with them and map where time was actually being lost later: duplicate calls, missed follow-ups, re-explaining trade details, or F&I not having what they needed. Once they saw the rework, the "extra step" became less annoying.

I also try to create a short bridge period: let people use the new process on real customers, then review one or two deals together and show what got easier downstream. Peer proof matters more than management proof, so I lean on the first few people who adopt it well to help coach the rest.

The key is not "because corporate says so." It's: here's how this helps you sell cleaner, hand off smoother, avoid surprises, and give the customer a better experience. Sustained use comes when the team feels the process protects their time instead of stealing it.

Automate Repetitive Tasks, Retain Human Review

Over my 28 years in industry and leading Triple Digital, I've found that early resistance usually happens when teams view a new data process as administrative overhead rather than a tool built to help them. The key to turning that around is framing the shift around eliminating routine friction rather than simply adding tracking steps.

We tackle this by conducting a one-to-two-week workflow audit where staff identify their own repetitive bottlenecks, like manually copying client details into a CRM or chasing down signed agreements. Once they see the new data workflow directly automate those specific pain points inside their practice management software, the upfront effort makes sense to them.

To secure sustained adoption, we maintain a clear human-in-the-loop approach where the system handles the clerical grunt work while employees retain final review and decision-making power. When the team realizes the process frees them up to focus on high-value client strategy instead of manual data entry, resistance turns into genuine buy-in.