How to plan UX, the right way
The most common gripe I hear from UX designers is that they're not invited into the process early enough. This is absolutely a problem. If you get on board when the code is done and time is running out, there's only so much you can do. But there's another common problem, rarely talked about. Getting on board too early.
Many companies I talk to today want to plan their UX in advance. Basically they want sketches of how the end user will interact with the finished project. Several things can go wrong with this approach:
- You get locked into what the project was supposed to be and you can no longer change it for the better.
- The sketches might not be technically sound. Small details can often be the largest technical hurdles.
- There might not be enough time to realize the planned UX, but it's just so tasty that your iterative process becomes a linear project doomed to miss the deadline.
- The designer(s) fall in love with an ideal, and are less open to change.
All of these issues, and all the ones I did not list, can be summed up in this sentence:
Premature UX is like masturbating before sex
No one is satisfied, it doesn't help you with the actual project and worst of all: The people involved in the pre-production process feel they've done some real work. Worst case they might feel that their job is already done. Just as the real work starts.
When and how to plan UX
Instead of trying to plan out a theoretical product of a project, find the parameters:
- Define a problem that the project is trying to solve, without actually proposing the solution.
- LIst the key issues and responsibilities the project must adhere to.
- Set measurable targets for the project, then divide by half.
This way the problem solving is a part of the project, and the project may run more smoothly. It also forces UX to be a part of the project process instead of just something to check off before the project starts.
As always, the key to great UX and design is iteration. Having UX as a part of the development process, without the limitations of a set goal, makes a vast difference.