SaaS Product Discovery

Receipts for Product Decisions

UX Research

Workflow design

Documentation systems

The Client and the Challenge

From Ambiguity to Answers

A client in software development wanted documentation to drive a SaaS product.

The Client and the Challenge

From Ambiguity to Answers

A client in software development wanted documentation to drive a SaaS product. In a nutshell, they wanted to see if

Goal

Find the Problem ASAP

Design a workflow that captures decisions fast, keeps context connected, and stays easy to use.

Timeline

3 months

Role

UX Researcher

Deliverables

UX Requirements

Tools

Figma · Bubble · Excel · Whimsical · Miro

My Process

Be Like a Sponge and Absorb

1

Discovery and interviews

Capture as many assumptions about the problem space and brainstorm questions.

Synthesis

Refine interview scripts with open-ended questions that get people talking.

2

Flow and information architecture

Translate interview findings into sticky notes on a board and define objects.

3

Prototype concepts

Refocus scope boundaries that log major project milestones and pivots.

4

What Worked Best

Framing in Terms of Customer Value

Noun foraging to identify the "objects" users focus on in their work. This clarified their mental model and highlighted where to dig deeper and iterate.

Converting interview findings into objects

We reviewed a RAID log weekly to stay on task. It surfaced assumptions early, before they became surprises.

Lightweight scope boundaries

Tight, iterative loops

Even in research, asteady cadence drives results. Sprint rhythms kept insights sharp and assumptions visible.

Object-mapping curated over the first 4-week design cycle to capture all applications.

Entity Relationship Diagram (ERD) generated from object-mapping.

Results

Clarity First. Rework Last.

Some users aligned more with the tool. We logged that direction in our decision trail, with timestamps.

Validation direction based on user behavior

Prototype-ready flows that teams would use

Rough sketches, Figmockups, and coded pages on Bubble to test and repeat with new changes.

A framework stakeholders can get behind

An early MVP sets the foudation. A design system enables rapid prototyping. No-code tools made handoff faster and build-ready.

Results

Clarity First. Rework Last.

Some users aligned more with the tool. We logged that direction in our decision trail, with timestamps.

Validation direction based on user behavior

Prototype-ready flows that teams would use

Rough sketches, Figmockups, and coded pages on Bubble to test and repeat with new changes.

A framework stakeholders can get behind

An early MVP sets the foundation. A design system enables rapid prototyping. No-code tools made handoff faster and build-ready.

Results

Clarity First, Rework Later

Some users aligned more with the tool. We logged that direction in our decision trail, with timestamps.

Validation direction based on user behavior

Prototype-ready flows that teams would use

Rough sketches, Figmockups, and coded pages on Bubble to test and repeat with new changes.

A framework stakeholders can get behind

An early MVP sets the foudation. A design system enables rapid prototyping. No-code tools made handoff faster and build-ready.

How My Process Changed

Optimizing For What Works

High Clarity

Aim for higher quality research data (interviews, surveys, card sorting, noun foraging).

Low Friction

Keep sprints simple. One iteration at a time. Streamline each step so handoff is smooth sailing.

Standardize

Systematized how research insights become flows and requirements for developers to translate.

Reframe

Adjust direction when the data disagrees. Collaborate on the real problem, then log decisions.

How My Process Changed

Optimize What Works

High Clarity

Aim for higher quality research data (interviews, surveys, card sorting, noun foraging).

Low Friction

Keep sprints simple. One iteration at a time. Streamline each step so handoff is smooth sailing.

Standardize

Systematized how research insights become flows and requirements for developers to translate.

Reframe

Adjust direction when the data disagrees. Collaborate on the real problem, then log decisions.

Before

After

Slide between images

Translated interview insights into rough mockups and into UI using prebuilt components.

Prototype feature concept based on validated user patterns.