Sunday, December 18, 2011

Catalign Quarterly – Dec 2011

Catalign Quarterly is an attempt to put together insights relevant for fostering a culture of innovation in organizations. This is a first such issue.

There are five articles in this issue. The first two articles are insights from guest speakers at our innovation management workshop at IIMB last October. The first article summarizes how innovation program at Tanishq evolved over the last 7 years. The second one presents insights from Cognizant on how to build creative confidence. The third article is an inspiring narrative from Gyanesh Pandey, CEO of Husk Power Systems which is electrifying rural India (HQ in Bihar). Then there is a review of an excellent book called “Where good ideas come from” by Steven Johnson. Finally, we have the latest benchmark data on the idea management systems from INSSAN (Indian National Suggestion Scheme Association).

1. Managing innovation: journey of Tanishq, jewelry division of Titan

2. Building creative confidence: Insights from Sukumar Rajagopal of Cognizant

3. Gyanesh Pandey tells Husk Power Systems story of Bijli from Bhoosa

4. book review: “Where good ideas come from” by Steven Johnson

5. Benchmark data from INSSAN Excellence contest in suggestion schemes 2011

Tuesday, December 13, 2011

Who improved the world more: Thomas Edison or Ramana Maharshi?

Steve Jobs visited India along with his friend Kottke in 1973 in search of a crash course on enlightenment. Unfortunately, one of most promising gurus of the time, Neem Karoli Baba, had died a few days before the duo made it to his Ashram in Kainchi in Uttarakhand. They met a few other babas but the crash courses didn’t turn out to be very effective. Steve recalls his realization at the end of the trip in his famous quote, “We weren’t going to find a place where we could go to for a month to be enlightened. It was one of the first times that I started to realize that may be Thomas Edison did a lot more to improve the world than Karl Marx and Neem Karoli Baba put together”.

Among the three people Steve mentioned I have no expertise on two: Karl Marx and Neem Karoli Baba. However, I have a huge respect for Thomas Edison – I consider him to be the father of systematic innovation and have written a dozen articles in this blog referring to Thomas Edison & his contributions. I also know a few things about another baba: Ramana Maharshi – who fits the bill of a spiritual teacher who didn’t do much, didn’t speak much, didn’t travel much, didn’t wear much etc. – I guess you get the picture. In this article I want to visualize a hypothetical tennis match between Thomas Edison and Ramana Maharshi where points are scored based on “improvement to the world”. Shall we begin?

Before we begin, it may be good to look at a few things that were common to both Edison and Ramana. First, both were school dropouts. Edison had 3 months of formal schooling while Ramana went to school till age 15. Second, both were gifted with deep sleep. Three, both gave more importance to experiential learning to knowledge-from-the-books. Now let’s turn to the differences especially in how much they “improved the world”.

Let’s start with Thomas Edison, for the simple reason that he is umpire-friendly. It is much easier to count the score. In a career spanning sixty one years (1868-1930) Edison filed 1093 patents. That makes a batting average of 1 patent every 20 days. He made huge contributions to bringing practical incandescent bulb, gramophone and movie camera to the world. He made several improvements to telecommunications and storage battery. His legacy General Electric is one of the largest and most admired companies in the world today. He has inspired countless innovators – most notable being Henry Ford who remained his lifelong friend and Steve Jobs. With such an impressive scoring line-up, the question should be more like “How many Ramanas do we need to match one Edison?” Nevertheless, let’s go ahead and give Ramana a fair chance.

Let’s look at Ramana’s “career” from the point he started living in a cave called Virupaksha Cave in 1900 on a mountain called Arunachala at Thiruvannamalai where his “not-doing-much” started. Ramana lived there for 16 years after which he and his disciples built an Ashram at the foothills of the same mountain where he lived for the rest of his life till 1950. Ramana mostly wore a cloth diaper and preferred silence to talking as a medium of communication. His notable contributions to worldly matters included cooking – he was the chief chef of the Ashram for several years and architecting the Ashram design. You must be thinking this doesn’t look like much of a match so far. Be patient. As we noted earlier, Ramana is not very umpire-friendly.

An important aspect of Ramana’s day-job was having dialogues with visitors to the Ashram – either through silence or through words. Some people would come from nearby places, others would come from places as far as US. I don’t know the total number of unique visitors who met Ramana. More importantly, was meeting Ramana making any difference? Sometimes ‘yes’ and sometimes ‘no’. Again this ratio of “yes-visitors” to “no-visitors” is not known. And even if we take the total number of “yes-visitors” to be a million (perhaps a gross exaggeration), Edison can win the match hands-down just with his light bulb. Well, on what basis do we give Ramana any points? So let’s ask, “What is the crux of his teaching?” At least we will give him some points for that and make this match less embarrassing.

This is where the game becomes really tricky. Because the crux of Ramana’s teaching is concerned with the umpire himself i.e. the scoring system in my mind. Ramana felt that the biggest problem in the world was that the umpire ("I") falsely identifies himself with the scoring system. Steve Jobs himself was a super-umpire. He not only had opinions, his opinions thrived on super-villains (like Bill Gates). However, I really appreciate Steve for an important and yet overlooked keyword in his quote: "may be". I would like to stay with "may be" until I really understand the "I who wants to keep the score" very well.

Hope you enjoyed the match!


I read Steve Jobs quote in “iCon: Steve Jobs, the greatest second act in the history of business” by Young and Simon, Wiley-India, 2008, pg 25.

