Teach Your Software Developers This Ideation Design Process

  • 2,108 views
Uploaded on

A method we worked out to involve software developers in the design process. These slides supported a speech. Not all the delivered content is in the slides.

A method we worked out to involve software developers in the design process. These slides supported a speech. Not all the delivered content is in the slides.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,108
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Teach your software developers this Ideation-Design process to reduce your usability work downstream Do you ever feel your usability work involves _ a mop and bucket?
  • 2. 6 slides in 30 minutes , so please refer to the handouts on the Proceedings CD +
  • 3.  
  • 4. With no designers on my Dev teams, I decided to help our software developers to do better
    • I borrowed from Bill Buxton, GK VanPatter, and Edward De Bono
    • I had help from my dedicated colleagues and boss (Director of Product Management)
    preferences
  • 5. With help, everyone can work outside their comfort zone for a while Ideation Judgement Experience Thinking
  • 6. Sketching helps people to ideate, so they can saturate the design space with ideas
    • Tell me: what do YOU think makes a good sketch?
  • 7. Each person does 5 + sketches , or you may as well go home
    • Ideas: cheap, disposable, easy
    • Saturate the design space
      • Resketch: borrow + borrow
    • When someone has fewer than 5 sketches
      • What Bill Buxton does
      • Be assertive: ask for 5
  • 8. Sketching occurs in a process that iteratively but separately uses the team’s creative & analytical strength
    • Tell me: which hat is what?
  • 9. Problems and solutions
    • Take time for white hat, work, before everything
    • Set four 4-hr meetings
      • Add’l members add ½ hr
    • Sketching
      • 5 in advance: mandatory
      • 5 in advance: done alone
      • The sticking point
      • Facilitator mustn’t sketch
      • Guidelines in the handout
    • Limit black-hat remarks
    • Stalemate? Rate the: cost, confidence in the estimate, code stability, code maintainability, easy to learn, easy to explain, hard to forget
    • Got standards? Use those instead
    • To teach this, use mixed modes, ½ day
  • 10. Your questions