1. Welcome!
  2. Prefer Light Colored Skin? CLICK HERE...

My Regular UX Practice for New Product Design

These steps are not linear. Some steps can be skipped or can happen in any order.

UX Design Process for New Products

Design Process for Re-designing Products

UX Artifacts for The Existing Product

 

Step 1 - User Research

Plan of Attack! (My idea from experience)

  • As for the new product design, this is the most difficult and time consuming step
  • Finding reasonable target users is the key factor
  • Don't confuse buyers and end-users
  • Before interview, prepare enough domain knowledge for the target area
  • During interview, don't infuse your ideas into the user's
  • After interview, setup next around of interview
  • Keep in mind, ideal product doesn't mean MONEY!
 

Step 2 - Develop Persona

Plan of Attack! (My idea from experience)

  • Persona must be from User Research
  • Mostly, it is not reusable to other product
  • Sometimes, it is not based on roles but money spending (Consumer Markets)
  • It should be evolved based on current situation/policy
 

Step 3 - User Stories/Use-cases

Plan of Attack! (My idea from experience)

  • Persona itself is not enough to create User Stories
  • Develop main features (Stories) out of persona's goals, challenges, needs and pain points with proper market research (with Contexts)
  • Drive use-cases from all the Stories
 

Step 4 - Conceptual Wire-frame

Plan of Attack! (My idea from experience)

  • Use any familiar tools to create the Conceptual Mock-up
  • Pen and Pencil are quicker, but it may have some limitations to reuse/reproduce various other flow of mock-ups
  • As per Enterprise Software, Conceptual model may include pre-defined common styles (Hi-Fidelity Mock-up)
  • Balsamiq, Axure or Excel/PowerPoint/Visio ...
 

Step 5 - User Concept Validation

Plan of Attack! (my idea from experience)

  • Validate main stories across various users including every persona if possible
  • Validate more stories before go to the next stage
 

Step 6 - Visual Style Guide

Plan of Attack! (my idea from experience)

  • It takes a very long time to create a new Style (Guide)
  • Publishing style (guide) doesn't guarantee proper implementation by developers
  • Use Bootstrap Style if possible (Many things are per-defined)
 

Step 7 - Testable Wire-frame

Plan of Attack! (my idea from experience)

  • At this stage, all the wire-frame should be logical enough to develop
  • All the wire-frame should be verified by developers
  • All the wire-frame should be verified by QA (able to Test if implemented as it is)
  • Prepare for the unknown factors (resource, Knowledge, time limit ...)
  • Usually need various solutions (mock-ups) if the feature size is large, such as short term solutions and long term solutions.
  • If we follow true Agile, long term solutions will be changed based on the start (short) term delivery
 

Step 8 - Usability Test

Plan of Attack! (my idea from experience)

  • Full Scale usability testing is necessary for the New Product
  • Sometimes it is hard to get proper users (in Enterprise Software)
  • Testing the software/product, not testing People
  • If the user requires software/product domain knowledge to operate, then the usability testing may not work properly