For more on Ramana Maharshi, I recommend Arthur Osborne’s “Ramana Maharshi and the path of self-knowledge” or David Godman’s interview with Maalok.

Wednesday, December 7, 2011

Benchmark data from INSSAN Excellence Contest in Suggestion Scheme – 2011

Idea management systems exist in the organizations at different levels – process improvements (kaizen), new product development (NPD), new business development (NBD), Intellectual property management (IPR) etc. Indian National Suggestion Scheme Association (INSSAN) has been benchmarking the suggestion schemes in primarily manufacturing sector for the past 20 years. The latest bulletin (Sept-Oct 2011) presents the benchmarking data from 27 organizations for financial year 2010-11 – Automotive (6), Engineering (6), Fertilizers (7), Associated (6) and Steel (2). Mr. Sudhir Date has presented the highlights in the bulletin (pg 14).

As discussed in an earlier article, I try to view the innovation metric from following three perspectives: (1) idea pipeline (number of ideas & participation of employees) (2) idea velocity (rate at which ideas move forward) (3) batting average (net potential impact in savings / revenue). Let's apply this lens to the INSSAN 2011 data.

Idea pipeline: Ideas per person per year is an excellent proxy for idea pipeline. For the past few years TVS Motor consistently stands out for ideas per person per year metric. On an average, a TVS employee gives a suggestion almost every week (46 in a year) as compared to India average of once in 2 months (6.5). India average has been hovering around 5-6 for the past 5 years. Participation percentage varies from 22% in Fertilizer sector to 90+% in Steel and Auto sectors (see figure below). Steel and Auto sectors were the first in India to embrace suggestion schemes. So this is not surprising. More the participation, more sustainable is your process.

Idea velocity: Unfortunately we don't have a good data on this. Lowest lead time for evaluation of suggestion is definitely an indicator and Maruti’s performance of 2 days is commendable. However, we don't have average data on this and we can guess why.

Batting average: Suggestion schemes measures the impact primarily through savings. Savings per accepted suggestion is a good indicator. India average of Rs.19,681 makes a good case for running the suggestion schemes.

On an average 70% of the suggested ideas are implemented and that looks pretty healthy.

Following table shows the data sector-wise.

Let’s hope we get similar data for other types of idea management systems in India as well.

Related articles:

Idea management systems in India: Benchmark data from INSSAN 2005-2008

INSSAN 20th Annual convention: where shop-floor innovators are heroes

INSSAN convention: sources & types of innovations and a good practice

“Where good ideas come from” by Steven Johnson

“Where do good ideas come from?” This question is typically approached from two directions. One: What kinds of people create good ideas? Two: What kinds of environments create good ideas? Steven Johnson’s book “Where good ideas come from” approaches the question from the second direction and identifies seven patterns that recur in fertile environments. His TED talk gives a great overview. Let me articulate three of the seven patterns below:

1. Adjacent possible: In the year following the 2004 Indian Ocean Tsunami, the Indonesian city of Meulaboh received eight incubators from a range of international relief organizations. By late 2008, when an MIT professor name Timothy Prestero visited the hospital, all eight were out of order – due to power surges, tropical humidity and lack of expertise to repair them. Prestero is an expert on robust designs and the founder of Design that Matters organization. He realized that designing an incubator in developing country wasn’t just about creating something that worked. It was also a matter of something that could be maintained by local people. Rosen, a Boston doctor, observed that small towns in Indonesia were able to repair the Toyota 4Runners. So Rosen approached Prestero with the idea: What if you made an incubator out of automobile parts? That is how NeoNurture incubator was born. It was doubly efficient because it tapped both the local supply of parts and the local knowledge of automobile repair.

Johnson observes that good ideas are like the NeoNurture device – they are inevitably constrained by the parts and skills that surround them. That is why encouraging prototyping is so important because it validates if we know what kind of spare parts to look for and whether we have the skills to put them together. Charles Babbage designed a programmable computer in 1837 but couldn't build a prototype in his lifetime (died: 1871) because the spare parts were simply not available. It wasn’t an “adjacent possible” idea for the time. Do you encourage prototyping? Do you make spare parts easily accessible?

2. Slow hunch: Charles Darwin wrote about his moment of epiphany on September 28, 1838 when he conceptualized the famous theory of natural selection. However, more than a century later, when a psychologist Howard Gruber went through the copious notes that Darwin had kept he realized that Darwin had been working on the key concepts from 1837 onwards. Sir Tim Berners-Lee designed the first prototype for sharing information with hypertext in 1980 at CERN. However, it is only in 1989 that he submitted the proposal for building world-wide web. The first web-site was build at CERN and put online on August 6, 1991.

Good ideas are more like slow hunches. They often mature by stealth, in small steps and fade into view. Does your organization encourage working on hunches?

3. Exaptation: What is common between the two innovations: Printing press and Jaipur foot? Both took a set of mature technologies in one domain, combined them to solve an unrelated problem. Exaptation is a trait developed in an organism optimized for a specific use but then it gets hijacked for completely different function. Johannes Gutenberg used the screw press technology used for making wines and made modifications to the metallurgy behind the movable type system to create a printing press. In case of Jaipur Foot, Dr. Promod Sethi and Ram Chandra a doctor-sculptor team looked at the retreading of a truck tire with vulcanized rubber in a roadside shop and applied it to create prosthetic legs – what is popularly known today as Jaipur foot.

