Posts Tagged ‘Heilmeier’

A CTO’s List of New Year’s Resolutions

December 30, 2009

Dilbert.com

There are many ways for Chief Technology Officers to be undone.   Appropriately enough  — in light of  Friday’s  college football bowl fest —  being an effective CTO is  like being a college football coach.  You don’t actually do the blocking and tackling yourself, but you’ll fail if the fundamentals are not done right —  even if your game plan is perfectly constructed.  I will have more to say in an upcoming  post about game plans, but today I want  to recognize the arrival of the  New Year with a short note about the fundamentals.

George Heilmeier, former DARPA Director, Bellcore CEO, and the inspiration for my” Guess Who’s Coming to Dinner?” series[1][2][3] was a mentor to me and to many other  technology leaders .  One day I asked him for a bit of career advice, and he hauled out a Heilmeier list — twelve  rules for CTO’s to follow if they have any hope of navigating the many dangers of the colliding worlds of innovation and execution.  I quickly found out that, true to form,  George had reduced best practices to a few rules of the road because dozens of others had asked for the same advice.  They are fascinating and valuable bits of advice, and they range in scope from broad business fundamentals to technology and culture.   I haven’t come across anyone who thinks that they are not important lessons — not to tuck away for future use, but to internalize and use as a platform for technology management in any setting.  It was December , so I turned George’s list into New Year’s resolutions.

  1. For each “client” establish/conceive a list of technologies and initiatives that drive his business and a list of technologies and initiatives that could change his business.
  2. Use the Catechism to get people to focus on the real “care-abouts” when making investment decisions and establishing priorities.
  3. Establish the physical, economic, and manufacturing limits of the technologies and capabilities that drive the business today.
  4. Establish a good working relationship with your peers
  5. Establish what [insert name(s) of  your CEO and Chairman] real priorities are.
  6. Establish the metrics for success in their eyes.
  7. Don’t shy away from doing some near term problem solving.  It builds credibility and respect.
  8. Never have your peers or clients come to your office for meetings with you.  Go to theirs.
  9. Any display of arrogance will cost you. Don’t do it.
  10. Compile a list of “innovations yet to be made”
  11. Make sure that each program or initiative is output oriented not activity oriented.
  12. Learn the [insert your company name here] culture.  It is unique.

Have a happy and safe New Year, and, by all means, don’t get caught when worlds collide.


[1] http://richde.wordpress.com/2009/09/22/guess-whos-coming-to-dinner/

[2] http://wwc.demillo.com/2009/10/11/guess-whos-coming-to-dinner-part-2/

[3] http://wwc.demillo.com/2009/10/19/guess-whos-coming-to-dinner-part-3/

Guess Who’s Coming to Dinner, Part 3

October 19, 2009

Note: This is a continuation of my Guess Who’s Coming to Dinner posts about the power of including innovators in strategic decision-making.

It took George Heilmeier an afternoon to convince Secretary of Defense James Schlesinger of the value of DARPA’s six “silver bullets”, capability-changing technologies that could guide system designers for the next decade:

  • Create an “invisible aircraft”.
  • Make the oceans “transparent”.
  • Create an agile, lightweight tank armed with a tank killer “machine gun”.
  • Develop new space based surveillance and warning systems based on infrared focal plane arrays.
  • Create command and control systems that adapted to the commander instead of forcing the commander to adapt to them.
  • Increase the reliability of our vehicles by creating onboard diagnostics and prognostics.

“Invisible aircraft” refers to the stealth technology that led directly to the F-111A Nighthawk and is good illustration of how innovators can influence events by focusing on business objectives.  In those days, half of the aircraft in a strike mission were there, not to fire weapons, but to detect and disrupt enemy radar.  Reducing aircraft radar cross-sections by a factor of 10,000 would lead to a ten-fold reduction in radar detection range and a corresponding increase in mission effectiveness.  Classified research in stealth technologies – mainly materials science – had been under way since the 1950’s, but DARPA’s idea was to use stealth as the primary criterion for aircraft design.  Performance and stability are the first casualties in this kind of design, so George knew that, not only would he have to integrate all of the component technologies it would take to produce a flyable, battle-worthy airplane, he would also have to convince the Air Force – run by and for pilots – of the usefulness of this way of designing an airplane.  Pilots understandably wanted to think that aerodynamics would be uppermost in the minds of designers, but DARPA wanted to turn that principle upside down.

