UX and Software Engineering in Harmony

916 views
776 views

Published on

UX and Engineering in Harmony (describing our Way of Working and ensuring coordinated teamwork across disciplines)

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
916
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • UX and Engineering in Harmony! (describing our Way of Working and ensuring coordinated teamwork across disciplines)
  • Not just about using a product. There is a whole story that influences the UX.
  • User – Own experience / expectationOutside World too – Competition, Press, Community
  • Should all be on the same side but it often doesn’t feel that way!
  • School/UniversityColleagues / PeersBooksWeb sitesBlogsPresentationsConferencesWord of mouth
  • Monolithic processesand disciplines usually overlap and continue to expand until bloated and unusable!Lean practices can detail the fundamental content and simply refer out to the body of knowledge elsewhere.
  • We need the software people to appreciate more of the skills of the UX professionals.Many companies / projects do not have these skills on board
  • This glove was worn by Neil Armstrong on the moon. The items in brackets were things to be carried out by Buzz Aldrin.Surgeryteams in hospital reduced death by surgical errors by 47% by using a simple19 question checklist that had questions such as “What is your name?”
  • This is the fundamental items defined for software development to help the practicesthat may be authored by many different people to compose together neatly when combined.
  • UX and Software Engineering in Harmony

    1. 1. UX and Engineering in Harmony!<br />Brian Kerr<br />bkerr@ivarjacobson.com<br />
    2. 2. What influences the User Experience?<br />Good Experience =&gt; Loyalty<br />
    3. 3. Who influences the User Experience?<br />Mgmt<br />Analyst<br />Developer<br />Prod/Proj Mgmt<br />User<br />Marketing<br />Architect<br />Company<br />Web Site<br />Tester<br />GraphicDesigner<br />CopyWriter<br />IXD<br />IA<br />
    4. 4. Isn’t it obvious how to play together?<br />Business<br />Technology<br />UX People<br />
    5. 5. How do people gain knowledge?<br />Often contradictory or in violent agreement!<br />Hard to find the real nuggets of information<br />Difficult for ‘mortals’ to put into practice<br />
    6. 6. Wouldn’t it be good if…<br />Brief, simple and understandable guidance<br />See the big picture, and the details in context<br />Multi-discipline<br />See just the parts you need to see<br />Info at your fingertips<br />Paper, electronic, where ever you need it…<br />Access to deeper knowledge<br />Examples, books, online resources, people<br />Dynamic yet stable<br />Essential foundations should be long-lived, details change and evolve<br />Enabled for growth<br />Eco-system of information / community<br />Encourages creativity, without dictating specific techniques<br />
    7. 7. A bit of organisation<br />The “Essentials” are in the cards<br />Things To Do<br />Competency / Skill set<br />Things To Produce<br />Key Concepts<br />
    8. 8. Card metaphor to focus on the ‘Essentials’<br />The “Essentials” are in the cards<br />Things To Do<br />Competency / Skill set<br />Things To Produce<br />Key Concepts<br />
    9. 9. Benefits from describing the ‘Essentials’<br />Beginner<br />Intermediate<br />Expert<br />Teams<br />Teams of mixed skills<br />People appreciate other disciplines<br />People without formal training can make a sensible start<br />Awareness of competencies/skills missing on the team<br />Give structure to the knowledge within a discipline<br />Bring disciplines together<br />
    10. 10. How many Developers in the world? How many UX professionals?<br />
    11. 11. Even experts can do with guidance!<br />
    12. 12. A basic foundation to build upon<br />$<br />!<br />!<br />!<br />Team<br />Specified System<br />Backlog<br />Defect<br />Opportunity<br />Implemented System<br />Change<br />Task<br />Project<br />Executable System<br />Risk<br />Test<br />Way of Working<br />
    13. 13. Practices separate concerns<br />$<br />TechnicalPractices<br />Iterative<br />Use Case<br />Architecture<br />Component<br />Product<br />Cross-Cutting Practices<br />Modeling<br />Process<br />Team<br />
    14. 14. Concentrating on these first<br />User Research<br />User Interface Design<br />Graphic Design<br />Branding<br />Competitive Analysis<br />SEO / Findability<br />Accessibility<br />Industrial Design / Service Design<br />And more interesting creative ones…<br />Beginning to work on these UX practices <br />I might need some help!!!<br />
    15. 15. Connect with me @<br />bkerr@ivarjacobson.com<br />BrianKerr<br />briankerr.wordpress.com<br />

    ×