15. A framework for how architects
can think about user experience
New Perspective
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. Implicit
Personas Purpose Prototype
“I use a similar application at home, and that works”
“Should I have read the manual?”
“The performance of this application sucks!”
20. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
21. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
“I don’t think it installed properly…”
“Err.. How long did you guys spend developing this?”
“Excuse me! I have a suggestion…”
22. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
23. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
41. Sally – “Road Warrior”
38, Married
2 Children
5 years of computer experience
Mostly Windows/Office, experienced with
PowerPoint
Has between 10 and 20 clients – mix of
small and medium businesses
Relies on laptop and mobile phone device
Implicit > Personas
42. Sally – “Road Warrior”
Needs from your application:
“Keep me connected to customer data
regardless of my location”
Implicit > Personas
44. Derek – “Call Center
Operator”
25, Single
9 years of computer experience
3 years of which in a call center
PDA/gadget junkie – “lifehacker”
Relies on call center application
Gets bonus if exceeds monthly target
call quota
Implicit > Personas
45. Derek – “Call Center
Operator”
Needs from your application:
“I want the application to decrease my time per call”
Implicit > Personas
47. Jim – “Executive”
57, Married
4 Children, all left home
Very limited computer experience
Brenda (his admin) used to print all his
Email until very recently
Likes to show off his Blackberry on the
golf course
Implicit > Personas
48. Jim – “Executive”
Needs from your application:
“I want the high level, abstract view of my customers”
Implicit > Personas
49. Conversations
“For Sally, a Web Interface may make
sense. But Peter has a lot of keyboard
shortcuts we need to implement.”
Implicit > Personas
50. Conversations
“Jim will have access to a printer via his
admin, but Sally works on the road, so
may need another option for printing”
Implicit > Personas
51. Conversations
“For Jim, red/white buttons may work,
but we should check that this is the case
for Derek in our offshore call center”
Implicit > Personas
52. Takeaways
Use 3 – 7 personas as the first
step of designing any user
experience
Use personas to help resolve
arguments in the development team
Look at the personas that Microsoft
uses (Persona Lifecycle)
Implicit > Personas
Source: Persona Lifecycle [Pruitt, Adlin] Morgan Kaufmann
53. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
66. Implicit > Purpose
Takeaways
Don’t confuse tasks and goals when
working on use cases
Focus on the goal of your application,
and apply context at each step
Look into the Office UI licensing for
using the ribbon in applications
67. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
77. Implicit > Prototype
Paper
Wizard of Oz
Many different ways of prototyping
PowerPoint
Card sorting
Visio
Flash
More Information: Effective Prototyping [Arnowitz, Arent, Berger] Morgan Kaufmann
78. Implicit > Prototype
Often static, one-way presentations
(shown only to management)
Few re-usable design assets
Looks different to what gets delivered
79. Implicit > Prototype
High Fidelity Prototype
“Polished” look and feel
Great for management
Too high fidelity for users
Low Fidelity Prototype
“Sketch” look and feel
Great for user feedback
Don’t show management
Source: Paper Prototyping / Neilsen Norman
80. Implicit > Prototype
High Fidelity Style
Control Base
Low Fidelity
Style
Source: Paper Prototyping / Neilsen Norman
83. Implicit > Prototype
Takeaways
Software Architects don’t do enough
prototyping
Try to obtain re-usable design assets
(not necessarily code assets)
Switch between low and high fidelity
to target the correct users
84. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
85. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
105. Interface > Platform
Windows Presentation Smart Client with Windows Presentation Microsoft Office
Foundation Client ClickOnce Deployment Foundation XBAP SharePoint Web Part
Windows Vista Gadget PowerShell CmdLet InfoPath Media Center Add In
Windows Live Messenger Command Line Microsoft Office Add In Media Player Add in
Add In Application
Windows Live Messenger ASP.NET Microsoft Office COM Add XBOX/XNA Application
Activity Window In
Windows Forms ASP.NET Mobile Microsoft Office Business Windows Mobile Pocket
Application Application Outlook Application
Windows Desktop Search ASP.NET AJAX Microsoft Office Smart Ink Enabled Tablet
Add In Docs Application
Windows Forms via Internet Explorer Add In Microsoft Office VBA Windows Mobile 5.0
Terminal Services Application
System Tray Applet Silverlight Microsoft Office VSTO Add Windows Mobile 5.0
In Smartphone Application
(We actually think it’s nearer to 50, but we ran out of time)
109. Interface > Platform
Takeaways
“Gut Feel” may work technically, but
often is not optimal
Pressure vendors to create more
guidance for selecting a UI
If you have different visualization
ideas, let me know
110. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
129. Interface > Productivity
Takeaways
Often the most productive user
experiences are not the best looking
Map the productivity curve to
personas when designing interfaces
Look at existing experiences to see if
there is an extensibility option
130. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
145. Interface > Performance
Takeaways
How many “milliseconds”
conversations focus on engineering
Consider skewing performance
conversations around expectations
Use AJAX to optimize for scenarios
of good user expectations
146. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
147. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
156. Infrastructure > Proven
RITE
Rapid Iterative Testing and Evaluation
Willing user
Etc.
Modify [4]
Modify [2]
Test
Test
Feedback
Feedback
Feedback
Feedback
Test
Test
Modify [3]
Modify [1]
158. Infrastructure > Proven
Takeaways
Trust takes time. Don’t risk this by
releasing a buggy v1.0 for time’s
sake
Installation, exception handling and
undo are all parts of the experience
Implement the RITE methodology to
get accurate feedback from testing
159. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
162. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT
Prototyping
Development
IT
of Services
IT
UI is created
User / BA
User Testing
Project Complete
164. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT
Prototyping
Development
IT
of Services
IT
UI is created
UI Designer
User Testing
UI Polished User / BA
Project Complete
166. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT + Designer + User / BA
Prototyping
Development
Development IT
Designer + User / BA
of Services
of UX
UI and Services
IT + Designer
Integrated
User Testing User / BA
Project Complete
168. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT + Designer + User / BA
Prototyping
Development
Development IT
Designer + User / BA
of Services
of UX
UI and Services
IT + Designer
Integrated
User Testing User / BA
Project Complete
171. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT + Designer + User / BA
Prototyping
Development
Development IT
Designer + User / BA
of Services
of UX
UI and Services
IT + Designer
Integrated
User Testing User / BA
Project Complete
172. Infrastructure > People
Project Starts!
Use cases created IT + User / BA
IT + Designer + User / BA
Prototyping
Development
Development IT
Designer + User / BA
of Services
of UX
UI and Services
IT + Designer
Integrated
User Testing User / BA
Project Complete
173. Infrastructure > People
Designer Developer
XAML
Challenges:
• How much code level understanding will designers require?
• Who owns check-in of XAML artifacts?
• Will we require an “interface stub” for communication?
174. Infrastructure > People
Takeaways
Great SDLC more than often leads
to Great User Experience
Understand what types of designers
your SDLC model will support
Support interaction between
developers and designers
175. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
182. Infrastructure > Proactive
Rating scale in the application
Remote troubleshooting
Effective status updates
183. Infrastructure > Proactive
Takeaways
Think how users are going to provide
1 3 11 proactive feedback into the SDLC
2 Figure out a strategy for when things
go wrong
Provide status – both good and bad
– to users where possible
184. Implicit
Personas Purpose Prototype
Interface
Platform Productivity Performanc
e
Infrastructure
Proven People Proactive
185. Overall Takeaways
Implicit
Be Implicit by defining personas, purpose
Personas Purpose Prototype
and prototyping before you start coding
Interface Define the Interface – think about how the
platform choice, productivity, and
performance will affect the user Performanc
Platform Productivity
e
Support an Infrastructure that enables
Infrastructure
proven, proactive applications designed by
a team that understands user experience
Proven People Proactive