The world changed after that.  By the 1980’s many high-performance military planes operated so close to the their performance envelopes that they were difficult or impossible to control without computerized assistance.  There was, in fact, a sort of dark  murmur among military pilots who understood both avionics and computers.  I was directing software test and evaluation oversight projects for the Director of Defense Test and Evaluation at that time.  One of our systems was an advanced fighter aircraft that was being retrofitted with computerized flight controls.  Some of the test pilots had done graduate work in computer science, and were clearly comfortable shifting between flying jet fighters and thinking about computer software.  One of them had a poster taped to the wall of his cubicle.  It showed a mocked-up  pilot’s eye view from the cockpit of a military  airplane that was clearly spiraling into the ground.  On the heads-up display was a graphic that looked something like this:

>>ATTENTION. FATAL ABORT.

>>GENERAL EXCEPTION FAULT 1080XX.

>>PROGRAM ABEND AT LOCATION 001001010111011.

>>RESTART PROGRAM? Y/N

We were talking about an operational test that he would be flying the next day, but all I could do was stare at the poster. I was a software tester.  I knew that fatal error messages like this were common. They came bundled with the price of the software. Most graduate students knew it, too. I thought to myself “This is the bravest guy I have ever met.”

In approving the silver bullets Schlesinger had promised to keep Pentagon staff off  Heilmeier’s back, but the Air Force resisted DARPA every step of the way:

During this period, the Air Force was not at all supportive of DARPA designing and building aircraft and would not cooperate with us.  We needed their help but received none.  As a last resort, I went to see AF Chief of Staff, Gen. David Jones to plead the case. When I entered his office, I was shocked to see that the general, who had refused to help us in no uncertain terms, was present.  I thought that the program was dead and me with it.[1]

Jones listened to George’s pitch, turned to his reluctant General and said, “We’re going to help these guys.” It was not a question.  Whether this was a directive from Schlesinger or a result George’s powerful presentation is not really important.  The Air Force cooperated from that point on, and on the morning of December 1, 1977, George watched from the end of a runway at Edward Air Force Base as the first prototype of a stealth aircraft took off.

Tying a technology agenda to business goals empowers both sides, and it puts both the passive and active resistors in an organization in a bind.   The cost of resisting change is to put their own goals at risk, often with unpleasant career consequences.  It also allows technology leaders to form new agendas that bypass an unmovable bureaucracy.  Here is how Heilmeier summarizes these lessons:

  1. When you really believe in a concept and the people involved, practice “no excuses” management.  The meaning of this is that you must remove all of the bureaucratic impediments to success.
  2. “Breaking glass” and going around the bureaucracy can be done if you believe in your cause and refuse to quit.
  3. In a game changing initiative, a small group must take on a larger group who won’t always “play fair”.

The danger in this approach is  that success depends almost entirely upon personal commitments, and those commitments can easily be undermined by a change in leadership.  When that happens — as I know from personal experience –  entrenched interests  come roaring back, hell-bent on toppling whatever was achieved.  The time frame for achieving goals has to fit within the tenure of the “small group” because worlds will inevitably come crashing together.

I will have more about this is a later post.


[1]George H. Heilmeier,  “A Moveable Feast – Kyoto Prize Lecture (SD Version)” 2005

Guess Who’s Coming to Dinner, Part 2

October 11, 2009

Dilbert.com

