Svcc12 designparternship

370 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
370
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Svcc12 designparternship

  1. 1. Design PartnershipUday GajendarPrincipal Product DesignerCitrix | Santa ClaraSVCC / 10.6.12
  2. 2. “ I"asked"Paul"if"he"would"come"up"with"a" few"options,"and"he"said,"‘No,"I"will"solve" your"problem"for"you"and"you"will"pay" me."You"don’t"have"to"use"the"solution."If" you"want"options"go"talk"to"other"people. ” Steve%Jobs
  3. 3. PartnershipCollaborationCooperation Teamwork Empathy
  4. 4. Typical scenario: Sound familiar?
  5. 5. Typical scenario: Sound familiar?
  6. 6. Can7we7get7someone7to make7this7pretty?
  7. 7. Today’s Agenda Intro Identifying,the,need Hiring,a,designer Core,design,skills General,design,process Major,deliverables Related,issues... Last,bit,of,advice
  8. 8. Identifying the needYou need a designer to create products that are usable& desirable, help achieve user’s tasks & goals, addpolish and quality, ensuring an cohesive fit of featuresto user contexts & perceptions.It’s7more7than7skinning7widgets7or7slicing7icons.7A7helluva7lot7more!
  9. 9. VSDesigners7aren’t7there7to7make7it7“pretty”. They7want7to7create7a7great7product.
  10. 10. we gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta ship trust%the%processwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta shipwe gotta ship
  11. 11. fear • doubt • uncertainty • anxiety • disbelief • angst
  12. 12. Design,skills,,process,, collaboration
  13. 13. %“What%I%do%have%are%a%very%particular%set%of%skills;%skills%I%have%acquired%over%a%very%long%career.%Skills%that%make%me%a%nightmare%for%people%like%you.”
  14. 14. T ake note!Core design skillsWhat to look for...•7Empathy •7Sketching •7Communicates7well•7Imagination •7Writing •7Debates7on7the7merits•7Iterative •7Wires7/7Comps •7Values7criticism•7Holistic •7Prototyping •7Adaptable7to7tech •7Considers7all7sides
  15. 15. Core design skillsWhat to look for... provocateur"•"therapist"•"advocate"•"visualizer
  16. 16. Less unicorn... ...More Swiss army knife
  17. 17. Rise of the hybrids!Blending skills and backgrounds...
  18. 18. Hiring a DesignerWho do you need? What roles to play?•7Visual7Designer crafts7the7pixel7details:7type/color/grids/icons•7UI/Interaction7Designer drives7the7taskOlow,7layout,7behavior•7Information7Architect organizes7content,7draws7diagrams•7Prototyper vividly7animates7digital7behavior•7Researcher observes7users7and7afOirms7usability•7Writer prepares7the7content7voice,7tone,7diction
  19. 19. Hiring a designerHow do you find the right one?• The Portfolio vs The Resume• A Design Interview• The Design Exercise• Venues: BayCHI, IxDA, AIGA, IDSA, UPA
  20. 20. Typical backgrounds• Fine and Liberal Arts• Graphic / Industrial / Interaction Design• Human-Computer Interaction (HCI)• Human Factors / Usability / Cog Psych• Library Science / Information Studies• Architecture / Interior Design
  21. 21. BayCHIIxDA SFUPABehanceDribbbleCore77 / CoroflotBoxesAndArrowsJohnny Holland
  22. 22. Design-oriented portfoliosWorking with a designer !
  23. 23. HCI-oriented portfoliosWorking with a designer !
  24. 24. Understand T ake note! Evaluate Verify Visualize Assess ModelingDesign process
  25. 25. Product Design ProcessDiscovery Conceptual Detailed " Implementation Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  26. 26. Product Design ProcessDiscovery Conceptual Detailed " Implementation Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  27. 27. DesignBriefCitrix Product Design Process
  28. 28. Goals & Aspirations Kim “Customer sat is •  Providing quality service in a what matters timely manner. most to me.” •  Keep work and home life separate Frustrations Personal •  Constantly logging into computer •  Fairly patient when which takes a long time dealing with customers •  Dealing with printer issues •  Does not try to fix computer problems, quicker to have family Workstyle •  Works an 8 hour shift in the office friend resolve it •  Usually does not travel •  People are more important to her than machinesCitrix Product Design Process
  29. 29. Product Design ProcessDiscovery Conceptual Detailed " Implementation Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  30. 30. Product Design ProcessDiscovery Conceptual Detailed " Implementation Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  31. 31. Product Design ProcessDiscovery Conceptual Detailed " Implementation/Close Down Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  32. 32. Product Design ProcessDiscovery Conceptual Detailed " Implementation/Close Down Post Ship Design Design 1 2 3 4 5Citrix Product Design Process
  33. 33. Main design deliverables ke Ta ote!Design Brief statement7of7the7problem,7scope,7goals,7criteria nPersonas archetype7proOiles7of7primary7usersScenarios contextual7stories7of7usageTask Flows diagrams7of7tasks,7branches,7and7pathsArchitecture overview7map7of7content7&7actionsWireframes schematic7structural7drawings7of7UI7layoutComps hiROidelity7visual7renderings7of7UIPrototypes behavioral7renderings7of7the7UISpecs detailed7recipe7for7construction7of7approved7design
  34. 34. Teamwork/collaborationIt"takes"mutual"respect"and"trust."Value"each"other’s"expertise"and"professional"judgment."Designers"are"fair"to"challenge"the"tech"constraints,"and"Devs"are"fair"to"challenge"the"design"rationale.Designers7aren’t7there7to7make7it7“pretty”.They7want7to7create7a7great7product.
  35. 35. T ake note!Design collaboration
  36. 36. Design collaboration
  37. 37. Rapid prototyping = essential
  38. 38. from XenClient Tech Preview, May 2010Hi-res prototype = the spec!
  39. 39. Important to remember...There is no perfect design. Everything is subject tocompromise, trade-offs, constraints, etc.Good design takes time. Just like good code, there’siteration and reflection and shouldn’t be rushed.
  40. 40. Strong but fair points• ASAP is not a schedule. It’s a freakout.• No doc’d requirements or functional specs? No design!• Need a DACI model with clear roles defined.• Designers don’t have to react to every opinion.• PMs (and devs) are not art directors. Period.• Want user feedback? Great! Just fit it in the schedule.• Email is not the record. Get a trackable online place.• Sketches and wires are not the spec.• Design is a full-body commitment. Get ready!
  41. 41. Why,should,you,care,about, all,this?
  42. 42. Creating UX value for everyone
  43. 43. Brands Products Services Platforms Systems“Improving%the%human%condition.”
  44. 44. soulbeauty “I%want%to%put%a%ding%in%the%universe.” integrity
  45. 45. Last bit of adviceTradeoffs are essential to a working relationship. All aboutmanaging expectations, assumptions, and dependencies.The designer is your ally in delivering a great product.
  46. 46. PartnershipCollaborationCooperation Teamwork Empathy
  47. 47. Contact infoUday,Gajendaremail udanium@gmail.comtwitter, @udaniumweb www.udanium.comblog www.ghostinthepixel.comlinkedin www.linkedin.com/in/udanium

×