Nailing it down
        Specifying experience design so it can be built




        UX Australia
        Joe Sokohl
      ...
A bit about me




                          2

Friday, August 27, 2010
A bit about me




             http://www.uxaustralia.com.au/conference-2010/design-thinking-is-this-our-ticket-to-the-bi...
My Aussie props




                          3

Friday, August 27, 2010
My Aussie props




                          3

Friday, August 27, 2010
My Aussie props




                          3

Friday, August 27, 2010
Agenda


  Defining the damn things

  What’s the problem

  What are some solutions

  What’s your story




        ...
Agenda


  Defining the damn things

  What’s the problem

  What are some solutions

  What’s your story




        ...
So what’s the big deal, anyway?

   Determining what the problem is




                                     5

Friday, Au...
Who this talk applies to


  Agencies

  Independent UXers

  Highly regulated areas: healthcare, government,
     mili...
Who this talk might not apply to


  Heterogenous teams

  UXers who also do front-end development

  Co-located, nimbl...
Who this talk might not apply to


  Heterogenous teams

  UXers who also do front-end development

  Co-located, nimbl...
Typical documentation approaches

   Research artifacts such as competitive reviews, heuristic analysis, mental models/
 ...
Typical documentation approaches

   Research artifacts such as competitive reviews, heuristic analysis, mental models/
 ...
FiveDs Summary

            Discover                 Design                   Define                   Develop            ...
FiveDs Summary

            Discover                 Design                   Define                   Develop            ...
What’s the difference between reqs & specs?

   Requirements

        Requirements cannot be “gathered”

        Requir...
What’s the difference between reqs & specs?

   Requirements

        Requirements cannot be “gathered”

        Requir...
What’s the difference between reqs & specs?

   Requirements

        Requirements cannot be “gathered”

        Requir...
What’s the difference between reqs & specs?

   Requirements

        Requirements cannot be “gathered”

        Requir...
Where do they break? Why




                             12

