Composition of multiple devices, including a laptop and smartphone, displaying the responsive web app interface

Project Summary

Challenge

The team was tasked with creating a mobile version of DEL that matched the established design and functionality of the desktop version.  The key challenge was to adapt the interface without compromising the user experience or essential features.

Approach

Understanding the importance of user experience continuity and the limitations of mobile screens, I organized a workshop with conversational design specialists and engineers. This UX-led exercise was the first step in evaluating the situation and aligning the team’s efforts.

Result

After the launch, user and stakeholder feedback started coming in. I recommended creating a backlog to document and prioritize this feedback, enabling us to address it in future tests and updates, ensuring the mobile experience evolved with user needs.

My Role

As the Sr. UX Architect, I led the UX design, overseeing a Jr. UX Designer while collaborating with copywriters, product designers, and engineers.

Discover

Research findings revealed

Initial Research was conducted on the current desktop experience using cognitive walkthroughs and stakeholder interviews to gather insights that will shape the mobile design strategy.

Insights into Action

Define

Defining features and scope

During the Define stage, a feature prioritization exercise was conducted to identify the primary features, which helped to scope the project work and finalize the brief for the client’s review.

Feature Prioritization Matrix

Understanding the importance of user experience continuity and the limitations of mobile screens, I organized a workshop with conversational design specialists and engineers.

I asked them to identify the five most crucial features that users need to control their experience. The result was a feature prioritization matrix, which served as a foundation for the mobile design strategy.

I then tested our assumptions with users to ensure the mobile experience matched their mental models and expectations of how it should work.

Feature prioritization diagram with features mapped on XY axes, showing importance versus feasibility
Designed in FigJam
Design

Designing mobile experience

During the Design stage, wireframes were created to map out the navigation, information architecture and functionality of the mobile experience, followed by usability testing and multiple iterations based on user and client feedback.

Wireframes

After key features were identified, I created low-fidelity wireframes to map out key functionalities. These included:

  • The first screen introduces the experience. Users can choose to proceed and must consent to data collection before accessing the app.
  • When users select the chat option at the beginning of a session, they are immediately directed to a screen with the chat feature activated.
  • When users choose to communicate using voice, the voice option will be activated, allowing them to switch to chat at any time.
  • When user paused session, there will be a notification and option to continue either by chat or voice.
  • To protect user’s privacy digital assistant experience will be paused after 5 min idle time.  User will see a notification on the screen upon returning.
Wireframes flow illustrating the navigation for a mobile experience, showing step-by-step user interactions
Designed in Figma

Usability testing & layout iterations

Due to a tight timeline, I conducted remote unmoderated rapid usability testing using Lyssna platform. The goal was to test the control panel on the mobile screen, focusing on user interaction with key features. I conducted a first-click test where users were asked to complete five tasks.

First Click Test Results

By observing where users clicked first, we could gauge their instinctive reactions and identify any areas of confusion or hesitation. The insights gained from this test allowed us to make informed design adjustments as follows:

  • Based on user feedback, controls for sound and mic were made accessible and visible on the left side of the screen at all times to improve ease of access during interactions.
  • The pause/resume icon was redesigned to better communicate its dual functionality, addressing user confusion observed during testing.
  • Due to limited screen real estate, labels were added to icons in the submenu rather than on the main screen, ensuring clarity without cluttering the interface.
Side-by-side comparison of two interface designs showing changes made after usability testing
Remote usability testing was performed using Lyssna

After the First-Click Test, a series of subsequent usability tests and layout iterations were conducted based on user feedback. Each iteration focused on refining the design, addressing user-identified issues, and improving the overall user experience.

Deliver

Finalizing and executing

In the Deliver stage, the focus shifts to preparing the layout and functional specifications document for development. The outcome is a polished, user-validated product, with post-launch evaluation and feedback guiding future improvements.

Key Deliverables

During the Deliver phase, key steps were taken to ensure the successful implementation and launch of the mobile experience:

  • Finalized the layout and functional specifications, enabling the development team to begin building the mobile experience.
  • Tested the product throughout the development cycle and iterated based on user feedback.
  • Launched the product, followed by comprehensive QA testing to ensure quality and performance.
  • Created a backlog of updates for the next phase to ensure the mobile experience continued to evolve in response to user needs.
Multiple smartphones showcasing the final product screens of the mobile experience