Letting Go of Perfectionism—Learning to Prioritize in Product Management

In this episode of “Product Excellence: Insights from Award-Winning Leaders | Strategies for Success,” Jenna Gaudio shares her journey from being a detail-oriented perfectionist to learning the importance of prioritization in product management. She discusses the challenges of managing an ever-growing backlog and the value of focusing on current priorities rather than trying to complete every task. If you’re struggling with perfectionism in your product role, this episode offers key lessons in letting go and focusing on impact.

🔑 What You’ll Learn:

  • The Backlog Myth: Why striving for an “empty backlog” is an impossible and misguided goal.
  • Prioritization Over Perfection: How focusing on what truly matters leads to better product decisions.
  • Letting Go of the Past: Why older backlog items often lose relevance as new insights emerge.

🔔 Subscribe for more expert insights from leading product managers: https://www.youtube.com/theproductway

P.S. Want even more?
Join The Product Way on Patreon for full-length discussions with Jenna Gaudio and other award-winning product leaders, plus exclusive content you won’t find on any other platform. 👉 Unlock strategies, case studies, and more: https://www.patreon.com/theproductway

Connect with Us:

About the Podcast:

Product Excellence: Insights from Award-Winning Leaders | Strategies for Success
“Product Excellence: Insights from Award-Winning Leaders | Strategies for Success” brings you behind the scenes with the top product management minds who have shaped some of the world’s most successful products. Each episode features award-winning product leaders sharing their real-world experiences, lessons learned, and the strategies that have driven their success. From building innovative digital products to navigating the complexities of stakeholder management, you’ll hear firsthand how these experts have achieved product excellence. Whether you’re an aspiring product manager or a seasoned leader, this podcast offers valuable insights, actionable takeaways, and inspiration to elevate your product management career.   Tune in WEEKLY to discover the key strategies that make products—and product leaders—truly exceptional.

Leading Product for Media Giants & Banking Innovators

In this episode of “Product Excellence: Insights from Award-Winning Leaders,” we sit down with David Clements, the product lead for Wireless, home to major UK radio stations like talkSPORT and Virgin Media. David has a rich history in both media and finance, having also led product for The Sun newspaper and worked on mobile banking apps for the Royal Bank of Scotland and Barclays. Tune in as he discusses the unique challenges and rewards of building mobile apps for both industries, and how he’s navigated the evolving landscape of product management across multiple sectors.

🔑 What You’ll Learn:

  • Leading Media Product Development: David’s role in mobile apps for national radio stations under Wireless and News UK.
  • Experience with Global Media Brands: Insights from managing products for The Sun and other leading publications.
  • Mobile Banking Expertise: How David applied product management skills at top UK banks like RBS and Barclays.

🔔 Subscribe for more expert insights from leading product managers: https://www.youtube.com/theproductway

P.S. Want even more?
Join The Product Way on Patreon for full-length discussions with David Clements and other award-winning product leaders, plus exclusive content you won’t find on any other platform. 👉 Unlock strategies, case studies, and more: https://www.patreon.com/theproductway

Connect with Us:

About the Podcast:

Product Excellence: Insights from Award-Winning Leaders | Strategies for Success
“Product Excellence: Insights from Award-Winning Leaders | Strategies for Success” brings you behind the scenes with the top product management minds who have shaped some of the world’s most successful products. Each episode features award-winning product leaders sharing their real-world experiences, lessons learned, and the strategies that have driven their success. From building innovative digital products to navigating the complexities of stakeholder management, you’ll hear firsthand how these experts have achieved product excellence. Whether you’re an aspiring product manager or a seasoned leader, this podcast offers valuable insights, actionable takeaways, and inspiration to elevate your product management career.   Tune in WEEKLY to discover the key strategies that make products—and product leaders—truly exceptional.

Evolving Product Processes—Focusing on Principles and Flexibility

In this episode of “Product Excellence: Insights from Award-Winning Leaders | Strategies for Success,” Harpal Singh explains his approach to managing product processes by emphasizing principles over rigid methods. He discusses how prioritizing customer insights, collaboration, and data helps unlock better results for teams. Harpal shares examples of how companies can break free from overly linear or rigid processes and focus on real business outcomes. If you’re looking to refine your product management approach, this episode offers practical strategies.

🔑 What You’ll Learn:

  • Rethinking Processes: Why focusing on principles and outcomes beats rigid workflows.
  • Common Pitfalls in Product Teams: How teams can fall into delivery or process traps.
  • Customer Insights vs. Assumptions: How to ensure true customer obsession drives decisions.
  • Adapting with Agility: The importance of simplicity and collaboration over complex systems.

🔔 Subscribe for more expert insights from leading product managers: https://www.youtube.com/theproductway

P.S. Want even more?
Join The Product Way on Patreon for full-length discussions with Harpal Singh and other award-winning product leaders, plus exclusive content you won’t find on any other platform. 👉 Unlock strategies, case studies, and more: https://www.patreon.com/theproductway

Related Links:

Connect with Us:

About the Podcast:

Product Excellence: Insights from Award-Winning Leaders | Strategies for Success
“Product Excellence: Insights from Award-Winning Leaders | Strategies for Success” brings you behind the scenes with the top product management minds who have shaped some of the world’s most successful products. Each episode features award-winning product leaders sharing their real-world experiences, lessons learned, and the strategies that have driven their success. From building innovative digital products to navigating the complexities of stakeholder management, you’ll hear firsthand how these experts have achieved product excellence. Whether you’re an aspiring product manager or a seasoned leader, this podcast offers valuable insights, actionable takeaways, and inspiration to elevate your product management career.   Tune in WEEKLY to discover the key strategies that make products—and product leaders—truly exceptional.

