PocketCFO - Cash Flow Calendar
Who
Small business owner
Why
They need a better way to keep track of their cash flow

My Role
End-to-end solo designer
Collaborated with engineers and financial experts

Duration
May 2020 to July 2020 (6 weeks)

Problem Overview

Problem
Imagine you lost a lot of businesses due to COVID-19 so you need to understand your current and future cash flow situation. 1) You find it difficult to track the expenses and see patterns/trends by looking at the transactions list from excel. 2) You find It is hard to read the financial models and you don't have an account in your team.
Solution
I created a calendar view in the app to help entrepreneurs track and manage their cashflow in a more intuitive and simple way.
RESEARCH

Understand the Problem and Users

I first conducted 24 competitor audit to better understand the market and 14 user interviews about how do founders currently manage their finance especially the cash flow. Then I asked them to do a card sort exercise- sort the information from most important to least important if they want to know about their cash flow on a daily basis. Besides that, I also consulted with financial expert in our team.

Some Insights

of users have no financial background and they  regularly struggle with cash flow

of users have been kept up at night by concerns about when to pay AP and when to collect AR

of users check their cash flow on a daily or weekly basis

Competitive Audit

I conducted a comprehensive competitive audit of 24 similar products to understand the business, product, and design tactics used by other companies in solving the problem of tracking Cashflow/ Account Payables/ Account Receivables.

A simplified User Flow

I created this simplified user flow first to highlight the key user behavior during the process after synthesis all the research data.

Frame Design Challenges

Based on different use cases, I defined four key problems and came up with the design challenge for each problem.

Solution
How Might We

Enable users to explore meaningful bites of data and visualization with efficient layouts and workflows.

Experience Pillars

To ensure a comprehensive and seamless product experience, I coined seven major "Experience Pillars." Each Pillar describes a key step in the user's journey from discovering the product, using the product, and realizing value from the product. Breaking the product and experience down into segments also made it easier to:
● Break down the design process into approachable steps
● Communicate and influence cross-functional stakeholders

You can easily switch your calendar between different types of Calendar Views. But there are different mindset when users see these two views:

● For the daily view: users tend to see more detailed information of a particular transaction. For example, I want to how many calories I should have for each day and then I can make some decisions.

● For the weekly view: user's expectation is to see high-level information. For example, check the total calories assumption to see if I stay healthy this week.

Experience Flows

For each of the seven "Experience Pillars" above, I created experience flows. I brought these flows into design critiques to explore how effective they solved user needs.

Information Architecture

After consolidate the key steps. With the design focuses, I started designing from info architectures. I tried to organize the information with intuitive logics to provide easy and understandable hierarchy for users. For example: I designed the layout from high level to actionable. from general to detail, from top content to additional exploration. Grouped information into categories.

I have solved important UX problems along the way...

Now came the fun part of problem-solving ✏️ + 💻 ! Here I’d love to share my design, research findings, and our reflection through these 4 Design Challenges. 🤔

Design Challenge 01 - How to make it look more insightful at a glance?
01 - Scenario
01 - Solution & Iteration
01 - High Fidelity
Design Challenge 02 - How to help user eliminate unexpected bills and overdue payments
02 - Scenario
02 - Solution & Iteration
02 - High Fidelity
Design Challenge 03 - How to help user make a quicker decision on collecting money?
03 - Scenario
03 - Solution & Iteration
03 - High Fidelity
Design Challenge 04 - How to present complex data on different time scale
04 - Scenario
04 - Solution & Iteration
04 - High Fidelity
Results & Impact