Being “technology driven” is often not the best path to real innovation.  Part 1 of this post was distilled from a conversation with George H. Heilmeier, former director of DARPA, CEO of Bellcore, inventor of the liquid crystal display and winner of the 2005 Kyoto prize. It was based in part on the “Heilmeier Catechism”, an approach to technology strategy that begins, not with the technology but with the business problem to be solved.  It was shared widely with the many younger managers who came under George’s influence over the years, and I have heard from a fair number of them in recent weeks.  All had their own stories to tell about why the approach of “selling to investment bankers” was exactly the right way to think about positioning R&D in a larger organization.  In all of our discussions, George has always been insistent about two things: the negative power of vested interests and the failure of  technology transfer by “throwing technology over the transom”.  Out of this came his notion of an “interdisciplinary team” with representation from R&D, product engineering and manufacturing, where leadership and balance shift as time goes on. This is the dinner table.   As important as these ideas are for day-to-day management of R&D, they are critical when it comes to initiating projects that are transformative, where commitment to change comes from handshakes at the top of the organization.

Shortly after the Regional Bell Operating Companies began divesting themselves of Bellcore, but before George stepped down as CEO, the appetite for applied research began to change.  To some extent, this was part of a natural evolution of the company from a captive R&D Lab to a stand-alone corporation whose owners – eventually the employee-owned defense systems integrator, Science Applications International or SAIC — demanded not only profitability but also growth in a market that was already growing at 15% per year.   The “30/30 Frontier” (30% revenue growth with 30% operating margins) was a wake-up call for all R&D managers in the company and it was a personal lesson for me in how to engage corporate management with initiatives that were tied to  bet-your-job objectives.

I was in charge of computing research at the time,  and three things were important to me.  First, was Heilmeier’s  commitment to funding forward-looking work at the corporate level, which meant that annual spending goals had to be set by reaching a consensus among product, research,  sales, and marketing teams.   Second was the freedom that Bob Lucky  — Bellcore’s senior VP of Research –  gave to his senior leaders to push the boundaries of the business. Third, was the collaborative but demanding relationship that I had with Chief Operating Officer Sanjiv Ajuha, who was himself a veteran software development manager.

Sanjiv was in turn looking for three business advantages that at first blush seem to be mutually contradictory.  The first two were obvious: near-term competitive advantage for the company’s large software systems and  game-changing inventions that would shake up the marketplace in the long run.  The third was revenue against which corporate R&D investments could be scored.  Near-term objectives were rolled up into product R&D costs while long-term objectives were used in 3-5 year investment planning.  Scoring R&D spending against revenue hardly seems like a competitive advantage but in my view it was the critical piece of the puzzle because it forced us to run a business.  It forced us to operate a business unit with profit and loss goals, not just another corporate cost center (which tend to develop unhealthy  entitlement cultures).   It also forced us to be very hard-nosed about tracking research contributions that led to revenue in existing product lines.  I would like to think this is a classical WWC strategy because it made us  focus externally on business objectives that affected the entire company.

I’ll have a lot more to say in later posts about some of the tools we used to do this, but the example that Heilmeier kept in front of us – because it took some convincing to make sure the lessons stuck – is for me the most compelling part of this story and the one I returned to time and again as I found myself inventing new frameworks in other organizations.

As DARPA Director, George reported to Nixon’s Secretary of Defense James Schlesinger.  Schlesinger himself had impressive academic and technology credentials.  He had served as head of the Atomic Energy Commission and Director Central Intelligence. Schlesinger’s DARPA operated like a technology incubator full of “technology entrepreneurs” as Heilmeier called his staff.  Under Heilmeier, DARPA settled on six over-arching themes, all of them aimed at somehow changing the nation’s military posture in ways that would be understandable not only to the Secretary but also to the staff and line officers who were frequently unhappy with DARPA’s “help”:

  • Create an “invisible aircraft”.
  • Make the oceans “transparent”.
  • Create an agile, lightweight tank armed with a tank killer “machine gun”.
  • Develop new space based surveillance and warning systems based on infrared focal plane arrays.
  • Create command and control systems that adapted to the commander instead of forcing the commander to adapt to them.
  • Increase the reliability of our vehicles by creating onboard diagnostics and prognostics.

