Innovation is a result of an unaddressed problem.
Contrary to general perception, design process strives to find the correct problems. Solution to these form the second half of the process and which has complete dependency on the earlier, yet is more celebrated.
A designer observes a given brief, studies it in the context and then identifies the problem(s). He finally calls upon his knowledge and experience to address these. Often enough, reaching out to experts. Later, he iterates solutions at various levels of implementation, progressively validating in the context.
In the case of jugaad, the journey to innovation travels in the opposite direction. The innovator is the user himself. He defines the brief after he has already pinpointed the problems, then makes do with his limited knowledge to address these. In ideal cases, this leads to innovations that are appropriate for his use, and exceptionally, a genius product to generalise.
Much like any heroic story, jugaad innovations are also widely acknowledged. While its solutions are obviously admirable, the process itself isn’t. I offer a few words of precaution in this context.
A step-by-step comparison between the two reveals the risk. At the initial stages, jugaad does a better job in understanding the context and the defining of problems as the user (/innovator) understands his problems better than anybody else. On the other hand, a designer uses his observation skills to relate to the persona of the user, ideally, becoming the user himself. But this ideal case is by-default in jugaad and unrealistic in design process.
However, at solution stage, design process has its advantages. Being better equipped, given the expertise of a designer and access to experts, it not only leads to more efficient solutions but also makes sure that these are appropriate in larger system. Jugaad however depends solely on knowledge and capability of the innovator. In exceptional cases, smart workarounds come out. But these are rare, and bound to fall short of a designer’s resources.
In cases when the solution itself requires lesser expertise, a bigger knowledge pool might be irrelevant. But it can again be a risky proposition to generalise such cases. And that is what we would be doing if we recognise “jugaad” as a parallel process.
However, as I earlier stated, finding the correct problem(s) is crucial, and jugaad is better equipped. A more inclusive process might be to involve users with designers during initial phases. This can lead to exciting results with juxtaposition of experienced users and resourceful designers in brainstorming solutions.
Jugaad by itself should only be looked upon as a desperate option rather than a process. India, being a country well equipped with resources and aiming to be a world-class innovation hub, should do well to encourage correct processes in this endeavour.
Guest Post Contributed by Sumit Dagar, Kriyate