inspired-product

Solid

Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "product roadmap", "opportunity assessment", "product vision", "product-led growth", or "discovery vs delivery". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.

AI & Automation 1,169 stars 127 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Empowered Product Teams Framework Framework for building products customers love by structuring empowered teams that solve hard problems through continuous discovery and delivery. Based on a fundamental truth: the best product companies don't ship features -- they solve problems, and they give their teams the autonomy and accountability to figure out how. ## Core Principle **Empowered product teams** = cross-functional groups given problems to solve (not features to build) who own discovery and delivery end-to-end. The root cause of most product failures is not bad engineering or poor design -- it is that teams are building things nobody wants. Feature teams receive roadmaps and execute; empowered teams receive objectives and discover solutions. The difference between a feature factory and an innovation engine is whether teams are missionaries (driven by vision and empathy) or mercenaries (driven by a backlog handed to them). ## Scoring **Goal: 10/10.** When reviewing or creating product team structures, discovery practices, or delivery processes, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10. ## Framework ### 1. Product Discovery vs Delivery **Core concept:** Product work has two distinct tracks running in parallel. Discovery determines what to build (addressing risks before engineeri...

Details

Author
wondelai
Repository
wondelai/skills
Created
4 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

continuous-discovery

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

1,169 Updated 2 weeks ago
wondelai
Testing & QA Listed

continuous-discovery-habits

Product discovery framework based on Teresa Torres' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing assumption tests before committing to a feature, (4) writing or critiquing interview snapshots from customer conversations, (5) generating multiple solution candidates for an opportunity (especially with How Might We), (6) mapping a current-state customer experience or journey to surface unmet needs, (7) diagnosing why a product team is shipping without moving outcomes, (8) running a discovery pre-mortem before committing to a solution branch, (9) building or strengthening a weekly customer-interview habit, (10) connecting business outcomes to product outcomes to opportunities to solutions in a single coherent tree.

0 Updated 3 days ago
tomaszstaniak
AI & Automation Listed

product-discovery-coach

Coaches a product trio through continuous product discovery: weekly customer touchpoints, assumption mapping, story mapping, and the discovery / delivery dual-track cadence. Use when standing up a discovery practice from scratch, debugging why discovery isn't sticking, training a new product manager on continuous discovery, or designing a quarterly discovery plan around an outcome.

1 Updated today
varunk130
AI & Automation Solid

discovery-process

Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

4,665 Updated 1 weeks ago
deanpeters
AI & Automation Listed

product-manager

Senior product management guidance. Use when the user mentions PRD, product requirements, roadmap, feature prioritization, user stories, discovery, user research, JTBD, MVP, product strategy, backlog, sprint planning, story mapping, OKRs, A/B testing, product metrics, NPS, retention, activation, onboarding, pricing strategy, or any product management topic. Also triggers on: product manager, PM, CPO, product strategy, customer discovery, opportunity solution tree, RICE, ICE, MoSCoW, Kano model, product-market fit, PMF, user interviews, personas, feature requests, release planning, habit-forming products, Hook Model, trigger action reward investment, variable rewards, Nir Eyal, Hooked, engagement loops, DAU MAU ratio.

2 Updated 3 days ago
ceoimperiumprojects