ENTERPRISE UX CASE STUDY

Studio Designer

Studio Designer

Making financial workflows easier to follow, helping users review billable time, structure project fees and reconcile bank transactions.

Making financial workflows easier to follow, helping users review billable time, structure project fees and reconcile bank transactions.

My Role

UX Designer

UX Designer

Platform

Web and mobile

Web and mobile

Duration

11 months, 2023

11 months, 2023

THE PRODUCT

Context

Context

Studio Designer combines project management, product sourcing, a client portal and accounting for interior design firms, all in one system.

Studio Designer combines project management, product sourcing, a client portal and accounting for interior design firms, all in one system.

The bet
The bet

Interior designers shouldn't have to leave their workflow to track billable hours, reconcile a bank statement or send a client proposal.

Interior designers shouldn't have to leave their workflow to track billable hours, reconcile a bank statement or send a client proposal.

The reality
The reality

The legacy product recorded every transaction, but left people to assemble what it meant: totalling by hand, and reconciling the bank in spreadsheets outside the product.

The legacy product recorded every transaction, but left people to assemble what it meant: totalling by hand, and reconciling the bank in spreadsheets outside the product.

“For three years I built timesheets by hand and tallied billable hours at the end of every month. Any hour that slipped through was an hour the firm never billed.”

Me, before UX, as an interior designer and architect. I knew one side of this problem before I joined.

Who it's for

Interior designers and their studio's bookkeeper.

Interior designers and their studio's bookkeeper.

DashboardEntry point: at-a-glance overviewStats OverviewKPIs & utilisationRecentPick up where you left offProjectsDocumentsItemsQuick LinksTraining & KnowledgeGuides & onboarding02PlatformCore system, commerce & adminAccessSign UpLoginPlans & LicensingSubscription PlansLicensesPackaging ModulesAdministrationPermissionsAdmin Access [ADMIN]Catalog & ContentProductsInventoryCataloguesDocsMoodboard [PLUGIN]Browser plugin: browse & buyBrowse ItemsBuy / CheckoutCalendarScheduling & events03Time BillingFrom timer to invoiceSetupDefine the modelTier StructureEmployees & StructureGroups & PhasesBilling RatesEmployee GroupsActivitiesTime TrackingWeb Timer [WEB]Mobile Timer [MOBILE]Billing & InvoicingFlat Fee / Lump SumPhasesTime BudgetsInvoicingHourlyFlatMixedReportingTime AnalysisUtilisation & realisation04Studio PayAccounting & reconciliationSales TaxIncoming PaymentsExpense TypesAdvanced LedgerChart of accountsJournalPower User ToolsBulk & batch opsReconciliationMatch & verifyBank Import & MatchReconcile Money In / OutAudit View

Site Map

Site Map

Studio Designer covers projects, product sourcing, client approvals, billing and accounting. My work sat where hours turn into invoices and payments.

Studio Designer covers projects, product sourcing, client approvals, billing and accounting. My work sat where hours turn into invoices and payments.

My work. Hover to find it on the map

Time Tracking
Review time before logging more
Flat Fee
Fees built from project phases
Time Analysis
Budget health in one view
Bank Reconciliation
Matching moved into the product
Dashboard
What needs attention across the business

THE CHALLENGE

Why the redesign mattered

Why the redesign mattered

Across time, billing and finance, the same three problems showed up on almost every screen.

Across time, billing and finance, the same three problems showed up on almost every screen.

What the client said

Users find the platform hard to use.

Users find the platform hard to use.

Client leadership, 2023 quarterly review (paraphrased)

Billing and accounting were on their list of modules to fix. That is where my work sat.

Billing and accounting were on their list of modules to fix. That is where my work sat.

Recorded data, never meaning

Every screen was a raw ledger. Budget health, balances owed and reconciled status were left for the user to total by hand.

Friction point: Legacy Time Analysis meant reading raw financial columns, and the dashboard reported 537 orders and 601 invoices with no trend or next step.
Seen inTime Analysis, Dashboard
Fragmented, with the user as the glue

One job was spread across project-scoped screens, repeated filters and modal-on-modal forms. With no view across them, people held the workflow in their heads.

