Cisco · Learning Platform
UX Design Lead on a focused audit and strategy engagement for CiscoU — identifying gaps across Cisco.com, Cisco U., and the Cisco Learning Network, and shaping a prioritized roadmap the team could execute ahead of launch.
Cisco was preparing to launch Cisco U, but Cisco.com wasn't built to support it.
Course information was scattered across free and paid catalogs with no single source of truth, and users had no clear path from a search query to the right training content.
Without a coherent journey into Cisco U, the launch risked confusing customers and undercutting the new platform before it had a chance to land.
I audited traffic sources and user flows, then mapped an ideal site structure and navigation model connecting Cisco.com to Cisco U.
That work included site-wide navigation changes, in-context cross-linking from product and support pages, and a prioritized roadmap the team could act on immediately ahead of launch.
This engagement needed to clarify how users find and commit to Cisco training, connect Cisco.com to the new Cisco U platform, and give stakeholders a clear, prioritized path to ship before launch.
Give users one coherent path from search intent to the right training or certification content.
Bridge product and support surfaces to the new learning platform where intent was highest.
Replace scattered catalogs with a clear structure teams could navigate and maintain.
Leave stakeholders with prioritized recommendations they could execute before launch.
Chapter 01
Users searching for Cisco training had no consistent way to find, evaluate, or commit to a course.
Certification and training content lived disconnected from the rest of Cisco.com, with no cross-links from product or support pages where user intent was often highest. Auditing traffic sources and flows made the friction impossible to ignore.
[Short explanation of the finding and why it mattered.]
[Short explanation of the finding and why it mattered.]
[Short explanation of the finding and why it mattered.]
[Short explanation of the finding and why it mattered.]
[Placeholder — secondary discovery narrative. Use this block for observations, journey friction, or a finding that benefits from sitting beside a taller visual.]
Chapter 02
We didn't just redesign the interface. We changed the workflow around it.
Before
[Short explanation of the previous state — friction, workarounds, risk.]
After
[Short explanation of the redesigned state — clarity, speed, control.]
[Short explanation of the design change and why it mattered.]
[Short explanation of the design change and why it mattered.]
[Short explanation of the design change and why it mattered.]
[Short explanation of the design change and why it mattered.]
Chapter 03
[Placeholder — intro paragraph framing the shipped experience and how the pieces fit together.]
[Short explanation of this part of the solution.]
[Short explanation of this part of the solution.]
[Short explanation of this part of the solution.]
[Short explanation of this part of the solution.]
Chapter 04
What changed because this work existed?
[Placeholder — what changed for the business, revenue, risk, or operational scale.]
[Placeholder — what changed for operators, customers, or day-to-day workflows.]
Chapter 05
The most important design problem wasn't the interface. It was the system underneath it.
[Short reflection that shows senior judgment — tradeoffs, constraints, or a principle you carry forward.]
[Short reflection that shows senior judgment — tradeoffs, constraints, or a principle you carry forward.]
[Short reflection that shows senior judgment — tradeoffs, constraints, or a principle you carry forward.]
