Timenaut Desktop App Redesign - Google Design Sprint

Overview

Timenaut's team wanted a redesign for their application and for their website, as well as a new logo design and style guide.

Because they hadn't yet validated their business idea with real users, I proposed to facilitate a Google Design Sprint for them.

my Role

Design Sprint facilitator
UX/UI Designer

duration

July - Oct 2020

other Team members

Timenaut's CEO
Timenaut's CTO

My tasks

Facilitating workshops during the Google Design Sprint

High-fidelity prototypes

Validating the personas and the design with user tests

The Challenge

The challenge was to create a working prototype to capture the essence of Timenaut App. And then test this prototype with real users to validate both personas and Timenaut's business idea.

The Journey

For the process, I used Google Design Sprint 2.0 methodologies. We spent one day together with the team to capture the sprint goal and questions, as well as sketch some potential app solutions.

The Outcome

I created a prototype, and then validated it with 5 potential users. As we found out, the user is unfamiliar with the app concept, meaning we needed to rethink personas and the essentiality of the app.

Let's get into details! 

I What is the Timenaut app?

Timenaut is an automatic time-tracking app, that automatically tracks the user's computer app usage.

Then, Timenaut categorises the data visually so the user can see what he spent his time on during the day and how productive he was.

How Timenaut App looked like before

II Google Design Sprint : One-day kickoff

I combined the tasks of the first two days in the Google Design Sprint 2.0 together into one day.
This is what happened during the kick-off: 

  • We put together a long-term goal, picked three sprint questions and made a map
  • We looked for inspiration, and sketched down a 3-view sketch, using the 4-step-sketch method.
  • We voted on the sketches to see which solutions and solutions parts I should focus on when making a prototype.

Timenaut Design Sprint - longterm goal, sprint questions, map, lightning demos

Timenaut Design Sprint - sketching the solutions

The sprint questions

1 - Can we convince the user to keep using Timenaut after signup?

2 - Can we provide enough value for the user to get them to pay for Timenaut?

3 - Can we be seamless, yet essential?

III Google Design Sprint : Preparing for the prototyping

After kickoff, I gathered all the info and put together a user test flow and a storyboard.

The final prototype

I went straight for the high-fid prototypes. I decided to skip all wireframe and low-fid prototype steps to save up time.

The final prototypes before the user test validation

IV Feedback from user tests

We got a lot of amazing feedback from the users

I conducted five remote user tests, using Lookback.io platform

The main issue was that the users weren't familiar with the concept "automatic time tracking".
All of the users selected for the tests knew about manual time tracking application like Toggl or Clockify, so they were expecting Timenaut to behave the same way.

For us, this meant that Timenaut's web page needs to be more informative regarding what is automatic time tracking and what the benefits are. It also meant that we needed to refine our user personas a bit more.

The sprint questions, conquered

1 - Can we convince the user to keep using Timenaut after signup?

Yes!

BUT. The more important question lies in whether or not we can convince the user to download the app. This is something we will tackle next.

______________________________

2 - Can we provide enough value for the user to get them to pay for Timenaut?

Not conclusive, yet

As we figured from the user tests, the concept of Automatic Time Tracking is fairly new to users. So at the moment, the users don't yet feel the need for such software.

______________________________

3 - Can we be seamless, yet essential?

Seamless, yes. Essential, not conclusive yet

Seamlessness can be achieved if the software doesn't require too much user input, but categorises the time usage automatically. To confirm essentiality, we need to rethink and validate our user personas.

V Next steps

  • Team Workshop to rethink the main user persona that we want to focus on and their main problem.
  • Iteration sprint, during which we can find answers to questions about the essentiality of the app.
  • Finalising the app's high-fidelity prototype and the web page + further tests.

interested to see more?

Other recent Case Studies

UX/UI DESIGN | ILLUSTRATION

Codemagic Developer Type Test

Case Study

UX/UI DESIGN | APP DESIGN

Design concept for a Web Chat App

Case Study