Product DESIGN | RESEARCH

Re-designing order history for Microsoft

Post purchase matters
TEAM

1 Designer, 1 PM, 10 Engineers

TIMEline

September 2020 - Jan 2021

Platform

Desktop & mobile web

ABOUT THE PRODUCT

Account.microsoft.com (AMC) is account management experience for Microsoft customers. Order history is part of AMC. Customers come to order history to view order information or manage orders. It contains both physical and digital orders placed on Microsoft storefronts (e.g. Windows Store, Microsoft store, Xbox store).

MY role

Lead designer through end to end process: discovery, research, requirements, design, user testing, support through launch. As part of the project created and contributed to the AMC design system. Led the effort to identify future areas of investment and opportunities for order history.

impact

Our aim was to at least maintain the status quo across all metrics. Post the release we observed an overall improvement in all task completion rates, page's reliability score and CSAT score.

PROJECT BRIEF
Order history was being migrated from angular to react. We visually refreshed & redesigned the order history to ensure that our customers will have one place to view, act and engage with their purchases in a way that inspires trust and confidence in Microsoft.

Key experience highlights

One place to view, act and engage with purchases

Refreshed UI, improved IA, clear communication & actionable order history.

NOW
BEFORE

View order details without going anywhere

Removing hierarchy and maintaining context by bringing order details to L1.

NOW
BEFORE

Robust order management

Task simplification, better focus & leaner flow for order management.

NOW
BEFORE

Creating opportunities for upsell

Upselling Microsoft products during cold states.

NOW
BEFORE

Research & Analysis

WHY REDESIGN

The original Order History was on an Angular Code base that had to be moved to React. The task was to meet compliance date, as the angular code would soon be deprecated across the company. The initial scope was to design a new experience without any major redesign mapping the old.

We decided to use the compliance requirement as an opportunity to expand and provide value to our customer by refreshing the UI, future proofing the product by aligning to AMC & improving the experience.

Learning from others

We kickstarted the project by doing a product teardown of other e-commerce order history. The aim was to understand market patterns and any opportunity areas for the future. We studied products like Amazon, Myntra, Apple, Flipkart etc.

Listening to customers

We reached out to the customer support team to understand key issues for which customers require support. We learned order management is the top driver for customer support calls.

LOOKING INWARDS

We ran a comprehensive experience review of our current experience across the triad & design team.

KEY USER JOBS

👀 Viewing order information

Customers come to order history to track order status or know details about their order.

🤹🏽 Managing orders

Key order management task were: cancellation, return , request refund, change payment method, request tax invoice.

Problem Breakdown

🧩 Misalignment with AMC

Over years other pages had been updated however the entire order history was still legacy. New experiences and scaling AMC to other surfaces was being introduced leaving Order history difficult to update and scale.

🕰️ Dated & old user interface

Most web experiences across Microsoft used a fluent web design library as building blocks. Meanwhile, order history was custom code and components. It had sharp corners, strong shadows & a distracting type ramp.

📰 Scattered & disjointed information architecture

Difficulty in scanning & taking actions. Scattered & visually similar treatment of link & actions on order cards. Too many font weights & sizes. Difficult to differentiate between bundles and multiple orders

🐢 Hierarchy and long task flows

Opening a separate page for providing additional details around address & amount breakdown. All order management flows were long page by page flows.

Solution

FINAL APPROACH & DESIGN PRINCIPLES

🤝 Align order history to rest of the AMC

  • Flatten page hierarchy
  • Simplify task flows

🫶 Order history inspires trust & confidence

  • Clear communication
  • Actionable

Explore, Iterate, Test, Repeat

USER JOB: Viewing order information
Order CARDS EXPLORATIONS

Multiple directions were explored, reviewed with triad & design. These iterations didn't make it due to usability issues uncovered from testing, scalability issues, technical feasibility or accessibility.

👍🏾 Things that work

  • Separate treatment for actions & links
  • Focus on viewing & management

👎🏾 Things that need work

  • No way to know what order bundle contains without expanding them
  • Order details exists on L2

👍🏾 Things that work

  • Visual separation of viewing & management
  • Easy to scale across viewports

👎🏾 Things that need work

  • The drawer treatment failed during testing
  • Track shipping action exists in separation from rest of the actions
  • Visual conflict between order details & track shipping

