Cisco Blogs


Cisco Blog > Inside Cisco IT

Cisco IT’s User Experience Playbook: Content, Search, and Collaboration

Have you or one of your co-workers ever said “I can’t find my stuff!”? We’ve heard it a lot. Chapter 3 of Cisco IT’s User Experience (UX) Playbook is dedicated to never having to hear “I can’t find my stuff” again. 

Read More »

Tags: , , , , , , , ,

Cisco IT’s User Experience Playbook: Deliver a Consistent, Unified Experience

In my last blog, I introduced Cisco IT’s Playbook for Ensuring a Pervasive User Experience. We consider user experience (UX) a strategic priority that requires cultural change. The playbook is our guide for ensuring that this priority becomes part of our DNA. Each chapter of the playbook lays out ways that we can improve UX, and make it a pervasive, positive experience for users across the company.
Read More »

Tags: , , , ,

Some tuning on Cisco.com search

We’ve done some fine-tuning on the search on Cisco.com:

  • It should feel faster, especially after the first search you do
  • Results should be even more relevant
  • Popular features like the “information box” for key queries remain intact

Let us know how it’s working for you!

vni-search

 

Tags: , ,

Cisco IT’s Playbook for Ensuring a Pervasive User Experience

User experience (UX) is a strategic priority at Cisco IT. In fact, improving user experience is incorporated into our IT Vision, Strategy, and Execution statement. When we talk about user experience, we raise the importance of better UX design, a better user interface, and the ability to make it pervasive. But, what we are really trying to establish is a cultural change as to how we approach this strategic priority. That is the bottom line. How can we make it part of our DNA and embed it in our operating model? Read More »

Tags: , , , , ,

Project Squared: You Asked, We Listened

When we launched Project Squared in November of 2014, one of the things that was really important to us was to listen to our customers, and to use the things we heard to adjust the experience. We established several “listening posts” – ways for us to get feedback. Analytics and metrics were one way. Another way was a feedback capability right within the application. We encouraged our users to use the feedback feature to report problems, but to also make feature requests or generally tell us what they think.

Within a few weeks of launch, we already started to see some trends in the feedback we were receiving. The number one requested feature that we got – by a long shot – was the ability to leave a 1-1 room. For the engineering team, this was an unexpected request. Why do users want to leave a 1-1 room? After all, if a 1-1 room has no activity, it will downwards in the room list and you won’t see it anymore. So, what is the issue? Read More »

Tags: , , , , , ,