01
Complex product thinking
Translate workflow-heavy jobs, role differences, approvals, exceptions, and dense information into experiences people can navigate.
Brian Williams / Lead Product Designer
Complex products. Clear systems. Production-minded design.
I lead product design for workflow-heavy software, turning complex operational requirements into scalable experiences that can actually be built.
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
Why Brian
Product craft and implementation, considered together.
02
Systems thinking
Connect components to reusable interaction patterns, documented states, and product experiences without mistaking visual consistency for a complete system.
03
Design and engineering
Bring React, HTML, CSS, ServiceNow, and front-end experience into design discussions, prototypes, specification, and implementation review.
04
Hands-on leadership
Draw on 9+ years of management and team leadership across art direction, design reviews, stakeholder facilitation, and cross-functional delivery.
Selected work / Start here
Four different kinds of product evidence.
The enterprise cases are representative reconstructions, the commerce engagement is real commercial work, and the queue is an independent exploration. Each is labeled for what it is.
Representative case study
Orbit Operations
A composite exploration of an operational workflow split across requests, reviews, and handoffs. It shows how a queue, clear ownership, and visible exception paths can keep next steps connected.
Shows: Workflow architecture, exception handling, and product decisions
About 3 minutesView work
Representative case study
Nexus Case Management
A composite exploration of a multi-role product where forms, permissions, and status behavior need to work together. It focuses on the rules that help patterns stay consistent while roles have different actions.
Shows: Design-system thinking, states, and role-aware patterns
About 3 minutesView work
Real commercial work
eCommerce Platform
Brian designed and developed a commercial eCommerce platform generating more than $3M in annual revenue. That figure describes the platform-level outcome; it is not attributed to one design change.
Shows: Commercial design and development, with a verified platform-level outcome
About 3 minutesView work
Independent product exploration
Smart Queue Exploration
A fictional product exploration asks how an AI-assisted queue can bring potentially important work to a person’s attention. The concept keeps prioritization with the operator and is not presented as client work.
Shows: AI interaction judgment, uncertainty, and human control
About 3 minutesView work
Role match
Where I fit best.
Lead Product Designer
Hands-on ownership from discovery and workflow definition through interaction design, engineering partnership, and release.
Role-specific viewSenior Product Designer
End-to-end feature and product design for enterprise software, with close attention to information hierarchy and implementation.
Role-specific viewSelective Staff opportunities
A deliberate fit for enterprise systems, platform patterns, and design–engineering work—not a claim to a formal Staff title.
Role-specific viewEvidence index
What you need → where to see it.
- Complex workflows and operational ownershipOrbit Operations
- Data-heavy decisions and information hierarchyVector Readiness
- Reusable patterns, states, and permissionsNexus Case Management
- Commercial product design and developmenteCommerce Platform
- AI-assisted interaction judgmentSmart Queue Exploration
- Art direction, management, and team leadershipLeadership background
What I actually do
Work through the problem with the people building it.
- 01Talk with stakeholders and customers to understand the work, needs, and constraints.
- 02Map workflows and information architecture before committing to a screen-level solution.
- 03Explore interaction models and prototype decisions that benefit from being made tangible.
- 04Define reusable patterns and their states so behavior is clearer across features.
- 05Work with engineering early, review implementation, and resolve design questions through delivery.
- 06Set outcomes with the team and distinguish evidence from assumptions when evaluating the result.
Start a conversation
Building a complex product or platform?
I’m open to Lead and Senior Product Designer roles, and selective Staff opportunities, focused on enterprise products, systems, and delivery.