-
Notifications
You must be signed in to change notification settings - Fork 0
Process
Gordon325 edited this page Nov 29, 2018
·
2 revisions
Provide deliverable(s) for each of the Process phases. Provide files, links, assets, video, et al. of how you and/or your Team addressed each of the following phases. Ensure each phase utilizes one (or more) method(s). Reference User Experience Team of One, DESN 338 UX 1, DESN 348 UX 2, and Lectures.
The Who, Why, What, When, and How.
- Sample deliverables
- Project Brief
- Experience Map
- Card Sorting
- See Chapter 2: Getting Started
- See Chapter 3: Building Support for Your Work
- “If you’re only going to do one thing” see Chapter 1: UX 101
Stop guessing. Research it.
- Sample deliverables
- Client Interviews
- Personas
- Guerrilla User Research
- See Chapter 5: Getting Started
- “If you’re only going to do one thing” see Chapter 2: Getting Started
Ideas a fragile; proof ideas.
- Sample deliverables
- Lo-Fidelity to Hi-Fidelity wireframes
- InVision or Sketch app Prototype
- Lo-to-Medium Physical Model
- Chapter 7: Design Methods
- “If you’re only going to do one thing” see Chapter 7: Design Methods
Digitize it. Code it. Make it real.
- Sample deliverables
- InVision or Sketch app Prototype
- Beta-version of product (app, site, et al.)
- Hi-Fidelity Physical model
- Reference UX 1, UX 2, Web 1, Web 2, and/other VCD courses
- “If you’re only going to do one thing”, make it, but then evaluate it through the Process phases.
Nothing is perfect. How can it improved? What will replace it eventually? Why will it no longer be necessary?
- Sample deliverables
- Metrics from HotJar, Google Analytics, etc.
- User feedback and reviews
- Usability Tests
- Chapter 8: Testing and Evaluation Methods
- Reference UX 1 and UX 2
- “If you’re only going to do one thing” see Chapter 8: Testing and Evaluation Methods, Method 23
The process is not linear; it is circular. Reevaluate the outcomes and deliverables of each phase. How can it be improved?