1. + Ken Guzik Product / Interaction Designer User Experience Manager

2. + About User Experience Lead User Experience Manager Software Architect System architecture Engineering org Building creative teams Creating standards Setting UE priorities Evangelize UE Interaction design User research Look and feel

3. + Timeline Much of who we are now depends on where we’ve been…

4. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware Where I’ve Been

5. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware UI Frameworks & Applications for Xerox Viewpoint Xerox Notable Events During This Time ‣ IBM PC AT Introduced ‣ Apple Macintosh Introduced ‣ Windows 1 Introduced Xerox What I Learned ‣ Value of Consistency ‣ Importance of Work Flow ‣ Importance of User Models ‣ Challenge of Mimicking the Real World ‣ The Risks and Rewards of Abstraction

6. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware UI Frameworks & Applications for Go PenPoint Go Corp Go Corporation What I Learned ‣ Adapting What I Learned at Xerox to a new Platform ‣ Different Physical Interaction Models ‣ Designing for Mobile Devices

7. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware Lexicus Longhand Lexicus What I Learned ‣ Weaving New UI Models into Existing Systems

8. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware NIST Grant - All Digital HDTV Broadcast Studio What I Learned ‣ Being Productive in a Pure Research Environment ‣ Managing Across Large, Mostly Remote Teams Sun Microsystems

9. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware G-Force eLearn Central What I Learned ‣ The Challenge of Single Page Web Applications ‣ The Pitfalls of Following UI Trends ‣ The Risk of the Bleeding Edge G Force G-Force Systems

10. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware Blue Martini Analysis Center Blue Martini Blue Martini Software What I Learned ‣ Managing Large Applications Teams ‣ The Value of Selling Ideas ‣ Differences Between Technical and Consumer Applications

11. + Timeline Xerox Go Corp Lexicus Sun Microsystems G Force Blue Martini VMware VMware vSphere, View, Server, Go, WaveMaker What I Learned ‣ Creating and Growing Creative Teams ‣ Design and Evolution of Enterprise Applications ‣ Nuances of Designing for Consumers ‣ Importance of Independent Thinking VMware

12. + User Experience User experience is the totality of a user’s feelings about the products they use for entertainment or to accomplish tasks Ease to use Easy to learn Appropriateness of functionality Integration into the user’s environment Enjoyment of use Ways in which they make the user’s life easier

13. + Great User Experience Great user experience is about how the product “feels” when used

14. + Bad User Experience

15. +  User Centered Design (UCD)  Put users at the forefront of all design activities How Does Great Design Happen?  What are their problems?  Product requirements  Use cases  Who are the users?  Personas  Ethnographic studies  Contextual inquiry studies  Define the user experience  User models  Work flows  Information architecture  Refine the designs  User test  Prototypes  User test (again)  What is the technology?  Limitations / constraints

16. + Evolution of Design Creation of VMware vSphere VMware started with a vision to create a hands-off data center using virtualization Users were conservative and risk averse IT administrators To our users, virtualization was complex, mysterious and scary Simply providing great technology wouldn’t cut it The product had to “feel” simple and non-threatening

17. + Evolution of Design How could VMware bring virtualization to the enterprise? Focus on the user experience as a primary goal Make the user experience simple, familiar and approachable Remove the “mystique” of virtualization Make the most complex operations ridiculously simple Instill a culture of great UE across the company Hire a dedicated UX design lead (Ken)

18. + Initial Concepts Single Pane of Glass As Familiar and Comfortable UI as Possible (Windows Explorer) Well Known UI Models VMware VirtualCenter Concept Model

19. + Initial Concepts Alternate VirtualCenter Concept Model Separate Navigation From Views Less Familiar to Windows Users Well Known UI Models Multiple Windows for Increased Visibility Rejected

20. + 1.0 Design Very limited functionality VM management and Host/VM monitoring only Simple wizard based VM deploy Drag and drop VM Migration Not much else

21. + 2.0 Design Full datacenter automation High availability Host load balancing (DRS) Fault tolerance Scale out to 1000s of VMs Full host, VM, network and storage configuration

22. + 3.0 Design Continuing to build out functionality Policy based automation High level intelligent monitoring Scale out to 100Ks of VMs Integration with other mgmt UIs

23. + What happened to the small user? As the product scaled out, care was taken to ensure things worked on a small scale But… Complexity creeps in, and the usability for the small datacenter suffers Time to rethink the small users’ needs Better understanding of use cases lets us consider a different product that addresses their needs

24. + Downsize & Simplify Conceptual single host UI model Supports only the most valuable use cases Fully automated with minimal user interaction Focus on small business needs

