The New Inner Game: Your Unfair Advantage in the Age of AI

TL;DR

• The commoditization of technical skills is accelerating: AI tools now handle tasks that once required years of specialized training, shifting competitive advantage from what you know to how you think and adapt.
• Your "inner game" — self-awareness, emotional regulation, and metacognition — becomes the primary differentiator when external skills can be replicated or automated.
• Product builders must cultivate three core capacities: the ability to hold complexity without premature resolution, comfort with identity fluidity as roles evolve, and skill in asking better questions rather than having all the answers.
• This isn't soft skills rebranded — it's recognizing that in an age where AI handles execution, human judgment, taste, and the ability to navigate ambiguity become the scarcest resources.

---

We're living through a peculiar moment in the history of work. The skills that took me years to develop as a product manager — writing SQL queries, creating wireframes, analyzing user cohorts — can now be accomplished by someone with the right prompt and an AI assistant. This isn't theoretical. I watch it happen weekly.

The question that keeps me up isn't whether AI will replace product managers. It's more unsettling: What happens when the technical moat disappears entirely?

Lenny Rachitsky's recent exploration of "the new inner game" tackles this head-on, and while I agree with his fundamental premise — that our internal operating system matters more than our external toolkit — I think the implications for product builders go even deeper than he suggests.

The Great Skill Compression

Let's establish the landscape. We're experiencing what I call "skill compression" — the rapid collapse of time between novice and competent practitioner across technical domains.

A decade ago, becoming proficient at data analysis required learning SQL, understanding database architecture, mastering visualization tools, and developing statistical intuition. That journey took months or years. Today, a product manager can describe their question in natural language, and an AI agent writes the query, executes it, identifies patterns, and suggests visualizations. The entire stack compressed into minutes.

This pattern repeats across domains:

• Design: Figma proficiency once signaled serious craft. Now AI generates component libraries and responsive layouts from descriptions.
• Code: Junior engineers ship features using AI pair programmers that would have required senior developers a year ago.
• Research: Synthesizing user feedback across hundreds of interviews — a weeks-long analysis — happens in an afternoon with the right tools.

The compression isn't complete, and expertise still matters. But the delta between "can do the task" and "does it exceptionally" is narrowing in ways that fundamentally alter the game.

Why the Inner Game Matters Now

Rachitsky frames the inner game as your psychological operating system — how you process information, regulate emotions, maintain resilience, and make decisions under uncertainty. When everyone has access to similar tools and information, these internal capacities become the primary source of competitive advantage.

I think this is correct, but here's my take on why it matters specifically for product builders: The nature of our work is shifting from execution to curation and judgment.

Product management has always involved judgment, but we could hide behind execution. You demonstrated value by shipping features, analyzing metrics, writing specs. These were tangible, legible outputs. When AI handles much of that execution, what remains is the illegible work — the taste, the strategic sense, the ability to hold ten conflicting user needs in your head and synthesize a coherent direction.

This illegible work demands a different inner game than execution did.

Three Mindset Shifts for Product Builders

1. From Resolution to Complexity-Holding

Product builders are trained to resolve ambiguity. Someone presents a messy problem; you create clarity through frameworks, data, and decisive action. This instinct served us well in a world where gathering information was expensive and analysis was slow.

AI inverts this. Information is abundant. Analysis is instant. The bottleneck isn't reaching a decision — it's ensuring you're solving the right problem.

The new skill is complexity-holding: the capacity to sit with contradictory information, resist premature pattern-matching, and let understanding emerge rather than forcing it.

Practically, this means:

• Extending your discomfort window: When user research reveals conflicting needs, the instinct is to segment or prioritize immediately. Instead, live with the contradiction longer. Ask why both things might be true. The insight often lives in the tension.
• Questioning your first frame: AI makes it trivial to analyze data through any lens. The danger is analyzing the wrong question thoroughly. Spend more time interrogating your assumptions about what matters before diving into analysis.
• Building tolerance for "I don't know yet": In meetings, on Slack, in roadmap planning — practice saying "I need to sit with this" without anxiety. Model that good judgment sometimes requires patience.

This isn't analysis paralysis. It's recognizing that in a world where execution is cheap, the cost of solving the wrong problem is higher than the cost of taking time to understand the right one.

2. From Fixed Identity to Fluid Self-Concept

Here's an uncomfortable truth: the job title "Product Manager" might not mean the same thing in five years that it does today.

When AI handles execution, the role shifts. Maybe it becomes more like a film director — setting vision, maintaining taste, orchestrating talent (human and AI). Maybe it fragments into specialized functions. Maybe it merges with design or engineering in ways we can't predict.

Rachitsky touches on this, but I think product builders face a specific identity challenge: we've built our professional self-concept around a set of capabilities that are actively commoditizing.

The inner game shift required is moving from "I am a product manager who does X, Y, Z" to "I am someone who creates value by..." and being genuinely open to what fills that blank.

This is harder than it sounds. Our identities are deeply tied to our expertise. Letting go of "I'm the person who understands our data model" or "I'm the one who writes the best PRDs" feels like losing something essential.

But clinging to a fixed identity in a fluid landscape is a trap. The product builders who thrive will be those who can:

• Decouple self-worth from specific skills: Your value isn't your Figma proficiency. It's your judgment about what to build and why.
• Experiment with identity: Try on different roles. Spend a sprint acting like a creative director. Another as a data scientist. Notice what feels generative.
• Embrace the discomfort of not knowing what you are: This sounds abstract, but it's practical. The anxiety of "what's my role if AI does this?" is real. The inner game is feeling that anxiety without letting it drive premature closure.

