tezvyn:

Product Strategy

Roadmaps, prioritization, product thinking, discovery

101 bites

Product Strategy30 sec read

How would you frame a major refactoring proposal using product strategy?

WHAT IT TESTS: reframing tech debt as delivery risk, not engineering chore. Tie refactoring to velocity loss and firefighting; shift accountability from dev-vs-ops fights to product ownership. RED FLAG: treating debt as hygiene needing blind business funding.

Product Strategy30 sec read

Objection Handling: Turning Customer 'No's into Trust

Objection handling turns customer feedback into trust, even when you say 'no.' Instead of just rejecting a feature request, you explain the 'why' behind your roadmap.

Product Strategy30 sec read

Influence Without Authority: Earn Your Influence Capital

Influence isn't rank; it's 'influence capital' you earn. Product managers use this to lead teams they don't manage by building expertise, strong relationships, and compelling data. The footgun is trying to make big asks before you've made these deposits.

Product Strategy30 sec read

Product Cannibalization: Eat Your Own Lunch

Product cannibalization means competing with yourself before someone else does. Apple famously did this with the iPhone, knowing it would kill the iPod. The footgun is accidentally shrinking your total market share instead of growing it with new offerings.

Product Strategy30 sec read

Repositioning: Changing Minds, Not Just Products

Repositioning changes how customers perceive your existing product. Netflix did this by moving from DVDs to streaming to meet new demand. Don't mistake it for rebranding—repositioning alters the core promise, not just the logo or colors.

Product Strategy30 sec read

Strategic Intent: Winning with Resourcefulness, Not Resources

Strategic Intent is a long-term goal that outstrips your current resources, forcing resourcefulness. Instead of matching resources to opportunities, you set an ambitious target like 'Beat Xerox' and rally the organization to close the gap.

Product Strategy30 sec read

The Golden Circle: Leading with Why

The Golden Circle is a framework for inspiring action by communicating from the inside out: starting with your purpose (Why), then your process (How), and finally your product (What). It's used to build loyalty by connecting on belief, not just features.

Product Strategy30 sec read

Principled Negotiation: Focus on Interests, Not Positions

Principled negotiation avoids a battle of wills by focusing on shared interests, not rigid positions. It's a method for finding mutually acceptable agreements in conflicts. Use it in business deals or team disagreements.

Product Strategy30 sec read

Strategic Narrative: Your Company's Source Code for Story

A strategic narrative is the source code for your company's story, defining its unique value. It's the blueprint for marketing, sales, and internal decisions, ensuring everyone tells the same story.

Product Strategy30 sec read

Platform Strategy: Solving the Chicken-and-Egg Problem

A platform isn't a product; it's an environment where groups create value for each other. This strategy is key for marketplaces (Uber) or ecosystems (iOS) where value grows with users.

Product Strategy30 sec read

Partner Enablement: Getting External Partners to Sell Your Product

Partner enablement removes friction for your external sales channels. It equips resellers and distributors with the training, tools, and content they need to sell your product effectively, especially when they also represent competitors.

Product Strategy30 sec read

Product-Led Growth (PLG): When the Product Sells Itself

Product-Led Growth (PLG) makes the product its own salesperson. Instead of a sales team, the product's features and user experience drive acquisition and expansion.

Product Strategy30 sec read

Rules of Engagement: API Contracts for Teams

Rules of Engagement (RoE) are an API contract for human teams, defining how they interact to prevent chaos. They clarify who owns a customer conversation or how feature requests are handled.

Product Strategy30 sec read

Customer Success Playbooks: Standardize Your Team's Responses

A Customer Success playbook is a recipe for handling key customer moments. It defines a standard workflow for events like onboarding or a drop in usage, ensuring every CSM follows the same proven process. Without them, customer experience is inconsistent.

Product Strategy30 sec read

Sales Enablement: Mission Control for Your Sales Team

Sales Enablement is a central nervous system for your sales team, connecting them with the right content, training, and coaching. It's crucial for complex sales cycles, ensuring consistent messaging. The footgun is treating it as just a content library.

Product Strategy30 sec read

Launch Readiness Checklist: Your Launch's Single Source of Truth

A launch checklist is a flight plan, not just a to-do list, coordinating every team from engineering to sales. It ensures marketing, sales, and support are aligned for a release.

Product Strategy30 sec read

Ideal Customer Profile (ICP): Stop Selling to Everyone

An Ideal Customer Profile (ICP) is a data-driven portrait of the perfect customer for your business. It helps focus marketing and sales on high-value leads, reducing acquisition costs.

Product Strategy30 sec read

Buy vs. Build: A Strategic Choice, Not a Cost Problem

The Buy vs. Build decision is a strategic choice, not just a cost problem. Buy commodity functions to gain speed and stability; build core features to create a unique competitive advantage. The footgun is ignoring total cost of ownership and strategic control.

Product Strategy30 sec read

ICE Scoring: Prioritize Features with a Quick Gut Check

ICE scoring is a gut-check for prioritizing features by multiplying Impact, Confidence, and Ease. It helps teams rapidly sort experiments or backlog items. The main footgun is its bias towards easy wins, potentially ignoring high-effort strategic projects.

Product Strategy30 sec read

Value vs. Effort Matrix: Prioritize What to Build Next

A Value vs. Effort matrix is a 2x2 grid for deciding what to build, plotting features by their potential value against implementation complexity. Product teams use it to prioritize roadmaps and justify resource allocation.