The Search for the Perfect Product Management Tool

In this episode of “Product Excellence: Insights from Award-Winning Leaders | Strategies for Success,” Jenna Gaudio discusses her struggles with finding a product management tool that balances both high-level strategy and detailed task management. She explains how most tools are either too simple or too complex and fail to communicate the full story of a company’s progress. If you’ve been frustrated by the limitations of roadmapping software, this episode offers insightful reflections on what’s needed in the market.

🔑 What You’ll Learn:

  • The Challenge with Tools: Why existing systems fail to tie strategy, roadmaps, and tasks together effectively.
  • The Complexity of Roadmapping: How roadmapping tools struggle to balance simplicity and depth.
  • What Executives Need: Insights into the gaps in tools for managing company-wide roadmaps and progress.

🔔 Subscribe for more expert insights from leading product managers: https://www.youtube.com/theproductway

P.S. Want even more?
Join The Product Way on Patreon for full-length discussions with Jenna Gaudio and other award-winning product leaders, plus exclusive content you won’t find on any other platform. 👉 Unlock strategies, case studies, and more: https://www.patreon.com/theproductway

Related Links:

Connect with Us:

About the Podcast:

Product Excellence: Insights from Award-Winning Leaders | Strategies for Success
“Product Excellence: Insights from Award-Winning Leaders | Strategies for Success” brings you behind the scenes with the top product management minds who have shaped some of the world’s most successful products. Each episode features award-winning product leaders sharing their real-world experiences, lessons learned, and the strategies that have driven their success. From building innovative digital products to navigating the complexities of stakeholder management, you’ll hear firsthand how these experts have achieved product excellence. Whether you’re an aspiring product manager or a seasoned leader, this podcast offers valuable insights, actionable takeaways, and inspiration to elevate your product management career.   Tune in WEEKLY to discover the key strategies that make products—and product leaders—truly exceptional.

Why Most Product Managers Struggle—And 3 Ways to Finally Get Ahead

Being a product manager often feels like solving a puzzle without all the pieces. From aligning stakeholders to prioritizing features, the challenges are endless—and so are the opportunities for growth. Here are three actionable strategies to tackle some of the biggest hurdles product managers face today.

1. Move From Tasks to Outcomes

It’s easy to get caught up in day-to-day tasks, but the best product managers stay laser-focused on outcomes. When faced with a long list of potential features or bug fixes, ask:

  • What’s the problem we’re solving?
  • How does this align with our overall goals?
  • What’s the smallest thing we can deliver to test this idea?

Outcome-focused thinking doesn’t just create better products—it builds trust with stakeholders who see you driving results that matter.

2. Make Prioritization a Team Sport

Prioritization is one of the hardest skills to master, especially when everyone thinks their request is urgent. The trick? Bring stakeholders into the process.

  • Use frameworks like RICE (Reach, Impact, Confidence, Effort) to create a shared language around decisions.
  • Set clear boundaries early so everyone understands what’s realistic.
  • Collaborate transparently—show your reasoning and invite feedback, but be firm when needed.

Involving others in prioritization doesn’t just make your job easier; it strengthens relationships and ensures everyone feels heard.

3. Invest in the Right Tools and Resources

No one succeeds in product management alone. The tools and resources you use can make or break your ability to deliver.

  • Templates and frameworks can save hours of reinventing the wheel.
  • Expert-led videos and workshops can provide fresh perspectives on tackling challenges.
  • A strong community of peers can offer support, advice, and inspiration.

This is exactly why I created The Product Way Patreon. It’s a space where product managers can access practical tools, actionable insights, and a supportive community to help navigate the challenges of our profession.

Take Action Today

These strategies—focusing on outcomes, making prioritization collaborative, and leveraging the right resources—can help you tackle today’s challenges with confidence. Whether you’re new to product management or stepping into leadership, the key is to keep learning and adapting.

If you’re looking for more ways to grow, The Product Way Patreon is a resource I’m excited to share. It’s designed to help product managers at every stage with exclusive content, tools, and opportunities to connect with others in the field.

👉 Check it out here

Product Managers Misunderstood: We Don’t ‘Rule’ Silicon Valley—We Navigate Its Complexities

I’ve never felt compelled to write a rebuttal before, but Amanda Hoover’s recent article, “Product managers rule Silicon Valley. Not everyone is happy about it,” misses the mark on what product management truly entails. As someone who has spent decades in this field, I’ve seen firsthand how product managers are often misunderstood and misrepresented—and this article perpetuates many of those misconceptions.

Amanda’s article opens with a premise that is as laughable as it is disconnected from the reality of product management. I’ve never met a single, halfway decent, product manager who felt they “ruled” their product, much less Silicon Valley. The criticisms raised in the article—many of which stem from anecdotal frustrations and surface-level observations—overshadow the reality of a role that has become indispensable in delivering value to customers and businesses alike. The reality of product management is far from the commanding caricature the title suggests.

Rather than rulers, product managers are navigators—balancing the competing demands of customers, engineers, designers, sales teams, and executives to ensure the right product gets built for the right reasons. It’s a job that requires influence without authority, empathy without favoritism, and vision without control. Far from being a reign, it’s a balancing act, often under pressure and scrutiny from every direction.

Mischaracterizing PMs as all-powerful “mini-CEOs” or obstacles to engineering progress grossly oversimplifies and undervalues a role that is critical to innovation and delivering meaningful customer value. This article perpetuates a narrative that overlooks the strategic, connective, and customer-focused value that product managers provide to organizations of all sizes.

It’s time to set the record straight. Let’s address these misconceptions head-on.

1. Mischaracterizing Product Managers as ‘Mini-CEOs’

