top of page
4-2.png

Case Study - Real Digital

How a 8 days design sprint helped the product team to set up an elaborated relaunch of the product detail page, from deep problem understanding until prepared user stories

When successful startups scale, it's time for an evolution.
The speed and agility of small tech teams are incredible - yet the »better done than perfect mentality« has taken its toll. It was about time to clean up the code, design, processes and to sharpen the goals.

An important step of that journey was the relaunch of the product detail page from scratch. Not only is it the most viewed page for this well-known European marketplace -we also wanted to set new standards in the way customer facing product teams work in this company.

 

An 8 days design sprint was conducted, - in this time the whole product team elaborated the relaunch, from deep problem understanding until prepared user stories. Developed by Google, a Design Sprint is a framework for solving problems and generating reasonable concepts (www.thesprintbook.com/). Often it compresses the work of months within days. 

DAY 1 - 

GET STARTED

  • The whole product team and key stakeholders kick of the design sprint

  • Align on vision, goals and scope together

  • Collect open questions and whom it needs to answer them

  • Facilitate a large benchmark research to open up your mind

DAY 2

CUSTOMER RESEARCH

  • User interviews about live website

  • User interviews about competitor websites

  • Gather user needs and wishes

DAY 3

DATA DAY

  • Collect all available quantitative data about the page usage

  • Find patterns that provide information about the future concept

  • Define Proto-Personas to sympathise with main target group

DAY 4-5

COLLECT BUSINESS REQUIREMENTS

  • Get an aligned understanding of all requirements from the business perspective such as product data, logistics, marketing, finance, legal, customer service

  • Understand the technical and organizational concept of the page

DAY 6

SYNTHESIS

  • Sort business and user requirements

  • Use data to prioritize your findings - especially to eliminate content

  • Report your progress daily to all stakeholders (f.e. in a Slack-Channel)

DAY 7

CRAFT IDEAS

  • After gaining a deep understanding of the context of the page, the whole product team goes into ideation mode

  • Develop technical framework and feasibility in parallel

  • Align with key stakeholders within short feedback loops

DAY 8

TEST CONCEPTS

  • Test your prototype with real users 

  • Adapt your concept after every test

  • Finalize your prototype

  • Slice your first User Stories

This Design Spring is a successful example of how to build and improve features. 
The new pages had an 4% increase in conversion rate and a 40% decrease of loading time.
But above all, it is a cultural shift in the way we collaborate with each other.
It is important for the team and all stakeholders to have common goals, a deep problem understanding and an open and experimental solution space. This sets the road to a continuous and fast implementation. 

If the members of your product team become experts of their product, their responsibility, productivity and creativity will increase enormous.

Sophie.png

Sophie Zaubitzer

  • 174857_edited

It is kind of fun to do the impossible.
 

Rainer1.png
  • 174857_edited

Rainer Collet

A product doesn't get better by adding stuff.

It's perfect if you can't remove.

bottom of page