Loading...
Loading...
Found 10 Skills
Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach. Use when: **Starting a new venture** to avoid building something nobody wants; **Before writing a line of code** to validate problem-solution fit; **Pivoting decisions** to systematically test new directions; **Early-stage fundraising** to prove market validation; **Product roadmap planning** to prioritiz...
Discover all customers of a given company by scanning websites, case studies, review sites, press, social media, job postings, and more. Use when you need competitive intelligence on who a company sells to.
Validate that the problem you want to solve is real, painful, and worth solving before building anything. Master Cindy Alvarez's structured approach to problem discovery interviews. Use when: **Before solution interviews** to confirm the problem exists; **Early customer discovery** to understand the problem space; **Pivoting** to find new problems worth solving; **Market expansion** to understand problems in new segments; **Feature prioritization** to validate which problems matter most
Strategic framework for discovering and designing product innovations based on Clayton Christensen's Jobs to Be Done (JTBD) theory from "Competing Against Luck". Use when you need to: (1) understand customers' true motivations, (2) design a new product or feature, (3) conduct customer discovery interviews, (4) analyze competition through the "jobs" lens, (5) diagnose why a product isn't selling or customers are churning, (6) create positioning strategy, (7) build a jobs-oriented organization.
Help users run effective customer discovery conversations and extract actionable insights. Use when someone is preparing for user research, planning discovery interviews, writing interview questions, analyzing findings, validating problems, understanding customer behavior, or trying to learn what customers actually want. Triggers include mentions of "customer interviews", "user research", "discovery calls", "talking to customers", "validating ideas", "customer conversations", "problem validation", or questions about what to ask customers.
Analyze what customers truly need by discovering the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", or "product-market fit". Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. Trigger with 'jobs', 'to', 'be'.
Document your business model on one page and systematically de-risk it. Master Ash Maurya's adaptation of Business Model Canvas optimized for startups and uncertainty. Use when: **Starting a new venture** to articulate and test your business model; **Preparing for customer discovery** to document hypotheses to validate; **Pivoting decisions** to compare alternative business models; **Investor conversations** to communicate your model concisely; **Team alignment** to get everyone on the same page
Facilitates the first step of a proven customer-interview method: deciding exactly what you're trying to learn, written as numbered goal questions (G1, G2, …) that your hypotheses and interview questions will later be designed to answer. Interviews the user about their business — new idea or established company, B2B or B2C — then drafts a tailored goal-question list, critiques and revises it with them, and preserves the result in a GOALS.md file. Load when the user wants to interview customers, plan customer discovery or customer development, validate a startup idea, or answer unaskable questions like what to charge, how to position, who the ideal customer is, or what to build. Do NOT load for job or hiring interviews, for writing survey questionnaires, for analyzing customer interviews that have already been conducted, or when a goal-question list already exists and the user wants the next step (hypotheses).
Get the first 50 real users through channels the founder's ICP already uses. Use when the product shipped and nobody came, the founder is "posting more" with no result, or is reaching for paid ads before product-market fit.
Run developer customer discovery via a Technical Advisory Board (TAB). Use when the founder has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.