Friction point: Time Tracking split related information across three panels, and reconciliation left the product altogether as a CSV export matched by hand.
Seen inTime Tracking, Bank Reconciliation
High friction in, low legibility out

Fill-everything forms put a rate in every cell, on a dated, low-contrast interface that gave little guidance. It was also the first screen a new user met.

Friction point: Setting up a flat fee meant working through hundreds of editable cells, and logging time started with long forms.
Seen inFlat Fee setup, time entry
  1. Time Billing

Logging, pricing and checking billable time

Logging, pricing and checking billable time

Time Billing is how a firm turns hours into invoices: logging time, pricing it, and checking it against budget. That work runs through Time Tracking, Flat Fee Billing and Time Analysis, and in each the legacy screens left the sorting to the user.

Time Billing is how a firm turns hours into invoices: logging time, pricing it, and checking it against budget. That work runs through Time Tracking, Flat Fee Billing and Time Analysis, and in each the legacy screens left the sorting to the user.

Legacy Time Tracking

Legacy Time Tracking

One screen for review, logging and setup

One screen for review, logging and setup

Review, tracking and configuration all shared one screen with no hierarchy between them. Even routine entries felt administrative, because nothing told you where to start.

Review, tracking and configuration all shared one screen with no hierarchy between them. Even routine entries felt administrative, because nothing told you where to start.

Key issues we identified

  • No clear priority or starting point

  • Related information split across 3 panels

  • High entry friction with long forms

  • Too many actions competing for attention

Key issues we identified

  • No clear priority or starting point

  • Related information split across 3 panels

  • High entry friction with long forms

  • Too many actions competing for attention

Redesigned Time Tracking

Redesigned Time Tracking

Show logged time before asking for more

Show logged time before asking for more

The redesign separated review from entry, so people could see existing work before adding more. The timer stayed, since it was already part of how people logged time, but it moved into context and stopped competing for the top of the page.

The redesign separated review from entry, so people could see existing work before adding more. The timer stayed, since it was already part of how people logged time, but it moved into context and stopped competing for the top of the page.

Key decisions

  • Review first: Time entries lead the page

  • Filters up front: Find what matters fast

  • Clear actions: Start timer and add entry are prominent and simple

  • Scalable list: Expandable rows reveal detail only when needed

Key decisions

  • Review first: Time entries lead the page

  • Filters up front: Find what matters fast

  • Clear actions: Start timer and add entry are prominent and simple

  • Scalable list: Expandable rows reveal detail only when needed

Add Time Entry

Add Time Entry

One modal for timed and back-logged entries

One modal for timed and back-logged entries

The same modal handles a running timer and manual back-logging, so there's one way to record time however it happened. Total time and billable time are separate fields, because not every hour spent on a project can be billed.

The same modal handles a running timer and manual back-logging, so there's one way to record time however it happened. Total time and billable time are separate fields, because not every hour spent on a project can be billed.

Mobile Time Tracking

Mobile Time Tracking

On mobile, the screen is cut down to two things: starting a timer and seeing what's running.

On mobile, the screen is cut down to two things: starting a timer and seeing what's running.

Legacy Rate Schedule

Legacy Rate Schedule

Priced by employee and task code

Priced by employee and task code

The legacy model priced by employee and task code, not by project. It handled hourly billing fine, but setting up a flat fee meant working through hundreds of editable cells that didn't reflect how the project was actually sold.

The legacy model priced by employee and task code, not by project. It handled hourly billing fine, but setting up a flat fee meant working through hundreds of editable cells that didn't reflect how the project was actually sold.

Flat Fee Management

Flat Fee Management

Build a fee from the project's phases

Build a fee from the project's phases

The client asked for flat fees to become their own record, separate from the rate matrix, holding phases, budgets and optional hourly allocations. My part was deciding how a fee gets built.

The client asked for flat fees to become their own record, separate from the rate matrix, holding phases, budgets and optional hourly allocations. My part was deciding how a fee gets built.

Progressive Fee Builder

Progressive Fee Builder

Hourly rates appear only when a project needs them

Hourly rates appear only when a project needs them

