15. New Perspective As architects and developers, we are in a position to affect user experience
16.
17. “ Was this application really designed for me?” “ Why doesn’t this application help me get my work done?” “ If it wasn’t for this application, I’d do stuff differently”
19. Personas Purpose Prototype Ideas “ I use a similar application at home, and that works” “ Should I have read the manual?” “ The performance of this application sucks!”
21. Personas Performance Productivity Purpose Prototype Platform Interface Ideas “ Err.. How long did you guys spend developing this?” “ I don’t think it installed properly…” “ Excuse me! I have a suggestion…”
34. “ For Sally , a Web Interface may make sense. But Derek has a lot of keyboard shortcuts we need to implement.”
35. “ Jim will have access to a printer via his admin, but Sally works on the road, so may need another option”
36. “ For Jim , a red button may mean danger, but we should check for Derek in our offshore call center”
37. Takeaways Source: Persona Lifecycle [Pruitt, Adlin] Morgan Kaufmann Do you use personas today? If so, how many? (3 – 7 personas per application is recommended) How do you use the word “user”? (Think about personas to help define who you are writing the application for) Do you know how Microsoft uses personas? (Use “Persona Lifecycle” for VSTS related personas)
38.
39.
40. Create new document Type text Format the text Email to editor
41. Create new document Type text Format the text Email to editor Task Task Task Task Goal
42.
43. Create new document Type text Format the text Email to editor Task Task Task Task Filter
44. Create new document Type text Format the text Email to editor Task Task Task Task Guess the Goal
45.
46. Create new document Type text Format the text Email to editor Task Task Task Task Apply Context Apply Context Apply Context
51. Takeaways In use cases, how do you deal with tasks and goals? (Focus on the difference between the two) How do you use context in your applications? (Use context to help guide the experience) Could the Office UI be suitable for your application? (Refer to the list of ISVs supporting controls)
52.
53.
54. You want to build a house… You hire a building architect… You discuss requirements…
68. Takeaways Are you able to re-use any assets? (A prototype in XAML allows many design assets to be reused) What prototyping do you do? (Software Architects don’t do enough) What fidelity do you use? (A mix of high and low fidelity prototypes can be used for different feedback loops)
80. 32 (We actually think it’s nearer to 50, but we ran out of time) Windows Presentation Foundation Client Smart Client with ClickOnce Deployment Windows Presentation Foundation XBAP Microsoft Office SharePoint Web Part Windows Vista Gadget PowerShell CmdLet InfoPath Media Center Add In Windows Live Messenger Add In Command Line Application Microsoft Office Add In Media Player Add in Windows Live Messenger Activity Window ASP.NET Microsoft Office COM Add In XBOX/XNA Application Windows Forms Application ASP.NET Mobile Microsoft Office Business Application Windows Mobile Pocket Outlook Application Windows Desktop Search Add In ASP.NET AJAX Microsoft Office Smart Docs Ink Enabled Tablet Application Windows Forms via Terminal Services Internet Explorer Add In Microsoft Office VBA Windows Mobile 5.0 Application System Tray Applet Silverlight Microsoft Office VSTO Add In Windows Mobile 5.0 Smartphone Application
82. Application Connectivity Graphics Look and Feel Interaction Environment Installation Integration Hardware Developer IQ Persona Location Mobility Training Personalization
83.
84. Takeaways What can Microsoft do to help? (We need to create more guidance for helping abstract technology selection decisions) How do you select technology? (Gut feel may result in short term gain, but often long term pain) Would a tool like this be useful? (And if so, do you have any other ideas for visualization?)
104. Takeaways Is productivity important for different roles in your organization? (Map personas to the productivity curve) How do you measure productivity? (Often the most productive applications are not the best looking) Can existing experiences be extended? (Often extending an experience results in greater productivity)
114. Takeaways Have user’s expectations been met? (Sitting with users before a new system is deployed can help set expectations) How do you plan for performance? (Conversations around milliseconds tend to be engineering focused) What technology do you use? (AJAX can help address specific expectations that the user may have)
127. Takeaways How do you deal with installation, exception handling, and undos? (They are all part of the experience) What is your quality bar? (Trust takes time) What is your user testing strategy? (The RITE methodology can help find errors that would go otherwise undiscovered)
131. Project Starts! Project Complete Use cases created IT + User / BA Prototyping IT Development of Services IT UI is created IT User Testing User / BA
133. Project Starts! Use cases created Prototyping Development of Services UI is created IT + User / BA IT IT IT User Testing Project Complete User / BA
137. Project Starts! Project Complete Use cases created IT + User / BA Prototyping Development of Services IT UI and Services Integrated User Testing User / BA Development of UX
140. Project Starts! Project Complete Use cases created IT + User / BA Prototyping Development of Services IT UI and Services Integrated User Testing User / BA Development of UX
141. Project Starts! Project Complete Use cases created IT + User / BA Prototyping IT + Designer + User / BA Development of Services IT IT + Designer User Testing User / BA Development of UX Designer + User / BA
142.
143. Takeaways What types of designers do you need? (Recognize the different designer roles and how they can work within the SDLC) Does UX factor in to your SDLC? (Incorporating UX into the SDLC can help create a better output) Do your developers and designers talk to each other? (We need to support this)
153. 2 1 3 1 1 Takeaways What happens when things go wrong? (How does the architecture of an application handle exceptions?) How do your users provide feedback? (Proactive feedback can be very powerful input for the SDLC) Do you provide status? (Good and bad status reports can help users better understand failure)
154.
155. Overall Takeaways Define the Interface and think about how the platform choice, productivity, and performance will affect you Remember the Internals that enable proven, proactive applications designed by a team that understands user experience Realize Ideas by defining personas, purpose and prototyping