Teach Your Software Developers This Ideation Design Process

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    Teach Your Software Developers This Ideation Design Process - Presentation 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

    + JeromeRJeromeR, 2 years ago

    custom

    1069 views, 1 favs, 0 embeds more stats

    A method we worked out to involve software develope more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1069
      • 1069 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories