Success of change (improvement) programs

Financial Times has another interesting take on success of process improvement projects in Management – Failing to cope with change? 

At the meeting, survey data were presented which suggested that, while 37 per cent of UK board members believed that their change programmes were generally successful, only 5 per cent of middle managers did. 

As we discussed in the recent post on key success factors for lasting process improvement results, managers have an inordinate amount of responsibility and power to drive success.

A confident leadership team may know that the right choices have been made. But it may take longer for this to become apparent to the rest of the organisation. Of course, there are two other possible explanations for this gap in perception: wishful thinking in the boardroom or plain bad communication. 

The keys to success (real not imaginary) remain the same: long-term focus, metrics, rewards/raises tied to metrics and manager involvement.  I guess the point the article makes may be important to – a consistent simple message from the executives (and board) to the teams:

Send a small number of simple messages again and again,” he advised. “And the larger the organisation, the simpler the message has to be.


Questioning and Skepticism in R&D

The New Scientist had an article about questioning culture in organizations Living in denial: When a sceptic isn’t a sceptic: “

A climate denier has a position staked out in advance, and sorts through the data employing ‘confirmation bias’ – the tendency to look for and find confirmatory evidence for pre-existing beliefs and ignore or dismiss the rest. Scepticism is integral to the scientific process, because most claims turn out to be false. Weeding out the few kernels of wheat from the large pile of chaff requires extensive observation, careful experimentation and cautious inference. Science is scepticism and good scientists are sceptical.

R&D management probably is as close to science as we would get in most commercial ventures.  As we saw in a recent post, one needs to encourage questioning and skepticism to drive innovation.  However, managers need to strive to keep the entire process constructive and avoid “rote denial.”


Where Process-Improvement Projects Go Wrong

Here is a very interesting article from MIT Sloan Management Review on effectiveness on Where Process-Improvement Projects Go Wrong. I have read the results of a survey on cost cutting that more than 90% of the organizations surveyed failed to maintain savings for more than 3 years.  This article mentions another interesting result: more than 60% organizations adopting 6 sigma are dissatisfied with the results.

The underlying thesis is that even though process improves under the management attention in improvement projects, it revers back to original unless organizations puts in place concrete practices to make sure changes stick.  Normally, the pre-improvement practices exist because of culture / team member tendencies.  These are difficult to change and or maintain.  The article points out four lessons:

First, the extended involvement of a Six Sigma or other improvement expert is required if teams are to remain motivated, continue learning and maintain gains.

Second, performance appraisals need to be tied to successful implementation of improvement projects. Studies point out that raises, even in small amounts, can motivate team members to embrace new, better work practices. 

Third, improvement teams should have no more than six to nine members, and the timeline for launching a project should be no longer than six to eight weeks. The bigger the team, the greater the chance members will have competing interests and the harder it will be for them to agree on goals, especially after the improvement expert has moved on to a new project.

Fourth, executives need to directly participate in improvement projects, not just “support” them. Because it was in his best interests, the director in charge of the improvement projects at the aerospace company created the illusion that everything was great by communicating only about projects that were yielding excellent results. By observing the successes and failures of improvement programs firsthand, rather than relying on someone else’s interpretation, executives can make more accurate assessments as to which ones are worth continuing.

 I think the fourth point is probably the most important one.  I have seen many a six sigma projects failed because there was no real incentive to change, no pressure from the executive in-charge to drive performance and no clear way to measure performance to start with…


How Do Innovators Think? Harvard Business Review

Harvard Business Review has an interesting article about How Do Innovators Think?  The entire article is a good read, but here is the list of capabilities/tendencies of innovative people:

  1. Associating: Connect ideas together
  2. Questioning: Ask why, how, what
  3. Observant: Look into details
  4. Networking: Know who to talk to and how to reach them
Clearly a good list.  The one thing that they make a point of (and I agree completely) is inability of even the most creative people to question – mainly due to cultural/social learnings:

 We think there are far more discovery driven people in companies than anyone realizes. We’ve found that 15% of executives are deeply innovative, meaning they’ve invented a new product or started an innovative venture. But the problem is that even the most creative people are often careful about asking questions for fear of looking stupid, or because they know the organization won’t value it.

 I guess the biggest challenge for R&D managers then is to develop an environment that encourages civil and constructive questioning.


Three Big Assumptions Leaders Should Question

In an article in the Washington Post, John Boldani points out Three Big Assumptions Leaders Should Question

  1. It is important for organizations to set firm goals
  2. Quick wins are essential to managers in transition
  3. Senior leaders believe in their CEOs
Many organizations I have seen suffer from too much focus on goals.  One widely known example of this is in “Stuffing the Channel” at the end of the measurement period to meet sales goals and get bonuses.

It is important for organizations to set firm goals. People need to have direction so it is important to point them in the right direction. But such a single-minded focus on goals may end up damaging individuals and the organization says a study conducted by Maurice Schweitzer of Penn’s Wharton School. Relentless pursuit of goals tempts managers to cross ethical boundaries and abandon ‘sound business practices.’ Unreached goals may then end up frustrating an organization rather than helping it to succeed.

