A Developers Take on Cooper         Adam Jordens          @ajordens
My Background             Technical Lead     GenoLogics Life Sciences                    Founder     AppiityTypically work...
● In software, features cost almost nothing. ● In hardware, features almost always increase costs.               FEATURE-I...
Goal Directed DesignDesign first;                    As developers, we prideprogram second                   ourselves on ...
Goal Directed DesignWhen was the last time you     Separate responsibility forread the persona involved in   design from r...
Goal Directed DesignHold designers responsible     Thinking Pointfor product quality anduser satisfaction              Who...
Goal Directed DesignUntil a persona is defined, a   Define one specific user fordeveloper will think of         your produ...
Goal Directed DesignWork in teams of two:          Were already doing it, this isdesigner and design            just a for...
Goal Directed DesignResearch                  ● Understanding business                            and user needsModelling ...
Goal Directed DesignResearch                         Modelling & RequirementsObservation, Interviews and      Personas, Sc...
Goal Directed DesignFramework Definition            Detailed DesignDefine the big picture; mast    Iterate at greater and ...
Goal Directed DesignImplementation Support           Done Done Done: Both                                 visually and fun...
Takeaways ● Create / update our                     Cooper is a formalized   personas                                proce...
Upcoming SlideShare
Loading in …5
×

A Developers Take on Cooper

392 views

Published on

I recently attended the Interaction Design training at Cooper (http://www.cooper.com/#training:interaction_design).

This presentation is a brief overview of the training and Cooper process from the perspective of a software developer.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

A Developers Take on Cooper

  1. 1. A Developers Take on Cooper Adam Jordens @ajordens
  2. 2. My Background Technical Lead GenoLogics Life Sciences Founder AppiityTypically work with teams of It has been rare to have a3 or 4 Developers, a QA dedicated design resource onrepresentative, and a Product the teams Ive been a part of.Manager. Oh yeah, I cant draw.
  3. 3. ● In software, features cost almost nothing. ● In hardware, features almost always increase costs. FEATURE-ITISMost people developing software products dont know preciselywhat constitutes a good product, or the processes that canhelp get them there. "Goal Directed Design"
  4. 4. Goal Directed DesignDesign first; As developers, we prideprogram second ourselves on an ability to deliver against all odds.Think about what should be Often, to our own detrimentbuilt before starting to build and the detriment of ourit. product. Lean thinking is relativelyGoals are stable and persist new to product teams.across time.Contexts, tasks, needs andtools change over time.
  5. 5. Goal Directed DesignWhen was the last time you Separate responsibility forread the persona involved in design from responsibilityyour feature? for programmingDo you understand theunderlying goal or scenario Optimal designs are notyour feature is addressing? necessarily easy to implement.Scenarios provide the gluebetween user stories and arecritically important. Programmers want the product to be easy to code, designers desire to make the product easy to use.
  6. 6. Goal Directed DesignHold designers responsible Thinking Pointfor product quality anduser satisfaction Who is responsible for product quality and user satisfaction right now?Designers need to have thenecessary authority foreverything coming in contactwith the user.The design spec is not Including any installers,merely a suggestion but a documentation, etc.plan to be followed.
  7. 7. Goal Directed DesignUntil a persona is defined, a Define one specific user fordeveloper will think of your product; then invent athemselves as the user. persona - give that user a name and an environment and derive his or her goals Avoid talking about specific users, talk about their persona and goals. Powerful design tool, foundation for everything.Tasks are transient. Goal != Task
  8. 8. Goal Directed DesignWork in teams of two: Were already doing it, this isdesigner and design just a formalization of it withcommunicator outcomes (design spec).Generators and Synthesizersin Cooper terminology.Improves product quality and Developers often arent thedesign documentation. best at coming up with ad hoc designs.
  9. 9. Goal Directed DesignResearch ● Understanding business and user needsModelling ● Share with the entire product teamRequirements Definition ● Decide what the product should doFramework Definition ● Come up with a good conceptDetailed Design ● Design it in detail and make sure it is feasibleImplementation Support ● Ensure that the design is built as expected
  10. 10. Goal Directed DesignResearch Modelling & RequirementsObservation, Interviews and Personas, Scenarios, UsageCreative Exercises Patterns, Work Environments ● Stakeholders Scenarios are the glue ● Customers between user ● End users stories, everyone needs to ● Subject matter experts read and understand them. ● Competitors Extract personas from actual research.Not everyone is a stakeholder. Personas should have goals.
  11. 11. Goal Directed DesignFramework Definition Detailed DesignDefine the big picture; mast Iterate at greater and greaterheads, nav bars, content detail, screen by screen.areas, etc.Dont sweat little details, Collaborate with developers,widgets, field names, data. figure out the limitations.Scenarios provide guidance. Create challenging designs.Avoid painting the walls Optimize for intermediates:before creating a blue print. no one stays a beginner. "Key Interactions"
  12. 12. Goal Directed DesignImplementation Support Done Done Done: Both visually and functionally.The design doesnt stopwhen its been passed to thedevelopment team.Designers need to ensurethat the finished productsatisfies the original intent.Work with developers toensure consistencythroughoutthe entire application.
  13. 13. Takeaways ● Create / update our Cooper is a formalized personas process covering everything upstream of development. ● Establish written scenarios It eases communication ● Ecosystem and Workflow amongst remote teams. maps Involve others to break a ● 15 minute rule stalemate.20min * 3 shots better than 60m * 1 shot All too often we build designs ● Design in pairs (at least) and define interactions ourselves.

×