Enterprise UX & information architecture
Designing dense, role-based applications for people who need speed, clarity, and access to a great deal of information without losing the structure of the work.
Work by type
A chronological portfolio explains how my career developed. This view reorganizes the same work around capabilities: what I was asked to understand, design, document, deliver, or lead.
Designing dense, role-based applications for people who need speed, clarity, and access to a great deal of information without losing the structure of the work.
Building the programs that collect, organize, test, and distribute customer feedback so that scores and comments become usable evidence.
Making behavior explicit before and during development: what the system must do, what can go wrong, and how rules and exceptions shape the experience.
Using technical fluency to make ideas testable, expose implementation constraints early, and keep designs connected to data and production reality.
Helping users, operations, design, engineering, vendors, and leadership arrive at a shared understanding of the problem and a workable path through it.
Browse by artifact
Some visitors want the case. Others want to see the actual form of the thinking. This provides a direct route to both.
Preconditions, rules, exceptions, acceptance criteria, and the detailed behavior required of a system.
02 Functional flowsVisual models showing decisions, alternate paths, system responses, and the movement from one state to another.
03 Wireframes & prototypesLow- and higher-fidelity representations used to test structure, interaction, information density, and feasibility.
04 Site maps & navigationWays of organizing information so users can understand where they are, what is available, and where to go next.
05 Surveys, dashboards & analysisInstruments and views that turn customer feedback into measurable, interpretable, and actionable information.
The organizing principle
Every label should answer a useful question: what kind of problem was this, where did I solve it, and what can a visitor inspect to judge the work?
Okay, back to the short version →
The first three pages establish who I am, how the work developed, and what kinds of problems I solve. The next layer is the individual case study.