Since so many ask so often, I will finally share my #UX process (a thread):
1) Get clear on why this app, site or system exists, who needs it and what they expect to be able to do with it.
2) Assess the current state of the app, site or system and map out how people use it.
1) Get clear on why this app, site or system exists, who needs it and what they expect to be able to do with it.
2) Assess the current state of the app, site or system and map out how people use it.
3) Determine where and how the product (and the company) is falling short and what the consequences of each of those instances are, for users and for the business (existing or new research).
4) Prioritize and rank those failure areas: how bad and how often?
4) Prioritize and rank those failure areas: how bad and how often?
5) Assess + analyze competitors: UX, features, functionality.
6) Make recommendations for UX + UI improvements.
7) Be willing to completely blow all of this up and do something else entirely depending on the company, the team, the users, customers, constraints, etc.
6) Make recommendations for UX + UI improvements.
7) Be willing to completely blow all of this up and do something else entirely depending on the company, the team, the users, customers, constraints, etc.
8) Never introduce *anything* that forces teams to alter their current processes, because (a) that requires change across the ENTIRE organization and its infrastructure, which isn't gonna happen and (b) no one's gonna be willing to do more work than they're doing now.
And finally...
9) Don't make a ridiculous fucking diagram of the process that grossly overcomplicates any/all of the above for no good reason.
#ProductDesign #UserExperience #TheDoubleDiamondIsBullshit
9) Don't make a ridiculous fucking diagram of the process that grossly overcomplicates any/all of the above for no good reason.
#ProductDesign #UserExperience #TheDoubleDiamondIsBullshit
• • •
Missing some Tweet in this thread? You can try to
force a refresh