Amanda perpetuates the idea that product managers see themselves as “mini-CEOs.” While this term is often used, it’s a misnomer that undermines the collaborative nature of the role. Product managers don’t wield the top-down authority that CEOs do; instead, they lead through influence, alignment, and empathy. Far from dictating terms, PMs serve as facilitators, synthesizing input from engineers, designers, marketers, and other stakeholders to ensure that products meet customer needs and business objectives.

The reality is that PMs are accountable for outcomes without direct control over the teams executing the work—a challenging dynamic that demands exceptional communication, trust-building, and prioritization skills.

2. Oversimplifying Tensions with Engineers

The article leans heavily on the notion that product managers create friction with engineers by questioning decisions or slowing down progress. While such conflicts can arise, they are not inherent to the role—they reflect poor performance by ineffective PMs. A PM who creates unnecessary friction or fails to collaborate constructively isn’t fulfilling their responsibilities and shouldn’t remain in the role—just as with any other position.

Good PMs foster mutual respect, maintain open communication, and ensure that engineers have the context they need to succeed while making sure everyone feels heard and valued. They work collaboratively to ensure that products solve real problems and deliver value.

In fact, PMs are partners to engineers, working alongside them to ensure that the product not only functions well but also resonates with users. The narrative of PMs as meddling outsiders fails to capture this essential partnership.

3. Overlooking the Strategic Value of PMs

Amanda’s account focuses on operational aspects like attending meetings and juggling stakeholder demands but overlooks the strategic core of product management. PMs are not mere “task managers”; they are the custodians of a product’s vision. By defining priorities rooted in market research, user insights, and business goals, PMs ensure that development efforts deliver meaningful impact. Without this strategic guidance, companies risk building technically impressive products (e.g., “powered by AI”) that fail to solve real customer problems.

Critiques labeling PMs as a “useless role,” often found on platforms like Reddit and Blind, stem from a misunderstanding of the macro-level value PMs bring. These comments, while provocative, are anecdotal and underrepresent the broader impact PMs have on product success.

4. Misrepresenting Product Management as Easy or Superfluous

The perception that PMs “steal a living” or could be easily replaced by roles in other departments significantly undervalues the unique skill set the role demands. After all, who hasn’t, at some point, thought, I could do that person’s job—whether it’s the CEO, a sales lead, or a designer? But the reality of any role, including product management, is always far more complex than it appears from the outside.

PMs must:

  • Navigate ambiguous, high-stakes decisions with limited information.
  • Balance conflicting priorities across diverse stakeholders.
  • Translate abstract business goals into actionable plans.
  • Keep the customer at the forefront while managing organizational dynamics.

The suggestion that engineers, marketers, or others could “do the job in addition to theirs” dismisses the inherent complexity of product management. This misconception often stems from a misunderstanding of the role and typically points to flawed organizational structures or poor execution—not the necessity or value of the role itself.

5. Missing the True Challenge: Bad Product Management vs. No Product Management

The real issue in companies where product managers are seen as ineffective is often bad product management—not a lack of need for PMs.  A misaligned or underperforming PM can create significant frustration, but the solution lies in improving hiring, training, and role clarity—not removing PMs altogether. Writing off the entire profession due to isolated failures is as illogical as declaring “engineers are unnecessary” because of poorly written code.

6. Failing to Recognize the Role’s Evolution and Importance in AI

Amanda acknowledges that AI will elevate the importance of PMs, but she fails to connect this to the unique challenges of managing innovation in an AI-driven era. As AI transforms industries, the PM’s role in understanding customer needs, ethical considerations, and long-term implications becomes even more critical. Engineers may build AI solutions, but PMs ensure those solutions solve meaningful problems and align with human values.

In Summary

Amanda’s article captures some of the criticism product managers face, but it fails to provide a balanced or informed view of their true function. By reducing the role to a parody of inefficiency and conflict, it overlooks the profound impact that PMs have on driving innovation, aligning teams, and delivering value to customers.

Let’s be clear—part of the blame also lies within the field of product management itself. The profession has long struggled to clearly define its role and articulate its value, leaving it vulnerable to misunderstanding and misrepresentation. I hope this article serves as a step toward addressing these challenges and fostering a clearer, more accurate understanding of both what product managers truly contribute — and what they are not.

Product managers are not the “mini-CEOs” or “fluff creators” that some may perceive them to be. They are the connective tissue of organizations, ensuring that products are not only built, but built with purpose. We would all be better served by focusing not on questioning the necessity of the role, but on addressing the gaps within the profession—by better defining it, cultivating stronger PMs, and emphasizing the significant impact they make when the job is done well.

Jeremy Horn
The Product Guy

Overcoming Challenges in Stakeholder Management: Strategies for Navigating High-Stakes Decisions

In the first part of this series, we explored the fundamentals of stakeholder dynamics, focusing on communication, influence, and transparency. However, product managers often face even greater challenges when navigating high-stakes situations with senior leadership or dealing with conflicting priorities across departments. These moments can be politically challenging, as they require balancing the immediate demands of stakeholders with long-term product goals.

Even with best practices in place, product managers often face controversial and uncomfortable challenges when managing stakeholders.  In this second part, we’ll dive into some of the more difficult and contentious aspects of stakeholder management. From handling feature requests that lack customer validation to managing unrealistic expectations, we’ll discuss practical strategies to maintain alignment and avoid common pitfalls. Through these insights, you’ll be better equipped to handle the pressures of managing up and leading your product toward success.

1. Feature Requests from Top-Level Management

