3
Design System Documentation Site
Cisco Systems
Muse Reference Site: +50% Sign-Ups
Empowering teams to scale with a unified source of truth.
Project Overview
The Muse Reference Site serves as the centralized hub for our design system, providing patterns, templates, guidelines, and documentation resources. It supports in creating and publishing digital experiences for Cisco.com. I led the end-to-end design as part of Cisco's Global Marketing reimagined initiative to expand the design system and provide an accessible platform for our internal team and vendors.
Team
Studio Design Team, Lead Developer, Product Mangers, Accenture UI/ Visual, Business SMEs, Stakeholders.
[Category]
Cisco Systems
[My Role]
Lead UX Designer, Product Owner
[Platform]
Responsive Design
[Timeline]
April 2021 - October 2022
Problem
Cisco's outdated Publication Hub (Pub Hub)
Pubhub (image below) didn't align with current design system that made it a problem for users to conduct their daily work.
Goal
Retire Cisco outdated 'Pub Hub' as it no longer served business needs.
Ensure that the platform is accessible so that users can publish pages effciently on Cisco.com.
Create a reference site platform that expanded on the rebranded Muse design system as part of Cisco's Reimagine initiatives.
Frustrations
Fragmented documentation and resources made it difficult for users to perform tasks efficiently.
The site’s misalignment with our design system prevented users from accessing accurate information.
Pub Hub lacked guidance on 'when' and 'how' to use components and patterns.
Process
1. User Research
Conducted user interviews to understand their pain points and needs.
Synthesized data to define user personas and prioritize MVP features.
Conducted competitive benchmarking to identify best practices for documentation sites.
1. User Research
Conducted user interviews to understand their pain points and needs.
Synthesized data to define user personas and prioritize MVP features.
Conducted competitive benchmarking to identify best practices for documentation sites.
2. Insights
Users want visuals and live examples on the site.
Users value prescriptive authoring templates and resources.
Guidelines on how components and patterns function, with clarity on what defines good versus poor implementation.
2. Insights
Users want visuals and live examples on the site.
Users value prescriptive authoring templates and resources.
Guidelines on how components and patterns function, with clarity on what defines good versus poor implementation.
Impact
93% increase in unique vistiors to the site.
50% increase in user sign-ups.
Created 6 templates and 18 pattern pages on the site for users.
Final design of Patterns and Templates pages
3. Design Solution
Conduct workshops with stakholders to prioritize features and user types.
Focus on creating template and pattern pages so that users can publish faster.
Buy-in a front-end platform that fulfills 90% of MVP requiremnts.
3. Design Solution
Conduct workshops with stakholders to prioritize features and user types.
Focus on creating template and pattern pages so that users can publish faster.
Buy-in a front-end platform that fulfills 90% of MVP requiremnts.
4. Testing & Iteration
Conducted card sorting test to identify information architecture.
Facilitated workshops to define real problems, align on users needs and business goals.
Collected feedback through usability testing to refine terminology and streamline content.
4. Testing & Iteration
Conducted card sorting test to identify information architecture.
Facilitated workshops to define real problems, align on users needs and business goals.
Collected feedback through usability testing to refine terminology and streamline content.
Final Design
Key Learnings
It takes a village
Consistent collaboration across teams ensured advocacy, consistency, and real world usage.
It takes a village
Consistent collaboration across teams ensured advocacy, consistency, and real world usage.
Testing often
Gathering user feedback often ensured quality control so that it resonated with users. Staying true to our principles.
Testing often
Gathering user feedback often ensured quality control so that it resonated with users. Staying true to our principles.
Page Structure Matters
Defining information achitecture and content hierarchy helped eliminate redundancies.
Page Structure Matters
Defining information achitecture and content hierarchy helped eliminate redundancies.
Cisco Systems
Design System Documentation Site
Muse Reference Site: +50% Sign-Ups
Empowering teams to scale with a unified source of truth.
Project Overview
The Muse Reference Site serves as the centralized hub for our design system, providing patterns, templates, guidelines, and documentation resources. It supports in creating and publishing digital experiences for Cisco.com. I led the end-to-end design as part of Cisco's Global Marketing reimagined initiative to expand the design system and provide an accessible platform for our internal team and vendors.
Team
Studio Design Team, Lead Developer, Product Mangers, Accenture UI/ Visual, Business SMEs, Stakeholders.
[My Role]
Lead UX Designer, Product Owner
[Platform]
Responsive Design
[Timeline]
April 2021 - October 2022
Learn more
Impact
93% increase in unique vistiors to the site.
50% increase in user sign-ups.
Created 6 templates and 18 pattern pages on the site for users.
Final design of Patterns and Templates pages
Problem
Cisco's outdated Publication Hub (Pub Hub)
Pubhub (image below) didn't align with current design system that made it a problem for users to conduct their daily work.
Frustrations
Fragmented documentation and resources made it difficult for users to perform tasks efficiently.
The site’s misalignment with our design system prevented users from accessing accurate information.
Pub Hub lacked guidance on 'when' and 'how' to use components and patterns.
Goal
Retire Cisco outdated 'Pub Hub' as it no longer served business needs.
Ensure that the platform is accessible so that users can publish pages effciently on Cisco.com.
Create a reference site platform that expanded on the rebranded Muse design system as part of Cisco's Reimagine initiatives.
Process
1. User Research
Conducted user interviews to understand their pain points and needs.
Synthesized data to define user personas and prioritize MVP features.
Conducted competitive benchmarking to identify best practices for documentation sites.
2. Insights
Users want visuals and live examples on the site.
Users value prescriptive authoring templates and resources.
Guidelines on how components and patterns function, with clarity on what defines good versus poor implementation.
3. Design Solution
Conduct workshops with stakholders to prioritize features and user types.
Focus on creating template and pattern pages so that users can publish faster.
Buy-in a front-end platform that fulfills 90% of MVP requiremnts.
4. Testing & Iteration
Conducted card sorting test to identify information architecture.
Facilitated workshops to define real problems, align on users needs and business goals.
Collected feedback through usability testing to refine terminology and streamline content.
Final Design
Key Learnings
It takes a village
Consistent collaboration across teams ensured advocacy, consistency, and real world usage.
Testing often
Gathering user feedback often ensured quality control so that it resonated with users. Staying true to our principles.
Page Structure Matters
Defining information achitecture and content hierarchy helped eliminate redundancies.
< Previous Project
3
Design System Documentation Site
Cisco Systems
Muse Reference Site: +50% Sign-Ups
Empowering teams to scale with a unified source of truth.
Project Overview
The Muse Reference Site serves as the centralized hub for our design system, providing patterns, templates, guidelines, and documentation resources. It supports in creating and publishing digital experiences for Cisco.com. I led the end-to-end design as part of Cisco's Global Marketing reimagined initiative to expand the design system and provide an accessible platform for our internal team and vendors.
Team
Studio Design Team, Lead Developer, Product Mangers, Accenture UI/ Visual, Business SMEs, Stakeholders.
[Category]
Cisco Systems
[My Role]
Lead UX Designer, Product Owner
[Platform]
Responsive Design
[Timeline]
April 2021 - October 2022
Final design of Patterns and Templates pages
Problem
Cisco's outdated Publication Hub (Pub Hub)
Pubhub (image below) didn't align with current design system that made it a problem for users to conduct their daily work.
Goal
Retire Cisco outdated 'Pub Hub' as it no longer served business needs.
Ensure that the platform is accessible so that users can publish pages effciently on Cisco.com.
Create a reference site platform that expanded on the rebranded Muse design system as part of Cisco's Reimagine initiatives.
Frustrations
Fragmented documentation and resources made it difficult for users to perform tasks efficiently.
The site’s misalignment with our design system prevented users from accessing accurate information.
Pub Hub lacked guidance on 'when' and 'how' to use components and patterns.
Process
1. User Research
Conducted user interviews to understand their pain points and needs.
Synthesized data to define user personas and prioritize MVP features.
Conducted competitive benchmarking to identify best practices for documentation sites.
1. User Research
Conducted user interviews to understand their pain points and needs.
Synthesized data to define user personas and prioritize MVP features.
Conducted competitive benchmarking to identify best practices for documentation sites.
2. Insights
Users want visuals and live examples on the site.
Users value prescriptive authoring templates and resources.
Guidelines on how components and patterns function, with clarity on what defines good versus poor implementation.
2. Insights
Users want visuals and live examples on the site.
Users value prescriptive authoring templates and resources.
Guidelines on how components and patterns function, with clarity on what defines good versus poor implementation.
Impact
93% increase in unique vistiors to the site.
50% increase in user sign-ups.
Created 6 templates and 18 pattern pages on the site for users.
Process
3. Design Solution
Conduct workshops with stakholders to prioritize features and user types.
Focus on creating template and pattern pages so that users can publish faster.
Buy-in a front-end platform that fulfills 90% of MVP requiremnts.
3. Design Solution
Conduct workshops with stakholders to prioritize features and user types.
Focus on creating template and pattern pages so that users can publish faster.
Buy-in a front-end platform that fulfills 90% of MVP requiremnts.
4. Testing & Iteration
Conducted card sorting test to identify information architecture.
Facilitated workshops to define real problems, align on users needs and business goals.
Collected feedback through usability testing to refine terminology and streamline content.
4. Testing & Iteration
Conducted card sorting test to identify information architecture.
Facilitated workshops to define real problems, align on users needs and business goals.
Collected feedback through usability testing to refine terminology and streamline content.
Key Learnings
It takes a village
Consistent collaboration across teams ensured advocacy, consistency, and real world usage.
It takes a village
Consistent collaboration across teams ensured advocacy, consistency, and real world usage.
Testing often
Gathering user feedback often ensured quality control so that it resonated with users. Staying true to our principles.
Testing often
Gathering user feedback often ensured quality control so that it resonated with users. Staying true to our principles.
Page Structure Matters
Defining information achitecture and content hierarchy helped eliminate redundancies.
Page Structure Matters
Defining information achitecture and content hierarchy helped eliminate redundancies.
Final Design