This post is primarily for beginners venturing into user experience design.
It is essential that within the first week or two of joining your job, you define the process that will ride you through the early phase of requirement gathering to the final delivering of product.
Here is the very first UX process that I defined, which is indicative of what worked for me in my early years, and one that has evolved and continues to evolve for each project that I do.
Few factors that cause updates to a UX process include:
- The project scope
- Involvement level desired by the client
- Cross teams involved
- The budget
- Project timelines
- The experience level of the UX designer
Apart from tying in strategy, ideation, production and deliverables into a logical timeline, the benefits UX process include (and are not limited to):
- Visibility of techniques that can be used at each stage
- Transparency of interaction points when working with cross-teams
- Keeps everyone on the same page
- Well defined stages and timelines for strategy, research, analysis, design, and production ( that’s not to say this is a waterfall methodology but very much an agile approach to iterative design)