User Centric Tech Processes

From California Technology Festival Wiki
Revision as of 20:37, 28 April 2015 by Vivian (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  • Dont separate digital inclusion in design for users
  • Ask "do people even want to do this?" when creating an app/platform.
  • Understanding user needs and what they are using right now (and not using).
  • Acknowledge what cant be done through tech.
  • Prototyping - many different levels, from start to finish
  • Start with the goal. (What is it?).
  • User testing (+observing this)
  • self testing, understanding your skill level
  • ERR on simplicity.
  • Figure out, document, articulate what the literal things are that want to accomplish.
  • Relationnship with users are the beginning of design for users.
  • Remember before you were here you were a user.
  • Watch people use you tool.
    • have them talk through
      • what they are doing
      • theyre seeing
      • they miss

Questions

  • What do you want to do?
  • how would it help your work?
  • When you are hiring a techie or a designer

Beware

  • What is the simpliest/ cheapest way to solve this problem?
  • manage expectations of changes later
  • You can always add more later
  • dont do/ build everything at once
  • validate simple ideasfirst
  • get a second opinion.
  • When you do custom you need a plenup.
  • think about total cost over long term.