Concepts in Product Management, page 31
RFM Analysis: Find Your Best Customers
RFM analysis segments customers by scoring their Recency, Frequency, and Monetary value. This helps identify your best customers (high RFM), those at risk (low R/F), and new high-spenders.
Agile Facilitation: Guiding Teams to Outcomes
An Agile Facilitator is a neutral guide, designing the *process* for a team to reach its own conclusions, not just running the meeting. They are crucial for sprint planning, retrospectives, and conflict resolution.
Evidence-Based Management: Metrics Over Gut Feel
EBM replaces 'I think' with 'I know because the data shows...' It's about making decisions using evidence, not just intuition. Use it to prioritize features with user data or optimize processes by measuring cycle time. The footgun is metric fixation.
Five Whys: From Symptom to Root Cause
The Five Whys is a root cause analysis technique that traces a problem to its origin by asking 'Why?' repeatedly. It's used in post-mortems to find the underlying process failure, not just the surface-level symptom. The footgun is stopping at human error.
Hypothesis-Driven Development: Stop Guessing, Start Learning
Hypothesis-Driven Development treats new features as experiments, not foregone conclusions. It's used to de-risk major changes by first testing the core assumption with a minimal product. The biggest footgun is writing vague, untestable hypotheses.
Throughput: Measuring What Gets Done
Throughput measures how many work items a team *finishes* in a time period, not how busy they are. It's used for forecasting future work and spotting bottlenecks. The footgun: never compare throughput between different teams, as item sizes and context vary.
Classes of Service: Prioritize Work Beyond 'First In, First Out'
Classes of Service are policies that prioritize work by its business impact, not just arrival time. When a bug, a deadline, and normal work compete, CoS tells you which to pull first.
Flow Efficiency: Are You Working or Waiting?
Flow efficiency measures the ratio of active work time to total lead time, revealing how much time tasks spend just waiting. Use it to diagnose why features take so long to ship. The biggest footgun is optimizing work speed when most delays hide in queues.
Right-Shifting Forecasts: Why Your Deadlines Keep Moving
A forecast is like a GPS ETA in traffic; new tasks are like accidents ahead, pushing your arrival time further out. This happens when initial estimates are treated as fixed deadlines, ignoring new scope. The footgun is anchoring on the first date given.
Nexus Framework: Scaling Scrum Without Breaking It
Nexus is a lightweight wrapper for 3-9 Scrum teams working on one product. It adds a coordinating Nexus Integration Team and shared events to manage dependencies and deliver a single, integrated increment each sprint.
Nexus Integration Team: Air Traffic Control for Scrum
The Nexus Integration Team is like air traffic control for multiple Scrum teams, guiding them to a single, integrated product. It's used in the Nexus framework to coordinate 3-9 teams on one product, resolving cross-team dependencies and integration failures.
Communities of Practice: Scaling Knowledge Across Teams
A Community of Practice is a cross-team guild for a specific skill, like 'frontend' or 'testing'. It's how large orgs prevent knowledge silos, standardize tooling, and mentor juniors. The footgun: they fail without dedicated time and a clear charter.
Agile Center of Excellence: Internal Consultants, Not Process Police
Think of an Agile CoE as internal consultants, not process police. They enable teams by providing coaching, tools, and shared standards. They're useful for scaling Agile consistently, but fail when they become a bureaucratic bottleneck instead of an…
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