Project Info
The Problem
The Solution
The Process
To bring myself up to speed, I reviewed a large amount of documentation, including the interviews themselves and user personas. I familiarized myself with the current experience and other LinkedIn marketing websites to determine problem areas and commonly used interaction patterns. I also worked closely with the content designer to ensure I understood the product offerings, as well as previous explorations and business decisions. I completed a site audit to determine user problems.
Site audit
Inconsistent product naming and categorization.
Didn't show all available products in one area, or include clear product descriptions—even on the all products page!
Header and footer navigation product listings differed from each other.
Inconsistent styling and information architecture, unclear copy.
Visual Decision tree: help the user determine needs via questions
Additive build: core products + add ons of additional value until all products are included
Talent Lifecycle/Journey: how the product portfolio holistically solves for business needs across entire talent journey
Category buckets: business challenges with filtering
What are current best practices? What architecture is easily understood?
Comparative analysis
Category Buckets/Grouping by product type was by far the most common pattern. Checklists were used for comparing two or more products. Visual Decision trees were hard to find – most took a quiz form and seemed like an engineering challenge or a lot of clicks.
How might we visualize how our products connect to each other (and how they don’t), so users can understand which ones are right for them, learn more about them, and consider buying?
Site map
The best change for users was to restructure the entire site.
The visual decision tree was best placed as the main CTA on the home page. Related products would be shown as an add-on once the quiz was finished. This could also solve the talent lifecycle story.
The all products page needed to show all products, with a clear short descriptor of each to help user's determine what was right for them.
The comparison pages needed to show products that were a true apples to apples comparison, instead of comparing against products that served a different need.
The top navigation had already been researched with new product categories for site-wide consistency.
Typographic hierarchy for the entire site needed updated.
What if we implemented an e-commerce structure for product discovery and eventual purchase experience?
Wireframes
Hi-Fi iterations V1-4
Hi-Fi iterations V5-9
The final all products page put like products together. For similar products, the more advanced version was placed on the right. Filters were included to help users determine their needs. Product names take you directly to information about that single product.
I stuck two CTAs, a button or tertiary text link, to simplify user comprehension. Products that could be bought online used a primary button, while products that need to be bought via a sales representative used a secondary button. The tertiary text link was used as progressive disclosure to take users to the compare page for that product, where they could find more information.
The final compare products pages used left hand vertical tabs, to navigate between product functions. It included a link to the all products page so users could get a complete overview.
The page header included language about the comparison experience to set context, while the first section under the product title was used to give more information about the product function.
Cards were used for each product, with consistent button styling , title links, and product version placement as the all products page. Icons were included on the top right, next to the title, to help users determine which product was best for their company size. This consistency helps reduce user's mental load.
Beneath this section was the true comparison experience: a checklist for each product version, with like functions grouped together in accordions for progressive disclosure. This provided a true apples to apples overview.
The Takeaway
What are current best practices? What architecture is easily understood?
I was brought on to help redesign SimpleStage's product interface and develop a design system that would be adaptable, expandable and flexible as the platform grows and evolves.
Combine 3 project touch points (design presentation, feedback and design iterations, and bug tracking) into one, easy-to-use product.
UI Designer
Design system management
UX design. support