Design systems · Utrecht, Netherlands
I build design systems with rules your team can use.
I help product teams define reusable interface patterns and document how they behave. My experience includes a company-wide system at IMO Health and reviewing vendor work against United Airlines’ existing system.
Tell me about your projectI start with the patterns your product already needs.
Complex software repeats decisions across screens: selecting records, filtering a table, showing a status or handling a form error. I review those patterns in your product and look at where the design files and implementation disagree.
That review helps define the scope. Your team might need a component library, clearer usage guidance or a focused review of an existing system.
I document behavior alongside appearance.
I define the component states and usage rules that affect implementation. A table needs a clear selection model. A form needs error and disabled states. The documentation should explain how those decisions work across the product.
I work with your engineers to connect the design guidance to what they can build and maintain. I agree the component scope and documentation with your team before starting.
I have worked with both new and established systems.
At IMO Health, I worked on a company-wide design system for clinical products. At United Airlines, I reviewed a vendor interface against the Orion design system and translated findings into specific interface requirements.
The Safety Hub case study shows how that review related to usability research and the vendor's implementation work.
Read the Safety Hub case study ↗
If the immediate concern is a workflow people struggle with, a focused UX audit can help define the changes before extending the library.
I define a scope your team can maintain.
I start by reviewing the current design files and the implemented product with your team. I need to know who uses the library, which patterns are repeated and how your engineers maintain their components.
A focused engagement can cover an audit of the library, a set of component designs or usage documentation. I agree those outputs with you before starting, including who will own future changes.
I work from Utrecht with teams across Europe and North America. I keep reviews connected to the product work, so the library is assessed against the screens your team needs to deliver.
I start with the problem you need to solve.
Send me a short description of your product, where you need help and your timing. I work directly with your team from Utrecht, with remote engagements across Europe and North America.
Prefer email? hello@studiogridline.com