Difference between revisions of "User Centric Tech Processes"
Jump to navigation
Jump to search
m (1 revision imported) |
|||
| Line 9: | Line 9: | ||
* ERR on simplicity. | * ERR on simplicity. | ||
* Figure out, document, articulate what the literal things are that want to accomplish. | * Figure out, document, articulate what the literal things are that want to accomplish. | ||
| − | * | + | * Relationship with users are the beginning of design for users. |
* Remember before you were here you were a user. | * Remember before you were here you were a user. | ||
* Watch people use you tool. | * Watch people use you tool. | ||
**have them talk through | **have them talk through | ||
***what they are doing | ***what they are doing | ||
| − | *** | + | ***they're seeing |
***they miss | ***they miss | ||
| Line 25: | Line 25: | ||
==Beware== | ==Beware== | ||
| − | *What is the | + | *What is the simplest/ cheapest way to solve this problem? |
*manage expectations of changes later | *manage expectations of changes later | ||
*You can always add more later | *You can always add more later | ||
| Line 33: | Line 33: | ||
* When you do custom you need a plenup. | * When you do custom you need a plenup. | ||
*think about total cost over long term. | *think about total cost over long term. | ||
| + | |||
| + | |||
| + | [[Category: 2014 Richmond]] [[Category: Process]] | ||
Latest revision as of 19:57, 4 May 2016
- 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.
- Relationship 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
- they're seeing
- they miss
- have them talk through
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 simplest/ 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.