👍🏾 Things that work

  • Clean & organised
  • Easy to scale across different order types
  • Overall positive response during testing

👎🏾 Things that need work

  • The grid fails in case of mobile & smaller viewports
  • Accessibility & contrast issue in drawers
  • Track shipping action exists in separation from rest
  • Too many subsidiary section add to page scroll
STATUS TRACKER EXPLORATIONS

Status tracker was explored & tested in tandem with order card layouts to align it with the overall structure.

Right aligned
Progress on top
Left aligned text

Right aligned
Progress on bottom
Right aligned text

Centre aligned
Progress at bottom
Left aligned text

Centre aligned
Progress on top
Left aligned text

ORDER DETAILS EXPLORATIONS

👍🏾 Things that work

  • Consistent with old behaviour
  • Enough real estate to provide all details

👎🏾 Things that need work

  • Adding hierarchy to order history
  • Breaking AMC design pattern

👍🏾 Things that work

  • Focus on details
  • Can be scaled and initiated from other surface
  • Maintains page context
  • Positive feedback during testing

👎🏾 Things that need work

  • Crunch of space in case of multiple orders or bundles
  • Opening on mobile adds a long scroll to the dialog

Final Experience

USER JOB: Viewing order information
DESIGN PRINCIPLES: CLEAR COMMUNICATION & Actionable
Order history inspires trust & confidence
  • Improved IA provides clear communication of order information.
  • All task management is in one place.
  • Hierarchy in tasks based on usage & importance
  • Order filters are moved to the top and are sticky once users scroll, making it easier to find orders.
  • Order card structure scales seamlessly across single, multi orders & bundle orders for physical & digital orders.
DESIGN PRINCIPLES: CLEAR COMMUNICATION
Improved & revised order status trackers

Revised status tracker that is easier to read. Completed & delivered states are highlighted using colour.

CLEAR COMMUNICATION
Viewing order bundles without taking the entire page

Drawers are closed by default, saving real estates and making scanning order history easier. Bundle drawer provides you a sneak peak into your order without a need to keep them expanded.

Flattening hierarchy
View order details without going anywhere

Customers can expand and view details right there on Order history. It ensures the context is maintained and customers can manage their order too. The drawer also leveraged an existing user behaviour across AMC & windows.

CLEAR COMMUNICATION & Actionable
Accessibility improvements

Improved tabbing order for more accessibility friendly post purchase experience.

Explore, Iterate, Test, Repeat

USER JOB: Managing orders
Key Management Tasks

Each management task had multiple flows. We didn’t do a major overhaul of flows. Just fine tuning, simplification and aligning them to rest of the AMC. We mapped key task flow to understand the experience holistically.

TASK MANAGEMENT EXPLORATIONS

Multiple approaches were experimented across different tasks. Each task’s key flow was tested. For the purpose of the case study I will illustrate one of our explorations with order return flow.

👍🏾 Things that work

  • Low dev cost
  • Maintaining status quo

👎🏾 Things that need work

  • Loading multiple pages for each step
  • Misaligning with AMC design patterns
  • Felt slow & combersome

👍🏾 Things that work

  • Maintains context of order history
  • Better focus
  • Impression of speed
  • Real estate to fit larger orders

👎🏾 Things that need work

  • Learning curve, as no other place on AMC, uses left pane
  • Cannot be scaled to other surfaces

Highlights

USER JOB: Managing orders
DESIGN PRINCIPLE: TASK SIMPLIFICATION
Cancel orders easily

Improved and cleaned up the language to avoid confusion. Moving the flows to modal to provide better focus, scalability and impression of speed. Aligned with AMC design patterns.

DESIGN PRINCIPLE: TASK SIMPLIFICATION
Review & return orders

Modal experience provided better focus, scalability and impression of speed. Cleaned up IA for review dialog, making it easier to read.

DESIGN PRINCIPLE: TASK SIMPLIFICATION
Change payment method

Customers can switch, add or update payment methods. Adding payment iconography increased trust. The new flow completed the task in context without customers redirecting to new page and breaking the flow.

DESIGN PRINCIPLE: TASK SIMPLIFICATION
Request invoice

Invoice scenarios that were unique to countries like China or Brazil were designed with constant feedback from the local teams to ensure me were meeting standard guidelines.

IMPACT

Post release we observed an overall improvement in all task completion rates, page's reliability score and CSAT score.