Does your organization create a space for the "doctors" & "sculptors" to come together? Or does your organization encourage Chandras to visit new places like “cycle shops”?

I highly recommend this book for anyone interested in finding out “Where good ideas come from?” I am sure you will get a fresh perspective.

Thursday, December 1, 2011

Building creative confidence: Insights from Sukumar Rajagopal of Cognizant

When you ask the question, “How many of you are creative?” to either students or employees in India, very few, perhaps only 20%-30% of people typically raise hands. Why is that? There is a school of thought which says that it is primarily a confidence problem. Ability to be able to speak up your idea in a meeting with managers / senior managers without fear of failure / ridicule is what is called “creative confidence”. Mr. Sukumar Rajagopal, Senior Vice President, Chief Information Officer and Head of Innovation at Cognizant, shared his insights on how to build creative confidence based on his experience of running a managed innovation program at Cognizant. He was one of the guest speakers at our workshop on innovation management at IIMB last month. How do you build creative confidence? Let’s look at a few of the insights Sukumar shared.

If you want to build creative confidence, breakthrough innovation is not a good place to focus

Organizations need all kinds of innovations: breakthrough, enhancing, sustaining etc. However, if you want more people to feel confident about how they can contribute to innovation, then breakthrough innovation is not the right place to focus. Why? First, breakthrough innovations are rare, they don’t happen very often. Second, breakthrough ideas create cognitive dissonance and hence early reactions are usually negative (see a study from Cornell). Robert Goddard, the father of modern rocketry was ridiculed in New York Times in 1921, “Professor Goddard does not know the relation of action to reaction and seems to lack the basic knowledge ladled out daily in high schools”. Note that this does not mean that breakthrough innovation is not important.

Each of us is empowered to implement ideas within our own area of work

When people suggest ideas related to areas where they don’t have any control, then most of them get ignored. This leads to frustration. Lack of empowerment to experiment is a major hurdle in moving ideas forward. Hence, ideas within your own area of work are excellent candidates where the employees can experiment without asking for anybody’s permission. Perhaps one can fail and still continue without worry of any punishment.

When small ideas are implemented, the idea authors build credibility

If you want people take your big idea seriously, you need credibility. How do you build credibility? One way to do it is by implementing small ideas first. If you say that over the last year I have implemented 7 ideas, chances are high people might take your potentially big idea seriously.

Direct creative energies at problems that have stakeholders & sponsors

When we go to people and say, “Give me all your ideas”, we will be inundated with thousands of ideas like “Cafeteria food should be like this” or “Give all of us laptops”. These ideas don’t go anywhere unless they address problems that have stakeholders and sponsors. And when nobody looks at your ideas, the idea authors will get frustrated. Hence it is better to launch idea campaigns with sponsored challenges and make sure that you will implement top 5 / 10 ideas.

Sukumar derives a lot inspiration from Toyota’s kaizen, a system through which employees implement millions of ideas every year. Percent of people who have submitted one or more ideas last year is a good indicator of the creative confidence in the organization.

Related article:

40 years, 20 million ideas: The Toyota suggestion system

Wednesday, November 23, 2011

Gyanesh Pandey tells Husk Power Systems story of Bijli from Bhoosa

I got an opportunity to listen to Gyanesh Pandey, CEO of Husk Power Systems in IIM Bangalore last month. I don’t know why but I find the HPS story of producing Bijli from Bhoosa (electricity from husk) fascinating. And listening to the story from Gyanesh increased my fascination even further. Based out of Bihar, HPS is doing to eradicate needless darkness in rural India what Aravind Eye Hospital has done for eradicating needless blindness. It has so far electrified 450 villages / hamlets (mostly off-grid) in Bihar & UP. I have tried to condense the narrative below by keeping Gyanesh’s language as much as possible. You can find the fuller version of the story here.

I grew up hating my place (in North Bihar). Nothing made sense to me. Every single thing in the village costs you a little more, quality is poorer and people are lethargic. During holidays, I reluctantly came home from the boarding school. I tried to find reasons for not coming home. I could feel the depression all around.

I ended up becoming an engineer and going to the US for higher studies. During my PhD I came home to attend my sister’s wedding. On one of those evenings with the extended family members I was telling them stories of America. Naively I ended up saying, “It’s hard to tell you guys – You can’t even dream of how it is (in the US)”. I didn’t mean to offend anyone. However, an old guy in the room said, “For us, it will always be a dream. Because people like you will always maintain a distance from us.” I don’t know what he meant, but his words resonated somehow somewhere with me. This was 2001.

I automatically assumed that something is not being done because technology for doing it doesn’t exist. This was a big mistake. For the next 5 years, I partnered with Ratnesh Yahav, my best friend from childhood and experimented with several leading edge technologies like polymer solar cells, fuel cells, micro-tidal energy and finally Jatropha based bio-diesel. All of them failed. By 2006 I was back to Bihar from the US and badly depressed after the Jatropha project failure.

At this point, I got an appointment to see a director at the Renewable Energy Development Agency. He asked me, “How are you going to electrify villages?” I said, “I don’t know. I will do something”. He hit a buzzer and called the peon. “Call the guy who just left the room” Then he told me, “Talk to him. He sells gasifiers. Why don’t you use something like that?” I knew biomass gasification was an old technology developed by Hitler for wartime. People don’t use it anymore. The dealer told me that there were 40 gasifiers being used in Bihar. I said, “Wow!” He thought I am an NRI and he was trying to sell gasifiers to me.

