01 / Evidence
Workflow ownership
Keep the current owner, decision context, and recoverable next step connected across handoffs.
Explore related workRole focus / Enterprise Product Design
I focus on enterprise experiences where an action depends on the right information, the right role, and a clear path through routine and exceptional work. Product design needs to make system behavior legible without hiding the complexity teams actually need.
Relevant evidence
01 / Evidence
Keep the current owner, decision context, and recoverable next step connected across handoffs.
Explore related work02 / Evidence
Pair priority signals with freshness context and a route to the underlying information.
Explore related work03 / Evidence
Preserve the case record while available actions reflect the role and access state.
Explore related work04 / Evidence
Use front-end fluency to account for technical constraints and review design intent in implementation.
Explore related workSelected work
Representative case study
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
Representative case study
A composite exploration of data-heavy operational decisions: how to make signals, reporting freshness, and the path to underlying detail legible without treating a dashboard as the final decision.
Shows: Information hierarchy, signal quality, and operational decision support
Real commercial work
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
Start a conversation
I’m open to Lead and Senior Product Designer roles, and selective Staff opportunities, focused on enterprise products, systems, and delivery.