01 / System creation
One foundation, many enterprise products
Tokens, components, templates, and the rules for evolving one foundation across seven products.
Case study · Password requiredDesign Systems · Senior / Staff Designer
Shared foundations.
Better product decisions.
I design systems for complex enterprise products: the foundations teams share, the patterns people learn, and the boundaries that keep products coherent as they grow.
See the systems in useCoherence, from the inside out
04 / ProductDecisions people can make
03 / TemplatesRecurring jobs, shared structure
02 / ComponentsPredictable patterns and states
01 / FoundationsTokens · type · modes · spacing
Selected systems work
One foundation.
Different levels of the problem.
02 / Product-level systems
Smart Commercial Suite
Repeatable interaction rules for a modular credit workspace, proven in two pilot workflows.
Case study · Password required03 / System application
Credit Portfolio Monitoring
Using a system migration to restructure a product around three expert jobs.
Case study · Password requiredWorking principles
The library is a starting point.
The product is where it earns its place.
Start with the recurring job
Understand the information, decisions, and environments a system needs to support before choosing a component.
Make the rules explicit
Connect tokens, components, templates, and interaction behavior so teams can make coherent local decisions.
Prove the foundation in use
Apply the system to demanding product work; distinguish a shared gap from a product-specific need.