Concepts in Product Management, page 16
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 Bumps: Testing Prices with Temporary Increases
A product bump is a temporary price increase for an in-app purchase to test user price sensitivity. It helps you find the optimal price without permanently changing it for everyone. The footgun is misinterpreting statistical noise from small test groups.
Law of Large Numbers: More Data, Truer Average
The more you repeat an experiment, the closer your average result gets to the true, underlying average. This is why A/B tests need sufficient traffic and casinos can reliably predict earnings. The footgun is mistaking it for the 'law of averages' fallacy.
Refactoring: Cleaning Code Without Breaking It
Refactoring is like renovating a house's internals without changing its outward appearance. It improves code design and readability without altering external behavior, making it easier to maintain or extend.
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.
In-Product Discovery: Finding Growth Inside Your App
In-product discovery is finding your next growth lever by observing users within your live product, not just in pre-launch research. It's used to scale existing products via in-app experiments.
Central Limit Theorem: Why Averages Form a Bell Curve
The Central Limit Theorem explains why averages of samples tend to form a bell curve, even if the original data doesn't. It's the foundation for A/B testing and quality control. The footgun is assuming it works for small or non-independent samples.
SOLID Principles: Writing Maintainable Object-Oriented Code
SOLID principles are five design rules for writing maintainable object-oriented code. They guide you toward creating flexible systems that are easy to change. The footgun is treating them as rigid laws, leading to over-engineered and complex solutions.
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.
The Hybrid GTM Model: PLG Meets Enterprise Sales
A hybrid go-to-market model blends a self-serve product with a sales team, letting users start on their own and bringing in sales for big deals. B2B SaaS uses this for efficiency, but the footgun is creating friction if the handoff isn't seamless.
Hypothesis Testing: Is Your Data Signal or Noise?
Hypothesis testing is a courtroom trial for your data: you assume a default 'null hypothesis' is true until your data provides enough evidence to reject it. It's used in A/B tests to validate changes.
Trunk-Based Development: One Mainline to Rule Them All
Trunk-Based Development means all developers commit to a single shared branch, main or trunk. This is common in CI/CD environments for frequent updates.
Beta Programs: Testing with Real Users Before Launch
A beta program is your final dress rehearsal with a real audience. It's for validating user experience and catching deal-breakers before a public launch, not just finding bugs.
Entitlements: Use Feature Flags for Permanent Access Control
Entitlements use permanent feature flags to control long-term access, like a bouncer for your app's VIP section. This is how you manage premium tiers or special user permissions, ensuring the right customers always see the right features.
A/B Testing: Making Decisions with Data, Not Guesses
A/B testing is a controlled experiment pitting two versions of a product against each other with real users. It's used to see if a change, like a new button color, improves a metric like clicks.
Simple Design: The Simplest Thing That Could Possibly Work
Simple Design means building only what's needed now, not what you might need later. In agile projects like Extreme Programming, this keeps code lean for changing requirements.
Growth Accounting: What's Really Driving Your Growth?
Growth accounting splits your growth into two parts: adding more resources (like ad spend) and getting better with what you have. Use it to see if growth came from a bigger budget or a better product.
Type I vs. Type II Errors: False Alarms vs. Missed Detections
A Type I error is a false alarm (a smoke alarm with no fire), while a Type II error is a missed detection (a fire with no alarm). This trade-off is crucial in A/B testing and medical diagnostics.
YAGNI: You Ain't Gonna Need It
YAGNI is a principle of radical simplicity: don't build features now just because you *think* you'll need them later. It forces focus on current requirements, preventing wasted effort on speculative work.
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.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles