1 · How I make design decisions
Clarity before pixels: every decision is shaped by the one above it.
| Order | Layer | The question I ask |
|---|
| 1 |
Enterprise constraintsThe boundaries |
How do I resolve competing needs without forcing a platform-wide rule?
Event-level reaction configuration |
| 2 |
Workflow designThe journey |
How do I replace a complex data model with an interaction model users already understand?
Product configuration |
| 3 |
Information architectureThe structure |
How do I decide what information belongs in the primary hierarchy?
Operator dashboard |
| 4 |
Interaction designThe details |
How do I keep interaction visible without distracting from the primary task?
Reaction system |
2 · How I simplify complex systems
Progressive disclosure: show the decision a user needs to make now. Reveal complexity when it becomes relevant.
- LivestreamDefault event configuration → advanced production options, revealed by earlier choices.
- TIBCO sales orderInitial selections → conditional fields → validation → downstream impact.
- Product configurationExisting row → copy → change two fields → submit.
3 · How I prevent costly errors
Designing systems that help people make correct decisions before errors become expensive.
- Operator workspacePrevent operators from discovering configuration problems during a live event.
- ReactionsPrevent interaction from overwhelming the video.
- Product configurationPrevent users from re-entering product data that didn't change.
- Sales ordersPrevent errors from propagating downstream into billing and fulfillment.
- OnboardingPrevent provisioning errors from reaching a new hire's Day 1.
4 · Decisions by project
Each decision lives in its case study, with the full reasoning one click away.