Project Overview
The goal of this project was to integrate an intuitive voice assist feature into a connected bike application, ensuring a seamless and safety-first riding experience. The system was designed to provide hands-free functionality while adapting to the rider’s context, such as speed conditions and environmental factors.
To achieve this, we structured the voice assist system to be context-aware, meaning commands were dynamically categorized and activated based on riding conditions. This ensured that riders could safely access essential features without distraction.
Role
UX Designer
Team
2 UX Designers, 2 Engineers, 1 Product Manager
Duration
1 month
Role
Axure, Figma, Miro
My Contribution
I researched real-world riding scenarios to understand voice interaction needs and identified gaps in the existing product. I structured voice commands based on speed and safety parameters, designed user flows and wireframes, and built a failure handling system with smart feedback. Through usability testing and iterations, I optimized the voice assist experience for seamless and safe interactions.
What is TVS Connect?
TVS Connect is a travel app designed to enhance the two-wheeler riding experience through TVS SmartXonnect technology. The app simplifies ride monitoring and provides features that make a riders' journey safer, more convenient, and more intuitive.
The problem was that riders sought a more connected experience, and competitors already offered advanced features that enabled hands-free riding and real-time performance analysis. Recognizing this gap, we aimed to strengthen TVSs' riding community by integrating a smart voice assist feature into the existing TVS Connect application, ensuring riders could access key information and controls seamlessly and safely while on the go.
What were we solving?
Competitors in the similar segment
Hero MotoCorp – Integrated "Hero Connect" with Google Voice Assistant in models like the Hero Xpulse 200 4V and Hero Destini 125 XTEC for hands-free navigation and call controls
The Ather 450X electric scooter includes voice-enabled navigation and command support via its connected Ather App.
Royal Enfield Introduced Tripper Navigation with limited voice-enabled assistance for models like Meteor 350 and Super Meteor 650.
Research
Conducted user interviews and field studies with riders to understand common pain points
1
Identified more than 80 voice commands and structured them into three use cases for optimal user experience.
2
Benchmarked industry best practices from leading brands analyzing their voice-assist functionalities, safety mechanisms, and real-time adaptability.
3
My Approach and Execution
Pain Points & Uncovering Insights Hover to uncover
Pain Point 1
Riders often struggle with manual controls while riding, leading to distraction and reduced safety.
Pain Point 2
Riders faced difficulty in using all voice commands while riding at high speeds, leading to usability and safety concerns.
Pain Point 3
Users abandon voice assistants that frequently misinterpret commands or fail to provide alternative solutions.
Pain Point 4
Users often found voice assistants overwhelming due to lack of command discoverability and confusion about what commands were available.
Defining Context-Aware command categories
Standstill Commands (O kmph)
1
These commands are available only when stationary, these commands allow riders to access ride statistics, adjust settings, and view important documents that require greater attention.
Standard Riding Commands ( 0- 80 kmph)
2
At moderate speeds, riders need quick, hands-free access to navigation, music control, call functions, and status updates, ensuring minimal distractions.
Safety-first Commands (Above 80 kmph)
3
At high speeds, only critical alerts, emergency commands, and basic ETA updates are enabled, while complex interactions are restricted to prioritize safety.
We organized voice commands by the rider's speed and needs for safety and ease of use. This allowed riders to access important features while reducing distractions at higher speeds.
To ensure our categorization was both intuitive and effective, we conducted a collaborative activity on Miro where stakeholders, designers, and real riders came together to analyze and classify these 80+ voice commands. This hands-on session provided valuable insights into which commands should be prioritized at different speeds and how riders naturally interact with voice features while on the road.
To further reinforce safety, if a rider attempts a restricted command while riding above 80 kmph, the system automatically triggers a voice prompt advising them to slow down before executing the command. This proactive feedback mechanism helps reduce distractions and ensures that riders remain focused on the road.
Designing for different scenarios
To create a seamless and intuitive experience for riders, I designed a series of interaction flows that addressed various use cases, from onboarding new users to managing high-speed command restrictions.
Educating the user about the newly added voice assist feature and the commands available
When users first try the voice commands, they'll get a helpful introduction. This flow shows them what commands they can use and teaches them how to talk to their bike. Everything is explained step by step to make it easy to learn and use.
First-Time User Onboarding Flow
This flow represents the first-time user experience when they interact with the voice assist feature. The onboarding is designed to help users become familiar with available commands while ensuring a guided experience.
Error Handling Flow for unrecognised or misunderstood commands
When the voice assistant doesn't understand what you say, our error handling flow helps you fix the problem. It gives you clear suggestions and helps you try again, making it easy to get your command right without getting frustrated.
Command Locked for Safety Flow
This flow ensures that high-speed safety restrictions are enforced, preventing users from executing non-critical voice commands while riding above 80 kmph. The system prioritizes safety by limiting command functionality and guiding the rider to slow down before using restricted features.
Cluster Interface in Action
Bringing Voice Interactions to the Rider’s Dashboard
The cluster interface plays a crucial role in delivering real-time feedback and ensuring a seamless voice-assisted experience while riding. This section highlights how the voice assistant interacts with the cluster display, providing visual feedback, alerts, and confirmations to keep the rider informed without distractions.
To further reinforce safety, if a rider attempts a restricted command while riding above 80 kmph, the system automatically triggers a voice prompt advising them to slow down before executing the command. This proactive feedback mechanism helps reduce distractions and ensures that riders remain focused on the road.
Impact Made
35% Increase in sales
The TVS Jupiter 125, featuring SmartXonnect voice assist, saw a 35% increase in sales due to demand for connected two-wheeler experiences
TVS users reported a 20% reduction in manual phone interactions while riding, thanks to voice-assisted features
Reduced usage of phone
80% of riders using TVS SmartXonnect stated that real-time voice feedback on navigation and alerts improved their riding convenience and reduced distractions
Increased Convenience
SmartXonnect’s real-time alerts & safety prompts have helped riders improve reaction times by up to 1 second, potentially preventing mishaps at higher speeds
Increased Safety
Initially introduced with the TVS Jupiter 125, the SmartXonnect system was later integrated into other TVS models, including the TVS NTorq 125, TVS iQube, and TVS Ronin, enhancing the connected riding experience across different vehicle categories.
In Retrospect …
Designing for Context Matters
Unlike traditional voice interfaces, designing for a high-speed riding environment required prioritizing safety over convenience. Understanding when and where a rider can interact with the system was critical in shaping the experience.
The Balance Between Safety & Usability
Implementing command restrictions at high speeds was essential, but it also required effective communication. Providing real-time feedback through voice prompts and the cluster display helped prevent frustration while keeping riders informed.
Cross-Functional Collaboration is Essential
Working closely with developers, UX designers, and stakeholders helped align design intent with technical feasibility. The categorization of commands based on speed required significant iteration and validation to ensure usability and compliance with safety standards.
View More Projects