One of the most contentious situations product managers face is dealing with feature requests that come directly from senior leadership. Often, these requests are made without supporting data or customer feedback, which can create tension between PMs and top-level executives. The CEO may want to introduce a new feature to impress investors, or a VP might suggest something based on personal preferences, despite little alignment with product goals.

Suggested Solution: The key is to respectfully push back when necessary. Use data to support your position and explain the trade-offs. For instance, if you’re asked to prioritize a feature that isn’t solving a customer problem, present research showing how the feature would impact user experience or how alternative features better serve your market. However, when push comes to shove, it’s also important to know when to compromise for the sake of maintaining relationships with key stakeholders.

2. Conflicting Priorities Between Teams

Another common challenge is when different departments have conflicting priorities. Engineering may want to focus on technical debt, while marketing wants to accelerate a product launch. As a PM, you’re often stuck in the middle, tasked with balancing both needs.

Suggested Solution: The best way to handle this is by facilitating conversations that bring all stakeholders to the table. Use these discussions to identify common goals and areas of compromise. By aligning on shared business objectives, you can guide teams toward decisions that benefit the broader product strategy.

3. Managing Unrealistic Expectations

Stakeholders often have high expectations for product timelines or the potential impact of new features. Sometimes, these expectations are simply not achievable given resource or time constraints.

Suggested Solution: Managing expectations early is crucial. Be upfront about what’s realistic and provide clear timelines. If a certain feature or initiative is expected to take longer than leadership would like, explain the reasons behind the delay. Being proactive in addressing concerns helps mitigate frustration down the road.

Navigating with Empathy and Strategy

Managing stakeholder dynamics, especially when navigating contentious or high-pressure situations, is one of the most challenging yet rewarding aspects of product management. Whether it’s pushing back on feature requests from senior leadership or balancing conflicting priorities across teams, the ability to influence without authority and drive alignment is crucial.

By staying data-driven, fostering transparency, and strategically managing expectations, product managers can turn even the most controversial situations into opportunities for growth and collaboration. Ultimately, the key is to remain adaptable and solution-oriented, ensuring that the product vision is realized while keeping stakeholders engaged and invested in its success.

With the right approach, even the toughest stakeholder challenges can lead to stronger partnerships, clearer strategies, and a more cohesive product direction.

How do you navigate these dynamics in your role, and what strategies have you found most effective?

Feel free to share your insights and experiences in the comments below!

Interested in more?

We recently discussed this topic and much more on at a recent TPG Live roundtable discussion.  Watch the replay here: https://youtube.com/live/IgwwPxPJk1U

And don’t forget to mark your calendars for our next TPG Live session on November 7th at 7 PM ET, where we will be exploring “Beyond IC & Introducing Product.” You can RSVP here: RSVP for the Next Event. Even if you can’t attend live, RSVP to receive a recap and a link to the recording afterwards.

What’ Next?

Read part 1 of this 2 part series where we explored: “Navigating Stakeholder Dynamics in Product Management: Practical Insights

Quantum Computing – An Update

In March 2022 I wrote a description of the Quantum Technology Ecosystem. I thought this would be a good time to check in on the progress of building a quantum computer and explain more of the basics.

Just as a reminder, Quantum technologies are used in three very different and distinct markets: Quantum Computing, Quantum Communications and Quantum Sensing and Metrology. If you don’t know the difference between a qubit and cueball, (I didn’t) read the tutorial here.

Summary –

  • There’s been incremental technical progress in making physical qubits
  • There is no clear winner yet between the seven approaches in building qubits
  • Reminder – why build a quantum computer?
  • How many physical qubits do you need?
  • Advances in materials science will drive down error rates
  • Regional research consortiums
  • Venture capital investment FOMO and financial engineering

We talk a lot about qubits in this post. As a reminder a qubit – is short for a quantum bit. It is a quantum computing element that leverages the principle of superposition (that quantum particles can exist in many possible states at the same time) to encode information via one of four methods: spin, trapped atoms and ions, photons, or superconducting circuits.

Incremental Technical Progress
As of 2024 there are seven different approaches being explored to build physical qubits for a quantum computer. The most mature currently are Superconducting, Photonics, Cold Atoms, Trapped Ions. Other approaches include Quantum Dots, Nitrogen Vacancy in Diamond Centers, and Topological.  All these approaches have incrementally increased the number of physical qubits.

These multiple approaches are being tried, as there is no consensus to the best path to building logical qubits. Each company believes that their technology approach will lead them to a path to scale to a working quantum computer.

Every company currently hypes the number of physical qubits they have working. By itself this is a meaningless number to indicate progress to a working quantum computer. What matters is the number of logical qubits.

Reminder – Why Build a Quantum Computer?
One of the key misunderstandings about quantum computers is that they are faster than current classical computers on all applications. That’s wrong. They are not. They are faster on a small set of specialized algorithms. These special algorithms are what make quantum computers potentially valuable. For example, running Grover’s algorithm on a quantum computer can search unstructured data faster than a classical computer. Further, quantum computers are theoretically very good at minimization / optimizations /simulations…think optimizing complex supply chains, energy states to form complex molecules, financial models (looking at you hedge funds,) etc.

It’s possible that quantum computers will be treated as “accelerators” to the overall compute workflows – much like GPUs today. In addition, several companies are betting that “algorithmic” qubits (better than “noisy” but worse than “error-corrected”) may be sufficient to provide some incremental performance to workflows lie simulating physical systems. This potentially opens the door for earlier cases of quantum advantage.

However, while all of these algorithms might have commercial potential one day, no one has yet to come up with a use for them that would radically transform any business or military application. Except for one – and that one keeps people awake at night. It’s Shor’s algorithm for integer factorization – an algorithm that underlies much of existing public cryptography systems.

