Design Thinking
The products and services have been every increasing in terms of numbers and forms. It is unstoppable chain of efforts when it comes to the journey of solving a problem. Why can not one design one ideal solution for a specific problem, that remains the best forever? Why keep designing new products and services for solving the same problem? Why can’t we visualize and think about the ideal solution as the final result or outcome and develop the ideal solution once for all? Is this an ideality ? Can this ideality be reality? If not, why and if yes when and how? Irrespective of those questions as mentioned, let us firs look into what is design thinking. It is thinking like a designer to solve a problem. It is about going to the person in pain and understand how this pain can be eliminated through a product or a service. Understand why this pain needs an attention and why this is worth a problem to be solved. Before working on designing a solution as a product or service, one needs to really understand the pain and problem and why it is significant enough to be addressed with time, money and resources. This much before even the product is designed. If we can not first learn to understand and appreciate the problem and pain and the people who are facing this, we can not succeed in designing a solution. We will create some solution but we will not be able to create the solution, as an impact that the end users are seeking. There is a need for having a process, to immerse in their problems. Designers need to collaborate with the stakeholders starting with the person in pain or people in problem. They need to understand their ecosystem and challenges. When the problem is being understood and their pain is being felt, the boundary of solution and what to expect minimum from such a solution evolves or rather starts emerging. The attributes of the solution or the criteria on which the solution could be called as a fit gets clearly articulated. These are solely from the perspective of the people facing the problem who will be buying these solutions from the market when they arrive. They will judge them whether they fit their needs and expectations of being a solution or not. Design thinking is a mindset for first to be focused on the people and their pains and problems from their perspective. Design thinking is a problem solving mindset. It leverages designer’s sensibilities to continually understand people’s needs, expectations, pains and problems in order to bring out solutions (products and/or services) that are feasible (solves the problems and fit the set of expectations (needs and desires of an individual in pain or facing the problem) such that these solutions can be converted into marketing opportunity. After why is established (i.e. if you have weighed the decision that you want to address those problems or they fall under your areas of interest and focus of providing value), it is then about how to move systematically and iteratively (continually) as a “solution designing or problem solving process” from the people who want or need the solutions to the solutions that people want or need. Design thinking is human centered approach to problem solving. It is iterative, collaborative and practical. The people (market) in pain (need) and people (who want to design and/or sell solution) in gain (profits), are always working together whether its dry or rain (irrespective of the market environment and inherent challenges). It is about being hands on. It is always about looking from the perspective of customers (people in pain). Every decision in the process of solving a problem, if customer centric. It improves the internal processes for designing, producing and selling the solution. Design thinking origins as back 1950s and 1960s. In those days it was mostly about the impact of the World War II in terms of application of new knowledge and strategic thinking to industrial design, production and management of operations. It is always an human effort in the realm of creative thinking to make this thinking (about designing a system that solves a problem) as a systematic process or approach i.e. more and more scientific and predictable. However it is unreasonable to say all problems can be solved at any given point in time. To solve a problem, one might need resources to exist so that a system designer can put them together to work in a particular and consistently repeated manner i.e. imposed by a design construct (arrived after multiple rounds of experimentation or cycles of learning-thinking-doing-reflecting). Experimentation and its outcome can be planned predictably. There are certain things in the process of designing a system or solution that needs learning through a discovery, that needs one to first carry or try out an experiment and then see if this works or fails to deliver the intended outcome. If the experiments yield unexpected outcomes, these data points and observations are then once again pushed to the design table to re-think and attempt a new design to be prototyped and validated. Irrespective of the problem or industry domain, such a process of innovation or problem solving, that deals with new resources or new designs, needs experiments to be carried out as a part of the learning through discovery phases. It takes time and remains uncertain in terms of putting a closure date to this. The only way to make things move faster at this stage (crashing the fuzzy end of the innovation process) , is to do as many well defined experiments and as quickly as possible. Not all problems need experimentation and also many times, if right resources are missing or non-existent (lets say yet to be invented or not accessible) or if there are resources available (already invented or discovered) then the real challenge is perhaps purely to “somehow” figure out the solution by designing or architecting a system using these resources










