Continuous Discovery Habits

Community of Practice as People Development

Build and evaluate a product community that scales growth cheaper than courses or coaches

Empowerment Without Anarchy

Leaders place the bets; teams figure out how to win them. Neither top-down nor bottom-up.

Innovation4 steps

Evaluative User Research (Hunt for Reasons They Won't Use It)

Test prototypes to find every reason people won't use it — and never let the researcher go alone

Feature Team vs. Empowered Product Team Diagnostic

Tell in minutes whether your squad is handed features to ship or problems to solve

Communication4 steps

Growing Into Public Speaking

Start with tiny friendly audiences, grow the room, and mine feedback from strangers and peers

Hire-Experienced vs. Train-Up Decision Matrix

Decide whether to hire an experienced product ops person or train one, based on time and coaching capacity

Leadership4 steps

Hiring Profiles by Product Ops Pillar

Match each product ops pillar to a distinct candidate background and skillset

Keep vs. Offload: The PM Decision-Rights Boundary

A clear line for what a PM keeps versus hands to product ops — decision rights never move

Strategy3 steps

Product-Lens Metrics: Monitoring Product Health vs. Business Health

Segment company metrics through a product lens so leaders can actually monitor their strategy

Innovation4 steps

Solution-Weighted Discovery

Spend a little time validating the problem; spend most of it winning on the solution

Communication5 steps

Story as a Design Tool

Draft, test, and package a leadership story across three lengths and three formats

Mindset4 steps

The Best-Teams Adoption Heuristic

Adopt a practice only if several of the best teams already use it — then strip the culture from the technique

Strategy4 steps

The Diseases of a Devolving Product Company

Four diagnosable diseases that turn a great product company into a feature factory

The Feature Team vs Empowered Product Team Diagnostic

Diagnose whether your team ships output or owns outcomes — and what that means for the PM role.

The Five Ingredients of Coaching Product People

A five-step loop for developing the product managers who report to you

Entrepreneurship4 steps

The Founder's First-PM Timing Rule

The founder IS the product manager until scale forces the handoff — around 20 to 25 engineers.

Innovation4 steps

The Four Product Risks and Their Owners

Valuable, usable, feasible, viable — any one fails and the product fails

The One-Quarter Empowered Team Experiment

Convert a single feature team into an empowered product team in one low-risk quarter

The PM Wheel

An eight-bucket self-assessment for locating a product manager's strengths and gaps

Self-Mastery4 steps

The Product Manager's Four Areas of Homework

The four knowledge domains a PM must own because nobody else on the team can bring them

Strategy5 steps

The Product Operating Model

Three dimensions and four competencies that separate companies that consistently innovate from the rest.

The Three Pillars of Product Operations

Structure a product ops function around data insights, customer insights, and process to free PMs for strategic work

The Three Sacred Accesses

Delegate anything off the PM's plate except direct access to customers, engineers, and stakeholders

Self-Mastery5 steps

The Value and Viability Skill Ladder

Climb from backlog administrator to real product manager by owning the two risks nobody else can.

Mindset4 steps

Think First, Then Challenge with AI

Reverse the default AI workflow: form your own answer, then use the model to attack it.

Strategy4 steps

Which Product Ops Pillar to Start With

Choose your first product ops investment by company stage and where your biggest fire is