Coming back to our meeting room. This is the crucial moment where you have to be with the feet on the ground, and pull down the meeting room too.
This means just a little more work for you!
Working with people is sometimes more complicated than the work itself. Sure this is a skill everyone has to master and it changes from one person to another (depending on everyone charisma) There’s no perfect master of these situations. Maybe can be called as such, one who keeps the balance.
How do we really handle these situations?
Let’s fast forward to the deliverable. Kindly discuss and visualize every bug or every element that needs to be fixed, before going to the “big thing” or before rushing into quick decisions.
Discus the behavior, include every scenario possible and the justice will speak itself. In this way we avoid the never ending discussions, blaming, the “I was right and she was wrong”. So, getting started is more important than being right or fighting for your opinion. This might be obvious for many people involved in the project but once is being discussed openly there are always unclear use cases. By taking this approach we can at least discuss on the ways on how we can improve.
Types of the deliverable.
What is a creation deliverable and what is it good for?
What we choose to make is to solve a situation of information transfer. We dig in options on how to do that. Usually it’s best to use low-fidelity because this phase is not focused on the quality of the visual rather than on the initial idea of how it would be. You start playing with solutions, once you found the problem and for whom will you solve it for, we can provide different options on how to solve it, so we create artifacts to get closer to the solution. This helps to externalize your understanding and put together the pieces of information that you gathered until now. We’re actually thinking through moving and placing the elements. And in this case the fidelity doesn’t have to be perfect. Actually the precision of high fidelity sometimes shifts the focus from your ability to explore and rearrange things. We are still in the backstage this moment. Walking through each step of the process helps you get the right answer. It’s generally where the source of good ideas come from.
Communicating everything that you learn from each session keeps the puzzle all together. Usually in iterations is good to keep the consistency otherwise we forget the main source of creation. Communicating is almost the half of what we do. Ones we bring the project/product at a certain stage we have to communicate it, share how it’s proceeding. It’s not going to be the final version so that’s why the communication is important to get there. To consider decisions, questions, critiques, new insights etc. *Be aware and careful to whom you’re trying to communicate, and if these ideas speak the same language to the one who is listening.
The validation allows us to share all the different research methods we used, and define if what we made is appropriate, how is that going to be effective and how are we going to reduce the issues before other expenses and investments flow in. There are different forms of validation. The reason why the deliverable have to be very well curated in each detail is because we are putting this product to the outside world and we want them to be as real as possible. If it’s difficult to understand them, you’re not going to be able to validate properly.
The people that we’re showing the work don’t always understand what you do, even inside your company. For different reasons they might not get focused enough, so what you show it’s best to be a stable version. When people don’t understand what you’re showing, it might be a signal for you that the design needs improvement. They don’t know how the product works, and the artifact has to be good enough to get that insight.