Friday, August 27, 2010
Where do they break? Why

              Spec need




                             Team proximity or regulatory need (or b...
Where do they break? Why

              Spec need




                             Team proximity or regulatory need (or b...
Requirements masquerading as specifications


  Traditional approach
   1.1.1. The system shall allow the teacher to clic...
A bridge to nowhere?




                          14

Friday, August 27, 2010
“ is not it at all,
That
That is not what I meant, at
all. . . . . .

                          ”



                     ...
Big, grandiose statement




                          Anything that specifies user
                          behavior or ...
Solutions

   More detail at the right time




                                   17

Friday, August 27, 2010
Requirement: Turn indicators




             1.3.2.5a: The system shall
             include the ability for the
        ...
Requirement: Turn indicators




                                 18

Friday, August 27, 2010
Sketches provide documentation




                                   19

Friday, August 27, 2010
Sketches provide documentation




   The genius in our styling department is that they not only have a great feel for
   ...
Detailed sketches




                          20

Friday, August 27, 2010
Embeded specifications




                           21

Friday, August 27, 2010
The finished product




                          22

Friday, August 27, 2010
Prototypes help, too




                          23

Friday, August 27, 2010
What Are Some Solutions

   Frameworks

   Style guides and pattern libraries

   Accurate diagrams and traceable notes...
What Are Some Solutions

   Frameworks

   Style guides and pattern libraries

   Accurate diagrams and traceable notes...
Embedding Specs with Wireframes or Prototypes




                                                  25

Friday, August 27,...
Embedding Specs with Wireframes or Prototypes




                                                  26

Friday, August 27,...
But...but...what about Agile?
                                           27

Friday, August 27, 2010
Sometimes specs fall into the wrong hands




                                              28

Friday, August 27, 2010
Special order 191




                          29

Friday, August 27, 2010
Special order 191



           Major Taylor will proceed to Leesburg, Va., and arrange for transportation of the sick and...
http://www.civilwar.org/battlefields/antietam/maps/antietammap3.html
                                                     ...
“ In preparing for battle, I have always
        found that plans are useless...




                                     ...
“ In preparing for battle, I have always
        found that plans are useless...




                          ...but plan...
So...




                          32

Friday, August 27, 2010
So...




     A specification is




                          32

Friday, August 27, 2010
So...




     A specification is
          The body of information that conveys sufficient
                detail to com...
So...




     A specification is
          The body of information that conveys sufficient
                detail to com...
What’s your story?




                          33

Friday, August 27, 2010
Many thanks!




      Joe Sokohl
      Joe@RegularJoeConsulting.com
      1.804.873.6964
      @mojoguzzi

Friday, August...
Upcoming SlideShare
Loading in...5
×

Nailing it down: Specifying experience design so it can be built

2,730

Published on



So you’ve done ethnographic user research. You’ve also analyzed log files. You’ve interviewed help desk and customer service folks, You’ve had heaps of meetings with stakeholders. And you’ve nailed a sense of the user, so you’ve got some great personas. You even held some design sketching sessions.

NOW what? While Dan Brown, Ginny Redish, and others have codified the early phases of experience documentation, there’s a disjunction that often happens when business analysts write requirements documents or developers and product managers write user stories. Despite the best personas and user/task grids and wireframes, other documents override the best UX intentions. We need to get back in the game and stay there in some role as products are developed. Design doesn’t end with design; development is the fruition of design.

Let’s discuss moving from design to development, with a concentration on specifying experience design artifacts for those who have to glean meaning from our work: developers, business stakeholders, and other teams. How does experience design specify its output in a way that developers can code and business can understand how the UX relates to business requirements? And are specifications the definition of design?

After quickly reviewing typical deliverables such as use cases, annotated wireframes, requirements specifications, and user stories, we’ll discuss where we should create, where we should influence, and where we should keep the hell away.

Published in: Design

Transcript of "Nailing it down: Specifying experience design so it can be built"

  1. 1. Nailing it down Specifying experience design so it can be built UX Australia Joe Sokohl @mojoguzzi CONFIDENTIALITY The concepts and methodologies contained herein are proprietary to Regular Joe Consulting LLC. Duplication, reproduction or disclosure of information is this document without the express written permission of Regular Joe Consulting is prohibited. Enjoy the work. We hope you find it useful. Friday, August 27, 2010
  2. 2. A bit about me 2 Friday, August 27, 2010
  3. 3. A bit about me http://www.uxaustralia.com.au/conference-2010/design-thinking-is-this-our-ticket-to-the-big-table 2 Friday, August 27, 2010
  4. 4. My Aussie props 3 Friday, August 27, 2010
  5. 5. My Aussie props 3 Friday, August 27, 2010
  6. 6. My Aussie props 3 Friday, August 27, 2010
  7. 7. Agenda Defining the damn things What’s the problem What are some solutions What’s your story 4 Friday, August 27, 2010
  8. 8. Agenda Defining the damn things What’s the problem What are some solutions What’s your story 4 Friday, August 27, 2010
  9. 9. So what’s the big deal, anyway? Determining what the problem is 5 Friday, August 27, 2010
  10. 10. Who this talk applies to Agencies Independent UXers Highly regulated areas: healthcare, government, military Anyone working with distributed teams (including cross-border, multiple time zone teams) 6 Friday, August 27, 2010
  11. 11. Who this talk might not apply to Heterogenous teams UXers who also do front-end development Co-located, nimble teams who don’t have a need to retrace steps 7 Friday, August 27, 2010
  12. 12. Who this talk might not apply to Heterogenous teams UXers who also do front-end development Co-located, nimble teams who don’t have a need to retrace steps Then again.... 7 Friday, August 27, 2010
  13. 13. Typical documentation approaches  Research artifacts such as competitive reviews, heuristic analysis, mental models/ affinity diagrams, and personas  User/task matrixes  Annotated wireframes  Concept models  Card sorts  And on and on and on... 8 Friday, August 27, 2010
  14. 14. Typical documentation approaches  Research artifacts such as competitive reviews, heuristic analysis, mental models/ affinity diagrams, and personas  User/task matrixes  Annotated wireframes  Concept models  Card sorts  And on and on and on... 8 Friday, August 27, 2010
  15. 15. FiveDs Summary Discover Design Define Develop Deliver Define project goals, Further define a Refine design details, Build and integrate Complete the business reqs, set of requirements create final design and front-end and commercialization of and initial scope. and create systems obtain signoff. back-end systems. the product and UX models Activities Activities Activities Activities Activities • Define goals • Brainstorming • Merge visual and • Image and page • Acceptance testing functional design creation • Key success factors • Scenario building • System and • Final content • Content integration knowledge transfer • VOC workshops • Wireframes • Test scenarios • Coding • Product deployment • EOC interviews • Visual direction • Object analysis, • Unit testing • Marketing campaign • B/U/S requirements • HL Info Architecture modeling, design • System staging in • Site analysis • HL Sys Architecture • Database analysis QA environment • Audience analysis • Define technology and design • Incremental QA and • Initial use cases • Design testing on multiple • Business processes documentation platforms 08/27/10 Friday, August 27, 2010
  16. 16. FiveDs Summary Discover Design Define Develop Deliver Define project goals, Further define a Refine design details, Build and integrate Complete the business reqs, set of requirements create final design and front-end and commercialization of and initial scope. and create systems obtain signoff. back-end systems. the product and UX models Activities Activities Activities Activities Activities • Define goals • Brainstorming • Merge visual and • Image and page • Acceptance testing functional design creation • Key success factors • Scenario building • System and • Final content • Content integration knowledge transfer • VOC workshops • Wireframes • Test scenarios • Coding • Product deployment • EOC interviews • Visual direction • Object analysis, • Unit testing • Marketing campaign • B/U/S requirements • HL Info Architecture modeling, design • System staging in • Site analysis • HL Sys Architecture • Database analysis QA environment • Audience analysis • Define technology and design • Incremental QA and • Initial use cases • Design testing on multiple • Business processes documentation platforms 08/27/10 Friday, August 27, 2010
  17. 17. What’s the difference between reqs & specs?  Requirements  Requirements cannot be “gathered”  Requirements are not features  Requirements are not specifications  Specifications  “Effective documentation combines text and images to describe the anatomy and physiology of a product.” 11 Friday, August 27, 2010
  18. 18. What’s the difference between reqs & specs?  Requirements  Requirements cannot be “gathered”  Requirements are not features  Requirements are not specifications  Specifications  “Effective documentation combines text and images to describe the anatomy and physiology of a product.”  My definition? A specification is 11 Friday, August 27, 2010
  19. 19. What’s the difference between reqs & specs?  Requirements  Requirements cannot be “gathered”  Requirements are not features  Requirements are not specifications  Specifications  “Effective documentation combines text and images to describe the anatomy and physiology of a product.”  My definition? A specification is  The body of information that conveys sufficient detail to communicate that which can be coded. 11 Friday, August 27, 2010
  20. 20. What’s the difference between reqs & specs?  Requirements  Requirements cannot be “gathered”  Requirements are not features  Requirements are not specifications  Specifications  “Effective documentation combines text and images to describe the anatomy and physiology of a product.”  My definition? A specification is  The body of information that conveys sufficient detail to communicate that which can be coded.  Just enough detail to enable the developer to understand the UX designer’s intent. 11 Friday, August 27, 2010
  21. 21. Where do they break? Why 12 Friday, August 27, 2010
  22. 22. Where do they break? Why Spec need Team proximity or regulatory need (or both) 12 Friday, August 27, 2010
  23. 23. Where do they break? Why Spec need Team proximity or regulatory need (or both) 12 Friday, August 27, 2010
  24. 24. Requirements masquerading as specifications Traditional approach  1.1.1. The system shall allow the teacher to click a control which displays the first answer in the lesson. NOTE: Subsequent answers can be accessed by individual controls after the first answer is displayed. The “Show Answers” and “Show First Answer” controls shall be displayed outside of lessons in a toolbar in the Learning Environment. Answers should be displayed to both the teacher and student. User story approach As a clinician and/or front desk assistant, I need to record the writer, provider(s), assistant(s), as well as the date and time of entry for every clinical note, so that I can maintain accurate clinical records. 13 Friday, August 27, 2010
  25. 25. A bridge to nowhere? 14 Friday, August 27, 2010
  26. 26. “ is not it at all, That That is not what I meant, at all. . . . . . ” http://static.guim.co.uk/sys-images/Guardian/Pix/pictures/2009/3/30/1238371335802/TS-Eliot-003.jpg 15 Friday, August 27, 2010
  27. 27. Big, grandiose statement Anything that specifies user behavior or activities that affect users belongs to the user experience team 16 Friday, August 27, 2010
  28. 28. Solutions More detail at the right time 17 Friday, August 27, 2010
  29. 29. Requirement: Turn indicators 1.3.2.5a: The system shall include the ability for the operator to indicate a changed direction of travel 18 Friday, August 27, 2010
  30. 30. Requirement: Turn indicators 18 Friday, August 27, 2010
  31. 31. Sketches provide documentation 19 Friday, August 27, 2010
  32. 32. Sketches provide documentation The genius in our styling department is that they not only have a great feel for design, but also for the fact that the design needs to function properly on a motorcycle. That melding of functionality and styling is what makes our motorcycles very, very special 19 Friday, August 27, 2010
  33. 33. Detailed sketches 20 Friday, August 27, 2010
  34. 34. Embeded specifications 21 Friday, August 27, 2010
  35. 35. The finished product 22 Friday, August 27, 2010
  36. 36. Prototypes help, too 23 Friday, August 27, 2010
  37. 37. What Are Some Solutions  Frameworks  Style guides and pattern libraries  Accurate diagrams and traceable notes  A proverbial seat at the table. 24 Friday, August 27, 2010
  38. 38. What Are Some Solutions  Frameworks  Style guides and pattern libraries  Accurate diagrams and traceable notes  A proverbial seat at the table. 24 Friday, August 27, 2010
  39. 39. Embedding Specs with Wireframes or Prototypes 25 Friday, August 27, 2010
  40. 40. Embedding Specs with Wireframes or Prototypes 26 Friday, August 27, 2010
  41. 41. But...but...what about Agile? 27 Friday, August 27, 2010
  42. 42. Sometimes specs fall into the wrong hands 28 Friday, August 27, 2010
  43. 43. Special order 191 29 Friday, August 27, 2010
  44. 44. Special order 191 Major Taylor will proceed to Leesburg, Va., and arrange for transportation of the sick and those unable to walk to Winchester, securing the transportation of the country for this purpose. The route between this and Culpeper Court-House east of the mountains being unsafe will no longer be traveled. Those on the way to this army already across the river will move up promptly; all others will proceed to Winchester collectively and under command of officers, at which point, being the general depot of this army, its movements will be known and instructions given by commanding officer regulating further movements. III. The army will resume its march tomorrow, taking the Hagerstown road. General Jackson's command will form the advance, and, after passing Middletown, with such portion as he may select, take the route toward Sharpsburg, cross the Potomac at the most convenient point, and by Friday morning take possession of the Baltimore and Ohio Railroad, capture such of them as may be at Martinsburg, and intercept such as may attempt to escape from Harper's Ferry. IV. General Longstreet's command will pursue the main road as far as Boonsborough, where it will halt, with reserve, supply, and baggage trains of the army. V.General McLaws, with his own division and that of General R. H. Anderson, will follow General Longstreet. On reaching Middletown will take the route to Harper's Ferry, and by Friday morning possess himself of the Maryland Heights and endeavor to capture the enemy at Harper's Ferry and vicinity. 29 Friday, August 27, 2010
  45. 45. http://www.civilwar.org/battlefields/antietam/maps/antietammap3.html 30 Friday, August 27, 2010
  46. 46. “ In preparing for battle, I have always found that plans are useless... 31 Friday, August 27, 2010
  47. 47. “ In preparing for battle, I have always found that plans are useless... ...but planning is indispensable. ” —Dwight Eisenhower 31 Friday, August 27, 2010
  48. 48. So... 32 Friday, August 27, 2010
  49. 49. So... A specification is 32 Friday, August 27, 2010
  50. 50. So... A specification is  The body of information that conveys sufficient detail to communicate that which can be coded. 32 Friday, August 27, 2010
  51. 51. So... A specification is  The body of information that conveys sufficient detail to communicate that which can be coded.  Just enough detail to enable the developer to understand the UX designer’s intent. 32 Friday, August 27, 2010
  52. 52. What’s your story? 33 Friday, August 27, 2010
  53. 53. Many thanks! Joe Sokohl Joe@RegularJoeConsulting.com 1.804.873.6964 @mojoguzzi Friday, August 27, 2010
  1. Gostou de algum slide específico?

    Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

×