OutbuildDesign operations2025–2026

Building a design practice: moving Outbuild’s UX from emergent to systematic

Role

Senior UX/UI Designer

Team

Head of Product, PMs, engineering, customer success, one additional designer

Timeline

Sep 2025 – ongoing

Platform

Web, iPad, mobile

Scope

Self-initiated, no formal mandate · Org-wide: product, engineering, customer success

TL;DR

The stake

I assessed Outbuild’s UX at Stage 3, Emergent. To scale, design needed shared standards, processes, and a research loop.

What I did

I assessed our UX maturity, wrote the mission and principles, built the core processes, and onboarded a second designer.

How I led

I started this without a mandate. I took the roadmap to the Head of Product, and gave PMs, engineering, and customer success each a specific way into the process.

Results

Stage 3 today, Stage 4 as the target.

UX maturity, NN/g model

I assessed Outbuild at Stage 3, Emergent, and wrote the roadmap to Stage 4.

Outcomes

Six weeks to a working foundation.

  • Six weeks to shared principles: unified design principles and a recurring designer meeting by October 21, 2025.

  • Core processes in place: design process, handoff checklist, specs, terminology document, research process, and a customer-success-to-UX channel.

  • Second designer onboarded, taking delegated tasks within her first couple of months.

  • Quarterly maturity review presented to the product team in December 2025.

  • Design status on the roadmap: I proposed a “needs design” column.

We don’t yet have a measured before-and-after maturity score. Stage 4 is the target, not a claim.

01 · Context & problem

Design was emergent. It needed a system.

I joined Outbuild on September 15, 2025. Within two weeks I told the product team where I thought we stood. On the NN/g UX Maturity Model, we were at Stage 3: Emergent.

Stage 4 would make our UX more systematic, scalable, and impactful. I started this work myself. Every other priority, from the design system to the Lookahead redesign, depended on a shared foundation.

02 · Constraints

No mandate, and no pause in delivery.

  • Delivery couldn’t pause. I built the practice alongside active product work, including the design system and Lookahead.

  • No formal mandate. My title was Senior UX/UI Designer, not design manager. Influence had to come from useful artifacts.

  • A small design team. A second designer joined about a month after me. Processes had to work for two people and scale past that.

03 · My role & influence

Influence through useful artifacts.

I owned the assessment, the roadmap, and every process artifact. I took the roadmap to the Head of Product in October 2025 and posted the mission and principles to the product team.

Each partner group got a specific way in. PMs got design specs and a request card. Engineering got a handoff checklist. Customer success got a direct line to UX.

04 · Strategy

A roadmap from Stage 3 to Stage 4.

The roadmap covered eight areas:

  1. Designer onboarding in Figma

  2. Standardized file organization

  3. Documented design and research processes

  4. The design system and its documentation

  5. A research repository

  6. Design-quality metrics

  7. UX benchmarking

  8. UX education for PMs and engineers

The first items finished were unified design principles and a regular designer meeting. Process documents followed within weeks. Measurement and benchmarking depend on that foundation, so they come later.

05 · Key decisions & trade-offs

Four decisions that shaped the practice.

1. Principles before process.

I wrote a mission first. Our goal was “To craft clear, scalable, research-driven design that fits every construction user and accelerates every development build.”

Four principles followed: “A clear foundation comes first,” “Measure twice, cut once,” “A clean job-site,” and “The design of all trades.”

The first principle sets an explicit order: clear, then efficient, then consistent, then beautiful. The tradeoff is deliberate. Visual polish waits until the workflow is clear.

2. A direct line from customer success to UX.

Support conversations show where users struggle. I set up a channel from customer success to design, alongside structured feedback from PMs, product leadership, and developers. I also requested product usage and screen-size data to ground research.

3. Onboard, then delegate.

When a second designer joined in October 2025, I wrote her onboarding plan. It set weekly design syncs, a process for requesting components, and a handoff of design-system work. I got her up to speed, then delegated tasks to her during her first couple of months. She went on to expand the design system.

4. Coded prototypes and AI-referenceable documentation.

During 2026, we moved key handoffs to coded prototypes for the Lookahead, iPad, and mobile apps. I merged the button documentation page into the Lookahead prototype so Claude could reference real components instead of inventing new ones. I then had Claude audit the prototype’s button variants, which surfaced several buttons to remove.

This created a new risk, and I named it. Designers were refining components inside prototypes, and those changes weren’t reaching Figma or Storybook. I raised it with our engineering lead as a process gap to close.

06 · Reflection

Process was the easy part.

The process documents were the easy part. The harder part is keeping Figma, prototypes, and Storybook in sync. Design-quality metrics and UX benchmarking turn this from process into evidence. That is what I would prioritize next.

Next case study