Skip to main content
Brian Williams.
Brian Williams / Lead Product Designer

I turn complex enterprise workflows into clear, scalable products.

I design enterprise SaaS and internal tools by structuring information architecture, modeling complex workflows, and defining interaction behavior—then carry reusable design systems into engineering.

View case studies View résumé

Product strategy + UX systems + technical execution.

01 / Define the workflow
OOrbit / Operations
J. Rivera

Team queue / 24 Sep

Work queue

Requests move forward with a clear owner and next step.

+ New request

Active

31

Due today

12

Blocked

4

Team queue 31My requests 08Escalated 02
Filter · Sort: oldest first
RequestSubmittedOwnerStageSLA
REQ-2084 · Network access reviewSep 24J. RiveraWaiting on reviewEscalation sentHighEscalatedNext: EscalateNext: Monitor response3d
REQ-2079 · Vendor access updateSep 23M. ChenNeeds approvalDue
REQ-2068 · Workspace setupSep 21A. BrooksBlocked · details5d

Queue state shown at 10:18 AM · illustrative interface / fictional data

02 / Design for scale ↗

Illustrative UI reconstruction · Not a client screenshot

What I design

Complex workflows
Operational processes, handoffs, and business rules made understandable.
Information architecture
Dense systems organized around where people are and what matters next.
Interaction systems
States, permissions, validation, feedback, and exception behavior.
Scalable product systems
Reusable patterns that support consistency from design through implementation.

How I handle complexity

Systems thinking in practice.

I rarely start with individual screens. I first model users, roles, information, workflows, states, business rules, and technical constraints; interface decisions follow once the structure is understood.

  1. 01 / 05

    Model the system

    Users, roles, information, rules, constraints

  2. 02 / 05

    Map the work

    Tasks, dependencies, handoffs, decisions

  3. 03 / 05

    Define behavior

    States, feedback, validation, exceptions

  4. 04 / 05

    Build the system

    Reusable interaction patterns and components

  5. 05 / 05

    Carry it to production

    Engineering collaboration, design QA, iteration

System model → interaction model → reusable product system → production experience.

The short version

Experience and verified career context

8+

years in product design

Enterprise product design and complex workflows

15+

years in digital design & front-end

Design, web, and implementation fluency

9+

years in leadership

Management, art direction, and team leadership

3

enterprise applications

UI/UX leadership across three applications

500+

users supported

Collective user base across enterprise products

$3M+

annual eCommerce revenue

Commercial platform designed and developed

Hands-on Lead Product Designer with experience spanning discovery, UX strategy, complex interaction design, design systems, engineering collaboration, implementation, and team leadership.

Real experience behind the reconstructions

Three enterprise applications · 500+ users · 9+ years leadership · $3M+ commercial platform

Career-level facts from professional work; not outcomes attributed to the representative cases below.

9+ years leading teams

Management, art direction, design review, client leadership, stakeholder facilitation, and hands-on delivery.

Featured work / 01

Complex problems, considered solutions.

Start with an NDA-safe representative case to see how I approach enterprise product challenges. Each reconstruction is clearly distinguished from verified career experience.

Short on time?

Choose the view most useful to you.

RepresentativeOrbit OperationsEnd-to-end workflow designRepresentativeNexus Case ManagementSystems and reusable patternsReal workeCommerce platformReal commercial design + development
Preparing for an interview? Start with the recruiter overview
How to read the workVerified · career factRepresentative · reconstructed scenarioIllustrative · fictional UI data
01Enterprise operations platformRepresentative case study

Orbit Operations Platform

Modeling complex operational workflows, information architecture, and role-based interactions.

Role Lead Product Designer (representative)

Focus Workflow orchestration · Role-based interactions · Reusable patterns

Reconstructed composite based on professional responsibilities. Names, interface content, and data are fictionalized.

View case study
Try previewPreview active
OOrbit / Operations
J. Rivera

Team queue / 24 Sep

Work queue

Requests move forward with a clear owner and next step.

+ New request

Active

31

Due today

12

Blocked

4

Team queue 31My requests 08Escalated 02
Filter · Sort: oldest first
RequestSubmittedOwnerStageSLA
REQ-2084 · Network access reviewSep 24J. RiveraWaiting on reviewEscalation sentHighEscalatedNext: EscalateNext: Monitor response3d
REQ-2079 · Vendor access updateSep 23M. ChenNeeds approvalDue
REQ-2068 · Workspace setupSep 21A. BrooksBlocked · details5d

Queue state shown at 10:18 AM · illustrative interface / fictional data

Illustrative UI · fictional queue data

02Enterprise decision-support platformRepresentative case study

Vector Readiness

Structuring changing operational data so people can interpret signals and make informed decisions.

Role Lead Product Designer (representative)

Focus Data hierarchy · Decision workflows · Complex states

Reconstructed composite based on professional responsibilities. Names, interface content, and data are fictionalized.

View case study
Try previewPreview active
VVector / Readiness
All regions⌄Last 30 days⌄

Decision support / Overview

Readiness signals

Updated 9:42 AM · fictional data

Readiness indexSep 23 point

87%91%

+4.2 pts+6 pts

Items changed

11

since prior period

Attention needed

7

across 3 groups

Reporting complete

93%

2 feeds delayed

Readiness over time

Trend context · weekly snapshot

View analysis →
Sep 02Sep 09Sep 16Sep 23Sep 30

Portfolio segments

by status
On track62%
Watch25%
At risk13%

7 exceptions · 3 overdue updates · 2 incomplete feeds

Areas to inspect

Drill into segments ↗
AreaReadinessChangeSignal
Service continuity91%+6 ptsImproving
Capacity planning72%−3 ptsWatch

Illustrative UI · fictional analytical data

03Multi-role case management systemRepresentative case study

