It’s a great time to be at Cisco. Earlier this week, Susie Wee, chief technology and experience officer (CTEO) for the Collaboration Technology Group, unveiled the “collaboration geeks”: the engineers, researchers and designers behind the technology, to a handful of press and analysts. We were excited (and a bit nervous!) to share how Cisco is approaching user experience (UE) and design. These changes aren’t just happening from the product side, but are also evolving our internal thinking about being more user-centric across the organization.
Have you ever heard of a CTEO? Probably not, because it is a new role that we created to address the importance of coupling user experience and technology. As CTEO, Susie is responsible for driving innovation and experience design in Cisco’s collaboration products and software services. The first step involved in making a cultural change is how we approach product design. But what does this mean for her team? Below is a short excerpt from our User Experience Day event.
At Cisco, we’re dedicated to changing the way we work, live, play and learn. We’re always looking to break down barriers among staff; one example is how we’re approaching user experience design. Our team is looking into principles, guidelines, and archetypes that represent an organizational-wide approach to user experience design. The design team really lays the foundation for growing the influence and scope of all the UE specialists into strategic conversations where user experience can impact what we design and how we design. We coined the term “XQ” as the eXperience Quotient of the organization. XQ is a tool and metric that we developed to measure our customer’s experience with our products and our user experience-centric development process.
Another example is how our engineers are thinking about their products from the user perspective and pulling in the user experience designers and my team (user experience researchers) as well. To showcase this at the event, engineers brought in a number of XQ demos to show this thinking firsthand: Read More »
While enterprise social networking has been covered extensively in the media and by IT analyst firms, one of the least discussed aspects of the topic has been the issue of design and the potential impact of design on employee adoption of such tools and applications. At the June Enterprise 2.0 Boston conference, I presented a session, “Design Considerations For Enterprise Social Networks: Identity, Graphs, Streams & Social Objects”, in hopes of drawing attention to the issue and to spark conversation around design practices. The session did not focus on any particular user interface (UI) technique or product implementation (e.g., e-mail, community site, social collaboration platform, etc.). Instead, the information was presented at a holistic and inter-disciplinary level, covering a collection of related issues:
Even as the latest breach headline fades away, we all know there is another waiting in the wings (read Part I of my blog). How can organizations protect themselves? There is no panacea for securing a payment environment, and implementing advanced technology alone will not make an organization compliant with the Payment Card Industry (PCI) Data Security Standard (DSS). The PCI DSS provides a solid foundation for a security strategy that covers payment and other types of data, but overall security does not begin and end with PCI compliance. Therefore, an organization’s security strategy should employ best practices and an architecture that will not only facilitate PCI compliance, but also help secure the cardholder environment, prevent identity theft, reliably protect brand image and assets, mitigate financial risk, and provide a secure foundation for new business services.
I realized a few years ago that all Data Center challenges can be solved with the sufficient application of money.
Need more computing capability? Buy new hardware. Struggling with hot spots? Purchase supplemental cooling infrastructure. Don’t have enough physical space? Pay to expand the Data Center or lease additional space.
More performance means greater cost, though. Some energy saving technologies buck that trend when compared to conventional facilities, but generally the more capability you want from a Data Center the more it will cost to build and operate.