TOOLS

Mapping is the action of outlining the context of the work in relation to what is known, unknown and what needs to be known, along with our scope and goals.

As a general rule, a failed idea is seen as the outcome of poor development or poor finalisation. However, in a high percentage of cases, the causes of this failure occur in the initial step, brought about by an incorrect statement of the problem.

Right from the outset we must seek not just solutions, but reasons behind the very search itself, –in other words–, why we are doing it, what for and for whom. And we must likewise be sure of who we are and what tools we are equipped with, plus we should be aware of what we know, and what we do not.

The main features of design are the use of tools and a qualitative research procedure that seeks to understand and define the challenge/problem to be solved using an understanding of the context and the individuals involved. In most cases we try to get inside the skin of the person involved in the problem or come to know the need for a solution by generating empathy. And we also try to get hold of upstream information; what is being done, what is possible/impossible.

Having done our work in the field and compiled as much information as possible (research), we make use of Visual Thinking techniques to summarise information via models that will help us understand and absorb what we have learned.

Once the correct framework for the work has been defined, it’s time to create ideas and develop solutions. A range of models exist for generating ideas, re-establishing hypotheses that have been identified (what if), generating forced relationships (hybridisation) and metaphor building, among other solutions.

An unexecuted idea is not worth anything. Developing prototypes is a part of the design process, and consists of realizing ideas. A prototype could be a drawing, a model or a cardboard box. It’s a way of defining and communicating an idea quickly; creating a communication and discussion hub.

This way we can provoke new questions and reveal hidden development and implementation needs.

Testing is a stage in the repetitive development procedure of an idea that makes it possible for you to get feedback from your target public. The aim of testing is to learn what works and what does not from the user’s point of view by means of adopting calculated risks. The purpose is to test certain features at an early stage without the final product in hand so that it can be modified or adapted.

The test step must be prepared with care: identify the tool to be used depending on the development stage of the idea. In the early stages we prefer more qualitative models and personal interviews, while in the mature stages we seek to reach the greatest possible number of users. The best approach is to deal with experienced individuals who know the subject area we are using and who are in turn, not making use of it (users/non-users).

The aim of the test is not just to seek the opinion of the user, but to understand and grasp his rational attitude (what he says about our solution) and his emotional response/reaction (what we observe or feel his opinion or feelings may be about our solution).