No more 100-page PDFs! What your UX design process should create instead...

Since we've already had to rescue a few of these projects, in this episode you'll hear a story about a failed UX design project.

The whole video

UX design projects can go wrong!


The current episode is about a case where the UX design process went wrong. Find out the reasons and how to do it better here!

We often make the experience: People come to us because they have already done a UX project, but it didn't go as it should.
What was usually the reason for that?


Problem number 1 is: The software and the hardware were developed and completed in one development cycle. But: software should always adapt to what it learns from use and remain fluid. Just because the hardware is developed once and rarely updated does not apply to the software.

Conceptual pitfalls

So the UX research phase was completed when the hardware was ready. A document was handed over from the agency to the client. The document was very large, several 100-page documents with all the design and research results. From the moment it was handed over, the project was complete for the design agency. The developers received the document and were to develop the interface based on the design document.
Does that sound plausible? Not to us it doesn't. It is really important to clarify at the beginning of the project 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 is this document used in practice. How are the findings from the research actually made usable? Who explains the results when something is unclear? And, for example, for developers who are looking at the document to develop features, there will certainly be some questions.

It's really important that designers and developers find a good way to work TOGETHER and not sequentially in the product development cycle.
The developers need the designers to understand the users and develop the features so that the users understand them.

So what should you really look for when starting and executing a UX design project?


1. What does the project structure look like?
2. How do you get useful results quickly without spending months doing research?
3. Ensure that the software is constantly evolving as new insights are gained about, for example, user behavior.
4. ensure meaningful handover and collaboration between developers and designers

Find out what else you can get wrong in the UX design process, how to quickly spot the red flags, and what your UX design process should actually do in the latest episode of Software for People!

Written by:
Lisa