However, if the goals are not firm than organizations tend to not really perform anyway.   If one enforces a culture that goals need not be met, how does one motivate and reward the organization?  I think a better approach would be to set up a tiered goal structure: An (exponentially) increasing reward for meeting or exceeding goals.  It is even more important to make these tiers somewhat achievable – encouraging teams to try to reach the next level (Remember the Lincoln Electric case in business school?)

Another key with goals is to have balanced goals: opposing goals that make sure that behavior does not become too goal focused.  In an R&D world for example, successful R&D projects are a goal most organizations have.  A success driven goal alone will encourage managers from hiding failures and impede risk taking.  A balancing metric would be wasted development effort: tying some fraction of bonuses to projects that fail – 90% of bonus for success and 10% for failures…  This would encourage R&D managers to take risks and encourage acceptance of failures.

The other recommendations are similar.  Senior leaders clearly should not always believe in the CEO.  However, a show of solidarity might be good for encouraging and motivating R&D teams.


Innovation Incentives

Slate Magazine in an article titled How to make America more innovative: give scientists more incentives to innovat: shows that just opportunity and skills are not enough to drive innovation.  Organizations need to align incentives with needed behavior to innovate successfully.

“Incentives matter for innovation, and it’s a critical lesson for the government bureaucrats set to disburse hundreds of billions of dollars through Obama’s national Innovation Strategy, which is supposed to return America to innovative pre-eminence. The way we spend those dollars will be at least as important as how much we spend, and if we want the next generation of ideas to be Made in America, Obama’s team had better get its incentives right.”

The authors point out that HHMI with guaranteed support for five years tends to have more publication than NSF/NIH funded project.  I think that in many R&D organizations, guaranteed employment may not have exactly the same results  – HHMI only allows people to work there for a few years.  Employees have to find a permanent home someplace else at the end of their stay.  This would probably drive some behavior.  Also, amount of money being awarded may have some impact on results as well.

Unfortunately, no simple solutions / rules.  Only thing for certain is that R&D managers have to keep incentives in mind when trying to drive innovation.


Freescale CTO on R&D Strategies

NE Asia Tech-On has interviewed Freescale CTO on R&D Strategies.  The interview does focus quite a bit on the semiconductor industry, but there are some useful hints for R&D managers everywhere.

First – a clearly defined strategy is quite useful do build focus and drive efficiency (even though it is not done very effectively in many organizations):

Before the Lehman Shock, we detected a sign of business recession. So, we decided to retreat from the business for mobile phones and announced it in October 2008. At the same time, we decided to focus on four areas, namely, automobiles, networking, consumer and industrial products.

Among them, we will cover almost everything in the fields of automobiles and networking, which we consider are our core businesses. In the fields of consumer and industrial products, we will cover part of them such as smartbook PCs and electronic book readers in the field of consumer products and smart meters, smart grids and home-use mobile medical devices in the field of industrial products.

It is also important to define what will be done in-house and what will be sourced from the outside.  Many organizations run into problems with open innovation when there is a conflict between what is being done internally and what is sourced:

We did basic researches when we were a part of Motorola. But, currently, we do not do basic researches in our company. We tie up with colleges and consortiums for them. For semiconductor makers, the day of technological development for technologies ended long ago. 

There is also a need for tighter communications between R&D and marketing, and FreeScale clearly recognizes it

What is important now is to solve customers’ problems. Therefore, the ideas of the R&D division are summarized as PowerPoint files. The sales stuff and marketing people bring them to our customers and ask their opinions. If the customers do not like the ideas, they will be dumped

However, I am not sure if PowerPoint files are the best approach to communicate R&D intent to customers for many organizations.  Who will be developing these documents?  How does one maintain version control?  How does one bring feedback from the customers back and incorporate the into R&D – through PPT?

Finally, one more hint about being responsive to customer needs vs. being submissive to customer demands:

We cannot make products that have an impact on business just by using the ideas of the R&D people. We are doing research and development by considering customers’ opinions and market needs as well as taking advantage of our technologies. I said that we tie up with colleges and consortiums. But, in addition to that, we are collaborating with the industry leaders and our partners to solve our customers’ problems. 


Customer Loyalty driving R&D

Corporate Executive Board has another one of their useful lists: Six Myths of Customer Loyalty. R&D managers probably are a key driver of customer retention and loyalty and three of these myths are relevant to R&D:

Myth 3: Customer Loyalty Efforts Should Focus on What Customers Say is Most Important
Myth 5: Developing Personal Relationships with Customers is the Best Way for Sales to Drive Loyalty
Myth 6: Employees Who Don’t Face Customers Cannot Affect Customer Loyalty

