Ellipse Design System
A system created to support consistency, scale, and everyday product work.
Role
Senior Product Designer, Design Systems
Timeline
1 year
Industry
Automotive / Global Brand
Team Size
2 designers
Scope
Design system strategy, foundations, components, documentation, governance, and rollout
Context
From scattered references to a system teams could rely on
Ellipse began by consolidating fragmented documentation, inconsistent libraries, and competing sources of truth into a single, authoritative system for Toyota’s digital platform. The goal was not just consistency, but trust, giving designers and developers a foundation they could confidently use and build on together.
Approach
A system built to operate at full maturity
Brand guidance was translated into usable digital foundations, components were normalized around real product needs, and behavior, constraints, and ownership were documented clearly. The name Ellipse reflects its role as a stable center, something teams could orient around as work evolved and scaled.
Adoption
Turning a system into a shared way of working
As Ellipse took hold, it became a coordination point across teams. Designers and developers aligned on patterns, reduced duplication, and shared decisions across silos. Regular updates, clear ownership, and in-office moments around system changes reinforced the system as part of everyday work.
Outcome
Internal order reflecting outward
Ellipse matured from scattered inputs into a shared platform and practice. Teams moved faster, spoke the same language, and relied on the system as a stable base for ongoing product development.
Let’s talk about what’s next at your org.
Download Resume
LinkedIn Profile
Ellipse Design System
A system created to support consistency, scale, and everyday product work.
Role
Senior Product Designer, Design Systems
Timeline
1 year
Industry
Automotive / Global Brand
Team Size
2 designers
Scope
Design system strategy, foundations, components, documentation, governance, and rollout
Context
From scattered references to a system teams could rely on
Ellipse began by consolidating fragmented documentation, inconsistent libraries, and competing sources of truth into a single, authoritative system for Toyota’s digital platform. The goal was not just consistency, but trust, giving designers and developers a foundation they could confidently use and build on together.
Approach
A system built to operate at full maturity
Brand guidance was translated into usable digital foundations, components were normalized around real product needs, and behavior, constraints, and ownership were documented clearly. The name Ellipse reflects its role as a stable center, something teams could orient around as work evolved and scaled.
Adoption
Turning a system into a shared way of working
As Ellipse took hold, it became a coordination point across teams. Designers and developers aligned on patterns, reduced duplication, and shared decisions across silos. Regular updates, clear ownership, and in-office moments around system changes reinforced the system as part of everyday work.
Outcome
Internal order reflecting outward
Ellipse matured from scattered inputs into a shared platform and practice. Teams moved faster, spoke the same language, and relied on the system as a stable base for ongoing product development.
Let’s talk about what’s next at your org.
Ellipse Design System
A system created to support consistency, scale, and everyday product work.
Role
Senior Product Designer, Design Systems
Timeline
1 year
Industry
Automotive / Global Brand
Team Size
2 designers
Scope
Design system strategy, foundations, components, documentation, governance, and rollout
Context
From scattered references to a system teams could rely on
Ellipse began by consolidating fragmented documentation, inconsistent libraries, and competing sources of truth into a single, authoritative system for Toyota’s digital platform. The goal was not just consistency, but trust, giving designers and developers a foundation they could confidently use and build on together.
Approach
A system built to operate at full maturity
Brand guidance was translated into usable digital foundations, components were normalized around real product needs, and behavior, constraints, and ownership were documented clearly. The name Ellipse reflects its role as a stable center, something teams could orient around as work evolved and scaled.
Adoption
Turning a system into a shared way of working
As Ellipse took hold, it became a coordination point across teams. Designers and developers aligned on patterns, reduced duplication, and shared decisions across silos. Regular updates, clear ownership, and in-office moments around system changes reinforced the system as part of everyday work.
Outcome
Internal order reflecting outward
Ellipse matured from scattered inputs into a shared platform and practice. Teams moved faster, spoke the same language, and relied on the system as a stable base for ongoing product development.
Let’s talk about what’s next at your org.
Ellipse Design System
A system created to support consistency, scale, and everyday product work.
Role
Senior Product Designer, Design Systems
Timeline
1 year
Industry
Automotive / Global Brand
Team Size
2 designers
Scope
Design system strategy, foundations, components, documentation, governance, and rollout
Context
From scattered references to a system teams could rely on
Ellipse began by consolidating fragmented documentation, inconsistent libraries, and competing sources of truth into a single, authoritative system for Toyota’s digital platform. The goal was not just consistency, but trust, giving designers and developers a foundation they could confidently use and build on together.
Approach
A system built to operate at full maturity
Brand guidance was translated into usable digital foundations, components were normalized around real product needs, and behavior, constraints, and ownership were documented clearly. The name Ellipse reflects its role as a stable center, something teams could orient around as work evolved and scaled.
Adoption
Turning a system into a shared way of working
As Ellipse took hold, it became a coordination point across teams. Designers and developers aligned on patterns, reduced duplication, and shared decisions across silos. Regular updates, clear ownership, and in-office moments around system changes reinforced the system as part of everyday work.
Outcome
Internal order reflecting outward
Ellipse matured from scattered inputs into a shared platform and practice. Teams moved faster, spoke the same language, and relied on the system as a stable base for ongoing product development.