product-skills

Applies Ryan Singer's Shape Up methodology to help product teams ship meaningful work on a fixed cycle. Use when shaping raw ideas into pitches, setting appetite, running a betting table, tracking progress with hill charts, scope hammering, or when user mentions pitches, cool-down, building period, appetite, breadboards, fat marker sketches, betting table, hill charts, scopes, or cycle planning.

Applies Bob Moesta's demand-side thinking and Jobs-to-be-Done framework to help product teams understand why customers switch, hire, and fire products. Use when conducting switch interviews, drawing forces diagrams, writing job statements, mapping demand timelines, understanding the struggling moment, analyzing why customers hire or fire your product, exploring passive or active looking behavior, researching JTBD, or when user mentions Bob Moesta, demand-side thinking, big hire, little hire, push/pull/anxiety/habit, or the four forces of progress.

Applies Jeff Patton's User Story Mapping to help teams build shared understanding, decompose work, and plan releases. Use when creating story maps, mapping user activities, writing user stories, slicing releases, planning walking skeletons, decomposing backlogs, breaking down features, facilitating discovery sessions, identifying MVPs, or when user mentions backbone, user journey mapping, release slicing, or flat backlog problems.

Applies Teresa Torres's continuous discovery habits to help product teams discover products that create customer and business value. Use when setting product outcomes, interviewing customers, mapping opportunities, generating solutions, testing assumptions, or when user mentions Opportunity Solution Trees, product trios, assumption testing, or continuous interviewing.