The gasifiers were running on rice husk. 40% diesel and 60% gas – what is called dual-fuel mode. I came home after talking to him and worked out the math. I realized that 40% diesel model would not be economical. I started thinking, “Why can’t we use 100% gas?”

I started by finding out all I could on gasification based power generation. I found a paper from IISc and it said you can’t run an engine only on producer gas. Gasification is where you burn a biomass that generates a certain mixture of carbon monoxide and nitrogen and that mixture is combustible and becomes fuel. IIT Delhi had done a project. However, I couldn’t find a single instance where anybody said, “It has worked”. I tried to talk to a professor and he wasn’t even willing to talk to me. I just knew that all these people are wrong. I had no reason why.

At this point a scientist from MNRE, Mr. S K Singh encouraged me. Singh helped getting me hooked with a small engine maker from Agra. This was in June 2007. By August 15, 2007 we had a working system. We had electrified our first village. Soon after this we put out 2 systems electrifying 5 villages. By then we were out of money.

How did Gyanesh-Ratnesh manage to raise money? How does HPS business model work? How did they do the pricing? You can find the full story here.

In photo: Prof. Abhoy Ojha of IIMB (left) along with Gyanesh Pandey.

Saturday, November 12, 2011

Managing innovation: journey of Tanishq, jewelry division of Titan

I got an opportunity to listen to Mr. L. R. Natarajan (LRN), head of innovation council at Titan and Chief Manufacturing Officer of Tanishq, Titan’s jewelry division. He was one of the guest speakers at our workshop on innovation management at IIM Bangalore. The first thing you notice about LRN is the passion he carries for building a culture of innovation. After listening to the seven year journey LRN presented, most of us felt, “There is a lot more we can do in my organization”. What kinds of innovation management practices are followed at Tanishq? Here is a short summary.

“What’s new” campaign (2004): The journey at Tanishq began in 2004 where each of the 14 manufacturing departments was given a structured white board. Each team was supposed to write “What’s new” they are attempting on the whiteboard given to them. Competitive spirit was created by defining a review process and attaching rewards. This simple and effective process is still active after seven years of its launch.

Dreaming workshop & HOD fund (2006): In 2006, Titan had a workshop called “future shock” in which the MD asked 600 managers to dream about “Where do you see Titan 5 years down the road?” More than 130 new business ideas were generated. Through a selection process they were narrowed down to 2 new brands to be launched: Goldplus and Eyeplus.

“HOD fund” was initiated after observing that purchase of any capital item goes through a long chain of approvals – Sr. Manager, Deputy GM, GM, VP, COO, Corporate finance, Corp purchase & finally MD. By then the person who initiated the process loses interest. HOD fund created a shorter route for innovative ideas. Each Head of the Dept (HOD) was given a budget of upto Rs. 1 Lakh which he can approve himself.

Innovation school of management (2008): Between 2004 and 2008, many ideas got implemented. However, a closer look revealed that ideas had come from only 10% of the employees. Innovation school of management was started to involve every employee in this journey. A six month course was created and a written test & viva were conducted to select the first batch of 30 participants. For the first 3 days, the participants are taught about what, why and tools and techniques on how to think creatively. Then they were given a challenge to work on. If the inventory is 1 crore the challenge could be “How can we manage with 10 lakh inventory?” All HODs are trained mentors and they mentor the participants. Each participant is given 6 hrs per week to work on the challenge. There is a review once a month. At the end of the course, the MD hands over the certificates. The goal is to have all the employees as trained innovators by 2014-15. So far 187 out of 400 employees in the factory have been certified through the school.

Currently innovation group in Tanishq has 9 full-time members with 1 division manager, 3 managers and 5 executives.

3 success stories: (out of several LRN presented)

1.      Diamond setting: The process for preparing the casting mould was improved so that a highly skilled job of diamond setting becomes easier. In place of 100 to 150 stones a karigar is now setting 1500 stones every day. This process improvement idea has been patented.

2.      Diamond bagging: Diamond bagging is a process of starting with a work order, picking the right set of diamonds from hundred different varieties, putting it in a bag and giving it to the production to put it in the necklace. The idea of automating this process came from the theme that was launched in 2007: “Simplify and automate”. After about 4 years of working closely with the machine building division, a robotic arm was created that automated diamond bagging. This may be first time diamond bagging got automated in the world.

3.      Gold out of stone: Hard silicon carbide crucibles were lying around the factory. People knew that these might contain gold. However, people didn’t know what to do. One day, Rajsekhar, one of the operators got a road-roller from his neighbor and crushed the crucibles. About four and a half kilos of gold was recovered.

Sunday, November 6, 2011

Beyond jugaad: A summary of current practices and participant takeaways in managing innovation

Three of us (Prof. Rishikesha T. Krishnan, Prof. S. Rajeev and I) facilitated a three day Executive Development Program at IIM Bangalore last month titled “Going beyond jugaad: Building a systematic innovation capability”. 22 executives from 12 organizations participated in the workshop. On the third & last day, one representative from each organization presented their current practices for managing innovation as well as areas they would like to improve upon based on the learning at the program. Here is an attempt to summarize their perspective (not meant to be exhaustive and limited by what I captured in my notes).