The security of today’s public key cryptography systems rests on the assumption that breaking into those keys with a thousand or more digits is practically impossible. It requires factoring large prime numbers (e.g., RSA) or elliptic curve (e.g., ECDSA, ECDH) or finite fields (DSA) that can’t be done with any type of classic computer regardless of how large. Shor’s factorization algorithm can crack these codes if run on a Quantum Computer. This is why NIST has been encouraging the move to Post-Quantum / Quantum-Resistant Codes.

How many physical qubits do you need for one logical qubit?
Thousands of logical qubits are needed to create a quantum computer that can run these specialized applications. Each logical qubit is constructed out of many physical qubits. The question is, how many physical qubits are needed? Herein lies the problem.

Unlike traditional transistors in a microprocessor that once manufactured always work, qubits are unstable and fragile. They can pop out of a quantum state due to noise, decoherence (when a qubit interacts with the environment,) crosstalk (when a qubit interacts with a physically adjacent qubit,) and imperfections in the materials making up the quantum gates. When that happens errors will occur in quantum calculations. So to correct for those error you need lots of physical qubits to make one logical qubit.

So how do you figure out how many physical qubits you need?

You start with the algorithm you intend to run.

Different quantum algorithms require different numbers of qubits. Some algorithms (e.g., Shor’s prime factoring algorithm) may need >5,000  logical qubits (the number may turn out to be smaller as researchers think of how to use fewer logical qubits to implement the algorithm.)

Other algorithms (e.g., Grover’s algorithm) require fewer logical qubits for trivial demos but need 1000’s of logical qubits to see an advantage over linear search running on a classical computer. (See here, here and here for other quantum algorithms.)

Measure the physical qubit error rate.

Therefore, the number of physical qubits you need to make a single logical qubit starts by calculating the physical qubit error rate (gate error rates, coherence times, etc.) Different technical approaches (superconducting, photonics, cold atoms, etc.) have different error rates and causes of errors unique to the underlying technology.

Current state-of-the-art quantum qubits have error rates that are typically in the range of 1% to 0.1%. This means that on average one out of every 100 to one out of 1000 quantum gate operations will result in an error. System performance is limited by the worst 10% of the qubits.

Choose a quantum error correction code

To recover from the error prone physical qubits, quantum error correction encodes the quantum information into a larger set of physical qubits that are resilient to errors. Surface Codes is the most commonly proposed error correction code. A practical surface code uses hundreds of physical qubits to create a logical qubit.  Quantum error correction codes get more efficient the lower the error rates of the physical qubits. When errors rise above a certain threshold, error correction fails, and the logical qubit becomes as error prone as the physical qubits.

The Math

To factor a 2048-bit number using Shor’s algorithm with a 10-2 (1% per physical qubit) error rate:

  • Assume we need ~5,000 logical qubits
  • With an error rate of 1% the surface error correction code requires ~ 500 physical qubits required to encode one logical qubit. (The number of physical qubits required to encode one logical qubit using the Surface Code depends on the error rate.)
  • Physical cubits needed for Shor’s algorithm= 500 x 5,000 = 5 million

If you could reduce the error rate by a factor of 10 – to 10-3 (0.1% per physical qubit,)

  • Because of the lower error rate, the surface code would only need ~ 100 physical qubits to encode one logical qubit
  • Physical cubits needed for Shor’s algorithm= 100 x 5,000 = 500 thousand

In reality there another 10% or so of ancillary physical bits needed for overhead. And no one yet knows the error rate in wiring multiple logical bits together via optical links or other technologies.

(One caveat to the math above. It assumes that every technical approach (Superconducting, Photonics, Cold Atoms, Trapped Ions, et al) will require each physical qubit to have hundreds of bits of error correction to make a logical qubit. There is always a chance a breakthrough could create physical qubits that are inherently stable, and the number of error correction qubits needed drops substantially. If that happens, the math changes dramatically for the better and quantum computing becomes much closer.)

Today, the best anyone has done is to create 1,000 physical qubits.

We have a ways to go.

Advances in materials science will drive down error rates
As seen by the math above, regardless of the technology in creating physical qubits (Superconducting, Photonics, Cold Atoms, Trapped Ions, et al.) reducing errors in qubits can have a dramatic effect on how quickly a quantum computer can be built. The lower the physical qubit error rate, the fewer physical qubits needed in each logical qubit.

The key to this is materials engineering. To make a system of 100s of thousands of qubits work the qubits need to be uniform and reproducible. For example, decoherence errors are caused by defects in the materials used to make the qubits. For superconducting qubits that requires uniform thickness, controlled grain size, and roughness. Other technologies require low loss, and uniformity. All of the approaches to building a quantum computer require engineering exotic materials at the atomic level – resonators using tantalum on silicon, Josephson junctions built out of magnesium diboride, transition-edge sensors, Superconducting Nanowire Single Photon Detectors, etc.

Materials engineering is also critical in packaging these qubits (whether it’s superconducting or conventional packaging) and to interconnect 100s of thousands of qubits, potentially with optical links. Today, most of the qubits being made are on legacy 200mm or older technology in hand-crafted processes. To produce qubits at scale, modern 300mm semiconductor technology and equipment will be required to create better defined structures, clean interfaces, and well-defined materials. There is an opportunity to engineer and build better fidelity qubits with the most advanced semiconductor fabrication systems so the path from R&D to high volume manufacturing is fast and seamless.

There are likely only a handful of companies on the planet that can fabricate these qubits at scale.

Regional research consortiums
Two U.S. states; Illinois and Colorado are vying to be the center of advanced quantum research.

