Innovation – A psychological barrier

This is the concluding part of the 3 part series on ‘How to stimulate innovation’.

When you talk to any of the engineers who don’t innovate and ask them for reasons, as per my experience, the only two responses that I could anticipate are ‘What is in it for me’ and ‘Innovation is not my cup of tea’. Regarding the former ‘What is in it for me’, I have already spoken about it in the 1st part of 3 part series (How to stimulate innovation). Regarding the latter ‘Innovation is not my cup of tea’, the response stems from the self limiting ability of the engineer(s) because most of them opine that Innovation is synonymous to being only complex and big. The self limiting tendency is what I call Psychological barrier to innovation. The thought that innovation is complex is the primary cause for self limiting tendency but the Innovation(s) can be as simple as listed in the blog post ‘Innovations – Keep it simple’ . The efficacy of the innovation is not measured by its complexity and scale but by the impact that it could create.

Self limiting ability prevents us from exploiting our full potential by drawing rigid boundaries around our comfort zone and providing an impression that our true capabilities are limited by those boundaries. But hardly do we realize that each of us have potential to innovate (at least incremental innovations, if not disruptive innovation). Just like hidden treasures in the world, there are definitely hidden talents within us (irrespective of the age). Few of us are fortunate enough to realize those talents by pushing our limits and expanding our comfort zone.

Though the DNA to innovate should have been inflicted in the minds of every individual in the college, nevertheless it is not too late for organization to do the job. Organization can pull engineers to take certain smaller steps that can eventually help them to expand their comfort zone. As a first step, Organizations should strive to break the myth that innovation is not always complex and big. To do so, organizations have to nominate existing Innovators as Influencer (remember Influencer in Tipping Point) to spread the message that Innovation is everyone’s capability and to provide motivational push to innovate.

Next in the sequence is to inculcate the ‘Solution Thinking’ among engineers as outlined in previous blog. Final step is to pull engineer to record their ideas through novel ways such as IDEA DAY or IDEA CONTEST where you coax a group of individual to share their ideas. Initially the focus should be on quantity of ideas and not on quality, later we can identify the patterns of those ideas to figure out what triggers each idea. Also institute mentors to help idea generators shape their idea. In this stage, the focus should be only on accumulating as many ideas as possible into the repository, never burden engineers to provide details such as the approximate $ value, target market etc. Those details should be provided jointly by Sales, Account team, PM after evaluating the applicability of idea to existing or new products.

Starting with above mentioned small little steps would instill stronger innovation culture into the Organization and one day lead the Organization to the cusp of major innovation.


Need for solution thinking to stimulate innovation

There are various types of innovations such as Product Innovation, Process Innovation and Service Innovation etc. Though I did not indicate explicitly, I was talking about stimulating “Product Innovation” in my earlier blog. One of the key drivers of product innovation is to derive new product ideas based on the deeper understanding of customers needs (both implicit and explicit). The new product idea can be based on application of new technology or any alternate product design that can enhance the usability or experience of the customers. The success of product innovation lies in our capability to understand both implicit and explicit needs of the customer. As I indicated in one of my earlier blog (The need for introspection of target market), the needs can change and it is the responsibility of Product Managers to keep well informed about the changing needs.

But focus of the blog is to facilitate engineers to gain broader understanding of the customer needs (at least explicit needs). Majority of the engineers keep themselves abreast with latest technology, the gap is only in the application of technology to generate new product ideas because of lack of awareness of customer needs. In other words, there is lack of solution thinking. Solution thinking is about the ability of engineers to successfully answer the following queries
Who is using our product?
Why are they using our product?
How are they using our product?

Solution thinking would facilitate engineers to identify product/solution gaps and it indirectly drives innovation to generate new product ideas to fill those gaps. We can make this very simple by having Product Managers communicate customer needs to engineers periodically through a forum or through streamlined process such as MRDs/PRDs. Later engineers can generate new product ideas based on those inputs. However customer needs are not something that is written on a wall, so by including engineers we are only expanding our capability to spot/understand more customer needs. Such inclusive focus will generate larger ownership among engineers and narrow the gap between product capabilities & customer needs.

We need to take a quick look at our history to figure out what is stopping our engineers from inculcating solution thinking. As a low cost deliver center, trtraditionally our focus has been on WHAT to develop and HOW to develop. Honestly our focus was never on WHY, please read my related blog post on the need to focus on WHY. Our emphasis on delivery excellence and engineering excellence etc has led to engineers working in silos with focus on specific modules of the entire product.

On the other hand, solution thinking requires a holistic view of how the product is used by the customers and how various components of the product inter operate to deliver a solution to the customer. By keeping our existing practices intact, I am only advocating for additional process (listed below) to inculcate solution thinking.

  • Product presentation delivered to all the new entrants to the product team. Product presentation would just have 3 steps
    • What is the product
    • Who are the users of the product
    • What are the specific business problems addressed by the product
  • Visual tools to explain how each element of the product interconnects with the rest of the elements
  • PRDs should not only list the features required but also highlight the needs that would be solved by those features.

The above 3 aspects might tell ‘Who is using our product’ and ‘Why are they using our product’. To understand ‘How are they using our product’, engineers have the distinct advantage of knowing it through support. While handling support issues, it is essentially that engineers’ not only focus on resolving the problem but to figure out how customer is using the product. We can do so through standard way of asking for the business implications of the problem for which support is sought. Customers define how the product is used and hence it is critical that we use customer support diligently to know how they are using our product.



Slaves of predefined processes

I recently joined an IT company and because of procedural delays, access card was not given on the date of joining. So I had to take the services of security guard to seek entry into my work place. The door to my workplace is placed few feet away on the path way adjacent to security guards place of work. So the door will not be visible and hence on my exit I used to knock on the door to gain the attention of the security guard. In case of few unsuccessful attempts, I resort to disturbing the employee sitting nearby to gain access to the door. I resorted to knocking procedure from day one after I notice few employees doing so. Hardly did I ever thought about any other better means to seek attention of the security guard to gain access to the door until the security guard requested me to call on his extension. Calling his extension will make things easier for everyone. At least I can easily be aware of his presence, so don’t end up knocking the door several times and causing trouble to others sitting nearby.
I suddenly realized how foolish I was, I could not even think of such simple solution. All I did was blatantly follow the procedure set by other. Had I started questioned it, maybe I could have prescribed a better solution.
The analogy might be very trivial and it might sound silly too. However, undoubtedly we are slaves to certain process that define how our day-to-day activities will be performed and it perfectly extends to our work place activities too. We often fail to question the status quo and blindly follow certain way of doing things. As mentioned in earlier 2 blogs, I am only reiterating the importance of ‘WHY’. Before I proceed any further let me clarify that I am not inimical to process, in fact I always have great regard for processes as success of all the major IT companies in India can definitely be attributed to their well oiled processes. Without those processes, there would utter chaos in bigger organizations.
When business drivers change and the factors affecting the business change, the old process that catapulted the organization to the height of success will definitely let down unless the organization cautiously changes its processes.
However when all those processes are indispensable to any organization and what I am trying to advocate here is that the radical thinking among individuals that spur innovation in process, business models and product development according to the changing needs of the business will not be possible without the revival of the old processes.