Before we look at how different organizations are managing innovation in India, it makes sense to see participant and company profiles. The 12 companies represented following sectors: Aircraft manufacturing (India center), Automotive manufacturing, Consulting, India centers of high-tech products, IT services, IT enabled services (BPO) & Media (leading FM radio channel). Titles of the executives varied from CTO, DGM Innovation cell, VP New business / Marketing, Group Manager, Sr. Development Manager, Mobile Architect, Technical Fellow, Senior Staff Engineer etc. All the participants were very serious and active players in the innovation initiatives in their respective organizations.

Let me classify their perspectives into 3 key areas: idea management, buzz creation and learning & development.

1. Idea management: Almost all the participating organizations had a system in place for managing ideas. What varied was the scope of the innovation. In some organizations there was a bias for the IP (patent) management. In some cases the global process for big ideas was very active. However, the contribution from India center was low. In some places the system was active only in some part of the organization and in a few places the existing approach was primarily top-down.

Key takeaways: Encourage small ideas, implement bottom-up approach, create a challenge book (problem focus), make the measurement system more robust, improve the idea velocity, use cross functional teams. A couple of executives said their focus would be large impact idea creation using strategy models.

2. Buzz creation: Many organizations had events such as sponsored challenge or bright idea campaign to generate ideas and buzz around innovation. In some cases these events generated several hundred ideas every year. Garage forums encourage prototyping, Tech fair creates a platform for technical paper presentation, Inspire series invites external speakers, Wall of innovation displays innovators, Quarterly newsletter raises awareness on innovations inside and outside the organization.

Key takeaways: Almost all executives felt that they need to improve the participation level. Some said they need to improve the reward and recognition system.

3. Learning & development: For educating employees on innovation, organizations conduct idea generation workshops using methodologies such as design thinking, encourage informal communities for knowledge sharing, sponsor MTech/PhD and introduce innovation during company induction program.

Key takeways: More awareness building, Spot new trends in a structured manner, Inculcate right brain thinking.

12 organizations is a small sample. However, we hope that the seriousness demonstrated by the executives spreads in their organizations and beyond. Let’s build a culture of innovation systematically!

Thursday, September 1, 2011

Innovation dashboard: 4 indicators of idea velocity

Last year I presented a simple innovation dashboard with 4 parameters: pipeline, prototypes, portfolio and participation. What do these parameters measure?

  • Pipeline: How many ideas do we generate?
  • Prototypes: At what rate do ideas move forward?
  • Portfolio: What is the total potential impact?
  • Participation: Is the innovation activity likely to sustain?

A few months back I wrote about innovation pipeline and how CEOs are using it for strategic decisions. In this article

I want to focus on idea velocity – the rate at which ideas move forward. What are the different indicators of idea velocity? Let’s look at 4 such indicators below.

1. Responsiveness: How fast does the system respond to an idea submitted? In places like Boardroom Inc, a Connecticut publisher, ideas get evaluated in weekly team meeting. Many small ideas can be implemented within the team and don’t need any approval of higher authority. In Toyota, it works in a monthly cycle and uses hierarchical approval system. Small ideas get evaluated and awarded locally. In any process that takes more than a month to respond to the idea author, it is a cause of concern. In a social network with a voting system, the feedback can start very quickly.

2. Prototypes: First prototype could be a paper sketch (used by Tata Nano team), a skit depicting the usage scenario or a computer simulation model. What matters is how fast does the idea go from a concept to a prototype? And then from the first to the second and so on. First AdSense prototype was built in a few hours by Paul Buchheit. Amy Radin, Chief Innovation Officer of Citigroup, looks at: getting x number of pilots in market by y date. Google says, it performed 20,000 experiments in 2010 to improve its search algorithm and finally took 500 ideas live.

3. Champions: How many ideas have a champion? Champions are people with clout. They can push your idea through the resistance faced within the organization or outside. You are lucky when the idea champion is the group chairman (like Ratan Tata). However, more often he is likely to be a senior manager like David Patrick at IBM. Sometimes, your customer could also become your champion. For example, Lego involved selected advanced users in co-designing & championing its Mindstorm NXT.

4. Dedicated team: Any not-so-small idea can run only so far as a side activity. It needs a dedicated team, even though it could be just 3-4 people to begin with. Dedicated team is an indicator of the seriousness and attention from the management. For example, Tesco India has a problem solving track where a cross-functional team attempts to solve a chronic problem of the businesses. Rigor and rhythm of innovation reviews play an important role in making sure that selected ideas get appropriate resources.

I am sure there are more or better indicators you may be using. Your input will really help me get a better view of this metric.

Monday, August 29, 2011

Poor Economics: Designing robust interventions to fight poverty through randomized experiments

When I hear a professor from MIT saying she knows how to fight poverty, my first reaction is that of skepticism. “Does she even know what poverty is?” That’s how my mind would respond. And yet when I heard the TED talk by Prof. Esther Duflo of MIT titled “Social experiments to fight poverty”, I was thoroughly impressed. It took me some time to understand what exactly in the talk that impressed me so much. Subsequently I bought the book “Poor Economics” which she co-wrote with Abhijit Banerjee. Now, I am slowly beginning to understand why Amartya Sen has said, “A marvelously insightful book by two outstanding researchers on the real nature of poverty”. In this article I want to highlight three things that I find interesting in the book.

