
At a glance
ROLE
Toolkit owner
COLLABORATORS
Lead, product designers, and engineers
SCOPE
Zero-to-one design toolkit
Focus
Architecture, templates, prototyping & engineering alignment
SUMMARY
Creating a scalable design toolkit that helps designers work faster, prototype confidently, and stay aligned with engineering.
I built the Microsoft Planner design library from the ground up, transforming fragmented components and inconsistent workflows into a shared system of reusable components and templates.
Built on Microsoft Fluent 2, the toolkit supported Planner's unique product needs while creating a more consistent and efficient experience for the design team.

The challenge
Before the toolkit, designers were creating components independently, resulting in duplicated patterns, inconsistent behaviors, and unnecessary rework.
Engineering faced similar challenges, often interpreting inconsistencies during handoff.

The Approach
I approached the project in three phases, prioritizing the patterns that would make the biggest difference in everyday workflows.
01. Audit
02. Build
03. Deliver
Designing a Scalable Architecture
Using Fluent 2 as a foundation, I built a component architecture that balanced Microsoft's shared standards with Planner-specific functionality.
Smaller components were combined into configurable compound components and complete templates, allowing updates to propagate throughout the system.

Built for Interaction

I built interaction states directly into components, including hover, focus, selected, disabled, and error states where applicable.
This allowed designers to create realistic prototypes without rebuilding common interactions, while keeping component behavior more consistent with engineering expectations.
The Grid View
Grid View was one of the most complex templates in the library.
It needed to accommodate different task configurations, interaction states, responsive behavior, and experiences for basic and premium users.
Rather than building separate layouts for every scenario, I structured the template around reusable components and configurable properties.
This gave designers the flexibility to create different experiences while maintaining a consistent foundation.
Design Meets Engineering
Throughout the project, I worked closely with engineering to account for implementation constraints such as spacing, alignment, component sizing, and responsive behavior.
By considering these requirements during component construction, I helped reduce ambiguity during handoff and established a more reliable shared foundation.
The Outcome




