• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Design for Developers:  Nashville Software School (Summary)

Design for Developers: Nashville Software School (Summary)



summary slides from the hands-on design workshop

summary slides from the hands-on design workshop



Total Views
Views on SlideShare
Embed Views



1 Embed 4

https://twitter.com 4



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • For today our definition is going to focus on ‘making things better for people’. You can probably think of examples you have already used today. Coffee Makers. Watches. Phones. Pens & Pencils (don’t have to use quills anymore). Some of you may have used a medical device such as a blood glucose meter. All of these things, in different ways, have been designed and re-designed to make things better for people. Good Design is based on tried and true, demonstrated design principles. Such as Functional.
  • We are just building paper prototypes todayYou can build a story board using sticky notes as frames; kind of like a comic book. Draw the UI in the frames showing a progression: first this, then that, then that.[page down]
  • Or sketch out a web page on the flip charts. Here is an example of a website with drop-owns and list boxes. Obviously NOT going for a nice, complete, polished design. Think BRAINSTORM. The purpose is to communicate your idea. There are more stickies, paper, markers, stickers for you to use. Plan on spending about a half hour – until 2pm on your prototype. Then spend another 15 minutes practicing your pitch. Plan to spend 5-7 minutes pitching your idea to Julie. You should include a little bit about your persona so Julie will know who you are designing for.
  • Stage two – when have better idea of contents/functions, more experience and focus
  • JakobNeilsen: useit.comA List Apart: http://alistapart.com/Fast Co Design: http://www.fastcodesign.com/Smashing Magazine: http://www.smashingmagazine.com/UX Booth: http://www.uxbooth.com/UX Pond Acute Search: http://www.uxpond.com/UX Stack Exchange: http://ux.stackexchange.com/UI Patterns: http://ui-patterns.com/Patterny: http://patternry.com/WebDev Refinery: http://webdevrefinery.com/Twitter Tim Brown ‏ @tceb62UX Archive ‏ @uxarchiveCrystal Ehrlich - UX ‏ @cbehrlichNielsen Norman Group ‏ @NNgroupPeter Morville ‏ @morvilleNick Finck ‏ @nickfAlan Cooper ‏ @MrAlanCooperxDA ‏ @IxDAFred Beecher ‏ @fred_beecherWebdesigner Depot ‏ @DesignerDepotAza Raskin ‏ @azaUX Yoda ‏ @UXYodaJared M. Spool ‏ @jmspoolPatrick Neeman ‏ @usabilitycountsChristopher Fahey ‏ @chrisfaheyJeffrey Zeldman ‏  @zeldman  

Design for Developers:  Nashville Software School (Summary) Design for Developers: Nashville Software School (Summary) Presentation Transcript