Watch the whole video
UX design projects can go wrong!
The current episode is about a case where the UX design process went wrong. The reasons and how to make it better can be found here! We often make the experience: people come to us because they have already done a UX project, but it didn't go that way.
What was the reason for that most of the time?
Problem number 1 is: the software and hardware were developed and completed in one development cycle. But: software should always adapt to knowledge gained in use and remain fluid. Just because the hardware is developed once and rarely updated, the same is not true for software.
The UX research phase was thus complete when the hardware was finished. A document was handed over, from the agency to the client. The document was very extensive, several 100-page documents with all the design and research results. From the moment of handover, the project was completed for the design agency. The developers received the document and were supposed to develop the interface based on the design document.
Does that sound plausible? Not for us. At the beginning of the project, it is really important to clarify what will happen after the UX design phase or after the UX research project in the first place, how the result will be recorded and made usable. A 100-page document is all well and good. But: how will this document be used in practice. How are the findings from the research actually made usable? Who explains the results if something is unclear? And for e.g. developers who will deal with the document in order to develop features there will certainly be some questions.
It is really essential that designers and developers find a good way to work TOGETHER and not one after the other in the product development cycle. Developers need designers to understand users and build features so that users understand them.
So what should you really look for when starting and running a UX design project?
What does the project setup look like?
How do you get usable results quickly without spending months doing research?
Make sure that the software is always evolving as new insights are generated about e.g. user behaviour
Ensures a meaningful handover and collaboration between developers and designers
What else you can do wrong in the UX design process, how you can quickly recognize the red flags and what your UX design process should actually accomplish can be found in the latest episode of Software for People!