Great

Fancy a Kerala houseboat as a vacation home?

Ever coasted down the backwaters of Kerala and lived the good life and wondered if you could own one of those beautiful houseboats as your...

Saturday, October 18, 2014

Brilliant ways to generate Ideas

I got this graphic from Futurethink and find their suggestions are great, practical, and very doable.


Click on the graphic to enlarge it.

Seven Chronic Innovation Problems

Bill Poston is the founder of Kalypso, a global innovation consulting firm. His experience has taught him that every company has its own set of challenges since they have their own history and culture, and operate in a certain way. He, therefore, came to the conclusion that while the above factors made each organisation unique, there were seven key chronic problems that ailed all of them, across the board.

He leads us through them in a webinar called: ‘Seven Chronic Problems for Innovation Officers to Address’. He has helped guide companies to generate return on innovation investment, and so here is what the expert has to say:

1.      Organisations lack an innovation strategy:  While the word innovation gets thrown around liberally in ‘strategy’ discussions, they don’t have a set of clear, growth goals that have to come out of innovation.  This starts with setting growth targets from innovation. It should answer questions as to what “we expect in terms of revenue and margin” and to have a clear idea of “how you are going to be able to deliver those returns and create linkages between investments you are making and those expected results.”  So asking questions like ‘what are your goals’ and ‘what risks are you prepared to take’ and if you are ‘going to use internal resources or leverage others outside the organisation’ are extremely vital.

2.      Lack of alignment: Since innovation is inherently cross-functional, there has to be buy-in from all business units and functions involved. Poston suggests it’s important to ‘understand the plan and communicate intent’. He has seen this lacking across R&D budget allocation, technical and commercial functions, marketing. He says all teams tend to undervalue the contribution of each other. A successful manager has to be able to get everyone on the same page and make sure the strategy gets implemented.
3.      Overloaded pipeline: He has seen budgets go up but the headcount has remained stagnant. So while there is money and hence, the expectations go up for what more can be done, but the ability to deliver hasn’t improved. He feels this “problem is so pervasive that it has become a normal mode of operation.” Research shows that pipelines should be loaded at 80% of the capacity, to give people breathing room to innovate and understand new concepts that may not have been given official sanction. He has seen companies that function well at a 110% level too. But at 200%-300%, it’s just too overloaded. 

4.      Rampant incrementalism: The willingness to assume higher levels of risk for higher levels of growth is very rare. Product portfolios are filled with small, low risk initiatives that have low returns waiting at the end. He said most product innovations are “minor packaging and labelling tweaks that don’t really affect the substance of the product. They may be line extensions which while being nice, are probably unlikely to move the needle on margins, sale or share.”

This problem has got worse in the last 10 years as a result of the financial crises and the short-term nature of the investment horizon.  Poston said, “The irony is that a low-risk portfolio is actually a giant risk to the viability of an organisation.” Such organisations are going to be overtaken by an upstart who disrupts the market.  So allocation of budgets over a mix of high and low risk projects in a portfolio, is a wise move to make.

5.      Unclear accountability: Have a chief innovation officer on board to manage things. He’s got to handle things that need to be done as a team. If accountability lies with the CEO or the chairman of the board, which is normally the case with many organisations, then these men/women are not going to be able to dedicate time from their busy schedules to look into details of every innovation project happening around their company. So the ideal person is one who is comfortable with both the commercial and technical aspects of the innovation business.

6.      Short-term orientation:  If an organisation’s horizon is short term, then it’s very difficult to look at long term initiatives. So an organisation needs to have executives who “elongate the planning horizon and develop a long-term investment view of the innovation priorities.”

7.      Lack of skills:  This is sort of like the overloaded pipeline situation.  There is a lack of key, technical and commercial skills, and people have not been hired who could do more high-end jobs for a while, at most organisations. This downsizing is affecting innovation because critical skills were not developed and in many cases, were not even identified.

These problems are equally present in both – small and large companies, and across industries. So everyone is equally laidback or confused about their approach to innovation.  Finally, Poston believes that revenue projections for a big idea need not be looked into in the early stages of the product cycle. He said, “Any revenue projections that are far out (in terms of time horizon) needs to be discounted by the potential of the organisation to actually deliver them.”

Graphic is from the webinar. This was written for Beyond Jugaad.

Wednesday, October 01, 2014

Digital Ethics: How Not to Mess Up with Technology

With innovation getting so much airtime in recent years, what is the consensus on how all that innovative technology is being used? To get some perspective, Gartner (a consultancy) hosted a webinar put together by their VP of Research, Frank Buytendijk, which debated Digital Ethics. What is Digital Ethics anyway? Buytendijk defines it as “A system of values and moral principles for the conduct of digital interactions among business, people, and things.”

He realises that most people go along with the ‘guns don’t kill, but people do’ school of thought. Similarly with technologies, it is people who are putting it to wrong use, so the responsibility should lie with them.  He, however, stated that technology has a “moral imprint”, even though it may have been created to solve a certain and usually common-place problem. So he feels that the innovator/s should be responsible for the unintended use that his/her invention is put to.

He used the example of TomTom, which is a bi-directional navigation software that people use in their vehicles. It gives data about traffic conditions as well as where the driver is at any given moment (in relation to the traffic congestion). It does aggregate and share its subscribers data with whoever pays for it. But the data shared is anonymous. The buyer of the data doesn’t know who was driving where, at a particular time of the day.

Even such ‘cleaned up’ data has its uses. It is being used by the Ministry of Infrastructure to map out where its own road-repair works are ongoing, and whether this is further causing traffic snarls. This turns out to be further value addition for TomTom users – even if indirectly. Another user of this data is the traffic police. They analyse the data to monitor speeds on various stretches of road. In doing this, they can plan speed traps to make drivers slow down and drive carefully.

So he asked, is this a good or a bad thing? Actually, both customers of the service and the media made a hue and cry, along the lines of ‘big brother is watching’ scenario, when it came to cops being given access to the data. TomTom’s share price fell and they had to rewrite their terms and conditions – to analyse their data for traffic jam patterns…and nothing more.

The reality is that ultimately, one cannot undo knowledge and pretend ignorance of the unexpected consequences of technology. Buytendijk suggests that monitoring is required. Here’s a framework to help you decide whether you are going to be indifferent or take a stand:       
  • Black Hat: Is your main goal to make a buck. There is no place for ethics in business.
  • Grey Hat: You just want to do your job and avoid an ethical discussion. If and when pushed into one, you make it up as you go along.
  • White Hat: You think through the ethics of technology. Ethical responsibility outweighs business responsibility. 
Which category you want to belong to, is entirely up to you.

Buytendijk does agree that the organisation you work with has to take a stand, but since an organisation is a collection of people, it has to start with someone who has to initiate the ‘ethics’ discussion.

In a sense, just like a good idea, even taking an ethical stand does begin with an individual…and then spreads out to others.

Graphics are sourced from the webinar: Digital Ethics: How Not to Mess Up with Technology. This was written for Beyond Jugaad.