Each of these “silver bullets” was so directly tied to a military objective that it took only a single meeting with Schlesinger to get his buy-in on the entire agenda.  In my next post I will describe how these technology challenges were turned into military capabilities and why it’s an important lesson for today’s climate where innovation and execution often seem to be at odds.

Guess Who’s Coming to Dinner

September 22, 2009

In the irreverent, satirical movie Brain Candy the scientist who is responsible for the eponymous drug that takes the world by storm and briefly turns an ailing pharmaceutical company into a global powerhouse is invited along with his team to the CEO’s house for a celebration.  While his nerdy team members are left at a dismal affair of chicken salad and soggy potato chips, the scientist is escorted to the real party, a sophisticated Bacchanalia complete with caviar, Champagne, celebrities, super models,and swimming pools.  Few Champagne-and-caviar parties in today’s corporate climate, but there is still a sense that when dinner is served for top decision-makers, R&D does not have a seat at the table or is – at best – a distraction.  R&D is a somewhat curious, uncomfortable, and frequently unwelcome guest.

There are obvious signals when the worlds of technology innovation and business execution are on collision courses.  There are early warnings that reverberate through organizations, but they tend to go unnoticed because corporations make  it  easy to set up effective filters.  Warnings can show up in the very language that R&D management uses to talk about the rest of the company.  In “Are R&D Customers Always Wrong?” I quote former GM research chief Robert Frosch talking about the

…ocean of corporate problems

as if they were the problems of some alien world into which the GM R&D Center had been dropped.  In “Well, what kind of fraud is it?” Edward clearly lived in a different world, and the many “Loose Cannons” who I still hear from were never able to bridge the gulf.  Everyone seems to be a helpless observer to a catastrophe over which they have no control.

My experience is that senior executives, starting in the boardroom, can too easily focus on events that are rushing at them — too fast for effective reaction — ignoring the events that are still far enough away to anticipate.   There is, for example, an overwhelming feeling  that, since the time of a chief executive  is so precious, every step should be taken to avoid diluting the CEO’s time with minutiae.  To be perfectly honest, technologists tend to do that – passion for a technology project can fill a briefing with flourishes that are meant to be savored and admired by peers, not convey actionable information to decision-makers.  But that doesn’t excuse what in my view has become the regrettable practice in large companies of filling virtually all executive time with managing cash, debt, and other financial indicators of performance.

Financial performance in a technology company rests on other factors, too. Market disruptors, for example, are rarely predicted by financial analysis.  Even annual strategic planning and investment is a barren exercise without the participation of an educated team to make sense of the alternatives.  In an industry with many acquisition targets the ones that should occupy the attention of senior management are not necessarily the ones that have the strongest near-term business cases because those may not be the ones that advance long term goals.  Intel chairman Andy Grove once said that a Board’s responsibility is to

…insure that company success is longer than the CEO, market opportunity, or product cycle.

I will have more to say in later posts about the collision between decisions that really advance long term goals and those that are simply chosen from a list of predetermined alternatives.  What starts in the boardroom is inevitably replicated at other levels.  To deal with all of the important factors that determine success of a technology company  technology leaders must have a seat at the table.  Avoid collisions by inviting them to dinner.

I’ve worked with many senior executives who have set a technology place at the table with oftentimes-spectacular results, but today I want to focus on my Bellcore mentor CEO George Heilmeier, winner of the 2005 Kyoto Prize for his invention of the liquid crystal display.  George, along with Bellcore research chief Bob Lucky and head of the software business Sanjiv Ahuja led the remarkable transformation of Bellcore from an inward looking R&D consortium to the profitable stand-alone supplier of telecom software and services that was divested by the Bell Operating Companies and acquired by systems integrator SAIC in 1997.   Bellcore generated enough cash in the first quarter after being acquired to pay back the entire purchase price. George took particular delight in his mentor role.  Even during his busiest days at Bellcore, he would wander into my office, put his feet up on the coffee table, and ask what was going on in the labs, a conversation that often went on long into the evening.

