When people picture an AI rollout, they picture an event. A kickoff meeting. A new platform with a login. A slide that says "transformation" and an elected champion who gives a talk on Friday afternoon. (And, if you're based in Kansas City like us, sometimes there's world-renowned barbecue involved.)
On a recent client project, we intentionally did none of the above. We didn't invent a brand-new way of working. We didn't hold months of discovery meetings with the entire team, hijacking people's calendars with meetings that they didn't ask for and didn't have time to attend. We didn't produce another AI-generated slide deck.
Instead, we emptied our cups and quietly sat down, human-to-human, over coffee with the people doing the actual work. We asked them what their biggest pain points were, listened to their answers and nudged them towards small changes that help collect useful data to build digital feedback loops without any additional effort on their part. Small local nudges with outsized impact on the system. We call these 'leverage points.'
Once we had enough of the initial map, we selectively planted some nudges inside the team's existing week, and then we mostly stepped back. A few weeks later, the team was using the new workflows without being asked.
Here's what we did, and why we think it worked.
Start where the team already is
Every team already has a rhythm: a Monday check-in, a shared inbox, a spreadsheet everyone quietly hates, a weekly report that takes someone half a day. We didn't ask this team to change that rhythm. We asked a simpler question: which part of your existing week costs the most time for the least thinking?
That's where we planted. The new process went into the tool they already opened every morning, at the step where they already did the work by hand. No new login to remember. No new meeting to attend. The people doing the task saw it change in place.
A garden bed that already gets watered is a better place for a new seedling than a corner of the yard with tons of weeds, where nobody walks past.
Keep it small enough to ignore
The first version did one job for a small group of people. It drafted, a person checked, and the work moved on. That's it. There was no company-wide switch to flip, and nobody was told their job was changing forever.
Small has a hidden benefit: it doesn't create resistance. A big announcement makes people ask what it means for them. A small improvement to a task they dislike makes them ask a different question: Nice. Could I get that for my day too?
Let the time saved do the selling
This is the part we'd most want other owners to hear. We didn't run a campaign to win people over. We didn't need to. The people who used the new process got a chunk of their week back, and they noticed. They mentioned it to the person at the next desk. That person asked for the same thing.
The return showed up on the people's own time, quickly, in a form they could feel. Nobody had to be convinced by a chart. When stakeholders see immediate payback on their own hours, adoption stops being a change-management problem. It becomes a queue of people asking to join.
Give it an owner and a review step
Quiet doesn't mean unmanaged. Every process we planted had a named owner and a human review step before anything reached a client or touched money. That's what keeps a small win from drifting into a small mess. It also kept trust high: people could see a person was still in charge of the result.
What we'd tell another owner
- Plant inside existing habits. Put the change where the work already happens, not in a new place people have to remember to visit.
- Start with one task and a few people. Small improvements travel by word of mouth.
- Pick work where the payback is felt quickly. Hours back in someone's own week beat any slide deck.
- Skip the fanfare. If it works, people will tell each other. If it doesn't, you've avoided a loud failure.
- Name an owner and keep a human check. That's what lets it last past the first month.
How this fits our Groundwork approach
This is the same shape as Groundwork, our fixed-fee four-week engagement. We Map the work worth improving, Plant a working first version inside the way your team already operates, Root it with an owner and a review step, and Grow from there only once it has earned its place. You don't need a big cultural moment. You need to gently nudge an existing process that gives people time back immediately.
If you'd like your team to adopt AI without the drumbeat and the disruption, we're glad to talk it through. Proudly based in Kansas City. Say hello.