Designing an experience that supports users’ motivations and goals is challenging enough, but it is far from all that is required in order to deliver a successful solution. The greater challenge for UX practitioners lies in positioning your work and your deliverables so that the organisation is able to implement the bulk of the recommendations and designs contained therein. Dumping a design and running, is not good enough. We must design solutions that will be implemented. The key is designing with consideration of the business drivers and the motivations of technologists responsible for bringing your designs to fruition. Actively engaging technologists and business owners throughout the work turns your deliverables from “Recommendations” to “Specifications”. In this talk, Matt Morphett of Amberdew presents a method for mapping out the specific motivations of three competing forces within your IT-based project and working with them as you undertake user experience design. Paper based tools are manipulated by representatives from each area in a group environment to negotiate the tradeoffs and compromises inherent in complex IT projects. The tools support structured decision making at all levels from the strategic intent of the project to “Can we update those drop-downs without a screen refresh?” The result is a usable and engaging design that meets business needs and will not be shouted down by cries of “Not technically possible”. Electronic copies of the tools and templates are linked on the final slide.

1. Designs That Ship
New tools for ensuring your UX work
reaches its audience
UX Australia 2010
Melbourne, Australia
Matt Morphett
twitter: @mattmorphett

2. Aim:
Design - Delivery Parity

3. Aim:
Design - Delivery Parity
What they designed... ...what shipped

4. Aim:
Design - Delivery Parity
?
What they designed... ...what shipped

5. Aim:
Design - Delivery Parity
?
What they designed... ...what shipped

6. Aim:
Design - Delivery Parity
?
What they designed... ...what shipped

7. “Real artists ship...”
Steve Jobs

8. “Real artists ship...”
Steve Jobs
...what was designed

9. The 180 page
survival trophy

10. The 180 page
survival trophy
...I made it through this nightmare UX
gig and all I got was this lousy document

11. Designing is
the easy part...
...getting them to implement your
recommendations is the challenge

12. Why don’t they implement?
•Because they don’t understand you
•Because they don’t believe you
•Because it is hard
•Because you didn’t tell them to...

13. Why don’t they implement?
•Because they don’t understand you
•Because they don’t believe you
•Because it is hard
•Because you didn’t tell them to...
Because your method wasn’t as
usable as your designs

14. The Dynamic

15. The Dynamic
Business
Users Architecture

16. The Dynamic
Business
Users Architecture

17. The Dynamic Motivations
Profitability
Service delivery quality
Reportability
Auditability
Process compliance
Business Practice standardisation
Regulatory compliance
Cleanliness of data
Users Architecture

18. The Dynamic Motivations
Profitability
Service delivery quality
Reportability
Auditability
Process compliance
Business Practice standardisation
Regulatory compliance
Cleanliness of data
Motivations
Implementability
Performance
Availability
Robustness
Scalability
Security
Maintainability
Extensibility
Accessibility
Users Architecture

19. The Dynamic Motivations
Profitability
Service delivery quality
Reportability
Auditability
Process compliance
Business Practice standardisation
Regulatory compliance
Cleanliness of data
Motivations Motivations
Specific User Goals Implementability
-------------------------- Performance
Intuitivity Availability
Learnability Robustness
Ease of use Scalability
Reduced typing / rekeying Security
Guidance not constraint Maintainability
Responsiveness Extensibility
Efficient operation Accessibility
Operational flexibility
Users Architecture

20. Example
Motivations
Profitability
Service delivery quality
Reportability
Auditability
Process compliance
Practice standardisation
Business Regulatory compliance
Cleanliness of data
Address
Street address 135 Bridge Rd
Suburb Bowen Hills
Postcode 4056

21. Example
Address
Unit number
Street number 135
Building name
Street name Bridge
Street type Road Motivations
Implementability
Suburb Bowen Hills Performance
Availability
Postcode 4056
Robustness
Scalability
State / Territory Queensland Security
Country Australia Maintainability
Extensibility
Unique postal identifier Q453687D Accessibility
Architecture

22. Example
Motivations
Specific User Goals
--------------------------
Intuitivity
Learnability
Ease of use
Reduced typing / rekeying
Guidance not constraint
Responsiveness
Efficient operation
Operational flexibility
Users

23. Example
Address 135 Bridge Rd., Bowen Hills 4056
Motivations
Specific User Goals
--------------------------
Intuitivity
Learnability
Ease of use
Reduced typing / rekeying
Guidance not constraint
Responsiveness
Efficient operation
Operational flexibility
Users

24. The key is...
•Understanding and working with
this dynamic
•Ensuring that the other parties do
too

25. What’s the Approach?
Deep breath... engage

26. Steps to engage
•Identify (ask: “Who could undo a
decision”)
•Acknowledge
•Engage

27. Research Stage
Explicitly work
through the
motivations
collaboratively

28. Research Stage

29. Design Stage
The “weekly focus” posters

30. Design Stage
Props
Architecture
Users
Business

31. Design Stage
Props
Architecture
Users
Business
Rami Banna - Cochlear (user fairy)

32. Design Stage
Props
Architecture
Users
8
Business
Rami Banna - Cochlear (user fairy)

33. Testing
Business
Users Architecture

34. Detailed Design
Notifications Pending (4) Active Cases (12)
Vs Business
Notifications Pending Active Cases
Users Architecture

35. Detailed Design
Notifications Pending (4) Active Cases (12)
Vs Business
Notifications Pending Active Cases
Less coding
Users Architecture

36. Detailed Design
Notifications Pending (4) Active Cases (12)
Vs Business
Notifications Pending Active Cases
See workload
without
navigating Less coding
Users Architecture

37. Product Strategy
Business
Users Architecture

38. Product Strategy
Business
Less buttons,
more modality
Users Architecture

39. Product Strategy
Business
Less buttons,
more modality
A button for
most functions
Users Architecture

40. Product Strategy
Business
One extra
button to
reduce
modality Less buttons,
more modality
A button for
most functions
Users Architecture

41. Deliverables
Make your specification
highly usable

42. Lollybag
Download at...
www.amberdew.com.au

43. Lollybag
Download at...
www.amberdew.com.au
Thanks!
Twitter.com/mattmorphett