When I joined the Nia chatbot platform redesign team, I quickly realized that our biggest challenge wasn’t adding new features — it was making existing capabilities more usable. Nia is a no-code platform that enables teams to build, deploy, and manage chatbots without writing a single line of code. Despite its power, the experience was overwhelming, especially for users who needed to work quickly and confidently.
So we set out to answer a simple question:
“How can we make building a chatbot feel less like assembling IKEA furniture without the manual?”
Getting Closer to Our Users
We began by connecting with the people behind the bots. I conducted 6 in-depth interviews with both experienced users and newcomers to the platform. These ranged from product managers and marketers to customer success leads — people who valued independence from engineering teams but often struggled to translate their ideas into functioning bots.
We also ran usability testing sessions on the current platform, observing real users as they attempted tasks like creating a new bot, configuring intents, and training responses.
Learning from the Landscape
o frame our improvements, we also looked outward. We conducted a competitive analysis of other no-code platforms — like Dialogflow CX, Landbot, and Botpress. While some platforms were extremely powerful, they came with steep learning curves. Others were beautifully simple but lacked depth.
We realized that our redesign needed to balance clarity and control. Our users wanted flexibility without complexity.
What We Found
As the research came together, four key themes emerged:
Cognitive Overload Was Real
The existing interface tried to show everything at once. It had a single-column layout that crammed configuration, training, and design into one continuous view. Users often had to scroll endlessly or open multiple tabs, which made even basic workflows mentally exhausting.Navigation Was a Maze
Switching between different parts of the bot — like intents, responses, and entities — felt like jumping between islands without a bridge. There was no clear sense of where users were in their journey or what step came next.Critical Actions Were Buried
In one usability session, a participant took almost a full minute to find the “Add Bot” button. It was hidden among a clutter of cards and panels, which meant users couldn’t even begin their journey without friction.Invisible Processes Created Doubt
After clicking “Save” or “Train Bot,” there was no immediate feedback — no progress bar, no confirmation message, not even a spinner. Users were left wondering, “Did that even work?”
These insights didn’t just show us what was broken — they showed us how users were thinking, feeling, and adapting to the platform’s limitations.
Meet Sneha— Our Archetypal User
We created a persona based on our interviews to keep our design team grounded:
Sneha, 32, Product Manager
Tech-savvy but not technical
Builds bots to support product workflows
Wants clarity, speed, and self-sufficiency
Gets frustrated by unclear layouts and missing feedback
How We Responded
Armed with research, we reimagined the platform with a user-first mindset:
Split View Layout: We divided the screen into left (navigation) and right (working area) panes to reduce cognitive load and improve orientation.
Consistent Visual Hierarchy: Clear sectioning, spacing, and contrast made it easier to find information at a glance.
Action Visibility: Buttons like “Add Bot” were made prominent and contextually placed at the start of the user flow.
Feedback Loops: We added visual indicators for actions like saving, training, or syncing, so users were never left wondering what was happening.
The Result
Early feedback from internal demos was clear:
“It just feels lighter. I know where to go next.”
“I don’t have to think twice — it just makes sense.”
This research journey was a reminder that even powerful tools can feel powerless if they don’t support how users think, move, and make decisions. By listening, observing, and testing, we turned a complex interface into a platform that works with users — not against them.
Impact
Reduced Time-to-Launch: With a clearer layout and streamlined workflows, users reported being able to create and deploy bots faster, especially first-time users like Sneha who previously felt blocked by ambiguity.
Improved Confidence and Independence: The enhanced feedback loops and visible progress indicators empowered non-technical users to navigate the platform with certainty, reducing reliance on engineering or support teams.
Increased Feature Adoption: By simplifying navigation and surfacing critical actions, more users discovered and used previously hidden or underutilized features — leading to a more robust use of the platform.
Lowered Cognitive Load: The split-view design and improved visual hierarchy significantly reduced cognitive strain, especially during multitasking. Users felt more oriented and less overwhelmed.
Positive Internal Reception: Early demo sessions sparked enthusiastic responses from stakeholders and product teams, validating that the redesign not only improved UX but aligned with broader business goals for scalability and customer retention.
What Sets It Apart
- Designed for Real-World Users, Not Power Users: While many no-code platforms cater to technical users, Nia’s redesign was purpose-built for cross-functional teams — product managers, marketers, and support leads — who think in outcomes, not code.
- Clarity Without Compromise: Unlike competitors that forced a trade-off between simplicity and depth, the new Nia interface offers structured flexibility — empowering users without overwhelming them.
- Task-First, Not Feature-First: The redesign flipped the experience from a tool-centric to a goal-centric model. Actions like “Add Bot” or “Train” are now placed where users naturally look for them, reducing friction and guesswork.
- Feedback as a Design Principle: From saving to training, every critical action now provides real-time visual feedback, building user trust — a subtle but powerful shift in the emotional experience of using the platform.
- Rooted in Field Insights: Every design decision was grounded in direct user interviews, real-world observation, and competitor benchmarking — ensuring practical improvements, not just aesthetic upgrades.