My Design Process
Regardless of the problem domain I use the same process skeleton and "fill it up" using various UX techniques based on the project specifics and constraints in place. At its core, the design process I use is an amalgamation of various design theories. The one, never changing variable is an active involvement of users and stakeholders.
This phase is all about immersing into the problem domain by conducting an in-depth research. This includes talking to the business, target audience and doing relevant secondary research. In particular, learning about:
- user goals, behaviours and pain points
- business goals and priorities
- technology environment
- problem domain/industry
Once the context is clearly defined, it's time to determine the problem in question and project scope. This often differs from the initial brief.
In this stage, multiple design concepts get developed and tested with real users. This can be in the form of rough sketches, wireframes, paper or interactive prototypes or mock-ups.
After a number of iterations on initial design concepts, the solution gets refined into a Minimum Viable Product - the product with the highest return on investment versus risk. This may be a prototype or an actual working product.
Rinse and Repeat
Lastly, the design process is all about iterating, iterating and iterating. This applies to both defining the problem and defining the solution.