One of George’s most enduring contributions to the R&D culture at Bellcore (and, as I later found out, to Texas Instruments, Compaq, and DARPA) was the Catechism.  I tried many times to get him to call it something else because I really believed that some in our multicultural environment would be offended by the term, but he always ignored my suggestion and in the end nobody seemed to mind very much.  The Catechism was George’s way of framing every strategic discussion, but he took particular care to make sure it was used to manage technology.  I later found out that others, including former Intel research head David Tennenhouse, who had also been swept into George’s wide path, had also carried the Catechism tradition forward.  According to the Catechism every strategic proposal in the company had to answer the following six questions:

  1. What are you trying to do? (No Jargon)
  2. How is it done today and what are the limitations of current practice?
  3. What is new in your approach and why do you think it will succeed?
  4. Assuming success, what does in mean to customers and the company?  This is the quantitative value proposition.
  5. What are the risks and the risk reduction plan?
  6. How long will it take?  How much will it cost? What are the mid term and final exams?

At Bellcore, George personally ran a Quarterly CEO Technology Council Review, where R&D managers from around the company would present their best ideas – always using the Catechism — for innovations to heads of the strategic business units, sales, and marketing.  Sometimes to the consternation of both the CFO and  the head of sales, George would reward skunk works projects that had terrific answers with additional resources to continue their work.  I wondered many times about the metaphor mixing in Question Six, but again it didn’t seem to both others.  There was no complicated process.  If you answered the questions well and the value proposition made sense, you got enough to get you going.  If the project was a little further along, you needed business unit heads to also buy in, and so on until it made sense to tie cost and revenue goals to the project. By that time the balance of the authority for the project was in a product group so the Technology Council could disengage. Amazing ideas came out of this process including the word’s first e-commerce products and an amazing quality transformation among the company’s more than 6,000 software engineers.

George Heilmeier’s Catechism was the inspiration for my Loose Cannon escalation process at HP.  HP was about 50 times larger than Bellcore so the idea of a quarterly CEO review was not feasible.  However my Technology Council was a direct pathway to the Executive Council so the effect was the same.

I sat down with George last spring for a wide-ranging conversation.  Much of what he had to say about both the Catechism and seats at the table has also appeared elsewhere – most notably in his five public speeches in conjunction with the Kyoto Prize.[1] The work that won him the Kytoto Prize was done in the 1960’s at RCA’s Sarnoff Laboratories in Princeton, where he had recently completed his PhD.   This included the discovery of electro-optic effects in certain kinds of liquid crystals that would be used to build  the first liquid crystal displays.   George always claims that he just “stumbled upon it” but he quotes Vladimir Zworykin, a television pioneer  with commenting:

“Stumbled, perhaps, but to stumble you must be moving.”

Heilmeier became disillusioned with the slow pace of change at RCA and left to spend a year as a White House Fellow, an assignment that turned into an appointment as Special Assistant to Secretary of Defense James Schlesinger and later to his appointment as head of DARPA.  Schlesinger and other White House mentors gave George a seat in senior policy discussions from the earliest day, and his growing comfort with proximity to important decision-making shaped his outlook on the value of a seat at the table. Two lessons stuck with him.  First was the negative power of vested interests:  in times of change those with the most to lose will fight tooth and nail to undermine it and those with the most to gain do not yet realize how much they have to gain.   Second was the negative aspect of “technology transfer”.  George was never a fan of throwing technology “over the transom”.  His commitment to providing an equal voice for innovation grew out of his experience that it was much better to form what he calls an “interdisciplinary team” with representation from R&D, product engineering and manufacturing  (he still believes that marketing is best done organically with all members of the team interacting with customers).   The leadership and balance of this team shifts as time goes on.  This is the dinner table.

In my next post, I’ll give you an example of these principles in action: a transformational event that could only have been successful with a seat at the table and that would have been killed by a distant CEO, undiluted with the minutiae of technological disruption.


[1] A Moveable Feast: Kyoto Prize Lecture (SD Version), 2005