When we first set out to add AI to our platform, we approached it like most teams do—we thought of it as just another feature. The goal seemed simple: give users a way to ask questions and get answers. On paper, it worked. But in practice, something was missing. The responses felt disconnected, sometimes generic, and often didn’t move users forward. It could talk, but it wasn’t actually helping.
At CMHWorks, one of our core principles is simple: Making Technology Easy. And when we stepped back and looked at what we had built, it was clear we weren’t living up to that standard. Users shouldn’t have to interpret vague responses or figure out what the system “means.” Technology should reduce effort, not add to it. And based on my experience using AI, we did not want our users to feel the same way.
That realization changed everything.
Our “Eureka” Moment
We stopped asking how to “add AI” and started asking what it would look like if we truly applied our principle—if this experience actually made things easier for our users. Not just answering questions, but understanding what they were looking at, what they were trying to do, and what mattered in that moment. That shift—from tool to experience—became the foundation for everything that followed.
Instead of letting it guess, we grounded it in the reality of the platform. It began to understand what users were seeing, what actions were available to them, and what was actually happening in their environment. The answers didn’t get longer or more complex—they just started to make sense. And more importantly, they became useful. Not just explanations, but guidance that reduced friction and helped users move forward without hesitation.
Context Is Everything
Then we tackled something even more important: continuity. Conversations shouldn’t feel like starting over every time. Making technology easy also means making it feel natural. Being able to pick up where you left off, to continue exploring an issue or revisit a previous question, turned isolated interactions into something much more intuitive. It started to feel less like using a feature and more like having a conversation that moves with you, and doesn’t leave you frustrated.
From there, we focused on the experience itself. We wanted it to feel responsive, immediate, and effortless. Instead of waiting for a response, users see answers take shape in real time. That small shift made a big impact. It reduced the feeling of waiting and replaced it with a sense of interaction—something that feels alive and present, rather than distant.
Feeling the Experience
But the biggest shift wasn’t technical—it was human. “Making Technology Easy” isn’t just about functionality. It’s about how something feels to use. People don’t want to interact with a system that sounds like a system. They want clarity, reassurance, and direction. So we stripped away the technical language, removed the friction, and focused on making every interaction feel natural and helpful – a meaningful user experience.
What we ended up building isn’t just something that answers questions. It’s something that helps people understand what’s going on and what to do next, right in the moment they need it. It removes uncertainty, simplifies decisions, and makes the entire experience feel lighter.
A Softer Landing
We didn’t set out to build a complex AI solution. We set out to make things easier—and we kept refining until it felt that way.
Along the way, it stopped feeling like something we added…
and started feeling like something the product needed all along.
And this is just the beginning.