Intractable problem, manageable sub-problems: Poverty eradication looks like an unsolvable problem. People from Karl Marx to Mahatma Gandhi have taken a shot at it. However, it is not clear whether we have a handle on it. Silver bullet approach like “give aids” is not helping. Banerjee-Duflo take a different view. They feel that instead of trying to answer the top question, why not look at some sub-problems – each of which might have a definite and practical solution. For example, in the talk, Duflo presents three such sub-problems: How can we have more kids immunized? How can we get more people to use bednets that can reduce malaria affliction? How can we get students to attend school more number of days for a given dollar spent on the cause? The book, like the talk, shows how we can go about systematically addressing these sub-problems.

Randomized experimentation: Let’s take the question of immunization. In Udaipur district of Rajasthan, it was found out that only 1% of the children are fully immunized. The vaccines are there and are available for free. It is not that the parents don’t care about their kids. When their kids get measles parents end up spending thousands of rupees in treatment. So you have empty village sub-centres on one hand, and crowded hospitals on the other hand. So looks like the intention is not translating into action. What do you do? Dulfo & team decided to try random trials in 134 villages in Udaipur district. For one third villages there was no change, another one third villages had immunization monthly camps conducted and the last one third had camp plus a kilo of lentil free for camp participant. As it turned out the immunization percentage jumped by a whopping 37%. Note that this approach is analogous to randomized control trials used in medicine to discover drugs.

Design as if implementation matters: The beauty of Banerjee-Duflo approach is not that it does not make any assumption about the culture, anxiety, aspirations of the poor. The experiments reveal their biases anyway. I call this approach of designing an intervention – design as if implementation matters. Note that the approach does not advocate laboratory experiments – the experiments are performed in-field in actual conditions. I feel that experimentation and immersive research are the heart and the soul of systematic innovation. Banerjee-Duflo approach epitomizes both. Now, I know why the TED talk struck such a chord with me.

I strongly recommend the book for every student of social innovation.

Saturday, August 20, 2011

Maganlal Gandhi: Mahatma Gandhi’s innovation partner

"He [Maganlal] was, in my opinion, a genius... He laid the foundation of the science of Khadi by writing his Vanat Shastra” said Mahatma Gandhi at the inaugural ceremony of Magan Museum of Khadi (pdf) at Wardha on Dec 30, 19382. Ever since I read this, I became curious about Maganlal Gandhi. Where did Maganlal learn the science of khadi? Was this science backed up by rigorous experiments? If so, where did Maganlal perform those experiments? I wanted to find out. Finally, I got a peek into the story when my friend Prof. Rishikesha Krishnan connected me to Prof. Shambu Prasad of XIMB Bhubaneswar. Shambu has done extensive research on science of Gandhi. I found answers to some of my questions in an excellent article written by Shambu “Gandhi and Maganlal: Khadi science and the Gandhian scientist”. Here is a short summary.

Maganlal Khushalchand Gandhi (1883-1928) was Gandhi’s nephew (a grandson of his uncle) and 19 years younger to him. Maganlal met Gandhi in 1902, two days before Gandhi was to leave for South Africa. Maganlal was then on the lookout for a job in his native Kathiawar. Gandhi asked Maganlal to come to South Africa offering it as a land of opportunities with ample scope for growth. Maganlal was immediately put into business and was running a family shop of the Gandhis. When Gandhi quit his practice and decided to set-up a farm and take to farming as an occupation, Maganlal was the first to join him unconditionally knowing it involves self-imposed poverty.

In a short time, Maganlal picked up several skills at Phoenix Farm - composing and running the machines in the press, farming, carpentry and tailoring, keeping accounts of the settlement and teaching the children Gujarati and Mathematics. It was Maganlal who suggested the name Sadagraha to Gandhiji when he solicited a better term for “passive resistance” in the local newspaper Indian Opinion. Gandhi later modified Sadagraha to Satyagraha.

Later in India, Maganlal set-up and ran the khadi laboratory at Sabarmati Ashram as he was the head of the Technical Department of the All India Khadi Board (later the All India Spinners Association). Maganlal traveled to Madras Presidency to learn the art. The technical department of the Ashram, tested several samples of yarn (over 300 every month) and gave feedback to the Provincial Congress Committees. These results were widely reported regularly in Young India and Navjivan. As a resource centre in the field of khadi the Ashram used to send its staff, spindles, specimens of yarn, and charts explaining the effect of the wheel to exhibitions all over the country. Gandhi relied on Maganlal to test the various machines and always wanted Maganlal’s opinion on technical developments whether it was Mirabehn’s discovery of the soft spindle, Shankarlal’s Gandiva spinning wheel or the Ramachandra lift pump.

In 1922, a ‘Khaddar Information Bureau’ was constituted to provide or collect information on khadi from the provinces, to inform congress committees and selected workers on reports from the centres. Maganlal edited its ‘Khadi Bulletin’. A syllabus was formulated in 1923 for the weaving school with a regular six-month course. A khaddar service scheme was also instituted under which 600 instructors were to be trained in home carding.

Maganlal passed away while at work in Bihar due to typhoid on April 23, 1928, at the peak of his life and that of the khadi movement. In a moving tribute, titled ‘My Best Comrade Gone’ Gandhi remarked that: ‘The world knows so little of how much my so-called greatness depends upon the incessant toil and drudgery of silent, devoted, able and pure workers, men as well as women. And among them all Maganlal was to me the greatest, the best and the purest.


1. Gandhi and Maganlal: Khadi science and the Gandhian scientist” by Shambu Prasad, Presented at the Seminar ‘Gandhi and his Contemporaries’ held at the Indian Institute of Advanced Studies, Shimla, April 13-15, 1999

