The Innovators Studio with Phil McKinney Podcast Por Phil McKinney arte de portada

The Innovators Studio with Phil McKinney

The Innovators Studio with Phil McKinney

De: Phil McKinney
Escúchala gratis

Forty years of billion-dollar innovation decisions. The real stories, the hard calls, and the patterns that repeat across every organization that's ever tried to build something new. Phil McKinney shares what those decisions actually look like. Phil was HP's CTO when Fast Company named it one of the most innovative companies in the world three years running. He co-founded a company and took it public. Now he runs CableLabs, the R&D engine behind the global broadband industry. This isn't theory. It's what happened. And what you can see coming if you know what to look for. Running since 2005, originally as The Killer Innovations Show, now The Innovators Studio. Tens of millions of downloads. Full archive at killerinnovations.com. New episodes at philmckinney.com.Copyright 2005-2026 Techtrend Group LLC. See philmckinney.com Desarrollo Personal Economía Gestión y Liderazgo Liderazgo Éxito Personal
Episodios
  • The R&D Metric Mark Hurd and HP Got Wrong

    The R&D Metric Mark Hurd and HP Got Wrong
    Mar 25 2026
    Twenty years. Nearly one thousand episodes on this show. And starting today, we're going to try something a little different this season. Season 21 is about the decisions that actually determine whether innovation lives or dies inside any organization. The real calls. Not the fluff stuff we read in academic textbooks. I want to actually put you in the rooms where these decisions are happening. What went right. What went wrong. My objective is to expose you to the patterns in innovation decisions so that you can recognize them. Recognize them in yourself, in the people you need to influence, long before you step into any landmines. So let's get into it. The Encounter on the Top Floor of Building 25 Making generational decisions on innovation investment can be a make-or-break moment. What I refer to as a CLM, a Career Limiting Move. In my case, it started with a chance conversation with Mark Hurd, HP's CEO. Let me take you back to 2005. HP headquarters is on Page Mill Road in Palo Alto, referred to internally as Building 25. The top floor is where all of the executive offices are. That's where Mark's office was. I was up there doing some meetings and got snagged by Mark. Now, Mark had a reputation. He was a big numbers guy. He believed in what he called extreme benchmarking. You tore into your competitors' numbers. You knew your own numbers in and out.1 Others had warned me about this. He had a famous quote that everybody shared: "Stare at the numbers long enough, and they will eventually confess." Mark believed you could not lead a critical role at HP if you did not know your numbers cold, inside and out. Didn't matter whether it was sales, CTO, a function, or a division. It didn't matter. And Mark tested everyone on the leadership team. Not just the leadership team. He would randomly stop employees and ask them for their numbers based on what group they worked in. It was non-stop. It was constant. To where support staff was literally constantly preparing briefing books for managers, VPs, leaders, just in case they got nabbed by Mark. In my case, I happened to be walking past his office. Mark waved me in. I sat down, and he immediately started drilling me on the CTO numbers. The number he focused on was R&D as a percentage of revenue. The Broken Benchmark: R&D as a Percentage of Revenue Now, if you've been a regular listener of this show, you know my opinion of that metric. R&D as a percentage of revenue is a meaningless number.2 It is absolutely meaningless. But every public company CEO at an innovation-dependent company, all the tech companies, AI companies, even automotive, they live by this number. It's a number that Wall Street looks at. You have to report it as part of your quarterlies, and from there it's simple math.3 When Mark grilled me, he was focused specifically on the PC group at HP. HP's number at the time for the PC group was about one and a half percent. R&D as a percentage of the PC group's revenue. Acer, which was a key competitor, was at 0.8%. Less than one percent. Roughly half of HP's number.4 Apple was at four percent.5 Mark's question, and he was really pounding on this, was: How do we get our ratios in line with Acer? Basically, he was saying: how do we cut costs so that our R&D expense as a percentage of revenue equals Acer at 0.8%? This is exactly the problem with choosing the wrong metric. Now I'm going to quote somebody who I think was probably one of the most insightful leaders in the business world. Charlie Munger. If you've ever watched any of his talks, he had a really strong opinion on certain metrics. Specifically EBITDA, earnings before interest, taxes, depreciation and amortization. Charlie referred to EBITDA as BS earnings. It was a metric Wall Street swore by, and Munger said it hid more than it revealed. His exact words: "Every time you see the word EBITDA, just substitute the word 'bullshit' earnings."6 R&D as a percentage of revenue is the same problem in a different disguise. It's the metric that makes every company look like it's investing when all it's doing is spending. Mark was using a broken instrument to make a generational decision. If you make decisions based on R&D as a percentage of revenue, and then you do comparisons like "let's make our numbers look like Acer," what you are actually deciding to do is cut your R&D. That is generational. You will destroy a company's innovation capability over the next ten to twenty years before you can even have a hope of rebuilding it.7 "We Are Not Apple and We Never Will Be" I looked at him and said: Why aren't we raising our R&D spend to match Apple? Mark didn't hesitate. He said: "We are not Apple and we never will be." I took offense at that. I was offended that he wouldn't even contemplate it. And I pushed back. I pushed back hard. I argued we could be Apple in areas where we had genuine advantage. Here's one example. Go back to September 2004, about a year before my meeting with Mark. Carly Fiorina was still...
    Más Menos
    14 m
  • The Innovation Metric Bill Hewlett and Dave Packard Used

    The Innovation Metric Bill Hewlett and Dave Packard Used
    Apr 1 2026
    Every public company in the technology industry measures innovation spending the same way. R&D as a percentage of revenue. Why? Because Wall Street tracks it. Boards benchmark it. CEOs get fired over it. And it tells you almost nothing about whether the spending is working. Bill Hewlett and Dave Packard knew that. From the very beginning, they measured something different. Something the rest of the industry has been ignoring for seventy years. And the proof was sitting in a paper that Chuck House pulled out and sent to me after a conversation at a Computer History Museum board meeting. By the end of this episode, you'll know what that metric is, why it works, and why the one everyone else uses makes it nearly impossible to tell whether your innovation investment is building the future or just burning cash. Here's how I found it. The Question That Wouldn't Let Go In the last episode, I talked about the argument with Mark Hurd. The question was over whether HP should cut R&D as a percentage of revenue to match Acer. I knew Mark was fundamentally wrong. But I couldn't prove it. The only metric on the table was R&D as a percentage of revenue. That was what Wall Street expected. It's what shareholders expected. It's what the board expected. But I couldn't argue against it, because I didn't have the data. I needed a better metric. So I decided to go back to the beginning. HP's complete financial records dating back to the 1940s. Division by division. R&D project by R&D project. The actual operating data. I got access to all of it. The HP archive team gave me direct access to Bill and Dave's original notebooks. Now, data alone wasn't enough. It was mountains and mountains of data, and you're trying to extract the signal. What is the trigger in that data? The conversation that cracked it open happened outside HP. The Man with the Medal of Defiance I was at a Computer History Museum board meeting, standing next to Chuck House, and I shared with him the struggle I was having. A little context on Chuck. He spent twenty-nine years at HP. He was the Corporate Engineering Director and he helped launch dozens of products. He's also the recipient, from David Packard himself, of the Medal of Defiance. The Medal of Defiance was given to him because David had told him at one point to kill a product line. Chuck went around that decision, put the product into the catalog, shipped it, and it turned into a phenomenal success. When David gave Chuck the medal, the citation was something along the lines of: "for going above and beyond the stupidity of management and doing what was right." Chuck and Raymond Price co-authored a book called The HP Phenomenon, published by Stanford Press. It's the deep dive into the history of the innovation culture inside HP, all of the metrics used back in the Bill and Dave days that put in place the structure that allowed HP to be successful. By the time I'm at HP, Chuck had long since moved on. He was running Media X at Stanford, the university's research program on innovation, media, and technology. But we both served on the Computer History Museum board. At that board meeting, I shared the argument I'd had with Mark and the search for a better metric. I had a strong feeling there was something around gross margin. That R&D investment impacted gross margin. But a feeling isn't an argument. I needed data. I needed to correlate R&D spend to margin, and that's extraordinarily hard to do when you've got all these different product lines and divisions. Chuck got this little smile on his face and said, "I need to send you something." The Paper and the Whiteboard What he sent me was a paper. A journal paper he and a few of his colleagues had written decades before. And it laid out the connection between research investment and margin performance. The correlation I suspected but couldn't prove was right there on the page. I read it that night. The next morning I emailed Chuck, and I was just really excited. What they'd written decades ago matched what I was finding in the data. That email exchange turned into an invitation. I asked Chuck to come to HP Labs. We met in a conference room in Building 3, the main building for HP Labs at the time. And I'll tell you, I look back on this and it makes me smile a little, because this conference room was just down the hall from Bill and Dave's offices. HP preserved those offices exactly as Bill and Dave left them. You can walk in there today, see their desks, see their offices, just as they were on their last day. There's something about being that close to where it all started that makes the history feel less like history and more like unfinished business. Chuck walked up to the whiteboard and drew two things. On the left side: R&D as a percentage of revenue. The metric every company reports. The metric Mark used to argue HP was overspending. Chuck's point was simple. That metric tells you how much you're spending. That's it. Nothing about whether your ...
    Más Menos
    20 m
  • How to Build a Decision System that Protects Your Thinking

    How to Build a Decision System that Protects Your Thinking
    Mar 10 2026
    The best decision-makers aren't better at deciding. They're better at controlling when, where, and how they decide. It took me twenty years to figure that out. Most people spend that time trying harder: more discipline, more willpower, more resolve to think clearly under pressure. It doesn't work. That's when mindjacking wins. Not through force. Through the door you left unguarded. The answer isn't trying harder. It's building systems that protect your thinking before the pressure hits. By the end of this episode, you'll have four concrete strategies for doing exactly that, and a one-page system you'll build before we're done. And I have something else to share at the end. Something I've been working toward for twenty years. Let's get into it. Why Willpower Fails and Design Works Ulysses knew his ship would pass the island of the Sirens. He also knew the song was irresistible. Sailors who heard it became incapacitated and drove straight into the rocks. He didn't try to be stronger than it. He had his crew fill their ears with wax and tie him to the mast, with strict orders not to release him, no matter what he said when the music reached him. His calm self setting rules for his compromised self. That's the core of everything in this episode. These are called commitment devices. The decision gets made early, when your thinking is clear, before you're tempted to take the wrong path. Studies tracking self-imposed contracts found that when people added meaningful stakes to their commitments, their follow-through nearly doubled. Not because they became more virtuous, but because they'd taken the choice off the table at the moment they were most likely to get it wrong. Stop asking "How do I resist?" Start asking, "What can I decide now, so I don't have to decide under pressure?" Before you can build the right commitments, you need to know exactly where your thinking breaks down. Not decision-making in general. Yours. Finding Your Personal Vulnerability Think back across the last few months. Where did your thinking most clearly cost you? Some people stall. They keep researching past the point of useful information, using "I need more data" as cover for avoiding a commitment they know they need to make. Others make their worst calls at the end of long days. Saying yes when they mean no, because no requires energy they've already spent. Some get caught by urgency. A deadline appears, the pressure closes off their thinking, and they move fast. Only later do they discover the deadline was manufactured to do exactly that. Others walk into a room with a clear position and walk out agreeing with the loudest voice, unable to explain exactly when they shifted. And some defend decisions past the point where the evidence says stop, because stopping would mean admitting something about themselves they're not ready to face. Identify yours. Write it down before we go further. Your primary vulnerability is a design target, not a character flaw. You can't build around something you haven't named. Four Strategies for Protecting Your Judgment Strategy 1: Control When You Decide Every morning I put on the same thing: a black golf shirt, blue jeans, and cowboy boots. Same brands, same routine, no decisions. My wife tolerates it. I've stopped apologizing for it. It's not a fashion choice. It's a cognitive load choice. Your brain has a finite amount of decision-making capacity each day. Every trivial choice draws from the same reserve you need for the decisions that actually matter. What to wear, what to eat, which route to take. Eliminating those choices doesn't just save time. It protects the mental fuel you'll need later. Decision-making capacity isn't flat across the day. It peaks early, when you're rested and fresh. It degrades, measurably, as conditions erode. The same call made at 8 a.m. and at the end of your seventh consecutive meeting aren't equivalent. Same person, different machine. Pull up your calendar from the last two weeks. Look at when your biggest decisions actually happened. For most people, it's not in a calm moment with a clear head. It's in the hallway, on a rushed call, in the last fifteen minutes of a meeting that ran over. That's not bad luck. That's the default you haven't changed yet. Write a standing rule: no significant, hard-to-reverse commitments after a certain hour or after a certain number of back-to-back meetings without a mandatory pause. Hold it like a policy, not a preference. Because preferences are exactly what disappear under the conditions where you need them most. Strategy 2: Build Your Kitchen Cabinet One of the things I credit most for whatever success I've had in my career isn't a framework or a methodology. It's four people. I call them my kitchen cabinet. They've seen my best decisions and my worst ones. They know when I'm rationalizing. They know when I'm avoiding. And they are not afraid to call me out when I'm off the tracks. Here's what surprises people when I describe them. ...
    Más Menos
    25 m
Todavía no hay opiniones