The builder starts from project phases. Employees, activities and hourly billing appear only if a particular project needs them, so setup follows the shape of the project.

The builder starts from project phases. Employees, activities and hourly billing appear only if a particular project needs them, so setup follows the shape of the project.

Contextual Activity Selection

Contextual Activity Selection

Activities edited without leaving the fee

Activities edited without leaving the fee

Activities are edited in a slide-over panel, so the fee stays on screen while you change them.

Activities are edited in a slide-over panel, so the fee stays on screen while you change them.

Buried inside invoicing

Buried inside invoicing

Time Analysis lived inside the invoicing workflow. That suited billing, but it meant reading raw financial columns and moving between modules to answer a simple question about how a project was doing.

Time Analysis lived inside the invoicing workflow. That suited billing, but it meant reading raw financial columns and moving between modules to answer a simple question about how a project was doing.

Give Time Analysis its own place

Give Time Analysis its own place

I set Time Analysis up as its own workspace and defined its structure, with budgets, tracked hours, invoicing progress and project performance in one place. The progress meter was designed by the Senior UX Designer; I organised the workspace around it.

I set Time Analysis up as its own workspace and defined its structure, with budgets, tracked hours, invoicing progress and project performance in one place. The progress meter was designed by the Senior UX Designer; I organised the workspace around it.

Budget Health View

Budget Health View

Progress indicators replace column-by-column comparison, so over-budget projects are easier to spot.

Progress indicators replace column-by-column comparison, so over-budget projects are easier to spot.

Employee Capacity

Employee Capacity

The employee view shifts reporting from a record of past hours to a read on current workload.

The employee view shifts reporting from a record of past hours to a read on current workload.

  1. STUDIO PAY

Bringing bank matching into the product

Bringing bank matching into the product

Time Billing ends at an invoice. Once a client pays it, or the firm pays a vendor, the money moves through the bank.

Framing the challenge

Framing the challenge

In the old product, reconciliation stopped at a CSV export, and matching bank transactions to the books happened outside it, by hand. Where reconciliation would sit in the financial flow was a business decision. My part was designing the reconciliation flow itself.

In the old product, reconciliation stopped at a CSV export, and matching bank transactions to the books happened outside it, by hand. Where reconciliation would sit in the financial flow was a business decision. My part was designing the reconciliation flow itself.

Illustrative examples, not client data: a bank statement, the payments recorded in the product, and the spreadsheet matching that happened between them.

SOURCE

Vendor Bills

Vendor Bills

SOURCE

Credit-card Payments

Credit-card Payments

SOURCE

Expenses

Expenses

→

→

Existing

Accounts

Payable

Accounts Payable

Accounts

Payable

→

→

Existing

Pay Run

Pay Run

→

→

New

Bank Import

Bank Import

→

→

New

Matching

Matching

→

→

New

Reconcile

Reconcile

Exploring possibilities

Exploring possibilities

I explored two ways of structuring the comparison. The first kept everything in a single list, expanding a transaction to reveal its candidate matches. It looked cleaner, but it meant holding one record in mind while scrolling to find the other.

I explored two ways of structuring the comparison. The first kept everything in a single list, expanding a transaction to reveal its candidate matches. It looked cleaner, but it meant holding one record in mind while scrolling to find the other.

Combined table: a bank transaction expanded to show its candidate matches beneath it
Bank transactionCandidate matches, opened one at a time

Option A

Combined table
Combined table

Each bank transaction expands in place to show its candidate matches underneath.

Each bank transaction expands in place to show its candidate matches underneath.

Gain

Everything in one list, with more detail per row.

Everything in one list, with more detail per row.

Cost

One match context open at a time, so comparing means expanding rows and scanning down the list.

One match context open at a time, so comparing means expanding rows and scanning down the list.

Side-by-side view: bank statements on the left, accounting records on the right
Bank statementsAccounting records, always in view

Option B · Chosen

Side by side
Side by side

Bank statements on the left and accounting records on the right, both on screen while matching.

Bank statements on the left and accounting records on the right, both on screen while matching.

Gain

Both records stay visible while matching.

