Start Lessons learned notes: Part#6
- We believe that people like <customer type> have a need for (or problems doing) <action/need/behavior>. We will know we have succeeded when <quantitative outcome>, or <qualitative outcome>, which will contribute to <KPI/success for our company>
- todo
- go to a lean UX meetup
- recruit UX and cut them some slack
- learn to do it yourself
- train together and then collaborate
- go on a site visit with your designer
- luxr.posterous.com
- the ladders
- techniques
- style guides
- get the mundane out of the way
- asset library
- Collaborative problem solving / design studios
- Outcome, not output
- create just enough design to get started
- Pairing designers with developers
- at the end of the session you have an experience, not a wireframe or documentation
- learned : human to human > paper to human
- big learning 2: personality in designers is key to success
- stay open to new ways of working together
- transparency builds trust
- style guides
- techniques
- Designers
- Designers do customer development. They call it research.
- Designers want to understand how users think about a problem.
- Design research reveals what users value
- Designers need organizational support
- Designers who know how to collaborate are the ones who win
- Designers work at every layer of the stack, from strategy to visual.
- Zach Larson – sidereel.com
- Information radiator
- information up on the walls
- public visible
- in a highly trafficked area
- =push instead of pull
- Theme backlog
- ux prototypes
- What’s a successful information radiator?
- information light
- cheap to build and maintain
- informs discussion so that conversations are richer
- the big rewrite
- exposed problems
- home base didn’t know what the product team was up to
- developers didn’t always know the most recent insights
- It was hard to define UX
- Radiators solved the problems
- Sketched ideas/user flows
- for big picture stuff too
- themes(with just enough detail) ex:
- Theme title: Social profile pages
- goals
- user registration, community
- Public version of profile pages to collect user actions and maybe share tracked shows
- see friends with connected accounts
- personalized urls
- goals
- Theme title: Social profile pages
- themes(with just enough detail) ex:
- answer basic question, make the most important info easy to access
- When to make an IR
- when folks keep asking for the same information
- when there is a core set of info to share
- when the people who see it will share a context
- only use it when people find it useful
- exposed problems
- Information radiator
Watch live video from Startup Lessons Learned on Justin.tv