Multi Product Integrations
Shared patterns.
Room for different work.
Designers were making similar workflow decisions across separate applications. I helped turn those repeated decisions into shared patterns, Figma libraries and a layout starter that teams could adapt.
01 / The repeated decisions
Different applications.
Familiar design problems.
Across the places I've worked, teams often defined their own workflows even when the interactions overlapped. We wanted a common starting point that could support those shared needs.
The work reached into everyday interface decisions: when to use a modal or drawer, where close controls belong, how information is read, and how labels relate to their values.
Label beside the value
Label above the value
02 / Adopt the better pattern
Consistency also meant
learning from another team.
Some applications had more developed dashboards and progressive-disclosure patterns. Their slide-in approach to creating and viewing records fit certain scenarios better than ours.
We adopted that approach and brought it into the shared Figma libraries and guidelines. The common system could incorporate a better solution that already existed elsewhere.
My contribution focused on defining workflow patterns and representing them in the system. In one real-estate engagement, I worked with three teammates; we divided the pattern work and iterated together.
Equipment inspection
In progress- Assigned to
- AMA. Morgan
- Due date
- Oct 14
- Location
- North site
Inspect equipment and note any follow-up work before the next site visit.
From a useful example to a shared pattern
- 01
Recognize a better fit
Another team's record workflow worked better for a particular scenario.
- 02
Make it part of the library
We adopted the pattern in the shared Figma library and usage guidelines.
- 03
Give other teams a starting point
The approach became available for reuse in applicable projects.
03 / Make it shared
The library was one part.
Adoption was the other.
We built component libraries with guidance for the patterns we defined together. I also created a layout starter for designers working in different problem spaces.
I worked with frontend developers to understand feasibility. They implemented the code.
The libraries were generally adopted across the projects I worked on. More established teams found adaptation harder, so collaboration remained part of the work.
Define the recurring decision
Give designers a shared way to think about workflow and layout choices.
Put it into something usable
Figma components, guidelines and a layout starter made the definitions available in design work.
Let other work improve it
A shared system could adopt an approach another team had already developed.