Problem This Solves
PMs lack a concrete benchmark for self-development and struggle to articulate what they are actually accountable for. Hiring managers have no shared rubric for evaluating PM candidates beyond vague job descriptions. Teams build roadmaps from intuition rather than structured inputs. These five essays provide operational frameworks that fix each of these gaps.
Key Principle
PM excellence is multi-dimensional and evaluable. McAllister maps nine competency dimensions. Nash reduces PM accountability to three responsibilities: Strategy, Prioritization, and Execution. Norton identifies six hiring characteristics. Rekhi defines six research inputs before any roadmap is written. Amazon's Leadership Principles offer a behavioral overlay applicable at any company. Used together, these frameworks give PMs and hiring managers a shared, concrete language for excellence.
Good Examples
McAllister's 80/20 Simplification: A 1% PM "knows how to get 80% of the value out of any feature or project with 20% of the effort" — scopes down ruthlessly to ship more and compound learning faster.
Nash's Two-Week Benchmark: Any PM two weeks into a role should give "not just a crisp, but a compelling answer" to "What game are we playing?" and "How do we keep score?" — specific enough to independently align the cross-functional team.
Nash's Brutal Prioritization: The question is not "what is the best list of ideas" but "what are the next three things the team is going to execute on and nail." Naming three forces real sequencing decisions.
Norton's Product Instinct Test: A candidate with genuine product instinct independently echoes concerns you already have about your product, teaches you something new about it, or surfaces something new and interesting in the market — without prompting.
Rekhi's Roadmap Inputs Applied in Order:
- Usage metrics — identify least-used features and friction points in flows
- User interviews — stay in problem space, not solution space
- Customer feedback and support requests — find recurring complaint themes
- Competitive analysis — use the products, read user forums and reviews
- Internal innovation — identify what other internal teams have built that applies here
- Audience surveys with conjoint analysis — quantify relative feature importance
Amazon's "Disagree and Commit": Leaders are obligated to challenge decisions even when uncomfortable. Once a decision is made, they commit wholly. This resolves the common PM failure mode of passive-aggressive non-commitment.
Bad Examples
Hiring for "Suits This Role": Norton explicitly warns that reasoning like "not perfect but suits this role" is "deadly thinking at a startup." It trades short-term fit for long-term mediocrity.
Former Engineers Who Re-own Technical Decisions: Norton notes that engineers transitioning to PM who still try to own implementation details "will crash spectacularly." PM authority over technical direction must be earned through influence, not assumed from prior expertise.
Roadmap by Brainstorm: Starting a roadmap cycle with feature ideation before running Rekhi's six inputs produces a list grounded in the loudest voices rather than evidence. Inputs must precede synthesis.
Vague Strategy: Without crisp answers to "What game are we playing?" and "How do we keep score?", teams cannot make independent decisions. Nash notes no amount of execution or prioritization compensates for missing strategy.
Key Quotes
- "The top 10% of product managers excel at a few of these things. The top 1% excel at most or all of them." — Ian McAllister
- "A 1% PM grinds it out. They do whatever is necessary to ship. They recognize no specific bounds to the scope of their role." — Ian McAllister
- "What game are we playing? How do we keep score?" — Adam Nash
- "Most products and companies fail not for lack of great ideas, but based on mistaking which ones are critical to execute on first and which can wait until later." — Adam Nash
- "Developing the right product roadmap remains as much art as it is science." — Sachin Rekhi
- "I'll take a wickedly smart, inexperienced PM over one of average intellect and years of experience any day." — Ken Norton
- "[Product instinct] can be tuned, but it can't be learned." — Ken Norton
- "Much of the time your job is to be the advocate for whoever isn't currently in the room." — Ken Norton
- "Thinking small is a self-fulfilling prophecy." — Amazon Leadership Principles (Think Big)
- "Frugality breeds resourcefulness, self-sufficiency, and invention." — Amazon Leadership Principles
Rules of Thumb
- Two-week rule (Nash): If you cannot articulate your product's strategy and the top three priorities within two weeks of joining, you are behind.
- 80/20 shipping (McAllister): Prefer 80% of the value at 20% of the effort over perfect features. Launch more, learn more, compound faster.
- Prioritize intelligence over experience (Norton): Raw intellect predicts PM ceiling; experience predicts current floor. Optimize for ceiling, especially at startups.
- Offense vs. defense balance (McAllister): Roadmaps need both offense projects (grow the business) and defense projects (reduce technical debt, operational drag, bugs). Neglecting either creates compounding costs.
- Inputs before synthesis (Rekhi): Never open a roadmap planning session without first completing all six structured research inputs. Synthesis without inputs is guesswork.
- Leadership by influence, not authority (Norton): Evaluate PM candidates through peer reference checks, not just manager references. Peers reveal how influence is actually exercised.
- Copy discipline (McAllister): Each additional word dilutes the value of the previous ones. Shorter is harder to write and more valuable when read.
Related References
- The PM Role and Core Thesis - The PM role these essays elaborate on
- Product Design and Improvement Questions - Product instinct that Norton and McAllister describe
- PM Culture by Company - Amazon's Leadership Principles in interview context