# Automated and Easy
way to manage your business

Case Study by Caue Mattos

General Assembly - London

February 2023

ROLE

Product Designer

TIMELINE

Nov/22 - Feb/23

PLATFORM

Mobile App & Web

# UX Design Process

# 1 - UX Tools

Figma
MAZE
Pen & Paper

# 2 - Discovery &
Research

Problem Statement
Affinity Mapping
Persona

# 3 - Define &
Solutions

HMW
Features Prioritizations
(MoSCoW & Matrix 2X2)
Solutions Skecthes
User Flow
Competitor Analisys
Sitemap

# 4 - Develop

Wireflow
Low Fidelity Wireframes
Usability Test (Modareted)

# 5 - Delivery & UI

High Fidelity Wireframe
Usability Test
(Unmodareted)
Style Guides & Components

# APP FINAL RESULT

Prototype Access

# PROBLEM STATEMENT

'Managers require a method to handle their inventory and sales processes, in order to save time, be more efficient and be organised in their daily operations.’

# AFFINITY MAPPING

# PERSONA

# HMW STATEMENTS

1 How might we help business manager... to handle their operation more easily and intuitively?
2 How might we help business manager... to save time by using automated tasks?
3 How might we help business manager... to bring more efficiency to business operations?

# FEATURES PRIORITIZATION

# USER FLOW

# SITEMAP

# WIRE FLOW

# WIREFRAME LOW-FIDELITY

# MODERATED USABILITY TEST

GOALS:
100% accomplishment rate for user tasks. This includes creating an order with a Quick Sale, splitting the bill by two, taking the payment from the customers and finishing the order.

METHOD: Moderated Usability Test.
DATA SOURCED: Qualitative and Quantitative.
INTERVIEWEES: 3.
TASKS TO PERFORM : 1.

# HIGH-FIDELITY PROTOTYPE

# UNMODERATED USABILITY TEST

Usability shows that users got stuck on the payment page.
NEEDED: The usability of the page must be restructured and retested.

# Redesigned:
UNMODERATED USABILITY TEST

Usability shows that users accomplish their goals by a 100% success rate.

# STYLE GUIDES

# MVP

Desinging the minimal solution

Using the idea of Minimum Viable Product, or MVP, means to deliver a basic usable product as fast as possible, to learn from provided feedback and iterate later. This approach of delivery was used as we found many features that would impact how the app worked. Launching features in stages, we reduced user's friction to learn from scratch how to use the app, and we also learnt every week which features were impacting and generating results with users.

# WHAT HAVE I LEARNED?

Reflecting back on the project

Sometimes projects are bigger than what is shown in the briefing. As soon as user research starts, new insights appear and new features are needed to solve problems. Also, when integrations with third parties happen, anything can change at any second. Therefore, limitations that change user journeys and business requirements will need to be revisited.