9. Identifying the need
You need a designer to create products that are usable
& desirable, help achieve user’s tasks & goals, add
polish and quality, ensuring an cohesive fit of features
to user contexts & perceptions.
It’s7more7than7skinning7widgets7or7slicing7icons.7
A7helluva7lot7more!
11. we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship trust%the%process
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
we gotta ship
18. Rise of the hybrids!
Blending skills and backgrounds...
19. Hiring a Designer
Who 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
20. Hiring a designer
How do you find the right one?
• The Portfolio vs The Resume
• A Design Interview
• The Design Exercise
• Venues: BayCHI, IxDA, AIGA, IDSA, UPA
21. 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
29. 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 machines
Citrix Product Design Process
30. Product Design Process
Discovery
Conceptual Detailed " Implementation
Post Ship
Design
Design
1
2
3
4
5
Citrix Product Design Process
31. Product Design Process
Discovery
Conceptual Detailed " Implementation
Post Ship
Design
Design
1
2
3
4
5
Citrix Product Design Process
32. Product Design Process
Discovery
Conceptual Detailed " Implementation/Close Down
Post Ship
Design
Design
1
2
3
4
5
Citrix Product Design Process
33. Product Design Process
Discovery
Conceptual Detailed " Implementation/Close Down
Post Ship
Design
Design
1
2
3
4
5
Citrix Product Design Process
34. Main design deliverables ke
Ta
ote!
Design Brief statement7of7the7problem,7scope,7goals,7criteria
n
Personas archetype7proOiles7of7primary7users
Scenarios contextual7stories7of7usage
Task Flows diagrams7of7tasks,7branches,7and7paths
Architecture overview7map7of7content7&7actions
Wireframes schematic7structural7drawings7of7UI7layout
Comps hiROidelity7visual7renderings7of7UI
Prototypes behavioral7renderings7of7the7UI
Specs detailed7recipe7for7construction7of7approved7design
40. Important to remember...
There is no perfect design. Everything is subject to
compromise, trade-offs, constraints, etc.
Good design takes time. Just like good code, there’s
iteration and reflection and shouldn’t be rushed.
41. 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!
46. Last bit of advice
Tradeoffs are essential to a working relationship. All about
managing expectations, assumptions, and dependencies.
The designer is your ally in delivering a great product.
