Could these be one system?
At Trek Health, I reframed five separate analytics reports as one shared model with multiple ways in.
See PivotThe interface is
the last layer.
I’m a senior product designer who brings structure to complex systems and products still deciding what they are.
- 01ObjectsWhat exists?
- 02RelationshipsWhat affects what?
- 03DecisionsWhere does judgment happen?
- 04InterfaceWhat needs to be visible now?
Good product design doesn’t hide complexity. It decides what belongs where.
I look for the product model beneath the interface, then use hierarchy, language, and interaction to make that model legible. The goal is less repeated thinking, better decisions, and enough detail to trust what happens next.
What should the product remember?
At Scope, I helped translate a manual implementation service into a structured product workflow.
See ScopeWhich complexity creates trust?
In reimbursement analytics, dense detail is often the evidence. CMA keeps it close without making it the starting point.
See CMAA useful prehistory
Philosophy taught me to question the model. Dance taught me to notice what structure does.
I studied both at Connecticut College. They seem far from enterprise software, but the habits carried over: examine the premise, understand the relationships, and make an experience coherent.
Today, I use those habits across product strategy, information architecture, interaction design, research, design systems, and AI product design.