Both records stay visible while matching.

Cost

Each list gets less width.

Each list gets less width.

Side by side went into final design.

Side by side went into final design.

I took both options to the client with the trade-off laid out, and the client chose this one.

I took both options to the client with the trade-off laid out, and the client chose this one.

Final Solution

Final Solution

START

1. Starting with outstanding transactions

1. Starting with outstanding transactions

Every session opens with the work that's still outstanding

Every session opens with the work that's still outstanding

A session opens on the transactions still waiting to be matched, so you can see how much is left before touching a single record.

A session opens on the transactions still waiting to be matched, so you can see how much is left before touching a single record.

Progress and account balances sit at the top of the page.

Progress and account balances sit at the top of the page.

2. Importing bank activity

2. Importing bank activity

Bank statements come in directly, no spreadsheet export

Bank statements come in directly, no spreadsheet export

Bank statements are imported straight into reconciliation, so the list you match against is the bank's own record. Before this, the work left the product as a CSV export.

Bank statements are imported straight into reconciliation, so the list you match against is the bank's own record. Before this, the work left the product as a CSV export.

UNDERSTAND

3. Reviewing imported transactions

3. Reviewing imported transactions

Payer, amount and date are visible before any decision

Payer, amount and date are visible before any decision

Imported transactions land in a review queue showing payer, amount, date and possible matches.

Imported transactions land in a review queue showing payer, amount, date and possible matches.

Nothing gets matched here. This step is for seeing what came in before acting on it.

Nothing gets matched here. This step is for seeing what came in before acting on it.

COMPARE

4. Comparing records side by side

4. Comparing records side by side

Bank and accounting records stay side by side

Bank and accounting records stay side by side

Bank activity and accounting records stay visible at the same time, so references, dates, amounts and client details can be checked without switching screens.

Bank activity and accounting records stay visible at the same time, so references, dates, amounts and client details can be checked without switching screens.

RESOLVE

5. Resolving unmatched transactions

5. Resolving unmatched transactions

Missing payments can be created without leaving reconciliation

Missing payments can be created without leaving reconciliation

Not every bank transaction already exists inside the accounting system. When one is missing, the payment can be created from within reconciliation, and the session carries on.

Not every bank transaction already exists inside the accounting system. When one is missing, the payment can be created from within reconciliation, and the session carries on.

Keeping this exception inside the main flow meant nobody lost their place in the queue to fix one missing record.

Keeping this exception inside the main flow meant nobody lost their place in the queue to fix one missing record.

6. Completing reconciliation

6. Completing reconciliation

The queue shrinks as records are matched

The queue shrinks as records are matched

Matched items leave the outstanding list and move to the reconciled view, and the balances update as you go.

Matched items leave the outstanding list and move to the reconciled view, and the balances update as you go.

  1. DASHBOARD

From one workflow to the whole business

From one workflow to the whole business

Each module above answers a question about one workflow. The dashboard concepts asked a wider one: what needs attention across the business right now?

Each module above answers a question about one workflow. The dashboard concepts asked a wider one: what needs attention across the business right now?

1

3

2

PERFORMANCE

How is the business doing?

How is the business doing?

OPERATIONS

Which projects need attention?

Which projects need attention?

RISK

Are there financial risks?

Are there financial risks?

ACTION

What should I do next?

What should I do next?

The legacy dashboard showed activity, but little about what needed attention.

The legacy dashboard showed activity, but little about what needed attention.

It reports volume, 537 orders and 601 invoices, with no trend or next step (1), spends prime space on a promo banner (2), and leaves a core module empty (3).

It reports volume, 537 orders and 601 invoices, with no trend or next step (1), spends prime space on a promo banner (2), and leaves a core module empty (3).

Deciding what deserved attention first was harder than designing any of the widgets.
Deciding what deserved attention first was harder than designing any of the widgets.

Exploring Multiple Directions

Exploring Multiple Directions

Four dashboard directions were explored. I worked on two of them: Unified Activity (B) and Action Hub (C).

Four dashboard directions were explored. I worked on two of them: Unified Activity (B) and Action Hub (C).

Performance Snapshot dashboard concept

