![]() As much as I would like to get away from updating a set of UX specifications 9 times, I really can’t because my company is regulated by the FDA. But, many organizations rely on these documents as part of a formal or even regulatory process. Now, there is the whole idea of Lean UX and spending less time on these deliverables. I can always judge my own specifications by whether or not I can understand the design 3 months later when a developer comes to ask me a question. Indeed this last point is most important. They communicate your design to the developers, the stakeholders and often yourself after you have moved on to a different project. This is why your specifications document (or documentation) is so important. I have written about this before in:įive essential elements in presenting UX design You can have what seems to be a perfect design, but if it is not well communicated or you simply cannot explain and justify decisions made, you will sink your design in the space of a single meeting. Indeed, it is as important as the design itself. Now what? What do you do with all that work and how do you communicate your design?Ĭommunicating design is a critical part of the entire design process and often where things go wrong. You might even have developed a prototype and conducted a little usability testing on the fly. So you figured out your design, met all the requirements and managed to create an interface that not only solves the end-users’ problems, but is also aesthetically appealing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |