Working as a UX architect / designer for the past five years has given me a good view of a variety of different processes. Some of those being great and others being ways that I do not want to ever do again.
Joining my new team recently there is a big emphasis on collaboration with our stake holders as well as getting validation early on from our users. As part of our process design principles are required in order to keep integrity within a project. Before working here I had used them more generally as a company view, where as here they change on a project by project basis.
The project I am currently working on is communicating ‘incidents’ to user, meaning when things go wrong we need to communicate this so that a user doesn’t get stressed about what’s causing the problem. The solution really should be ‘things shouldn’t go wrong’ but the world we live in is flawed so this is never going to be the case.
The principles for this project were formed from experiences our incident managers have had as well as running a stake holder work shop to collaborate on the vision through the means of a Studio workshop. A studio workshop essentially gives stakeholders a platform to align through visuals and ideas and permission to not have any right or wrong ideas. The end results are a few ideas from each person that are shared and critiqued. The result of this means that we have some ideas to start with but more importantly themes are made clear.
The next step is to take these themes, the business goal and user requirements to create the basis of the design. I found this article really useful in creation of the principles for this project: https://www.cxpartners.co.uk/our-thinking/design-principles/ There’s some great examples but also it shows the bad examples to get a better idea of how to write these.