What was your role in developing the Majesco Copilot Assistant?

As a UX Specialist, I worked on refining user flows, ensuring clarity in Copilot interactions, and optimizing decision-making processes. I focused on making sure users could easily understand and complete tasks while always having the option to exit if needed.

How did you approach designing and testing the user flows?

We used Miro boards extensively to map out, test, and refine conversation flows before development. This helped us visualize the process, identify pain points, and ensure a smooth user experience.

What tools did you use to build the Copilot interactions?

We leveraged Microsoft’s Copilot Studio to create topics and structure conversations. Since Majesco was one of the first companies to adopt this technology, I was frequently on calls with Microsoft to provide feedback and collaborate on best practices.

How did you ensure clarity in yes/no interactions?

We carefully structured yes/no questions to avoid ambiguity and tested them with users to confirm they were easy to understand. Additionally, we ensured that users always had an option to exit the flow at any stage without confusion.

What steps did you take to support development through UX work?

By outlining clear, well-structured flows in Miro and Copilot Studio, we provided developers with a solid foundation for implementation. This ensured consistency between design intent and final product functionality.

How did user testing influence the Copilot’s design?

Through iterative testing, we identified areas where users struggled with phrasing, flow complexity, or decision fatigue. We refined interactions based on this feedback to create a more intuitive experience.