3. From Answers to Questions

Product management has historically rewarded people who have answers. You're in the meeting to provide clarity, make decisions, unblock the team. The person with the answer has status.

AI is better at generating answers than humans are at generating questions. This flips the value hierarchy.

The new premium skill is question formulation — the ability to ask questions that open up possibility rather than close it down.

Consider two approaches to a feature decision:

Answer-oriented: "Based on the data, we should build the notifications feature because it shows a 23% increase in engagement in the prototype."

Question-oriented: "The prototype data shows engagement lift with notifications. But I'm curious — are we measuring engagement we want? What if the notifications are creating anxiety that shows up as engagement but erodes trust? How would we know?"

Both are valuable. But in an AI-augmented world where generating the first answer is trivial, the second approach — which reframes the problem and opens new lines of inquiry — becomes the scarce skill.

Practically:

• Audit your question quality: In your next ten meetings, track how often you offer answers versus questions. Aim for a 1:1 ratio.
• Practice second-order questions: When someone proposes a solution, ask "What problem does that solve?" Then ask "What problem does that solve?" The second question often reveals the real issue.
• Use AI to stress-test your questions: Feed your product question to an AI and see what it generates. If the answer feels complete, your question wasn't interesting enough. Refine until the AI's response opens more questions than it closes.

The Metacognitive Layer

Underlying all three shifts is a deeper capacity: metacognition — thinking about your thinking.

When technical execution was the bottleneck, you could succeed with relatively little self-awareness. You learned frameworks, applied them, and iterated based on results. The feedback loop was external.

When judgment and taste become primary, the feedback loop becomes internal. You need to notice your own cognitive patterns:

• When do you jump to conclusions?
• What triggers defensive reasoning?
• Which problems do you avoid because they make you uncomfortable?
• How do your emotions shape your product decisions?

This isn't therapy (though therapy helps). It's practical. A product builder who can notice "I'm pushing for this feature because it's technically interesting to me, not because it solves the user's core problem" has a massive advantage over one who can't.

Developing metacognition:

• Decision journals: After major product decisions, write down your reasoning, emotional state, and confidence level. Review monthly to spot patterns.
• Solicit process feedback: Don't just ask "was this a good decision?" Ask "how did I approach this decision? What did you notice about my reasoning?"
• Meditation or reflection practice: I'm not prescriptive about the form, but some regular practice of observing your own mental processes is invaluable. Even five minutes daily compounds.

The Paradox of Soft Skills

There's a temptation to dismiss this as "soft skills" rebranded. I think that misses the point entirely.

These aren't soft skills in the traditional sense — the ability to run a good meeting or give empathetic feedback. Those matter, but they're downstream of something more fundamental: the capacity to operate effectively when the external scaffolding disappears.

Technical skills were scaffolding. They provided structure, clear progress markers, and legible demonstrations of value. That scaffolding is dissolving. What remains is your ability to create value in ambiguity.

That's not soft. It's the hardest thing.

Practical Implications for Product Builders

If you're convinced the inner game matters, what do you actually do?

Start with self-assessment:

• How comfortable are you with ambiguity? (Not "do you like it" but "can you function effectively in it?")
• How attached are you to your current role definition?
• What's your ratio of questions to answers in product discussions?
• How often do you notice your own cognitive patterns in real-time?

Then build capacity systematically:

1. Create space for complexity: Block time for thinking without resolution. I schedule "problem-sitting" sessions where the only goal is to understand a problem more deeply, not to solve it.

2. Experiment with identity: Take on a project outside your comfort zone. If you're technical, lead a brand exercise. If you're design-oriented, dig into the infrastructure roadmap. Notice what shifts.

3. Develop a question practice: Start meetings by writing three questions you have about the topic. Don't share them immediately — see if the discussion addresses them naturally. If not, introduce them.

4. Build metacognitive feedback loops: Find a peer who will give you honest feedback on your thinking process, not just your outputs. Meet monthly to discuss how you're approaching problems.

5. Invest in depth, not breadth: When everyone can be competent at everything, depth in a few areas matters more than surface-level familiarity with many. But choose depth areas based on what compounds with your judgment, not just technical skills.

The Uncomfortable Truth

Here's what I think many product builders don't want to hear: developing your inner game is harder and slower than learning technical skills.

You can learn SQL in a few weeks. You can become Figma-proficient in a month. Building the capacity to hold complexity without anxiety, to maintain identity fluidity, to consistently ask generative questions — that's years of work.

And unlike technical skills, there's no clear curriculum, no certificate, no portfolio piece that proves you have it. It's illegible, which makes it uncomfortable for people who built their careers on legible demonstrations of competence.

But that illegibility is precisely what makes it valuable. If it could be easily taught, measured, and replicated, AI would eventually handle it too.

The Real Unfair Advantage

Rachitsky's framing of the inner game as an "unfair advantage" resonates because it identifies something that doesn't scale the way technical knowledge does.

When I can give you a prompt and you can do what took me years to learn, my technical knowledge isn't an advantage. But my judgment — developed through years of seeing patterns, making mistakes, and refining my sense of what matters — that doesn't transfer via prompt.

The inner game is your unfair advantage because it's genuinely yours. It's shaped by your experiences, your failures, your specific way of seeing the world. AI can augment it, but it can't replicate it.

For product builders specifically, this means the path forward isn't learning to use AI tools better (though that helps). It's developing the internal capacities that make you effective at the work AI can't do: holding complexity, making judgment calls with incomplete information, asking questions that reframe problems, and maintaining clarity of purpose when everything else is fluid.

That's the new game. And if you're not playing it yet, you're already behind.