UX Case Study

Strategies for Improving User 

Navigation: A Collaborative Process
for a “Launch Page” UX Design

Leading a product team through a 
series of
collaborative, online workshops to help discover
user pain points with their navigation of a
complex web app

The Problem

“Vehicle Ordering” is one of the most important modules that users of the FleetView® enterprise web apps use. The app allows clients and in-house users to manage and place orders for fleet vehicles. “Vehicle Ordering” is also sophisticated and data intensive. Within each order, users can select from hundreds of vehicle options and add complex specialty items. Despite the comprehensive features and powerful functionality, the web app does not currently have a home page or launch page.

For such a complex program, users need a simple way to navigate, a fast way to get the big picture, and a clear way to see the user flow of the program. A comprehensive launch page, which addresses these user needs, is a critical addition for the “Vehicle Ordering” web app.

The Solution

My first step before starting the UX Design for a new launch page for “Vehicle Ordering” was to design and conduct a series of workshops with product stakeholders. Participants were members of the Product Team, the Product Owner, and Business Analysts. I designed the workshop sessions to be collaborative. I did research and found that Miro, an online collaborative whiteboarding web app would support our collaboration even though we were all working remotely.

I was the workshop leader for multiple sessions with this group. As a team, a number of user needs and pain points were identified.

Users need:

  • Broad sections that represent the functional areas
  • Descriptive text for each section
  • A way to meet the needs of 3 different groups of users:
    • In-house – very familiar with the app
    • Clients (external) – medium familiarity with the app
    • New or less frequent users
  • Onboarding for users new to the app

Based on all of the identified user needs and pain points, I decided to use cards as a way to contain, organize, and simplify the broad topic sections. I had done UX/UI research on cards and learned of their many benefits for users. The “Launch Page” is a perfect place to use cards.


As part of the multiple workshop sessions, I showed participants new versions of my UX design. Each version addressed one or more of the user needs and pain points. Workshop sessions continued until the UX/UI design evolved to meet all the user needs and pain points. The product team was thrilled with the iterative workshop process that I led and the successful final design of the “Launch Page”. And the “Launch Page” UX that I did has been assigned a story number for final grooming leading to being added to a sprint for development.

UX design for a new “Launch Page” for the “Vehicle Ordering” web app. I led the Product team through a series of workshops to identify user needs and pain points. This helped guide my UX design of a new “Launch Page”.


My Miro boards for the workshops I led for the Product Team and stakeholders. I helped the team grapple with the menu item verbiage and explore the question, “Is our naming of the web app sections the clearest it can be?” This exercise provided clarity and some of the text was changed before finalizing the new “Launch Page” UX design.