2. “Mahatma: Life of Mohandas Gandhi” by D. G. Tendulkar, volume 5, page 6.

3. Maganlal’s photo is from "Magan Nivas" at Sabarmati Ashram.

Sunday, July 24, 2011

How GE develops innovation leaders through the LIG program

GE launched Leadership, Innovation and Growth (LIG) program in September 2006 and ran it till September 2008, mostly in Crotonville, epicenter of GE’s learning & development. Altogether 2,500 senior managers in 260 teams went through this four day program. The purpose of LIG was to make innovation and growth as much of a religion at GE as Six Sigma had been under Jack Welch. On day four the course wrapped up with a plenary session at which each team had 20 minutes to deliver a presentation to Jeff Immelt, GE’s CEO. When Immelt was asked why he devoted so much time to LIG, he said, “LIG gave me a way to drive change and develop leaders at the same time”. What happened at LIG? Here is an overview on what GE Power senior management team went through at LIG. (source: An excellent HBR article “How GE teaches teams to lead change” by Steven Prokesch, a senior editor of HBR who was invited to attend one of the LIG programs in October 2007).

LIG program is a brainchild of Susan Peters, GE’s VP of executive development and Daniel Henson, then CMO. Before attending the LIG, the senior managers at a business would assess their team’s success in creating a climate supportive for innovation. The assessment would generate an innovation dashboard that would be used during the program. During the program there would be talks by external gurus as well as internal role models. A large amount of time – about 15 to 20 hours – was set aside for breakout sessions. What happens during these breakouts?

During the first breakout on the morning of day one, the Power Gen team guessed and the learned their actual team scores for the 360 degree review of their growth values. This triggered a reassessment of almost every aspect of their business. Some of the questions that got raised by the team were: “We’re not as good at anticipating major trends as we ought to be”, “Is solar a good place to be?” or “Renewable energy, clean coal, nuclear – all are going to be policy dependent. Are we good at this?” The reassessment continued in this manner throughout the four days.

The reflections generated insights – may be the old rules don’t always apply; may be limits on carbon emissions and tax incentives for clean, renewable power matter more. That sparked a conversation about GE’s ability to understand and influence government policies. Managers agreed that it was deficient and that beefing it was therefore a priority. In the next breakout session the Power Gen managers talked soberly about the state of their core. Unless the operations are strengthened it is difficult to free up time for innovative thinking.

At another breakout session the team assessed their innovation portfolio by putting each project in one of the three boxes, a framework created by Prof. Vijay Govindarajan: incremental (aimed at strengthening the core), adjacencies (taking existing technologies to new markets or taking new technologies to its existing markets), nonlinear shifts (discontinuous shifts in technology or markets with radically new products or business models).

The final LIG session involved the reports to Immelt. Power Gen team led by Bolze talked about their biggest takeways from the program, their 10-year projection of revenues (from $13 billion to $40 billion with renewables’ share going from 30% to 50%), and a vision statement – “Powering the world responsibly”. They committed themselves to strengthening the core. They confessed they needed to get better at looking around the corners to spot nonlinear shifts. They listed the capabilities they needed to build: regulatory expertise, faster product development, creating emerging-markets products “in country for country”. They vowed to lighten up a bit and become more playful, a characteristic of innovative companies. As they spoke Immelt asked questions and shared observations.

Within a few weeks after the LIG session Steve Bolze, as required, sent a commitment letter to Immelt, laying out the measures his team would take to increase the pace of organic growth. Such a letter becomes a living contract between Immelt and the team.

image source:

Saturday, July 2, 2011

Managing innovation: story of Tesco India

Last week I got an opportunity to listen to Sandeep Dhar, CEO of Tesco Hindustan Service Centre (HSC) on how Tesco India manages innovation at CII Innovation Forum. Tesco is the third largest retailer in the world by revenue and the second largest in terms of profits. Tesco HSC is responsible for standardizing all back-office processes impacting Tesco business globally and it currently employs 4000 associates. Sandeep demonstrated with examples how Tesco has made innovation an every day practice. How is it different from other places? Let’s see in this article.

Idea qualification: At Tesco, like everywhere else, every idea needs to have a business case which typically means cost saving for an idea from HSC. However, at Tesco, it needs to meet two additional criteria: One, it should improve or maintain customer experience. Two, it should simplify or at least maintain employee work complexity. Several ideas end up getting dropped for not meeting these criteria.

Continuous improvement track: Small ideas are taken seriously at Tesco. In fact, if an idea can reduce average time taken to handle a customer at the TIL by one second, it saves the company 2 million pounds a year in UK alone. How to keep people motivated for doing continuous improvement? At Tesco HSC this is ensured by how the team KPI or SLAs are set. For example, there is a team in India which receives calls when particular equipment like a refrigerator or air-conditioning unit is malfunctioning. Team’s job is to call the relevant vendor of the town and the vendor would send people to the Tesco store for servicing. Typical KPIs of such call-centric team would be percentage of calls serviced in 90 seconds, percentage calls tracked to closure etc. With these metric the improvements would be directed towards improving the efficiency of handling calls. They deliver limited value. Tesco changed the KPI of the team to “reduce the amount of money Tesco spends on maintenance”. With this the orientation of the team changed. They started looking into the reasons for equipment failures, some of the early warning and on preventive maintenance measures. Two years after this change the maintenance budget has come down by 40 percent.