Illinois Quantum and Microelectronics Park (IQMP)
Illinois has announced the Illinois Quantum and Microelectronics Park initiative, in collaboration with DARPA’s Quantum Proving Ground (QPG) program, to establish a national hub for quantum technologies. The State approved $500M for a “Quantum Campus” and has received $140M+ from DARPA with the state of Illinois matching those dollars.

Elevate Quantum
Elevate Quantum is the quantum tech hub for Colorado, New Mexico, and Wyoming. The consortium was awarded $127m from the Federal and State Governments – $40.5 million from the Economic Development Administration (part of the Department of Commerce) and $77m from the State of Colorado and $10m from the State of New Mexico.

(The U.S. has a National Quantum Initiative (NQI) to coordinate quantum activities across the entire government see here.)

Venture capital investment, FOMO, and financial engineering
Venture capital has poured billions of dollars into quantum computing, quantum sensors, quantum networking and quantum tools companies.

However, regardless of the amount of money raised, corporate hype, pr spin, press releases, public offerings, no company is remotely close to having a quantum computer or even being close to run any commercial application substantively faster than on a classical computer.

So why all the investment in this area?

  1. FOMO – Fear Of Missing Out. Quantum is a hot topic. This U.S. government has declared quantum of national interest. If you’re a deep tech investor and you don’t have one of these companies in your portfolio it looks like you’re out of step.
  2. It’s confusing. The possible technical approaches to creating a quantum computer – Superconducting, Photonics, Cold Atoms, Trapped Ions, Quantum Dots, Nitrogen Vacancy in Diamond Centers, and Topological – create a swarm of confusing claims. And unless you or your staff are well versed in the area, it’s easy to fall prey to the company with the best slide deck.
  3. Financial engineering. Outsiders confuse a successful venture investment with companies that generate lots of revenue and profit. That’s not always true.

Often, companies in a “hot space” (like quantum) can go public and sell shares to retail investors who have almost no knowledge of the space other than the buzzword. If the stock price can stay high for 6 months the investors can sell their shares and make a pile of money regardless of what happens to the company.

The track record so far of quantum companies who have gone public is pretty dismal. Two of them are on the verge of being delisted.

Here are some simple questions to ask companies building quantum computers:

  • What is their current error rates?
  • What error correction code will they use?
  • Given their current error rates, how many physical qubits are needed to build one logical qubit?
  • How will they build and interconnect the number of physical qubits at scale?
  • What number of qubits do they think is need to run Shor’s algorithm to factor 2048 bits.
  • How will the computer be programmed? What are the software complexities?
  • What are the physical specs – unique hardware needed (dilution cryostats, et al) power required, connectivity, etc.

Lessons Learned

  • Lots of companies
  • Lots of investment
  • Great engineering occurring
  • Improvements in quantum algorithms may add as much (or more) to quantum computing performance as hardware improvements
  • The winners will be the one who master material engineering and interconnects
  • Jury is still out on all bets

Navigating Stakeholder Dynamics in Product Management: Practical Insights

Managing stakeholder relationships is one of the most critical and nuanced aspects of the role of product manager. Whether you’re a seasoned product leader or still sharpening your skills, mastering stakeholder dynamics requires an understanding of influence, expectation management, and alignment across teams and departments.

At its core, stakeholder management is about building strong relationships, fostering trust, and ensuring that everyone is working toward the same product vision. However, the reality is that stakeholders often have competing priorities and varying levels of influence. This can make managing expectations difficult, especially when dealing with senior leadership.

Understanding Stakeholder Dynamics

Stakeholders in product management aren’t just limited to your direct team; they encompass leadership, cross-functional teams, customers, and even external partners. Each group has its own set of expectations, and as a product manager, you are often in the middle, balancing different priorities. To navigate these dynamics successfully, consider the following:

  • Influence and Power Structures: Senior leaders like CEOs or VPs often have significant influence over product decisions. Their directives may override data-backed insights or customer needs, leaving PMs to balance the demand for quick wins with long-term product strategy.
  • Expectation Management: Different stakeholders will have different expectations of the product and the roadmap. Some may focus on innovation, while others are looking for short-term financial gains. Managing these expectations requires clear communication and negotiation skills.
  • Alignment: The most effective product teams are those where all stakeholders are aligned on the product vision and goals. Achieving this alignment is easier said than done, but it’s crucial for driving a successful product.

Practical Tips

While navigating stakeholder dynamics can feel overwhelming, there are some strategies that can help you manage these relationships more effectively.

  1. Communicate Early and Often
    A foundational principle of stakeholder management is consistent communication. Don’t wait for issues to arise; instead, proactively update stakeholders on product progress, challenges, and changes in direction. Keeping stakeholders informed reduces surprises and helps you manage their expectations more effectively.

    For instance, when presenting a roadmap update, include not only the “what” but also the “why.” Clearly explaining the rationale behind your decisions—whether driven by customer feedback, market trends, or technical feasibility—helps build trust and gives stakeholders a clearer understanding of the product’s direction.
  2. Influence Without Authority
    As a product manager, you often have to lead without direct authority over many of your stakeholders. One of the best ways to do this is by building strong relationships based on trust and credibility. When senior leadership pushes for a feature that doesn’t align with the product vision, use data to guide the conversation. Present customer feedback, market research, or case studies to make your case.

    For example, if a VP requests a feature that doesn’t address a customer need, share data showing how current customer pain points are being prioritized. This shifts the conversation from subjective opinions to objective insights.
  3. Prioritize Transparency
    It’s important to be transparent when you can’t meet certain demands. Instead of overpromising, explain what is achievable and why some requests may not align with the current product priorities. Transparency also helps you build trust and gives stakeholders a realistic understanding of what can be delivered within certain constraints.

Essential Navigation

