Tickets, organization and responsible consumption 🌿

Introduction

As we all may know, our paper resources are limited and running out, generating a big impact in our environment. One of the massive forms of paper consumption is in paper tickets emitted in retail stores, supermarkets and almost every street store.

Knowing that companies spend millions every year in paper tickets, and that 3,2 million kms tickets are printed every year only in Spain, I think it’s time we found a better solution for this.

Methodology

For developing this project I used the double diamond process, starting with research and observation in the divergent phase, and then establishing the definition of the problem in the convergent phase. And repeating the diamond, ideation and prototype in each divergent and convergent stage.

Marking a schedule for the following three weeks and a to-do list, I started the investigation of my topic by doing a desk research.

Observation 🔍

Desk Research

Searching the internet I came across with several Spanish mobile apps focused in digital ticket, but most of them only presented the paper ticket scan function. This means the paper is still being printed and thrown away once you don’t need it anymore.

Safari

By doing a contextual research I found Decathlon’s new option of receiving the ticket via email instead of printed (something that Apple has been doing for a long time) but if you take more than 30 seconds considering this new option they’re offering, the ticket goes printed by default.

I also came across with a curious fact about the famous company Eastpack, where they offer a thirty-year guarantee in some of their products. (Am I the only one thinking it’s impossible to keep a ticket for that long?)

Questionnaires

Through Google Forms I sent a list of ten questions and this is the quantitative information I got from 99 people between the ages of 16 and 55 years old:

  • 100% say they are concerned about our environment.
  • 75% use their mobile phone frequently, and 45% use it to organize themselves.
  • 99% would be interested in a mobile app to have digital tickets.

Interviews

I interviewed four people, with different ages and profiles to see how they interact with tickets in their day to day life, and to learn about their aims and frustrations.

To organize all the information I got from the interviews I created a Point of View canvas, and extracted these findings from the users:

  • “I wish I could get an extract of my expenses and be able to share it”.
  • “I keep every ticket in I need to return something, I classify them and throw those I won’t need”.
  • “The bank account information is very limited”.
  • “I would love to have everything in the same app”.

Definition 🖊

User persona

With all the information collected in the quantitative and qualitative research I created Carla Lopez, a 32 years old girl who says “I keep every ticket in case I may need it later”.

User Persona

Her goals are to be able to share her expenses, to change or return what she buys, to save paper and organize her tickets depending on their type. Her frustrations are not to be able to control her cash expenses, the limited information on her bank account, and having different apps to organize her finances.

Customer journey

I created Carla’s journey to the supermarket, where she faces a lot of problems that frustrates her, like receiving a paper ticket for starters.

Customer Journey

Insights

From all the collected information I defined these insights that I worked with to establish the problem afterwards.

  • Need of a digital ticket.
  • Need of a tool to organize tickets according to their type.
  • Need of more information in bank accounts.
  • Need of unification of financial apps.

Problem definition

After doing a How Might We process I defined the problem:

Creating a digital ticket service synchronized in real time with the bank account and mobile app to visualize, classify and organize tickets and expenses.

Ideation 💡

Based on the defined problem I generated possible ideas to solve it, and wrote them down on post-its. After that, I organized their hierarchy of importance in a MoSCoW, and then in an In & Out canvas to define which of those should be completely dismissed.

Benchmarking

After defining the functions that would involve my solution I compared them with my new direct competition, banks and other fintech apps currently in market.

Benchmarking

The only app that covers most of the functions presented is Fintonic, except for the digital ticket function which none of the apps cover it.

Sitemap

To define the functions hierarchies I created a sitemap, which also helped me to understand what the user’s journey would be inside the app. Then, I created the flow of the app. After a splash screen the user would have the option of login or signup if she’s not registered. In that case she would also have to synchronize a bank account.

Wireflow

Once the user is inside the app, she would have the feed of her bank and the information of the ticket in each expense, the option of scanning a QR code in case she would pay cash in the store, and categories to classify and organize her tickets and expenses.

Prototype 🔧

Wireframes

Finally, I started the prototyping phase by doing low fidelity wireframes based on the hierarchies of features and wireflow previously defined. Once I decided the structure of the app I went into Sketch to start doing the mid fidelity wireframes, where I started selecting some elements such as the typography.

Style guide

Starting with an inspirational moodboard I chose a colorful palette for the app, inspired by pop art colors, to generate a friendly relationship between the user and the content presented.

Style guide

I selected a flat style for the buttons, variating its color depending on its importance. I also created sixteen lined icons to represent different content and solid icons to represent location inside the app.

Features

So I present you Fintick, a merge between fintech with digital tickets that comes to give an end to paper tickets.

Prototype screens
  • Real time synchronization: users will be able to see the feed of their bank account in real time, and they will have access to the information of their purchase, a simple visualization with the items they paid for and also the option of its complete information, such as name of the company, etc.
  • Digital ticket: users will have the option of generating a new ticket as well. In case they pay cash, they could scan a QR code from the store, and then associate it to a bank account and classify it according to its categories.
  • Categories: users will be able to classify their expenses with # tags simulating a folksonomy. Users will have the option of generating reports based on their personal classification, and then share them.
Animation created with Protopie

Future phases

To generate a real MVP I would need to start a research focused on bank’s APIs, and store’s softwares. I would also need to incorporate a AAA contrast color option, as the colors chosen don’t pass AAA contrast levels. Then, I would need to test it with users, and iterate later. And lastly, create a landing page to promote the app.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here