Mosaic · Self-serve metrics case study

Metric Builder

Mosaic users can build custom metrics by dragging fields into a table, or by writing a formula.

Building one used to mean writing code-like formulas. As design lead, I designed the drag and drop builder, and metric creation time fell from an average of 12 minutes to under 5.

Role
Design lead, Metric BuilderOfficial title: Senior Product Designer
Timeline
8 to 9 monthsA phased project
Research method
Interviews and beta sessionsSMEs and beta clients, 5 to 7 participants
Time per metric
Under 5 minPer metric, down from an average of 12

The problem

Custom metrics were hard to build and hard to find.

Mosaic's pre-built metrics couldn't handle custom queries. Building your own meant formulas buried in data management settings, so use stayed low.

Bar chart, average time per metric, by skill level: Beginner 18 minutes, Intermediate 11 minutes, Advanced 8 minutes. Beginners took 10 minutes longer than advanced users.

Syntax

Code-like inputs intimidated users.

Beginners found the existing tools hard to learn, and preferred visual editors even to syntax they knew.

80%

of interviewees preferred a visual, inline, drag and drop UI

Trust

Advanced users didn't trust edits.

They saw a change to the original metric or report as a critical flaw in SaaS reliability.

Original metric

See how nesting works

Access

Access differed across areas.

Reporting and analysis each reached metrics in a different way.

A quarter of feedback was about these disjointed experiences

The five pain points, in full
  1. Overwhelming syntax editors. Code-like inputs intimidated users and added cognitive load. 80% of interviewees preferred a visual, inline, drag and drop UI.
  2. No intuitive metric tools. Novice users found the existing tools cumbersome and hard to learn. They preferred visual editors to complex syntax, even syntax they knew.
  3. Destructive edits. Advanced users worried that a change would affect the original metrics or reports, and saw that as a critical flaw in SaaS reliability.
  4. Accessibility hurdles. Feedback showed problems for users at every experience level, and about 45% asked for a more inclusive, easier approach.
  5. Integration gaps. Metrics sat deep in data management settings, and access differed across areas such as reporting and analysis. This made up a quarter of the feedback, all about disjointed experiences.

Mosaic's pre-built metrics were too rigid for custom queries that fit different business needs. Competitors offered similar tools, but their UIs were clunky and missed the chance for intuitive interactions.

The 30-second read

I designed one builder for every skill level.

Beginners leaned less on support, and experts kept their formulas.

01 · What I designed

People drag fields into a table to build a metric, and experts can still type a formula.

02 · What changed

After release, metrics took less time to build and more people used the feature.

My role: I was the design lead at Mosaic, a strategic finance platform. I led Metric Builder with developing designers, engineers, project managers and subject matter experts (SMEs), and owned the research, personas, journey map, wireframes, high-fidelity mocks, prototypes and user testing.

  • User research
  • Personas
  • Journey mapping
  • Wireframes
  • Prototyping
  • Usability testing
  • Data-heavy UI
  • FP&A

Walkthrough · 57 seconds

Three metrics get built, by dragging, by pivoting and by formula.

Research

I interviewed users and reviewed their tools.

People knew Excel and Sheets, but neither could nest metrics.

Beginner user

New Analyst

Design influence: Led to the visual interface and a streamlined workflow, so building a metric is quick and dependable.

  • Visual interface
  • Streamlined workflow

Way inDrag and drop

Advanced user

Experienced Analyst

Design influence: Shaped inline editing, metric nesting and non-destructive edits.

  • Inline editing
  • Nesting
  • Non-destructive edits

Way in= Formula

The insight

Beginners drag, experts type a formula, and both build the same metric.

I reviewed tools like Excel, Google Sheets, Looker, Tableau and Trevor.io, and found gaps in flexibility and ease of use. Most BI tools leaned on spreadsheets for entry-level users, which pointed to a hybrid with custom syntax for advanced users and a visual UI for beginners.

Two ways into the same metric. A beginner drags the ARR field into Values, and an expert types the formula equals MRR times 12. Both build the same row: ARR, 10,418,880 in January 2023, 10,662,180 in February and 10,987,560 in March.

Full persona details

New Analyst (beginner user)

  • Demographics. Early-career finance pro, 25 to 35, new to Mosaic, uses metrics for basic tasks.
  • Goals and needs. Wants pre-built and custom metrics in an easy, intuitive UI, to work faster and deliver tailored, polished data.
  • Pain points. Confused by syntax, worries about data mistakes, and depends on support.
  • Behaviors. Prefers drag and drop and inline edits, and likes the familiar feel of Excel and Google Sheets.

