Nate DouglasSenior Product Designer, home

Freelancer finances, made clearer.

I led a five-person design team on invoices, the dashboard and onboarding for a back-office app used by freelancers and small businesses.

Role
Lead product designer
Team
Led four other designers; worked with the CEO and Orchid B’s developers
Timeline
Oct 2022 to June 2023: two phases of 16 and 12 weeks, with a break between them
Product
Back-office web app for freelancers and small businesses. Shipped.
80% → 92.5%invoice satisfactionSurvey ratings, 5 people per round
30sfaster on the invoice task, on averageTimed task, round 1 against round 2
80% → 100%completed onboarding4 of 5, then 5 of 5
How these were measured

Two rounds of usability testing, five participants in each, 10 in total. Satisfaction comes from participants’ survey ratings.

My part

Lead designer on a team of five.

  1. 1 Sign-in flowsDesigned the sign-in and forgot-password flows for the first prototype.
  2. 2 Affinity mappingRan the affinity mapping that pulled the test feedback into four themes, then ranked the issues by severity.
  3. 3 Master reportWrote the master report the team and later stakeholders used.
  4. 4 Invoices and dashboardOwned the invoices tab and the dashboard. Added the onboarding progress bar after testing showed people couldn’t tell how long setup would take.
  5. 5 Style guideBuilt out the style guide and component library: spacing, type, icons and button states.
  6. 6 Team supportHelped teammates on their UI iterations, and we finished ahead of schedule.
The Orchid B dashboard: revenue history by month, recent invoices, a quick create invoice form and revenue by invoice status, with a product tour step pointing to the status chart
Problem

The first prototype worked, but it didn’t feel easy to use.

  1. People struggled to find invoice details and mixed up the invoice tab with recent suggestions.
  2. In onboarding, they couldn’t tell how long setup would take.
  3. The product tour got in the way, and people disagreed on whether it was useful.
The Orchid B dashboard with the product tour open over it
The dashboard, with the product tour that tested poorly in round one.
The brief
“We just want a tree that stands up and has the star at the top.”

The CEO described the product as a Christmas tree with too many ornaments. Every change had to make it simpler, not busier.

Claudio Romano, CEO and founder of Orchid B

Constraints

What we had to work inside.

Two fixed phases

16 weeks, then 12, with a break between them, from October 2022 to June 2023.

A working first prototype

Our first prototype already worked. The job was making it easier to use, not starting over.

A scope set at kickoff

One fix went past it: moving the tutorial into the side navigation. Some colleagues questioned that.

Decisions

Four fixes, each from something we saw in testing.

  1. The invoice list before and after, with an expandable invoice card
    Saw
    People struggled to find invoice details, missed information, and confused the invoice tab with recent suggestions.
    Call
    An expandable invoice card, so details open in place without losing your spot in the list.
    Result
    Invoice satisfaction rose from 80% to 92.5%, and the invoice task got 30 seconds faster on average in the retest.
  2. The dashboard before and after, with the redesigned revenue chart
    Saw
    People understood the revenue chart. The room to improve was letting them dig into individual categories.
    Call
    Change how the chart works, so the segment you pick expands and the overall breakdown stays visible.
    Result
    Everyone understood the chart in both rounds, and developers reused the design in the Orchid B mobile app.
  3. Onboarding before and after, with a three-stage progress indicator
    Saw
    People were unsure how long setup would take and went back to the personal information screen to find the next step.
    Call
    A three-stage progress indicator at the top of onboarding.
    Result
    Onboarding completion went from 80% in the first round to 100% in the retest.
  4. The product tour before and after, moved into the side navigation
    Saw
    People struggled with the tour and differed on whether it was useful.
    Call
    Move the tutorial into the side navigation, so people can skip it and come back later.
    Cost
    It went past the original scope, and some colleagues questioned it.
    Result
    One participant skipped the tutorial, then came back to it through the side navigation after logging in.
Design system

The style guide I built out.

I built the style guide and component library so the whole team designed with the same spacing, type, icons and button states. Ten sections, from the grid to the onboarding pieces.

The Orchid B style guide cover and its ten sections
IndexThe cover and the ten sections, from the grid down to the bigger pieces.
Desktop grid rules: a 1440px frame with 12 columns, 64px margins and 32px gutters
GridA 12 column grid on a 1440px frame, with 64px margins and 32px gutters.
The Orchid B wordmark in Helvetica Neue, Accessibility Black
WordmarkThe wordmark, set in Helvetica Neue in Accessibility Black.
Typography: SF Pro headings, subheadings, body and meta styles with Semibold, Medium and Regular samples
TypographySF Pro in semibold, medium and regular, from 35px headings down to 14px meta text.
Colors: main, accent and grayscale swatches with hex values
ColorsThe main colors, accent colors for invoice states like overdue, partial and approved, and a grayscale.
Iconography: small, dashboard menu, homepage, progress tracker, medium and large icons
IconographySmall, menu, homepage, progress tracker and large icons, sourced from Untitled UI Icons and Vuesax.
Small components: a delete confirmation modal, an income card, a contractor breakdown chart and a recent activity graph
Small componentsModals, plus the graphs and metric cards the dashboard is built from.
Standard input fields with their width, height, padding, radius and spacing
Input fieldsThe standard input field, with its sizes, padding, radius and spacing.
Drop-down selectors for dates, currency, frequency, category, filters and roles
SelectorsDrop-down selectors for dates, currency, frequency, category and filters.
The sign-up progress tracker, info and onboarding modals, feature and endorsement cards, invoice cells, badges and avatar frames
Modals, cells, cardsThe sign-up progress tracker, modals, cards, invoice cells and badges.
Onboarding intro and end modals, with phone and laptop mockups
Big elementsThe onboarding modals and the device mockups.

1 / 11Click a page to see it full size.

What people said

From people I worked with.

Benny Sun
“His ability to turn research questions into actionable results is nothing short of inspiring.”
Benny Sun, UX Research Director at Morgan Stanley · worked with me on Orchid B Read the recommendation ↗
Sebastian Negret
“He had a knack for making complex concepts easy to understand and was always able to communicate our design decisions in a clear and concise manner.”
Sebastian Negret, Lead Product Designer at FIU · on my Orchid B design team Read the recommendation ↗
Claudio Romano
“Thank you so much for the excellent work turned around in such short time.”
Claudio Romano, CEO and founder of Orchid B
Looking back

Bring up the tradeoffs earlier.

What I’d change

Raise tradeoffs earlier. Moving the tutorial into the side navigation went past the original scope. Next time I’d bring three things up front: what we saw in testing, the smallest fix, and what it costs to build.

What I’d do next

Watch the optional tour now that it has shipped: how many skip it, how many come back, and whether people who skip it still finish setup.