Skip to main content
Hiring overview

// Role focus · Design Systems Product Design

Build shared product behavior, not just shared controls.

My systems work starts with the product behaviors teams repeat. Reusable components are one layer; states, workflow patterns, permissions, and guidance for valid extensions help connect the system to real product work.

Role focus
Design Systems Product Design
Current title
Lead Product Designer, Seneca Resources
Each stop on the route is a piece of evidence below, linked to its work.
nexus / case workspacePeople servicesME
CASE MANAGEMENT / NXS-2084Workplace accommodation reviewConnected people. Clear next steps.
+ New case
Received Assigned In review Resolved
Case ownerMorgan Ellis
CategoryPeople services
Supporting review note

Brief, evidence, documents, and decisions share one case workspace.

Intake complete
Review pending
INDEPENDENT INTERFACE RECONSTRUCTION / FICTIONAL DATAExplore the working example

Relevant evidence

The work behind the role fit.

01 / Evidence

Foundations

Type, spacing, semantic color, focus, and accessibility establish the rules people build on.

Explore related work

02 / Evidence

Components

Common controls describe useful defaults while accounting for focus, disabled, validation, and permission states.

Explore related work

03 / Evidence

Patterns

Search, approvals, errors, and empty states carry interaction behavior across features.

Explore related work

04 / Evidence

Templates

Queue, record, form, and admin structures apply shared patterns to complete product jobs.

Explore related work

05 / Evidence

Product

Shared foundations lead into role-aware enterprise experiences; meaningful exceptions remain documented.

Explore related work

A system at product scale

Foundations → components → patterns → templates → product.

  1. 01

    Foundations

    Type, spacing, semantic status, focus, and contrast.

  2. 02

    Components

    Controls with behavior and state definitions.

  3. 03

    Patterns

    Repeated workflow behaviors: validation, approvals, and errors.

  4. 04

    Templates

    Reusable page structures for queues, records, forms, and admin.

  5. 05

    Product

    Role-aware experiences with documented rules for justified exceptions.

Selected work

A short path to relevant examples.

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

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

Start a conversation

Building a complex product or platform?

I’m targeting Staff, Principal, Lead, and Senior Product Design roles focused on enterprise platforms, design systems, and delivery.