The team went with Financial Insights (D) over the other three, including the two I worked on. The dashboard was still at concept stage when the project ended.

The team went with Financial Insights (D) over the other three, including the two I worked on. The dashboard was still at concept stage when the project ended.

PATTERNS ACROSS THE WORK

Different modules.

Different modules.

Recurring decisions.

Recurring decisions.

The same questions kept coming back on every module: what comes first, what each number is for, and what has to stay in view.

The same questions kept coming back on every module: what comes first, what each number is for, and what has to stay in view.

01

Sequence the work before adding options

Sequence the work before adding options

Time entries come before the timer, and project phases come before rates. In both, changing the order did more than adding a control.

Time entries come before the timer, and project phases come before rates. In both, changing the order did more than adding a control.

02

Numbers need a question behind them

Numbers need a question behind them

In Time Analysis, budget bars show whether a project is healthy. In reconciliation, the outstanding count shows how much is left.

In Time Analysis, budget bars show whether a project is healthy. In reconciliation, the outstanding count shows how much is left.

03

Keep both records on screen

Keep both records on screen

Bank and accounting records sit side by side while matching, and the fee stays visible while activities are edited in a slide-over.

Bank and accounting records sit side by side while matching, and the fee stays visible while activities are edited in a slide-over.

04

Extend what people already know

Extend what people already know

The timer, the component language and the ledger detail stayed in every module. What changed was the order the work happens in.

The timer, the component language and the ledger detail stayed in every module. What changed was the order the work happens in.

HOW THE WORK HAPPENED

Designing within a team

Designing within a team

I worked on four modules and two of the four dashboard concepts, inside a three-person UX team. Everything went through internal review first, then to the client and developers.

I worked on four modules and two of the four dashboard concepts, inside a three-person UX team. Everything went through internal review first, then to the client and developers.

UX Architect
UX Architect

Overall design direction, oversight and review.

Overall design direction, oversight and review.

Senior UX Designer
Senior UX Designer

Operations guidance, review, and the base component foundation I reused.

Operations guidance, review, and the base component foundation I reused.

Me, UX Designer
Me, UX Designer

Designing and iterating on the workflows I owned, and presenting them for feedback.

Designing and iterating on the workflows I owned, and presenting them for feedback.

Requirement or walkthrough → exploration → internal UX review → client and developer review → iteration.

Requirement or walkthrough → exploration → internal UX review → client and developer review → iteration.

WHERE THE WORK LANDED

Time Tracking

Time Tracking

Designed end to end

Flat Fee

Flat Fee

Designed end to end

Time Analysis

Time Analysis

Structure and IA

Dashboard

Dashboard

Two concepts, team chose another

Bank Reconciliation
Bank Reconciliation
Final design and developer review
Final design and developer review

The build went to another development partner, so I didn't measure implementation or usage.

The build went to another development partner, so I didn't measure implementation or usage.

REFLECTION

Next time, I'd test with working designers before final design.

Next time, I'd test with working designers before final design.

Everything here was shaped by client walkthroughs, team review and my own memory of month-end timesheets. None of it was tested with designers using the product day to day. With more time, I'd have put the timer flow and the matching screen in front of two or three working designers first. My experience came from one firm, and it was a few years old.

Everything here was shaped by client walkthroughs, team review and my own memory of month-end timesheets. None of it was tested with designers using the product day to day. With more time, I'd have put the timer flow and the matching screen in front of two or three working designers first. My experience came from one firm, and it was a few years old.

What this project taught me

What this project taught me

Make the next step obvious

Make the next step obvious

Across time, billing and reconciliation, the order of information and actions mattered as much as the components themselves. On any legacy system, that is where I look first now.

Across time, billing and reconciliation, the order of information and actions mattered as much as the components themselves. On any legacy system, that is where I look first now.

Take contested calls to the room

Take contested calls to the room

When a decision could go either way, I bring the options and their costs to the client and developers together. Side-by-side matching was settled that way.

When a decision could go either way, I bring the options and their costs to the client and developers together. Side-by-side matching was settled that way.

Create a free website with Framer, the website builder loved by startups, designers and agencies.