Skip to main content
Brian Williams.

How I work

From ambiguity to shipped product.

The work is not a fixed checklist. The right methods make risks visible, align the team, and connect insight to implementation.

01 / 06

Understand

Business goals, user needs, constraints

02 / 06

Model

Workflows, information architecture, journeys

03 / 06

Explore

Wireframes, prototypes, alternatives

04 / 06

Systemize

Components, patterns, design systems

05 / 06

Ship

Engineering partnership, design QA, iteration

06 / 06

Learn

Feedback, measurement, next iteration

01

Insight

What did we learn about the job, the system, or the constraint?

02

Decision

Which direction best solves the problem, and what does it sacrifice?

03

Design response

How does the interface and interaction model express that decision?

I use discovery workshops, interviews, workflow maps, information architecture, prototypes, usability feedback, component specifications, and design QA where they help answer a real product question. I avoid artifacts that exist only to decorate a case study.

Outcomes and evaluation

How I think about success

I define desired outcomes early, then choose measures with the team that can show whether the experience is working.

Efficiency

Task completion time · steps required · manual work removed

Quality

Error rate · completion rate · exception handling

Adoption

Feature usage · repeat usage · workflow completion

Experience

User feedback · usability · support friction

Delivery

Component reuse · implementation consistency · design debt

These are candidate measures for future evaluation, not reported project results. Not every engagement exposes every metric, but I define desired outcomes early so decisions can be evaluated against something more meaningful than preference.

Design + engineering

Design does not end at handoff.

  1. 01Figma
  2. 02Specification
  3. 03Implementation
  4. 04Design QA
  5. 05Refinement
  6. 06Release

My front-end background helps me evaluate constraints early, review built experiences against design intent, and work with engineering to resolve issues before release.

Design token

Status / warning

Component

Needs review

Implementation concept

<Status variant="warning" />

How products behave

Interaction Design

A polished interface is more than its resting state. I design how products respond, communicate status, preserve context, and recover as people move through complex workflows.