💡[Insight] Why PMs Should Prioritize Strategy Over Coding
Navigating the AI era by focusing on vision and value—not just code
👥 Read if: You’re a Product Manager who’s trying to learn AI
⏱️ Read Time: 3 min
The mantra is everywhere today: “To be a great PM in the world of AI, learn to code.”
The logic seems sound: empathize with engineers, understand the medium, and build credibility. For a Product Manager, especially in the dizzying age of AI, the pressure to get technical has never been higher.
But this advice is dangerously oversimplified. It confuses a supportive skill for the core competency.
The question isn’t whether understanding code is useful—it’s whether it’s the highest-leverage use of your time.
Is your primary value your ability to write a script, or is it your ability to answer the foundational questions: What should we build, why will it win, and how does it create lasting value?
The Critical Nuance: Not All PMs Are The Same
The first flaw in the “learn to code” argument is its one-size-fits-all approach. The PM role exists on a spectrum:
The Business/Application PM (This is likely you): Focused on end-users, market fit, and business outcomes.
Your product is a solution to a customer problem (e.g., a project management tool, a fintech app). Your strategic value lies in understanding the market, the user, and the business model**.The Platform PM: Serves internal developers or other product teams. You define the building blocks others use.
The Technical Infrastructure PM: Owns the underlying systems—databases, compute platforms. For you, technical depth is not just an advantage; it’s a requirement.
Not all PMs are the same, so this article is for the Business and Application PM.
For you, the value is not in the implementation but in the orchestration.
The Valid, But Limited, Case for Technical Literacy
Let’s be fair. Technical empathy is real and valuable.
Credibility & Communication: Understanding the difference between an API call and a full-scale model retraining prevents absurd requests and builds trust.
Scoping & De-risking: Tinkering with an API to grasp its limits can help assess feasibility faster. This is “coding to learn,” a means to a strategic end.
However, this is a supporting skill, like understanding basic financial modeling.
It informs your strategy; it is not your strategy.
The Strategic Layer: Where Your Real Value Lives
While your engineering partners master the how, you are the master of the what, why, and so what. This is your domain:
1. Market-Driven Discovery: Your value lies in identifying a valuable, unmet customer need. This comes from deep customer immersion, not from a code repository.
2. Designing the Moat: Any team can build a feature. Your job is to create a system that is difficult to replicate. Architect the competitive advantage.
3. Principles over Implementation: Establish the product’s constitution. You guide every technical choice and ensure coherent product development.
The AI Example: Where the “Learn to Code” Advice Falls Apart
Nowhere is the misalignment more acute than in AI. The chatter says: “Build a model to understand it.” This is a misallocation of a Business PM’s effort.
An engineer needs math skills. A Data Scientist must fine-tune models.A Business PM needs understanding:
Constraints & Failure Modes: Know how and when AI fails. Understanding this allows you to design products that *fail gracefully*.
Application & Fit: Your expertise is in judging where AI provides a 10x improvement.
Orchestrating the Lifecycle: Own the product’s success, understanding the entire journey of data and model monitoring.
Designing for Probability: Design a UI for systems that are probabilistic. Manage user expectations effectively.
Synthesis: Reclaim Your Role as the Architect
Learning to code is a tool, not a destination.
For the Business and Application PM, it will always be a secondary skill. Your primary value is in your ability to orchestrate the entire system of value creation.
The market rewards PMs who make great strategic decisions and design products that win. It does not reward PMs who can code.
So let’s move beyond generic advice. If you are a Business PM, deepen your strategic command of the technologies shaping your industry.
Disclaimer: All views expressed in this article are my own and do not represent the opinions of my employer.