good-strategy
Good Strategy Framework
A framework for evaluating, designing, and stress-testing strategies. Based on Richard Rumelt's "Good Strategy Bad Strategy" and enriched with Michael Porter's "What Is Strategy?" — the definitive works on distinguishing real strategy from the fluff that passes for it. Includes a built-in pre-mortem stress test.
Core Principle
Strategy is not a goal. Strategy is a coherent response to a challenge. Most organizations confuse strategy with ambition ("be the market leader"), goals ("grow 30% YoY"), or a list of priorities ("our strategic priorities are..."). None of these are strategy. A strategy is a diagnosis of the situation, a guiding policy for dealing with it, and a set of coherent actions designed to carry out the policy.
Porter adds a critical insight: Strategy is about choosing what NOT to do. The essence of strategy is choosing a set of activities that are different from competitors. Operational effectiveness (doing the same things better) is not strategy. Competitive advantage comes from performing different activities or performing similar activities in different ways.
Scoring
Goal: 10/10. When evaluating a strategy, rate it 0-10:
| Score | Description |
|---|---|
| 0-2 | No strategy. What exists is a list of goals, a vision statement, or a budget dressed up as a strategy. |
| 3-4 | Bad strategy. Contains fluff (inflated language saying nothing), fails to diagnose the challenge, or lists disconnected actions. |
| 5-6 | Partial strategy. Some elements of the kernel exist but they don't cohere. Actions don't flow from the diagnosis. |
More from tomaszstaniak/pm-ai-skills
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.
13working-backwards
Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use when you need to: (1) write a PR/FAQ document for a new product or feature, (2) validate an idea by defining the customer experience first, (3) stress-test a proposal with pre-mortem analysis, (4) align stakeholders around a product vision, (5) decide whether an idea is worth building before writing code.
9positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs
6first-90-days
Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use when you need to: (1) plan onboarding for a new leadership or management role, (2) build a 30-60-90 day plan, (3) diagnose the business situation you''re entering (STARS model), (4) plan critical early conversations with your new boss, peers, and team, (5) identify and avoid common transition traps, (6) accelerate time to value in a new role.
5escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.
5para-method
Personal knowledge management framework based on Tiago Forte''s "The PARA Method" and "Building a Second Brain". Use when you need to: (1) organize digital information into Projects, Areas, Resources, and Archives, (2) build a Second Brain for capturing and retrieving knowledge, (3) apply CODE methodology (Capture, Organize, Distill, Express), (4) design progressive summarization layers, (5) create actionable knowledge management systems, (6) connect knowledge to current projects, (7) reduce information overload through systematic organization.
2