Navigating stakeholder dynamics is an essential skill for product managers, requiring a delicate balance between influence, expectation management, and alignment. By proactively communicating, building trust through data-driven insights, and being transparent about what can and cannot be achieved, PMs can foster stronger relationships with stakeholders and drive product success.

Priorities often conflict and leadership pressures are high. Mastering these dynamics is key to not only managing expectations but also positioning yourself as a trusted leader within your organization. Stay tuned for part two, where we’ll explore the more challenging aspects of stakeholder management and offer practical solutions for handling them effectively.

Interested in more?

We recently discussed this topic and much more on at a recent TPG Live roundtable discussion.  Watch the replay here: https://youtube.com/live/IgwwPxPJk1U

And don’t forget to mark your calendars for our next TPG Live session on October 10th at 7 PM ET, where we will be exploring “Effective AI & Impediments to Done.” You can RSVP here: RSVP for the Next Event. Even if you can’t attend live, RSVP to receive a recap and a link to the recording afterwards.

What’s Next?

In Part 2 of this 2 part series on Stakeholder Dynamics in Product Management, we will explore actionable strategies for overcoming stakeholder management challenges.

How Saboteurs Threaten Innovation–and What to Do About It

“Only the Paranoid Survive”
Andy Grove – Intel CEO 1987-1998

I just had an urgent “can we meet today?” coffee with Rohan, an ex-student. His three-year-old startup had been slapped with a notice of patent infringement from a Fortune 500 company. “My lawyers said defending this suit could cost $500,000 just for discovery, and potentially millions of dollars if it goes to trial. Do you have any ideas?”

The same day, I got a text from Jared, a friend who’s running a disruptive innovation organization inside the Department of Defense. He just learned that their incumbent R&D organization has convinced leadership they don’t need any outside help from startups or scaleups.

Sigh….

Rohan and Jared have learned three valuable lessons:

  • Only the paranoid survive (as Andy Grove put it)
  • If you’re not losing sleep over who wants to kill you, you’re going to die.
  • The best fight is the one you can avoid.

It’s a reminder that innovators need to be better prepared about all the possible ways incumbents sabotage innovation.

Innovators often assume that their organizations and industry will welcome new ideas, operating concepts and new companies. Unfortunately, the world does not unfold like business school textbooks.

Whether you’re a new entrant taking on an established competitor or you’re trying to stay scrappy while operating within a bigger company here’s what you need to know about how incumbents will try to stand in your way – and what you can do about it.


Entrepreneurs versus Saboteurs
Startups and scaleups outside of companies or government agencies want to take share of an existing market, or displace existing vendors. Or if they have a disruptive technology or business model, they want to create a new capability or operating concept – even creating a new market.

As my student Rohan just painfully learned, the incumbent suppliers and existing contractors want to kill these new entrants. They have no intention of giving up revenue, profits and jobs. (In the government, additional saboteurs can include Congressional staffers, Congressman and lobbyists, as these new entrants threaten campaign contributions and jobs in local districts.)

Intrapreneurs versus Saboteurs
Innovators inside of companies or government agencies want to make their existing organization better, faster, more effective, more profitable, more responsive to competitive threats or to adversaries. They might be creating or advocating for a better version of something that exists. Or perhaps they are trying to create something disruptive that never existed before.

Inside these commercial or government organizations there are people who want to kill innovation (as my friend Jared just discovered). These can be managers of existing programs, or heads of engineering or R&D organizations who are feeling threatened by potential loss of budget and authority. Most often, budgets and headcount are zero-sum games so new initiatives threaten the status quo.

Leaders of existing organizations often focus on the success of their department or program rather than the overall good of the organization. And at times there are perverse incentives as some individuals are aligned with the interests of incumbent vendors rather than the overall good of the company or government agency.

How Do incumbents Kill Innovation?
Rohan and Jared were each dealing with one form of innovation sabotage. Incumbents use a variety of ways to sabotage and kill innovative ideas inside of organizations and outside new companies. And most of the time innovators have no idea what just hit them. And those that do – like Rohan and Jared – have no game plan in place to respond.

Here are the most common methods of sabotage that I’ve seen, followed by a few suggestions on how to prepare and defend against them.

Founders and Innovators should expect that existing organizations and companies will defend their turf – ferociously.

 

Common ways incumbents kill innovation in both commercial markets and government agencies.

  • Create career FUD (fear, uncertainty and doubt). Positioning the innovative idea, product or service as risk to the career of whoever adopts or champions it.
  • Emphasize the risk to existing legacy investments, like the cost of switching to the new product or service or highlighting the users who would object to it.
  • Claim that an existing R&D or engineering organization is already doing it (0r can do it better/cheaper.)
  • Create innovation theater by starting internal innovation programs with the existing staff and processes.
  • Set up committees and advisory boards to “study” the problem. Appoint well respected members of the status quo.
  • Poison funding for internal initiatives. Claiming that you’ll have to kill important program x or y to pay for the new initiative. Or funding the demo of the new idea and then “slow-walk” the budget for scale.
  • Poison startup financing sources. Telling VCs the incumbents already own the market. Tell Government funders the company is out of cash.
  • File Lawsuits/Protests against winners of contracts.
  • Use patents as a weapon. Filing patent infringement lawsuits – whether true or not. Try to invalidate existing patents – whether true or not.
  • Claim that employees have stolen IP from their previous employer.
  • File HR Complaints against internal intrapreneurs for cutting corners or breaking rules.
  • Isolate senior leadership from the innovators inside the organization via reporting hierarchy and controlling information about alternatives.
  • Object to structures and processes for the rapid adoption of new technologies. Treat innovation and execution as the same processes. Lack tolerance for failure at innovation. Do not cultivate a culture of urgency. Don’t offer a a structured career path for innovators.
  • Lock-up critical resources, like materials, components, people, law firms, distribution channels, partners and make them unavailable to innovation groups/startups.
  • Control industry/government standards to ensure that they are lock-in’s for incumbents.
  • Acquire a startup and shut it down or bury its product
  • Poach talent from an innovation organization or company by convincing talent that the innovation effort won’t go anywhere.
  • Influence “independent” analysts, market research firms with “research” contracts to prove that the market is too small.
  • Confuse buyers and senior leadership by preannouncing products or products that never ship – vaporware.
  • Bundle products (Microsoft Office)
  • Long term lock-in contracts for commercial customers or sole-source for government programs (e.g. F-35).

