Couverture de The Innovators Studio with Phil McKinney

The Innovators Studio with Phil McKinney

The Innovators Studio with Phil McKinney

De : Phil McKinney
Écouter gratuitement

Offres de saison | 0,99 € par mois pendant les 3 premiers mois

5,99 €/mois par la suite. Des conditions s’appliquent. Annulation mensuelle possible.
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 Direction Développement personnel Economie Management et direction Réussite personnelle
Épisodes
  • Mastering Critical Thinking in the Age of AI

    Mastering Critical Thinking in the Age of AI
    Oct 28 2026
    I asked two AIs one question, and both missed their own future. That's a critical thinking problem for anyone who uses AI. I asked them: "Take a look at consumer electronics and identify the top five unsolved problems that could become disruptions if a solution could be found." Here's what came back. Grok saw problems to fix, like phones built so you can't repair them. Claude saw opportunities to build, like AR glasses you'd wear all day. Same question, two different ways of seeing the industry, and each one read like the final answer. With AI, critical thinking comes down to three checks. And later, I'll have one of these AIs argue against my own pick. It landed a couple of punches. Let's get into it. Check 1: Cross-Check With a Second AI In my first video on critical thinking skills, one of the first steps was to cross-reference your sources. It still works. With AI, you cross-reference by asking a second AI the same question. Then read the two answers three ways. Where they overlap, you have a stronger signal. Battery was number one on both lists. That's the one I'd look at first. Where they split, your judgment starts. Grok: repair, software that kills devices, heat that limits on-device AI, and devices that won't connect.Claude: AR glasses, health sensing, memory costs, and trust in always-on devices. Both lists are defensible. Deciding which matters is your job. What's missing from both is the blind spot. That's where your own experience counts most. Here's what I'd have put on the list: agents that reliably act for you. The unsolved part is trust-grade reliability. An agent that's usually right can't be handed your money or your calendar. Solve that, and you stop opening apps. The agent does it for you, and the app store loses its cut. Two AIs, asked for the next big disruption, and both missed AI agents. Not very self-aware. That's a bigger deal than it sounds. In the early days, AI made things up. Fake sources. Fake people. Quotes nobody ever said. I learned to ask: what else is it making up? Today's models make up far less. The new problem is harder to spot. You get one confident answer to a question that has many good answers. It sounds finished, so you stop looking. That moment has a name. I call it mindjacking. This is the first in a series on thinking clearly in the age of AI. If that's useful, subscribe so you catch the next one. Check 2: Find the Hidden Assumptions In my first video, this was questioning assumptions. With AI, every answer starts from an assumption it doesn't tell you about. Grok's was right there in its first lines: "Consumer electronics is not short of features. It is short of physics and incentives." Everything after that was about what's broken. Claude started from what's next to build. You only find the hidden assumption if you ask. So after any answer that matters, paste this in: "What assumptions did you make? Now answer from the opposite starting point." So I did, and Grok rethought its whole answer. Its first line: "The last answer assumed the user's pain was the industry's unsolved problem." Then it listed what it had taken for granted. That people want phones they can repair. That upgrading every two or three years is a design failure, when it's what people keep paying for. Flipped, it gave me a different list: Getting a new device onto the shelf.A reason to switch when your photos and accounts live somewhere else.Who pays for the AI. Most of it wasn't on either list. And look what still isn't there. Agents. Your own assumptions count too, because the way you ask carries them. State an opinion and AI tends to lean your way. So ask, don't tell. "What are the risks of launching in March?" gets you more than "We should launch in March, right?" That prompt, and the others in this episode, are in a free checklist with a worksheet. Download it below. Check 3: Separate Evidence From Opinion In my first video, this was applying logic and avoiding fallacies. AI adds a new fallacy: clear, confident writing feels like clear, confident reasoning. Grok gave me repair grades, e-waste tonnage, and a compliance rate, with no sources attached. They read like facts. I checked. They held up. That time. Today's models make up far less, but far less isn't never. When an AI gives you a fact, a number, or a quote you plan to repeat, check it first. The first time, Grok was sure repair was the problem. The second time, it said sealed, "it just works" devices win "in every mass market that has been offered both." Every market. Same AI, opposite answer, same certainty. How sure it sounds tells you nothing about whether it's right. Some answers will tell you where the evidence ends. Claude labeled its fifth item: "This is my own judgment rather than something the sources rank." Grok's answer never separated fact from opinion. When it matters, ask: Which of this is evidence, and which is your judgment? And give it permission to disagree. I use AI every day, and I tell it: be brutally ...
    Afficher plus Afficher moins
    15 min
  • Why I Cried on Stage as a CEO

    Why I Cried on Stage as a CEO
    Oct 14 2026
    I cried on stage this week, in front of thousands of people. In front of the entire industry. The press in the room wrote about it. I couldn't believe it. Some people will tell you it isn't becoming for a CEO to cry in public, much less in front of the entire industry. They'll tell you it isn't good executive presence. So let me explain what happened in Atlanta last week. Let's get into it. On the Main Stage in Atlanta Last Tuesday I was in Atlanta for SCTE TechExpo, on the main stage for the opening session. Three of us were on stage: Chris Winfrey, chairman of the CableLabs board and chairman and CEO of Charter Spectrum; Mark Bridges, who takes over as CEO of CableLabs in January; and me. Let me give you a little context on how I got here. I was previously the CTO at HP, and I left at the end of 2011 thinking I was retiring. A week later, CableLabs called. Over the next five months, retiring turned into moving to Colorado to run CableLabs. I didn't come from cable. That wasn't my background. I'm grateful the board took a chance on an outsider, and glad I said yes when I wasn't sure what I was jumping into. The last two times I retired, from Teligent after the IPO and from HP, the next role came looking for me. This time, if anyone comes looking, I'll tell you right now: the answer is no. Innovation Is a Team Sport I've said this many times, here on the show and in the innovation boot camp courses I teach. Innovation is a team sport. That means the CableLabs team, the operators who fund the research lab, and our vendor partners. We could not have achieved our success without that community and the effort of everybody in it. Some of the articles are highlighting things that happened over my fourteen years, but none of it happened because of one person. This is by far the best job I have ever had, bar none. That's also why it is so hard to step away. That's what hit me on stage. It felt like I was saying goodbye to an industry and a CableLabs team I've been part of for fourteen years. Then I looked over and saw my grandson in the front row. Good Succession Plans Take Time I never wanted to be the leader gripping the desk, where someone has to pry his fingers off and push him out the door. I wanted to make the transition when I felt my successor was ready. Good transitions are not single events. It isn't the press release where you announce the new person and ride off into the sunset. A good succession plan is deliberate, and it takes time. Ours started 18 months ago, with me talking to the board of directors about my personal intent and about who I felt was ready. At CableLabs, we run a world-class succession process. For the last eight years, we've met with the board once a year and reviewed successors for every executive function at CableLabs. So the board knew our bench, how deep it was, and our plan to prepare people to step up into the next role. Mark Bridges is my successor as CableLabs CEO, and he is absolutely the right guy. He's been with CableLabs longer than I have - 16 years - and we've worked as a team for a decade. He's been our CTO for the last three years, and on August 1, he became president. He knows the organization and the CEOs of all our member companies. The board is unanimously united behind him, and so am I. I'm handing off roles and functions as we go, so that on January 1 he takes over the CEO title. I've also committed to both the board and Mark that I'll stay available to advise them throughout 2027. Who Is Ready to Step In for You? Let me ask you a question. If you left your role in 90 days, who is ready to step in and take on your function? If you think holding on to information makes you harder to replace, you're thinking it wrong. Strong leaders plan for their succession. You may have to leave for a medical reason or a family reason. Either way, you do not want to leave your organization in the lurch. So, who is ready? If you don't have anybody, start working on it now. The other question: which relationships exist only in your head or on your phone? Are you hoarding them, or are you sharing them with the person you've identified as your successor? If you want to be remembered as a model leader long after your career, leave the organization stronger than you found it, and hand it to somebody ready to take it further. Why Now? The question everybody asks is, why now, Phil? Why retire now? Age is part of it. I'm 66. But the real reason is my grandkids. I have five, ages 10 to 14, and I want to go do things with them. The oldest leaves for college in a handful of years, and I know how fast that clock runs. My 14 years at CableLabs flew by, and the years are going even faster now. I want to spend the time I have left with them. What's Next What I'm committing myself to is building the next generation of innovators. The YouTube channel and the podcast are staying. That's my investment in innovators out in the world. I'm also making that investment at ...
    Afficher plus Afficher moins
    13 min
  • How To Build Innovation Teams (My Playbook From HP and CableLabs)

    How To Build Innovation Teams (My Playbook From HP and CableLabs)
    Sep 23 2026
    Why do people believe you can build an innovation team by hiring a few smart people and giving them a creative space? In my experience, teams built on this false premise die within eighteen months. How do organizations get it so wrong? Innovation consultants have told them, or innovation books have taught them, that this is how you build an innovation team. Those experts have rarely built and led innovation teams that delivered. So why is this episode any different? I built and ran HP's Innovation Program Office (IPO), and the teams I led there were named to Fast Company's Most Innovative list three years running. For the last fourteen years, I've run CableLabs, the research and innovation lab for the global broadband industry, where our teams build technology that half a billion people use every day. This episode is about what it takes to build innovation teams, based on my experience doing it at scale—multiple times. By the end, you'll have the six steps I use, in the order they have to happen, what goes wrong when a team skips one, and a way to score your team today. I'll start with a decision I almost got wrong. In 2007, I was about to approve a 20 percent time policy at HP. Under what is called "20 percent time", employees spend about one day a week, a fifth of their working hours, on projects of their own choosing. Google had made it famous; everyone was talking about it, and it looked like the answer. Chuck House stopped me. Chuck had spent decades at HP working for Dave Packard, who founded the company with Bill Hewlett. "Before you do anything," he said, "you need to talk to Art." Art Fong was HP employee number nine. When I sat down with him, he told me something I didn't know. HP had already tried 20 percent time. In the 1950s. The company had watched Art work on his own ideas on Friday afternoons, so it gave everyone Friday afternoons. Most people sat around not knowing what to do with the time, and HP dropped it. "The ones who were going to innovate, like me, were already doing it," Art told me. "The mandate didn't change behavior." That was the lesson. You can't order people to innovate. The people who will innovate are already trying, and your job is to find them and clear the way. I never approved the policy. Google killed its "20% time" policy in 2013. What Art told me next shaped every innovation team I built after that, and we'll keep coming back to Art and his story. Let's get into it. The Innovation Team Fallacy The innovation team fallacy is the belief that if you hire smart people and give them a creative space, innovation will follow. It's easy to believe, because every successful innovation team you've read about had smart people and a place to work. That's the part you can see from the outside. What you can't see is what had to be in place before the work began. There's a second version of it, and it's the mistake I almost made with 20 percent time: copying what worked at another company and expecting it to work at yours. I'll come back to that later, with the story of a company that learned it the hard way. Teams also fail when you build the pieces in the wrong order. Get the order wrong, and it doesn't matter how talented the people are. Here are the six steps, in the order they have to happen: Build the culture before you hire anyone Recruit for specific roles, not just talent Adapt the process, don't adopt someone else's Fund it like innovation, not like operations Measure what keeps leadership bought in Lead it day to day Step 1: Build the Culture Before You Hire Anyone Culture is how people behave when nobody is telling them what to do, especially when something goes wrong. New hires don't learn it from what you say, or from the employee handbook. They learn it from what they see. Art Fong didn't describe HP's culture with a policy. He taught me through stories. One weekend, Bill Hewlett found a manager had locked the tool room with a padlock. Bill came back with bolt cutters, cut the lock off, and left a signed note on the door: "Never lock this again." He wanted his engineers to get to parts and equipment whenever an idea hit them. The note told every engineer at HP that the founders would remove anything that stood between them and their next idea. When Art tried to buy a house in Palo Alto, and discrimination stood in the way, Bill and Dave bought it from the seller themselves and sold it to him. No memo or values poster builds that kind of trust. It's built by what leaders do. Three things have to be in place before you hire your first person. Permission to fail without penalty. Innovation means working on ideas that are too early, too unusual, or too risky for the company's normal processes. Most of them won't work, and nobody brings you ideas like that if failure costs them. People watch what happens to the first person whose project gets stopped. If that person's next performance review takes a hit, your team stops proposing anything that might fail. ...
    Afficher plus Afficher moins
    38 min
adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment