Frame the work
Make the user, constraint, and useful outcome visible before choosing a screen.
Profile / 2026
Alex Morgan
Making complex tools feel clear enough to use with confidence.
Independent product designer working across interface systems, interaction design, and the details that make software easier to trust.
- Based
- Montréal, Canada
- Working on
- Product interfaces and design systems
A small mark, made to move
Figure 01 / Practice
Start with the decision someone needs to make.
The work moves between product intent and the interface people meet every day. Each part should make the next part easier to understand.
Shape the system
Set clear rules for type, state, and components so the product stays coherent.
Check the edge
Review empty, waiting, error, and narrow-screen states before calling it done.
Figure 02 / Selected work
Small systems, considered end to end.
A pair of sample projects showing the brief, the choices, and what changed. Open a record to read the working notes.
01Northline dispatch
Operations software2026
A route planning workspace for a regional delivery team that needed to spot exceptions before the morning handoff.
Challenge
The old board gave every route the same visual weight. Dispatchers had to open several panels to find late stops and missing assignments.
Approach
The new layout groups work by urgency, keeps the next action beside each exception, and gives operators a compact route history they can scan in sequence.
What changed
In the demo review, the team resolved the three sample exceptions without leaving the route overview. The design keeps the handoff visible when live data is unavailable.
- Product design
- Interaction states
- Prototype
02Common Ground tokens
Design system2025
A compact token and component set for a small product team moving from one interface to three.
Challenge
The team had repeated styles, but no shared language for deciding which values could change together across products.
Approach
Color, spacing, and type were named by role. A short component guide shows the intended states and where a component should not be used.
What changed
The system makes theme changes easier to review and gives new contributors a clearer route from a design decision to its implementation.
- Design tokens
- Component rules
- Documentation
Figure 03 / Field notes
Notes from the work.
Short essays on product practice, interface systems, and details worth keeping.
3 notes in the column
- PracticeOctober 08, 20264 min read
Design the pause, not the spinner
Waiting is part of a product's behavior. A useful pause tells people what is happening, what is safe, and what they can do next.
- SystemsSeptember 29, 20265 min read
Tokens are a promise to future you
A design token is more than a reusable value. It is a small agreement about how a system should change without losing its shape.
- Field notesSeptember 11, 20263 min read
Small type, clear decisions
Labels carry operational detail. Their size should follow the importance of the decision they help someone make.
Figure 04 / Next steps
Have a useful problem to solve?
Share the context, the people involved, and what a better outcome would change.