Experienced Analyst (advanced user)

  • Demographics. Seasoned analyst, 35 to 50, proficient Mosaic user, specializes in forecasting, budgeting, and risk assessment.
  • Goals and needs. Build and save complex queries with flexible syntax, and nest out-of-the-box or earlier metrics inside new ones to do more with them.
  • Pain points. Limited nesting options, inefficient workflows, and integration problems across other areas.
  • Behaviors. Relies on advanced controls, focuses on speed and precision.
The tools I reviewed
Microsoft Excel logoGoogle Sheets logoSpreadsheets

Excel and Google Sheets

Familiar, but no advanced SaaS nesting.

Looker logoBI tool

Looker

Users found the UI clunky for non-technical people and teams, with limits on custom metrics and nesting.

Tableau logoBI tool

Tableau

Strong on data visualization, but it cost more, took longer to learn and limited custom metrics and nesting.

Trevor.io logoAd hoc queries

Trevor.io

Non-technical users preferred it for ad hoc queries, citing Looker's complexity.

What I found

  1. Market share. Excel and Google Sheets led basic metric tasks in SMBs because people knew them, but they lacked advanced SaaS nesting, and users found custom queries inefficient.
  2. BI tool preferences. Small and mid-sized businesses favored Looker for its affordability and accessibility, but users found its UI clunky for non-technical people and teams. Tableau was strong on data visualization but cost more and took longer to learn.
  3. SaaS integration gaps. Tableau and Looker offered real-time analytics but limited custom metrics and nesting. Most BI tools leaned on spreadsheets for entry-level users.
  4. User feedback. Non-technical users preferred tools like Trevor.io for ad hoc queries, citing Looker's complexity, and cohort analysis often fell back on Excel or Sheets because BI tools got in the way. Users said they needed several different tools to get their work done.

From my review

Screenshots from my review, with people's names, emails and account names blurred.

Journey map

I mapped every touch point before development.

One edit had to show up in reporting, data management and analysis.

What my journey flow protected. One change in Metric Builder, the Opportunity Amount metric filtered from all statuses to Open and saved, updates Reporting, Data management and Analysis together: the report row, the metric list and the chart all show the Open amounts, from 642,300 in January 2023. The map also kept nesting consistent, kept edits non-destructive and flagged upgrades and scope. Two edge cases were caught before development: an invalid formula, underlined with a message about a missing closing parenthesis, and two people editing the same metric at once.

Open the full journey board in Figma

Design

I moved metric building into the table.

You can build without a formula, and reuse a metric without changing the original.

01 · Drop zones

Where you drop a field decides where it shows in the table.

Interviewees wanted to build visually, so the table itself is the editor. Columns make the headers, Rows the labels down the left, Values the cells, and Filters narrow the whole table.

AnswersCode-like inputs intimidated users

Animated mini of the builder. Date dropped into Columns becomes the month headers, from Jan 2023. Amount dropped into Values fills the cells. MStatus dropped into Rows adds Lost, Open and Won labels down the left. Moving MStatus to Filters folds the rows back into one and adds a filter strip above the table. Picking Open narrows the values to open opportunities.

02 · Inline settings

Click a field to change its settings right beside it.

Inline editing came from the experienced analyst, and it keeps you in the table. Number type starts as Number and switches to Currency, Percent and others.

Shaped byThe Experienced Analyst

Animated mini of the builder. Clicking the ARR field in the Values box opens its Number type settings right beside it. Number is the default, and picking Currency turns the ARR row into dollars, $10,418,880 for January 2023, while Revenue stays a plain number.

03 · Nesting

You can pull a saved metric into a new formula.

It comes in as a token, and the original never changes.

AnswersAdvanced users didn't trust edits

Animated mini of the builder. A search of saved metrics for "recur" finds Recurring Quarterly Expenses, and Insert pulls it into a new formula as a token, ROUND of Recurring Quarterly Expenses divided by Revenue, to 3 digits, which fills the row with 0.096, 0.080 and 0.087 for January to March 2023. The saved metric reads "In formula" and "The original never changes."

04 · Saved metrics

Saved metrics live in one catalog, so they can be reused.

When you save a metric, it goes to the top of the Metric Catalog, ready to use in the next one.

