Product and Engineering teams lacked a cohesive scalable style guide and component library, negatively impacting sprint efficacy.
Reduce duplicate work and make valuable sprint time more productive.
Author initial company style guide at speed and scale.
Make application deployment process more efficient, productive and humane.
Design team attrition over burdened remaining staff, making it difficult to focus on important deliverables. Lack of empathy between stakeholders created communication friction, which eroded trust and compromised important projects. Delivering the style guide was occurring along more important 'keeping the lights on' projects, so we were building the plane as we were flying it.
Interviewed all senior stakeholders to discover performance gaps and optimization opportunities.
Summarized findings into project scope definitions.
Organized timely project milestones, review sessions and design cycles.
The other designer on my team and I met with the product manager once a week to discuss progress on the guide, validating previous iterations and goals, and aligning on next steps.
We continued meeting to assess variable goals and to prevent scope creep.
After lengthy stakeholder interviews to determine product and engineering goals, the design team planned a styleguide execution strategy and timeline.
We went carefully week by week to ensure each section of the guide was accurate and thorough.
After months of careful planning and execution the final Shopping.com design spec document was completed.
We achieved overall site UX consistency, scalability and recovered valuable engineering resources which were allocated to more important features.
Reduction in engineering UI bugs
Cut length of iterative design cycles
Sprint efficiency gains
Engineering budget cost savings