Another team in India is responsible for making payments for the traffic violations of the truck drivers carrying Tesco supplies. Typical KPI would be timely payment of the fine and the accuracy of the payment. This KPI was changed to “figure out ways to reduce the fine”. One of the team members visited the traffic authority web site and found out a mechanism to challenge the fines. He and a couple of his colleagues started looking into the data and started challenging the fines selectively. At times the challenge would be successful, at times it wouldn’t. Then the team went one step further and analyzed the reasons for the traffic violations. They identified some commonly made mistakes and sent the information to the drivers. They were able to identify drivers who were more prone to making traffic violations.

Problem solving track: This is the track where the businesses are asked to share some of their chronic problems. Tesco India sets up cross functional teams to work on them. One such problem was related to Tesco’s online website. Tesco is world’s largest e-grocer. The web site has a favorites list which currently includes all the items a customer had shopped in the past. The drawback of this mechanism was that the favorites list becomes very long and inconvenient for the shopper. A Tesco India team worked with IISc experts and came up with a statistical algorithm that predicts what a shopper might be shopping on a day. For example, if you have purchased 3 gallons of milk on Monday, it would not show milk in favorites on Tuesday. But it may show it on Friday. This has resulted in reducing the favorites list to one third of the original size. This has been piloted and going into production.

In-store work experience: All managers in India go through Tesco Week in Store Together (TWIST) program whenever they visit a country with Tesco stores. For Sandeep a TWIST a year is mandatory. He said if he doesn’t spend a week working the store, his KPI goes down by a notch. When Sandeep spends a week in the store, he may spend a day at check-out counter, another day stacking products, third day he may be doing stock count, on the fourth day he may be going out with the delivery van.

Retail test lab: In 2007, Tesco HSC established retail test lab where recreated all hardware environments that exists in different Tesco stores. For example, sales counters and handheld devices etc. When IT develops a software it is tested in this simulated environment which improves the reliability of the deployment.

Saturday, June 25, 2011

Prof. Ulrich Weinberg on Design Thinking

Thanks to Prof. Rajeev and Supriya Dey of IIMB, yesterday I got an opportunity to meet Prof. Weinberg over lunch and subsequently attended his presentation “Design thinking: Looking beyond obvious” at IIMB. Prof. Ulrich Weinberg is the director of the School of Design Thinking at Hasso Plattner Institute, Potsdam, Germany. The school is modeled after D-school of Stanford. According to Prof. Weinberg at HPI D-school you get no credit points, no grades and no certificate worth any official value and yet within four years of its founding it has students from 70 disciplines and 20 nations. Natural question is: What is going on there? And what exactly do these students do that they value learning experience over credits and certificates?

The students participate in 1 hr, 3 hr, 1 day, 3 day, 1 week, 3 week and 6 week workshops / projects which progressively prepares them for the 12 week final project. Every project starts with a cross-functional team of 4 to 6 students and students rotate after every project. With students coming from disciplines as varied as art, history, medicine, engineering, psychology, law, forming a cross-functional team is not a challenge at HPI. The faculty works with industry-Government partners to generate a set of challenges. One such challenge came from DHL: How might we transfer packets from point A to B in the inner cities of future where no cars are allowed? London, Beijing, Mumbai are good candidates. If you feel that the challenge statement is simple looking, mind you it would have taken several days of work for the faculty members to work with DHL to arrive at the crisp looking statement which reflects user needs and pain points.

Out of the 12 weeks, half the time i.e. 6 weeks would be spent in understanding, observing and synthesizing the experience. This means going to the inner cities and observe how things work. Students observe how people walk to bus stops or train stations or cycle. In the DHL project the team was inspired by the workings of Dabbawalas of Mumbai. The most difficult part of this first phase is to switch your solution engine off. This is especially harder for engineers who are so used to solving problems. One of the deliverables is the creation of a detailed persona of the customers whose pain you are addressing. In the DHL case it could be thirty-five year old Chris or a twenty-two years old Sangeeta, a resident of the future city who either works for DHL or partners with DHL in moving the packet forward.

The next phase consists of ideation, prototyping and testing. Since the team has spent enough time in the field, ideation generates hundreds of ideas relevant to the problem. The school has created spaces with movable trolleys and white boards that help these teams in brainstorming. Every day there is a three minute presentation to the rest of the class on your prototype and you get immediate feedback. Weinberg says, “No other feedback can be as powerful as this inputs from your colleagues and faculty”.

The team working on DHL problem came up with an idea of citizen participation in packet delivery. They named it Bring.buddy. It taps all the consumers moving through a city each day, whether via bike, public transport or on foot. Interested participants indicate their travel route for the day using a downloadable smartphone app; a text message then lets them know of any packages needing delivery along the way. When there is such a package, the participant picks it up from the local kiosk where it's waiting and delivers it as they go about their daily business. In exchange for their help, the program rewards them with points that can be redeemed for free train tickets, merchandise coupons or CO2 credits. Check out the YouTube video BringBuddy.

Bring.Buddy created so much buzz in Shanghai trade show and even in Berlin that people started asking DHL when they are implementing it. Finally DHL has decided to pilot it in China along with the student team at HPI. Whether the service reaches market is anybody’s guess. However, can you doubt the learning the students are getting in the process?

If you want to get a glimpse of what design thinking experience might look like, I suggest watching 3-part video of Ideo’s Deep Dive.