Nexus Case Management

Designing coherent case workflows across roles, permissions, and shared interaction patterns.

Role Lead Product Designer (representative)

Focus Workflow architecture · Permissions · Reusable patterns

Reconstructed composite based on professional responsibilities. Names, interface content, and data are fictionalized.

View case study
Try previewPreview active
NNexus / Case workspace
Reviewer role⌄Specialist role⌄Help

Case / CX-3187

Address change request

Customer record · Opened 24 Sep · Updated 10:18 AM

Awaiting review

Current role

Case reviewerCase specialist

Workflow stage

Eligibility check

Assigned team

Account services

Case history

3 events

10:18

Review assigned

M. Chen · Reviewer

Yesterday

Documents received

Proof of address added

24 Sep

Request submitted

Customer portal

Documents

+ Attach
PDF

ID verification.pdf

Received · 24 Sep

PDF

Address proof.pdf

Needs review

Shared record pattern

Status and history persist across role views.

CompleteReviewBlocked

Illustrative UI · fictional case data

Real work

Commercial proof point: I designed and developed an eCommerce platform generating $3M+ in annual revenue. This is a separate real-work summary, not an outcome attributed to a single design change.

Explore eCommerce work

A closer look / 04

See how I work

Workflow model
Data analytics
Design system
Choose a weekender color and add it to the illustrative bagColorBag 0Bag 1Bag 2
Design → code

Why Brian

Design depth, systems thinking, and implementation fluency.

01

Complexity

I specialize in workflow-intensive enterprise software where users manage dense information, approvals, exceptions, and operational decisions.

02

Systems

I build reusable interaction patterns and design systems so teams solve product problems once instead of repeatedly.

03

Implementation

My front-end background helps me collaborate directly with engineering and carry design intent through production.

My product design point of view

Make the hard decisions visible before making the interface beautiful.

01

Model before styling

Start with the job, workflow, constraints, and information model.

02

Systems reduce future decisions

A good pattern solves more than the screen in front of us.

03

Bring engineering in early

Constraints are cheaper to understand before implementation.

04

Make tradeoffs explicit

Choose the right compromise intentionally, rather than implying a perfect answer.

Role alignment

Where I create the most value.

01

Enterprise products

Workflow-heavy internal and customer-facing systems.

02

Platform & systems

Reusable interaction models and cross-product design patterns.

03

Design + engineering

Technical product design with implementation awareness.

04

Product leadership

Discovery, stakeholder alignment, design reviews, mentoring, and delivery.

How I work / 02

From ambiguity to shipped product.

I stay involved from initial framing through implementation and release. Each artifact is a tool for making a better product decision, not process theater.

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

Explore my process

Design + engineering / 03

I design with implementation in mind.

My development background allows me to evaluate constraints early and collaborate with engineering before designs become expensive to change. I’m comfortable discussing React, HTML, CSS, responsive behavior, component states, and design QA.

More about my background

Design intent

Figma components · interaction specification · accessibility · edge cases

Implementation reality

React components · states · responsive behavior · production constraints

AI-enabled workflow / 04

AI accelerates execution. Product judgment stays human.

I use AI to explore possibilities and test ideas faster, then apply research, design judgment, and engineering context to decide what belongs in the product.

01 / TOOLSET

ChatGPT / Gemini

Requirements analysis, research synthesis, concept exploration, edge cases, and content modeling.

02 / TOOLSET

Prototyping / GitHub Copilot

Coded prototypes, interaction testing, front-end exploration, and implementation feasibility.

03 / TOOLSET

Higgsfield

Visual storytelling, concept visualization, and rapid communication assets.

Figma conceptCoded prototypeTested interactionRefined decision
Independent explorationHow I use AI responsibly

Leadership / 05

Leadership through clarity, systems, and execution.

Nine-plus years across management, art direction, design leadership, and stakeholder facilitation. I lead teams and stay hands-on with the work.

01 / How I lead

Set creative direction

At FCI Promos, led design and creative teams, guiding visual and digital direction across concurrent client work.

02 / How I lead

Lead design reviews

At Gaslight Media, led usability reviews and design critiques, then turned feedback into experience improvements and final UI.

03 / How I lead

Align stakeholders and engineering

At Seneca Resources, led design workstreams and aligned developers, analysts, QA, project managers, and stakeholders from concept through release.

04 / How I lead

Guide priorities and delivery

Managed priorities and delivery across team and client work while maintaining quality against scope and deadlines.

05 / How I lead

Stay close to the work

Across management, art direction, and product leadership roles, paired team guidance with hands-on design reviews and implementation decisions.

My approach to leadership

About / 06

Design, technology, and business in the same conversation.

I’ve spent my career working where design, technology, and business overlap. Visual design led to front-end development, UX, product design, and enterprise product leadership. That progression helps me connect the details of an interface to the realities of delivery and outcomes.

Career evolution

  1. Visual design
  2. Front-end development
  3. UX design
  4. Product design
  5. Product leadership

My career has moved progressively closer to the center of product decisions while retaining the visual and technical foundation I started with.

Read more about me

Career at a glance

Jun 2022–PresentLead Product Designer & Front-End DeveloperSeneca Resources / EY / DoD engagement
Jun 2021–Jul 2022Senior UI/UX DesignerGaslight Media
Jan 2020–Sep 2021Product Designer / Web DeveloperBedstone Creative
Jan 2017–Apr 2021Art Director & UI DesignerFCI Promos
2008–2017Digital Design & DevelopmentEarlier experience

Let’s connect

Have a complex product problem? Let’s talk.

Open to Lead and Senior Product Designer roles, and selective Staff opportunities, focused on enterprise SaaS, platforms, complex workflows, and design systems. US remote.

Email Brian LinkedIn View résumé