The idea is that one has to balance internal evaluation with voice of the customer.  Customers are becoming more fickle (necessarily – competitive pressure are enormous throughout the ecosystem.  As pointed out in a Forbes article: The New Normal: Your Customer Is In The Driver’s Seat:

“Today’s consumers are more diverse, more inter-connected and more demanding than ever. Their expectations are rising while their propensity to be loyal to companies is declining, so (let’s face it) they are in the driver’s seat. The questions for companies today are then: Are companies orchestrating where consumers go, and are they making the trip pleasant?”

Some key concepts to keep in mind when R&D managers interact with Product Managers or Marketing…
DPSTBNMT3VHA 


Big Pharma’s stalled R&D machines

Reuters has a Special Report: Big Pharma’s stalled R&D machine.  The industry is under tremendous pressure to develop new products and address new emerging markets:

One factor forcing Big Pharma to rethink its business model is the huge number of patents that are set to expire over the next five years. As patents run out on blockbuster prescription tablets like Pfizer’s $12 billion-a-year cholesterol medicine Lipitor and AstraZeneca’s $5 billion heartburn pill Nexium, cut-price generics are sure to rush in and slash margins. Between now and 2015 products with sales of more than $142 billion will face copycat competition, according to IMS Health, the leading global supplier of prescription drug data. It is the biggest “cliff” of patent expiries in the history of the pharmaceuticals industry.

Add in tougher regulatory hurdles and a brutal squeeze on healthcare budgets as cash-strapped governments push austerity programs and it’s little wonder that drug companies are cutting back and shifting focus. The strategy so far has been to buy promising new drugs from outside developers and boost investment in the relative safety of non-prescription consumer products. Big drugmakers are also moving into new markets — with Asia at the top of everybody’s list. It all adds up to a redesign of the multinational pharmaceutical company. In the 21st century, says Isaly, Big Pharma will primarily be a distribution business.

However, the existing/historic R&D model does not seem to work effectively:

The problem is, Big Pharma doesn’t have nearly enough new drugs in the pipeline to replace all those it is about to lose. Since 1950 — virtually the dawn of the modern era of medicine — a total of 1,256 new drugs have been approved by the U.S. Food and Drug Administration (FDA). But the industry today produces roughly the same number of new medicines that it did 60 years ago.

Ten years ago there was a lot of hope that process-led research systems would industrialize the hunt for new drugs. But that optimism may have been misplaced. A spike in drug approvals in the mid-1990s, it turns out, was not the result of any fundamental improvement in productivity but largely down to the FDA clearing a backlog of applications after the introduction of a new system under which companies paid “user fees” to help speed the process.

Despite pouring billions into research — more than $65 billion last year in the U.S. alone — the number of new drugs launched annually has fallen 44 percent since 1997, according to CMR International, a Thomson Reuters subsidiary.

It appears that the PE ratio of pharmaceutical firms have dropped below that of consumer goods companies such as P&G.  Instead of figuring out a way to make R&D more effective, the industry seems to want to move towards a more consumer goods model and cut R&D as much as possible:

The move to cut R&D, he says, is one of the most profound changes in the industry in decades. Some firms are pulling back from problematic areas like depression, where proving the value of new medicines in clinical trials is fiendishly difficult. Lack of progress in this field is a prime reason behind Glaxo’s decision to cut research in Verona. Other firms are cutting back in areas that used to be their bread and butter. Pfizer, for instance, is trimming research into cardiovascular drugs and AstraZeneca is ending discovery in psychiatric medicine. Instead of pouring money into R&D themselves, drugmakers are turning to smaller firms, outsourcing routine research functions and even buying in smart blue-sky discovery work.

However, the large gross margins can not be sustained in a non-R&D discriminated business.  Hence the industry seems to want to outsource R&D to contract research organizations (CRO):

They’re also happy to pick up Big Pharma’s leftovers. Glaxo, for example, is negotiating to sell its Verona site to a U.S.-based CRO called Aptuit. Parexel International Corp, which is based in Boston and conducts clinical trials for drugmakers around the world, is busy hiring hundreds of new staff — many of them refugees from Big Pharma. “It’s a brain shift,” says Parexel’s chief executive and founder Josef von Rickenbach. “The rate of outsourcing has continued to tick up pretty much every year across all clinical trial activities.”

Does it not mean that the fundamental problem is not necessarily that R&D is ineffective, but that is costs too much?  R&D will be not outsourced to CRO who can maintain lower costs and higher efficiencies by leveraging economies of scale.  My question is: How large does a company have to be for economies of scale to be no longer make a difference?  What does a company give up in strategic / competitive advantage by outsourcing critical R&D?


How to improve performance reviews

The article Yes, Everyone Really Does Hate Performance Reviews  in Wall Street Journal has some good advice on making performance reviews more effective:

The good news is that none of this is the way things have to be. The one-sided, boss-dominated performance review needs to be replaced by a straight-talking relationship where the focus is on results, not personality, and where the boss is held accountable for the success of the subordinate (instead of just using the performance review to blame the subordinate for any problems they’re having). In this new system, managers will stop labeling people ‘good guys’ and ‘bad guys’ — or, in the sick parlance of performance reviews, outstanding performers, average performers, and poor performers to be put on notice. Instead, they’ll get it straight that their job is to make everyone reporting to them good guys.

This is important (if difficult) in R&D management – especially larger organizations.  Most engineers tend to dislike performance reviews any way.  The fact that engineers work in cross-functional teams and have multiple bosses makes reviews even more difficult.  Functional managers may not have all the information about actual work performed by an engineer on a project team, while the project manager may not know the discipline involved sufficiently to value the effort.  Interesting conundrum.