How incumbents kill startups in government markets

  • File contract appeals or protests, creating delays that burn cash for new entrants.
  • File Inspector General (IG) complaints, claiming innovators are cutting corners, breaking rules or engaging in illegal hiring and spending. If possible, capture these IG offices and weaponize them against innovators.
  • Hijack the acquisition system by creating requirements written for incumbents, while setting unnecessary standards, barriers and paperwork for new entrants. Ignore requirements to investigate alternate suppliers and issue contracts to the incumbents.
  • Revolving door. The implicit promise of jobs to government program executives and managers and the implicit promise of jobs to congressional staffers and congressmen.
  • Lobbying. Incumbents have dedicated staffs to shape requirements and budgets for their products, as well as dedicated staff for continual facetime in Washington. They are experts at managing the POM, PPBE, House and Senate Armed Services Committees  and appropriations committees.
  • Create career risks for innovators attempting to gain support outside of official government channels, penalizing unofficial contacts with members of Congress or their staffs.
  • Create Proprietary interfaces
  • Weaponize security clearances, delaying or denying access to needed secure information, or even pulling your, or your company’s clearance.

How incumbents kill startups in commercial markets.

  • Rent Seeking via regulatory bodies (e.g. FCCSECFTC, FAA, Public Utility, Taxi/Insurance Commissions, School Boards, etc, …) Use government regulation to keep out new entrants who have more innovative business models (or delay them so the incumbents can catch up).
  • Rent Seeking via local, state and federal laws (e.g. occupational licensing, car dealership laws, grants, subsidies, or tariff protection). Use arguments – from public safety, to lack of quality, or loss of jobs –  to lobby against the new entrants.
  • Rent Seeking via courts to tie up and exhaust a startup’s limited financial resources.
  • Rent Seeking via proprietary interfaces (e.g. John Deere tractor interfaces…)
  • Legal kickbacks, like discounts, SPIFs, Co-advertising (e.g. Intel and Microsoft for x86 processors/Windows).
  • State Attorney General complaints to tie up startup resources
  • Create fake benchmark groups or greenwash groups to prove existing solution is better or that new solution is worse.

Innovators Survival Checklist

There is no magic bullet I could have offered Rohan or Jared to defend against every possible move an incumbent might make. However, if they had realized that incumbents wouldn’t welcome them, they (and you) might have considered the suggestions below on how to prepare for innovation saboteurs.

In both government and commercial markets:

  • Map the order of battle. Understand how the money flows and who controls budget, headcount and organizational design. Understand who has political, regulator, leadership influence and where they operate.
  • Understand saboteurs and their motivation. Co-opt them. Turn them into advocates – (this works with skeptics). Isolate them – with facts. Get them removed from their job (preferably by promoting them to another area.)
  • Build an insurgent team. A technologist, visionary, champion, allies, proxies, etc. The insurgency grows over time.
  • Avoid publicly belittling incumbents. Do not say, “They don’t get it.” That will embarrass, infuriate and ultimately motivate them to put you out of business.
  • Avoid early slideware. Instead focus on delivering successful minimal viable products which demonstrate feasibility and a validated requirement.
  • Build evidence of your technical, managerial and operational excellence. Build Minimal Viable Products (MVPs) that illustrate that you understand a customer or stakeholders problem, have the resources to solve it, and a path to deployment.
  • If possible, communicate and differentiate your innovation as incremental innovation. Point out that over time it’s disruptive.
  • Go after rapid scale of a passionate customer who values the disruption e.g. INDOPACOM; or Uber and Airbnb, Tesla in the commercial world
  • Ally with larger partners who see you as a way to break the incumbents’ lock on the market. i.e. Palantir and the intelligence agencies versus the Army and in industry, IBM’s i2, / Textron Systems Overwatch.

In commercial markets:

  • Figure out an “under the radar” strategy that doesn’t attract incumbents’ lawsuits, regulations or laws when you have limited resources to fight back.
  • Patent strategy. Build a defensive patent portfolio and strategy? And consider an offensive one, buying patents you think incumbents may infringe.
  • Pick early markets where the rent seekers are weakest and scale. For example, pick target markets with no national or state lobbying influence. i.e. Craigslist versus newspapers, Netflix versus video rental chains, Amazon versus bookstores, etc.
  • When you get scale and raise a large financing round, take the battle to the incumbents. Strategies at this stage include hiring your own lobbyists, or working with peers in your industry to build your own influence and political action groups.

Jared is still trying to get senior leadership to understand that the clock is ticking, and internal R&D efforts and current budget allocation won’t be sufficient or timely. He’s building a larger coalition for change, but the inertia for the status quo is overwhelming.

Rohan’s company was lucky. After months of scrambling (and tens of thousands of dollars), they ended up buying a patent portfolio from a defunct startup and were able to use it to convince the Fortune 500 company to drop their lawsuit.

I hope they both succeed.

What have you found to be effective in taking on incumbents?