AnswersAccess differed across areas

Animated mini of the builder. Clicking Save metric on Revenue and ARR shows Metric saved, and the Metrics breadcrumb opens the Metric Catalog, where the new Custom metric sits on top of the saved metrics list, ready to be reused. The count goes from 8 to 9.

Early wireframes (6)

I explored layouts with our growing library of wireframe components, so quick user tests could check the flows and structure before any detailed UI work.

Testing

I tested the builder with SMEs and beta clients.

I tested in rounds with 5 to 7 people, then in production.

Methods
Iterative sessions, plus production testing for UX and visual feedback.
What we heard
Clients called the UI "refined yet familiar" and said it sped up metric creation. They responded best to more control over metrics and the real-time canvas previews, and 80% of beta testers noted easier nesting and edits.

Product tour

You build a metric in four steps.

Step 4 is the other way in, a formula instead of drag and drop.

Metric Builder before any data is picked. In the Configure panel the Dataset select is open on its list, Revenue, General Ledger, Employees, Headcount, Opportunities and Billing, with the pointer on Revenue. Below it the four boxes, Filters, Columns, Rows and Values, wait for fields.
Dragging ARR onto the table, which already shows Date as months and a Revenue row. ARR stays ghosted in the field list and a white drag card follows the pointer. The table body is outlined and tinted, and a ghost ARR row with faint values opens at row 1, marked by a blue insertion bar on its top edge, with Revenue below it.
ARR clicked in the Values box. Its Number type settings open beside it, with Currency picked over the default Number, USD and 0 decimals, and the ARR row in the table now reads in dollars, from $10,418,880 in January to $11,840,640 in June.
Formula mode. The formula reads = ROUND( Recurring Quarterly Expenses / Revenue, 3), with the saved metric and the Revenue field as tokens. The table fills its first row from it, 0.096 in January 2023 to 0.082 in June. In the Saved metrics list, Recurring Quarterly Expenses is marked In formula.

Try it

Drag a few fields in and build a metric yourself.

Every drop updates the table, so you see the metric before you save it.

Interactive Metric Builder. Move the fields Date, Revenue, ARR, Amount and MStatus onto the table or into the Filters, Columns, Rows and Values boxes, and the table builds as you go: Date in Columns makes the month headers, numbers in Values fill the cells, MStatus in Rows adds one row per status, and fields in Filters narrow the table. Click a field to pick a box, click a chip to change its settings, click the title to rename the metric, save it with Save metric, and use Reset to start over.

  1. Drag Date to Columns
  2. Drag Revenue and ARR to Values
  3. Click ARR, pick Currency
  4. Add Amount, then MStatus to Rows
  5. Move MStatus to Filters, pick Open
Untitled metricDataset: Revenue
No filters

Configure

Data fields 5

Filters

Drop fields here

Columns

Drop fields here

Rows

Drop fields here

Values

Drop fields here

Results

Metric Builder saved time and cut support tickets.

Feature usage rose 35% within three months of release, and metric helpdesk tickets fell 45%.

Creation time per metric
About 12 minutes to under 5 per metric
Goal 1

Enhance usability.

A visual, table-based UI with drag and drop and inline edits, to cut creation time at every skill level.

Result

Under 5min per metric

Users said their tasks got simpler.

Goal 2

Boost flexibility.

Non-destructive nesting of pre-built or custom metrics, so advanced users can build on a metric without touching the original.

Result

80%of beta testersnoted easier nesting and edits

Users got more control and faster turnaround when creating or editing custom metrics, relied less on the support team, and non-technical users could do more on their own.

Goal 3

Drive adoption.

Bring metrics into every area of the platform, to cut silos, help teams work together and speed up workflows.

Result

35%more feature usage

Easier integration and shorter onboarding for new clients helped usage grow.

Support reduction

45%fewer metrichelpdesk tickets

Self-service let users at every skill level do more on their own.

Looking back

What held up

Working closely with SMEs and clients paid off.

We ran FigJam brainstorms and got steady input from SMEs and eager Mosaic clients, which sharpened our process and made the UI clearer for very different users.

What I would change

Scope changes stretched the timeline.

Metric Builder grew from an advanced feature into a tool for everyone, and planning on casual feedback wasn't enough. Next time I would add formal user research early to predict those changes and keep the work focused.

Metric Builder · Mosaic

Thanks for reading.

I kept the formula for experts and gave everyone else drag and drop.