25. + Focus on Tasks Cloud based management of local datacenter Primarily task and wizard based UI Integrated with community for automated recommendations Designed for the small business use cases Go.vmware.com

26. + More on VMware vSphere Ken Guzik’s portfolio page http://kenguzik.net/portfolio/vmware/vsphere Case study of the evolution from vSphere 1.0 to 2.0 User-Centered Design Stories, Real-World UCD Case Studies Case 12 – User Centered Design for Middleware Publisher: http://www.elsevierdirect.com/product.jsp?isbn=9780123706089http://www.elsevierdirect.com/product.jsp?isbn=9780123706089 Chapter: http://tinyurl.com/bghzy7lhttp://tinyurl.com/bghzy7l VMware vSphere product page http://www.vmware.com/products/vsphere/overview.html Video tour of vSphere 4.0 http://searchvmware.techtarget.com/video/A-tour-of-VMware-vSphere-4

27. + Evolution of Design Know what need the product fulfills Understand the product vision and growth path Know the technology Know the users Who are they? What do they need the software for? How will the product fit into their world? What do they love? What do they fear? Verify everything through research For vSphere, we performed: 5 contextual inquiries 35 user studies 6 months of design partner reviews Countless heuristic evaluations

28. + Evolution of Design Creation of VMware vSphere VMware started with a vision to create a hands-off data center using virtualization Users were conservative and risk averse IT administrators To our users, virtualization was complex, mysterious and scary Simply providing great technology wouldn’t cut it The product had to “feel” simple and non-threatening

29. + Evolution of Design How to bring virtualization to the enterprise? Focus on the user experience as a primary goal Make the user experience simple, familiar and approachable Remove the “mystique” of virtualization Make the most complex operations ridiculously simple Instill a culture of great UE across the company Hire Ken

30. + Initial Concepts Single Pane of Glass As Familiar and Comfortable UI as Possible Conventional UI Models VMware VirtualCenter Concept Model

31. + Initial Concepts Single Pane of Glass Simple Windows Explorer Model Familiar Tree Organization Conventional Top-Level Navigation

32. + 1.0 Design Very limited functionality VM management and Host/VM monitoring only Simple wizard based VM deploy Drag and drop VM Migration Not much else

33. + 2.0 Design Full datacenter automation High availability Host load balancing (DRS) Fault tolerance Scale out to 1000s of VMs Full host, VM, network and storage configuration

34. + 3.0 Design Continuing to build out functionality Policy based automation High level intelligent monitoring Scale out to 100Ks of VMs Integration with other mgmt UIs

35. + What happened to the small user? As the product scaled out, care is taken to ensure things worked on a small scale But… Complexity creeps in, and the usability for the small datacenter suffers Time to rethink the small users’ needs Better understanding of use cases lets us consider a different product that addresses their needs

36. + Downsize & Simplify Conceptual single host UI model Supports only the most valuable use cases Fully automated with minimal user interaction

37. + Focus on Tasks Cloud based management of local datacenter Primarily task and wizard based UI Integrated with community for automated recommendations Designed for the small business use cases Go.vmware.com

38. + Questions? VMware product line spans ~ 60 products Every product design has a story Every product had unique challenges Feel free to ask me!

39. Thanks

40. +

41. + Bad User Experience Bad user experience results when a product fails to help users accomplish their goals

42. + Designing a User Experience Accurate Product Requirements DNA of good UX design Understand the Target Audience Deomgraphics Know how the tools will be used

43. + UE @ VMware Creation of VMware vSphere VMware started with a vision to create a hands- off data center using virtualization Needed to sell into conservative and risk averse IT shops Virtualization was complex, mysterious and scary Simply providing great technology wouldn’t cut it

44. + UE @ VMware How to bring virtualization to the enterprise? Make the user experience simple, non- threatening, and approachable. Remove the mystique of virtualization Make user experience a focus for the whole company Hire Ken

45. + Design Fro m humble beginnings… Several simple models were proposed UI models needed to be familiar and common Conventional approaches would aid adoption UI needed to be immediately usable by anyone

46. + Design Single Pane of Glass Basic Windows Explorer Model Familiar Tree Organization

47. + Design Multiple Windows for Increased Visibility Separate Navigation From Views

48. + Design Tested the idea with early design partners Single application window was overwhelming favorite Made the application seem simpler Immediately understood how to navigate the application

49. + Design

50. + Evolving to 1.0 Testing the application Internally With design partners Polishing the interface Apply graphic design Catchy icons Clean look and feel

51. + 1.0