{"id":1894,"date":"2024-11-28T18:24:59","date_gmt":"2024-11-28T18:24:59","guid":{"rendered":"https:\/\/wanchamehtadesign.in\/?page_id=1894"},"modified":"2025-06-18T06:53:03","modified_gmt":"2025-06-18T06:53:03","slug":"chatbot","status":"publish","type":"page","link":"https:\/\/wanchamehtadesign.in\/?page_id=1894","title":{"rendered":"Chatbot"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

When I joined the Nia chatbot platform redesign team, I quickly realized that our biggest challenge wasn\u2019t adding new features \u2014 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.<\/p>

\u00a0<\/p>

So we set out to answer a simple question:
\u201cHow can we make building a chatbot feel less like assembling IKEA furniture without the manual?\u201d<\/strong><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

Getting Closer to Our Users<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

We began by connecting with the people behind the bots. I conducted 6 in-depth interviews<\/strong> with both experienced users and newcomers to the platform. These ranged from product managers and marketers to customer success leads \u2014 people who valued independence from engineering teams but often struggled to translate their ideas into functioning bots.<\/p>

\u00a0We also ran <\/span>usability testing sessions<\/strong> on the current platform, observing real users as they attempted tasks like creating a new bot, configuring intents, and training responses.<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

Learning from the Landscape<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

o frame our improvements, we also looked outward. We conducted a competitive analysis<\/strong> of other no-code platforms \u2014 like Dialogflow CX<\/strong>, Landbot<\/strong>, and Botpress<\/strong>. While some platforms were extremely powerful, they came with steep learning curves. Others were beautifully simple but lacked depth.<\/p>

\u00a0<\/p>

We realized that our redesign needed to balance clarity and control<\/strong>. Our users wanted flexibility without complexity.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

What We Found<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

As the research came together, four key themes emerged:<\/p>

  1. Cognitive Overload Was Real<\/strong>
    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.<\/p><\/li>

  2. Navigation Was a Maze<\/strong>
    Switching between different parts of the bot \u2014 like intents, responses, and entities \u2014 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.<\/p><\/li>

  3. Critical Actions Were Buried<\/strong>
    In one usability session, a participant took almost a full minute to find the \u201cAdd Bot\u201d button. It was hidden among a clutter of cards and panels, which meant users couldn\u2019t even begin their journey without friction.<\/p><\/li>

  4. Invisible Processes Created Doubt<\/strong>
    After clicking “Save” or “Train Bot,” there was no immediate feedback \u2014 no progress bar, no confirmation message, not even a spinner. Users were left wondering, \u201cDid that even work?\u201d<\/em><\/p><\/li><\/ol>

    These insights didn\u2019t just show us what was broken \u2014 they showed us how users were thinking<\/strong>, feeling<\/strong>, and adapting<\/strong> to the platform\u2019s limitations.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

    \n\t\t\t\t\t\t
    \n\t\t\t\t\t
    \n\t\t\t
    \n\t\t\t\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t

    Meet Sneha\u2014 Our Archetypal User<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t

    We created a persona based on our interviews to keep our design team grounded:<\/em><\/span><\/p>

    Sneha, 32, Product Manager<\/strong><\/em><\/span><\/p>