UX/UI Process
There is a truncated version of a UX design process referred to as the “Double Diamond.” It goes like this: 1. Discover insight into the problem. 2. Define the area to focus upon. 3. Develop potential solutions. and 4. Deliver solutions that work.
I rely on the above to quickly explain the process when asked… but it is not my full process. Below is a little closer to the mark for use with UX, but I also use variants of it for just about any professional project.
Discover
Gather project data about the issue or need: deadlines, familial elements, heat maps, player feedback and talk to engineers about hazards to avoid and constraints to keep in mind. Competitive analysis. SMITE (So My Initial Takeaway Equals...)
Develop
FEFO (Fail Early Fail Often.) Create quick wireframe-esque illustrations of solutions and test, gathering feedback and data. How does this issue (and solving it) impact adjacent features and issues? Look at the issue and adjacent issues from the standpoint of different player types.
Differentiate
Make ours better - it should solve more issues, be more accessible, and just be more clever in general. Refine.
Digest
Test and share. Show the survivors of the previous steps to others, to the stakeholder, and possibly to a focus or usability group. Gather data based on surveys. Refine. Make an intelligent decision.
Deploy
Get it out there. Track how well it is working. Refine if necessary.
Other principles I live by:
– SMITI: “So My Initial Takeaway Is…” I confirm my understanding of the project with the project lead or stakeholders, to avoid wasting time.
– Confusion timer: I set a physical timer in front of me whenever I have a question for which I have no answer. If I can’t find it in the project notes, and that time has passed – I get in touch with somebody. This avoids wasting time.
– FEFO: The classic “Fail Early, Fail Often.” UX is all about testing and making decisions based on gathered data.
discover
• identify scope
• identify target platforms)
• verify deliverable
• identify constraints in dollars, hours, colors, kb, pixels, accessibility, and platform
• discuss stakeholder review frequency
research
• design guideline analysis
• platform constraint analysis
• familial element analysis
• competitive analysis
• red route analysis (heatmaps/thought process/flow)
ideate
• consider knowns from research and discover stages
• imagine solutions
• wireframe
• flowchart
• internal department check
• review/refine/repeat
design
• rapid prototype
• verify accessibility:
optical, aural, physical
• verify full platform compatibility
• verify cultural suitability
• narrow candidates
• internal department check
• mockup for review
• review/refine/repeat
• finalize for testing
test
• deploy to beta
• usability and a/b testing
• explore feedback
• review/refine/repeat
• finalize for deployment
deploy
• finalize/launch
• explore feedback
• review/refine/repeat