refoundai/lenny-skills▌

Conduct effective usability testing using frameworks from 11 product leaders. \n \n Choose the right test fidelity: fake doors and Wizard of Oz tests for concept validation, prototypes for design feedback, production testing for optimization \n Small sample sizes (10 random users) reveal core friction points; direct observation of user behavior uncovers needs that surveys miss \n Test multiple design options simultaneously to measure relative performance, not single designs in isolation \n Bring

Generate and evaluate startup ideas using frameworks from product leaders. \n \n Guides users through understanding their background, information sources, and unique perspectives to identify differentiated ideas rooted in personal experience \n Applies the \"Why Now\" test to identify what has changed technologically, behaviorally, or infrastructurally to make an idea newly viable \n Flags common tarpit patterns and mistakes, including trend-chasing without specific problems, identical informati

Diagnostic guidance for time management, prioritization, and sustainable productivity habits. \n \n Helps users audit their calendar against stated priorities and identify bottlenecks in prioritization, focus, energy, or overcommitment \n Teaches time-boxing strategies, external task capture systems, and energy-aware scheduling based on peak cognitive hours \n Flags common mistakes including lack of capture systems, unprotected focus time, and saying yes to everything without strategic intent \n

Apply behavioral science principles to product design for habit formation and user retention. \n \n Focuses on understanding target behaviors, identifying barriers, and designing interventions using concepts like loss aversion, present bias, and status quo effect \n Emphasizes reducing friction for desired actions while adding appropriate friction to prevent mistakes, and leveraging smart defaults to guide user outcomes \n Includes guidance on creating celebration moments through micro-interacti

Design effective team rituals that embed culture and operational rhythms into your organization. \n \n Apply the golden rituals framework: name your rituals, template them for consistency, and teach them to every employee by their first week \n Focus on specificity and purpose—rituals should drive measurable outcomes and solve real problems, not just be generic meetings with new names \n Plan for adoption and sustainability by ensuring rituals can run without their creator and by introducing the

Apply systems thinking frameworks to understand complex multi-stakeholder problems and second-order effects. \n \n Maps systems by identifying all players, their incentives, and interactions; traces stocks (what accumulates) and flows (what moves between states) \n Helps identify leverage points where small interventions create large systemic changes and uncover feedback loops that amplify or dampen outcomes \n Flags common mistakes including optimizing locally, ignoring incentives, treating sym

Help teams articulate compelling long-term product visions grounded in user outcomes, not features or taglines. \n \n Provides frameworks from 101 product leaders (Notion, Airbnb, New York Times) covering four criteria for strong vision: lofty yet realistic, free of current technical constraints, and grounded in a potent user problem \n Guides users to describe the user's future world in 5–10 years rather than product features, with emphasis on emotional outcomes and behavioral change \n Include

Framework-driven approach to identifying and pursuing only sales-qualified leads worth your time. \n \n Focuses on aggressive disqualification and early-stage fit assessment, with the core principle that a clear \"no\" on the first call is a successful outcome \n Helps you define explicit disqualification criteria, design discovery questions that reveal fit efficiently, and systematize qualification decisions \n Emphasizes that conversion problems usually stem from pursuing wrong leads rather th

Framework-driven competitive analysis grounded in market realities, not feature comparison. \n \n Expands competitive set beyond direct competitors to include status quo, workarounds, and analog alternatives; helps identify the true threat (features, distribution, or business model) \n Surfaces structural asymmetries and unique advantages competitors cannot easily copy, with emphasis on grounding analysis in customer and market perspective rather than internal politics \n Flags common pitfalls:

Help users craft and deliver compelling presentations using proven techniques from product leaders. \n \n Guides narrative development before slide design, focusing on identifying the single takeaway the audience should remember \n Teaches structural patterns including \"what is vs. what could be\" contrast, descriptive slide titles as conclusions, and state changes every 3-5 slides to maintain engagement \n Covers delivery techniques: breathing exercises, maintaining eye contact, managing prese

Help users achieve stakeholder alignment using frameworks from 88 product leaders. \n \n Guides users through understanding stakeholder motivations, structuring pre-alignment conversations, and preparing for objections using the \"Most Obvious Objections\" framework \n Emphasizes presenting multiple options with trade-offs and a clear recommendation, rather than single proposals that invite criticism \n Teaches core principles including distinguishing disagreement from misunderstanding, building

Survey design framework grounded in product research best practices from nine leaders. \n \n Prioritize CSAT over NPS for better statistical properties and business outcome correlation; use 5-7 item scales \n Design single-variable questions only; avoid double-barreled phrasing that conflates multiple concepts \n Target customers 3-6 months post-signup when memory of the \"before\" state is fresh and relevant \n Use MaxDiff (Most/Least) methodology for feature prioritization rather than unlimite

Frameworks for designing organizational structures around speed versus coherence trade-offs. \n \n Contrasts centralized models (Apple: coherent user experience through central coordination) with decentralized models (Amazon: parallel execution through autonomous teams with minimal dependencies) \n Emphasizes functional structures over divisional ones to reduce management layers, restore startup speed, and keep leaders close to actual work \n Guides users through context discovery, trade-off ide

Navigate career transitions using frameworks from 76 product leaders who successfully pivoted roles and industries. \n \n Covers four transition types: new role, new function, new stage, or entirely new path; includes readiness assessment and low-risk experimentation methods \n Core principles emphasize progress over pay, relationship-building over linear promotion, and treating your career like a product with testable hypotheses \n Provides diagnostic questions to uncover motivations (\"pushes\

Product launch planning and execution framework based on strategies from 26 product leaders. \n \n Covers launch types (company, funding, feature, release), goal clarification (acquisition, recruiting, fundraising), and readiness assessment before designing the approach \n Core principles include pitching exclusives to single reporters, using funding as a news hook rather than the story, and separating soft launches from high-impact marketing events \n Emphasizes concentrated \"lightning strike\

Bridge design and engineering teams by clarifying roles, organizational placement, and hiring strategy. \n \n Defines design engineering as merging UX design with engineering to accelerate prototyping and production shipping, with scope varying from validation prototypes to production-ready code \n Emphasizes combining design sensibility with shipping ability rather than seeking unicorn-level expertise in both disciplines \n Guides organizational placement decisions, handoff friction diagnosis,

Structured 30-60-90 day onboarding framework drawing from 14 product leaders' approaches. \n \n Covers listening tours, milestone planning, early wins, and belonging through pairing rather than isolation on day one \n Emphasizes defining success at 90 days, 1 year, and 2 years before onboarding begins, plus identifying golden rituals to teach by first Friday \n Includes relationship design conversations, documented management philosophy, and early ownership assignment to accelerate ramp-up to 30

Team culture frameworks drawn from 138 product leaders at startups through Google and Airbnb. \n \n Focuses on articulating existing culture rather than inventing new values; helps identify behaviors in high performers and document what already works \n Emphasizes culture as a decentralized decision-making tool for remote and distributed teams, enabling sound choices when leadership isn't present \n Covers psychological safety, trust-building, and feedback loops as foundations for organizational

Structured hiring framework from 94 product leaders to make stronger candidate decisions. \n \n Apply 12 core principles covering reference checks, work trials, agency assessment, and T-shaped hiring to evaluate candidates systematically \n Use diagnostic questions to understand hiring stage, team gaps, and whether decisions are based on structured rubrics or intuition alone \n Challenge common biases like pedigree shortcuts, gut-feel-only decisions, and unicorn hiring; prioritize references, pa

Practical guidance for building effective AI applications using techniques from 60 product leaders and practitioners. \n \n Covers core prompting patterns: few-shot examples, decomposition for complex tasks, self-criticism, and context placement for cache efficiency \n Emphasizes architecture decisions over prompt tuning: context engineering, RAG data preparation, layered model supervision, and specialized models for specific tasks \n Provides evaluation frameworks: mandatory evals with binary P

Framework for writing job descriptions that attract the right candidates by defining business impact. \n \n Start with 12-month success: define what changes in the business after the hire, not a list of daily tasks \n Identify the spike: determine one or two areas where the candidate must excel, rather than seeking a generalist \n Replace proxies with outcomes: frame requirements around specific capabilities and progress, not years of experience or tool lists \n Use polarizing language intention

Structured guidance for running discovery interviews and extracting actionable customer insights. \n \n Covers interview preparation, question design, participant recruitment, and technique coaching based on principles from 43 product leaders \n Emphasizes collecting behavioral stories over opinions, watching users in context, and avoiding leading questions or solution pitching \n Includes frameworks like the Four Forces for mental structure and guidance on right-sizing sample sizes (7-14 interv

Negotiate job offers and compensation using strategies from product leaders. \n \n Focuses on identifying success factors beyond salary (tech debt, headcount, budget) and negotiating for those before discussing compensation \n Emphasizes collaborative language (\"Are you open to...?\") and live conversations with hiring managers over email negotiations \n Helps distinguish whether salary is the real goal or a proxy for respect, learning, autonomy, or growth \n Suggests alternative arrangements l

Framework for evaluating emerging technologies using insights from 22 product leaders. \n \n Start by clarifying the problem being solved, then assess technology maturity and stability for your specific use case \n Adopt a \"build and buy\" mindset: purchase tools for standard 90% functionality, build custom solutions for your unique 10% \n Prioritize mental bandwidth and core competencies over cost savings; constantly re-test assumptions about what new tools can actually do \n Design for modula

Frameworks for running more effective meetings drawn from 40 product leaders. \n \n Separates meetings into strategic (open-ended discussion) and operational (structured updates) to prevent mixing incompatible formats \n Emphasizes that meetings should only host discussion; discovery and decision-making belong in async channels \n Provides structured closing questions (what was decided, who does what by when, who else needs to know) to ensure alignment and prevent re-meetings \n Includes guidanc

Navigate tough feedback, performance, and conflict conversations using frameworks from 43 product leaders. \n \n Covers five conversation types: giving feedback, performance discussions, terminations, conflict resolution, and delivering bad news like denied promotions \n Teaches four core frameworks: Radical Candor (care personally + challenge directly), Situation-Behavior-Impact (objective, specific feedback), Nonviolent Communication (distinguish feelings from attributions), and structured ter

Strategic guidance for founders navigating capital raises and investor relationships. \n \n Emphasizes leading with your strongest proof point on the first slide, whether that's traction, team insight, or market opportunity, since investors form impressions within the first minute \n Challenges the assumption that venture capital is the right path by exploring alternatives like bootstrapping and assessing alignment with your goals and business model \n Prepares founders for the psychological rea

Framework for diagnosing and fixing supply-demand imbalances in two-sided marketplaces. \n \n Guides you through understanding your marketplace type, identifying whether you're supply-constrained or demand-constrained, and defining fill rate as your core liquidity metric \n Emphasizes that liquidity is fundamentally about reliability: how often buyers find what they want and sellers find buyers \n Highlights the \"whac-a-mole\" nature of marketplace management, requiring constant rebalancing of

Apply working backwards methodology to clarify product vision before building. \n \n Guides users through the core framework: identify the customer problem, write a mock press release, develop an FAQ, and evaluate three criteria (big idea, strategic fit, viable plan) \n Draws on insights from 12 product leaders including Ian McAllister, Bill Carr, and Melanie Perkins on starting with customer problems, defining ideal future states, and escaping incremental thinking \n Flags common mistakes like

Framework-based guidance for hiring and scaling sales teams from zero to repeatable revenue. \n \n Emphasizes proving founder-led repeatability (50-100 at-bats at 15-25% win rate) before hiring any salespeople \n Recommends always hiring sales reps in pairs to validate process and create performance baselines, not single hires \n Matches sales archetypes (hunters for outbound, growers for inbound/PLG) to your specific motion and buyer profile \n Delays VP of Sales hires until you have two reps c

Framework-based guidance for planning and running productive team offsites. \n \n Draws on five product leader frameworks covering purpose clarification, team readiness assessment, structure design, and logistics \n Emphasizes removing teams from day-to-day routines, using physical collaboration tools like whiteboards, and balancing strategy work with social connection \n Flags common pitfalls including overpacked agendas, soft skills training that masks underlying conflicts, and infrequent in-p

Help users pitch journalists and build lasting media relationships using proven outreach strategies. \n \n Follow a three-step framework: prepare your story and assets, identify reporters who cover your space, then pitch with exclusives one outlet at a time \n Avoid mass pitching and generic angles; frame stories around reader interests and trends, not your company's announcement \n Build relationships before you need coverage by engaging with journalists' work and becoming a trusted source over

Design sales compensation plans aligned with business goals and customer retention. \n \n Starts with the standard 50/50 base-to-variable split, then adjusts based on sales cycle length, customer churn patterns, and business model to avoid misaligned incentives \n Emphasizes tying compensation to customer outcomes and net dollar retention, not just closed bookings, to reward sticky deals over churny ones \n Guides ramp structures for new hires (3–6 months for SMB, 6–12 months for enterprise) wit

Guide organizations toward modern product practices through structural, cultural, and process change. \n \n Helps diagnose current state (feature teams, waterfall, output focus) and readiness for transformation, including stakeholder authority and expected resistance \n Emphasizes pilots over big-bang change: start with empowered product teams that demonstrate success, then build credibility for broader adoption \n Flags common pitfalls including treating framework adoption as the end goal, igno

Build strong engineering culture using frameworks from 19 product leaders. \n \n Diagnose current state across team size, practices, and pain points, then identify bottlenecks in developer experience, org structure, talent, or process \n Core principle: Conway's Law means organizational structure directly dictates architecture and product quality; align teams to desired outcomes \n DevEx is foundational; optimize for flow state, cognitive load, and feedback loops rather than toolchain selection

Frameworks for running productive one-on-one meetings drawn from seven product leaders. \n \n Emphasizes coaching over advising: shift to curiosity and empower reports to solve problems rather than providing immediate answers \n Recommends dedicated deep-dive conversations on past (life story), future (dreams), and present (career action plan) to build long-term development \n Includes monitoring for joy and recovery as performance indicators; treat lack of daily joy as a risk requiring interven

Strategic partnership and BD guidance grounded in insights from nine product leaders. \n \n Covers four core phases: understanding opportunities, assessing network vs. merit dynamics, designing pitches that show mutual benefit, and navigating negotiations with timing and leverage \n Emphasizes industry-specific dynamics—relationships dominate in healthcare, finance, and enterprise, while product merit matters more elsewhere \n Advises building scalable partner platforms rather than one-off deals

Framework-based guidance for working through imposter syndrome and self-doubt. \n \n Normalizes imposter syndrome as a universal experience among high performers, especially during growth periods, and reframes discomfort as evidence of appropriate challenge rather than inadequacy \n Helps users identify the specific fear beneath their feelings (exposure, mistakes, belonging) and articulate the gap between external evidence (accomplishments, hiring decisions) and internal feelings \n Provides con

Structured decision-making frameworks and processes drawn from 65 product leaders. \n \n Guides users through decision classification (reversible vs. irreversible), blocker identification, and framework selection to move from deliberation to action \n Covers core principles including making implicit assumptions explicit, using curiosity loops for advice gathering, and distinguishing when data-driven analysis ends and conviction takes over \n Flags common pitfalls: analysis paralysis, decision by

Navigate cross-functional friction using frameworks from 57 product leaders at Linear, Airbnb, and similar companies. \n \n Diagnose collaboration issues by identifying whether the root cause is role clarity, communication patterns, or structural misalignment \n Apply core principles including credit sharing, \"Yes, and\" thinking, written role expectations, and direct stakeholder-engineer connections to reduce handoff friction \n Build the product trio (PM, designer, engineer) as the core decis

Frameworks for delegating effectively by diagnosing blockers, matching delegation style to context, and building team autonomy. \n \n Diagnose why tasks are being held on to: identity, control issues, or lack of trust in the team \n Use energy audits and the Eisenhower Matrix to identify delegation candidates; distinguish between core competencies worth retaining and tasks that should be handed off \n Balance involvement with autonomy: provide context and parameters rather than prescribing every

Strategies for working effectively with managers and executives drawn from 35 product leaders. \n \n Proactively communicate upward with regular updates on priorities, blockers, and progress rather than waiting to be asked, using consistent formats like weekly emails \n Bring recommendations and point of view to your manager instead of just problems, reducing their cognitive load and positioning yourself as an ally \n Understand your manager's priorities and two levels up to tailor communication

Build meaningful mentor and sponsor relationships using frameworks from 19 product leaders. \n \n Distinguish between mentors (advice-givers), sponsors (opportunity-creators), and coaches (accountability partners); each requires a different approach and relationship-building strategy \n Start with small, specific asks that take minutes to answer via email, then build trust by following up with results before requesting larger commitments or ongoing relationships \n Maintain a stable of 3–4 mento

Framework for diagnosing energy drains, auditing calendars, and scheduling work around peak performance zones. \n \n Helps identify activities that energize vs. deplete you, then guides calendar restructuring to spend more time in your \"zone of genius\" \n Built on five productivity frameworks covering energy-driven scheduling, superpower activation, delegation strategies, and post-activity energy tracking \n Includes diagnostic questions and common pitfalls (ignoring energy signals, optimizing

Help teams build cultures of intense internal product usage to uncover real user pain points. \n \n Focuses on two core practices: requiring all team members to become active users of their own product, and using it intensely every day for real work rather than demo testing \n Provides a four-step implementation framework: assess current usage levels, identify gaps in firsthand experience, design systems that make dogfooding natural and required, and measure impact on product decisions \n Flags

Build a compelling promotion case by diagnosing blockers and framing advancement as solving company problems. \n \n Diagnose the situation by understanding current role, target role, manager relationship, and identifying whether blockers are visibility, advocacy, role availability, or skill gaps \n Core principle: perform at the next level before requesting the title; promotions recognize readiness, they don't develop it \n Frame promotion conversations around business impact and company needs,

Frameworks for developing and coaching product managers using proven practices from top-company leaders. \n \n Establishes competency models and definitions of \"good\" before attempting to develop any PM, ensuring coaching is contextual to company stage and needs \n Uses Bloom's Taxonomy to diagnose where PMs fall on the critical thinking spectrum (knowledge through evaluation) and targets development accordingly \n Provides a five-step coaching framework: define success, assess current state,

Framework-based guidance for designing and executing platform business strategies across marketplaces, ecosystems, and developer platforms. \n \n Covers platform lifecycle stages (moat-building, opening, closing) and helps identify which network effects and participant sides drive value \n Emphasizes treating platforms as products with dedicated management, reducing cognitive load through clear interfaces, and building comprehensive systems rather than isolated features \n Includes governance an

Structured frameworks for evaluating competing options and making clearer trade-off decisions. \n \n Applies mental models from 40 product leaders covering decision context, constraint identification, cost quantification, and framework selection \n Core principles include optimizing for order-of-magnitude over precision, applying the \"would I start this today?\" test to avoid sunk cost fallacy, and using weighted criteria matrices for multi-factor decisions \n Helps surface hidden costs like ma

Systematic evaluation framework for AI products using practitioner-driven methodologies. \n \n Guides users through understanding what \"good\" looks like, designing rubrics and test cases, and implementing scoring criteria aligned with actual user needs \n Emphasizes manual review and error analysis as prerequisites to building meaningful evals, with structured workflows for clustering failure patterns \n Flags common pitfalls including vague criteria, LLM-as-judge without validation, and Liker

Help teams set realistic deadlines and hit them consistently using frameworks from 13 product leaders. \n \n Diagnose timeline problems as estimation issues, scoping issues, distraction issues, or unrealistic stakeholder expectations, then apply the right framework (phase-based commitments, hill charts, or early shipping) \n Commit to phases within your control (discovery, solutioning, build, launch) rather than distant delivery dates; only provide engineering dates once solutioning is complete

Guide teams through learning-focused post-mortems and retrospectives using frameworks from 11 product leaders. \n \n Helps frame exercises as blameless learning opportunities rather than blame-focused reviews, with emphasis on psychological safety and honest sharing \n Covers core principles including pre-mortems with kill criteria, reframing failure as growth, and institutionalizing weekly impact and learnings reviews \n Guides users through structured questioning to surface systemic insights,

Structured framework for evaluating startup pivots using insights from product leaders. \n \n Applies the Four Ps framework (Problem, Persona, Product, Positioning) to diagnose what needs to change, rather than pivoting blindly \n Emphasizes rational distance from emotional attachment: assess whether you've truly exhausted possibilities or just lost momentum \n Challenges founders to consider magnitude: most pivots are too small (10%) when breakthrough often requires fundamental rethinking (200%

Help teams scope projects and cut features using frameworks from 15 product leaders. \n \n Teaches appetite-based planning: set fixed time budgets and vary scope instead of extending deadlines \n Covers eight core principles including MVP as validation tool, aggressive feature cutting, and the \"build the scooter, not the axle\" approach to end-to-end value \n Provides Wizard of Oz testing guidance to validate hypotheses manually before engineering investment \n Includes diagnostic questions and

Frameworks and principles from 47 product leaders for shipping faster without sacrificing quality. \n \n Emphasizes speed as a signal of competence and mastery; prioritizes shipping early to accelerate feedback loops and learning \n Guides quality tradeoffs by helping you define a Product Quality List checklist and identify which standards must be met before launch versus after \n Helps diagnose shipping blockers by asking diagnostic questions about scope, dependencies, decision-makers, and the

Framework for running design reviews using feedback hierarchy and structured critique. \n \n Prioritize feedback by value first (does it solve the problem?), then usability, then delight; defer aesthetic concerns until core value is validated \n Assign senior leaders as project sponsors to oversee quality through live demos and review 100% of shipped screens before launch \n Structure reviews around specific feedback requests; ask presenters exactly what type of input they need rather than openi

Design and scale internal platforms by abstracting common capabilities and planning infrastructure before hitting limits. \n \n Focuses on understanding platform purpose, assessing organizational readiness, identifying leverage points, and designing for actual developer adoption rather than theoretical needs \n Emphasizes invisible infrastructure qualities like reliability, performance, and privacy as critical success factors alongside visible features \n Recommends proactive infrastructure scal

Behavioral interview framework drawn from 75 product leaders' hiring experience. \n \n Emphasizes behavioral-based questioning to reveal actual capability over rehearsed answers; drill six levels deep into the \"how\" to uncover technical expertise \n Guides role-specific competency definition, interview structure design, and question crafting that surface genuine insight rather than confident delivery \n Flags common mistakes: performative STAR responses, insufficient probing, hypothetical ques

Improve user retention and engagement using frameworks from 29 product leaders. \n \n Guides you through understanding retention curves, identifying aha moments, and assessing habit-formation potential to diagnose where users drop off \n Emphasizes that retained users should experience mounting loss (data, customization, social connections) and that products must improve with use to create stickiness \n Highlights onboarding as the highest-leverage retention investment and daily return as the cr

Frameworks for building and scaling product operations functions across growing teams. \n \n Bridges product and operations by creating systems that enable PMs to focus on strategy rather than operational overhead like release management, enablement, and cross-functional coordination \n Standardizes processes, tooling, and insights across product teams while preserving PM decision-making authority; product ops informs, not decides \n Addresses common scaling challenges: surfacing user research a

$22

Framework for defining a single, customer-centric metric that aligns teams and drives product decisions. \n \n Measure value delivered to users, not revenue or internal activity; use proxy metrics like messages sent or nights booked that correlate with long-term outcomes \n Ensure simplicity and universal understanding across the company; avoid composite scores and technical jargon that obscure meaning \n Verify actionability by confirming teams can influence the metric through their work, and a

Synthesize customer feedback into actionable product insights using frameworks from 56 product leaders. \n \n Guides users through identifying patterns across multiple feedback channels (NPS, support, interviews, social) and clustering by behavioral pathways rather than demographics \n Emphasizes distinguishing root causes from surface-level complaints, with techniques for uncovering what users don't explicitly state \n Includes principles on prioritizing signal over noise, talking to churned us

Framework-driven pricing design and optimization using insights from 46 product leaders. \n \n Guides users through understanding business models, assessing value delivery, identifying constraints, and designing iterative pricing strategies \n Emphasizes willingness-to-pay research as the foundation for pricing decisions and product roadmap prioritization \n Covers key transitions: freemium vs. paid models, self-serve to sales-led (around $10K–$15K ARR), and sampling premium features in free tie

Framework-based assessment of product-market fit using signals from 46 product leaders. \n \n Apply the Sean Ellis \"very disappointed\" survey as a leading PMF indicator, targeting 40% threshold before long-term retention data is available \n Diagnose stage through retention curves, reference customer counts, and customer pull signals; distinguish between vanity metrics and genuine PMF evidence \n Recognize PMF across four levels (nascent to extreme) with segment-specific fit; understand that P

Frameworks and principles for clearer, more persuasive business writing drawn from 38 product leaders. \n \n Applies the pyramid principle: lead with your conclusion, then support it, rather than building up to an answer \n Emphasizes cutting preamble and unnecessary context to start at the point of highest relevance or tension \n Guides users to test clarity by ensuring someone unfamiliar with the topic could understand the core message \n Covers recurring mistakes: burying conclusions, over-re

Navigate product planning in uncertain environments using adaptive frameworks from 44 product leaders. \n \n Emphasizes optionality over prediction: maintain flexibility to pivot when new information emerges rather than committing to rigid roadmaps, especially critical in fast-moving AI/ML contexts \n Teaches decision frameworks including type one/two decisions (reversible vs. irreversible), data as compass not GPS, and explicit decision triggers tied to learning rather than calendar dates \n Co

Frameworks for building and scaling product communities from 18 leaders at Notion, Figma, and WordPress. \n \n Identify your community type (user, agency, or partner) and find the \"atomic unit of sharing\" that members naturally want to showcase \n Start with listening to early members through 1:1 calls before imposing structure; begin with your 20 most vocal organic supporters \n Design for quality over rapid growth by implementing application processes and cohort-based onboarding to maintain

Develop product taste and intuition using frameworks from 10 product leaders. \n \n Grounded in core principles: intuition as hypothesis generation, taste as a learnable skill built through exposure hours, and deliberate self-observation of your own product reactions \n Guides users to identify gaps in their judgment, suggest targeted practice activities, and know when to trust gut instinct versus data \n Includes diagnostic questions to surface what products users analyze regularly, how they no

Guide users through transitioning from pure product-led growth to sales-assisted expansion using product usage signals. \n \n Helps define Product Qualified Leads (PQLs) and Product Qualified Accounts (PQAs) based on actual product engagement rather than marketing metrics \n Covers the complete handoff workflow: identifying usage signals that trigger sales outreach, designing smooth transitions from self-serve to sales-assisted, and aligning product and sales team incentives \n Emphasizes person

Craft compelling product positioning and messaging using frameworks from 58 product leaders. \n \n Guides users through understanding target audience, identifying competitive frames, finding differentiated value, and testing message resonance \n Emphasizes positioning as foundational to all marketing, with weak positioning creating pipeline friction and customer confusion \n Flags common mistakes: feature-first messaging, positioning by generic adjectives, trying to appeal to everyone, and compa

Navigate enterprise sales deals through buying committee dynamics, procurement, and overcoming customer indecision. \n \n Helps identify deal stage, map stakeholders (champion, economic buyer, decision-makers), and arm internal advocates with role-specific materials \n Addresses the root cause of deal loss: customer fear of messing up and being blamed, not just competitive pressure or missing urgency \n Guides procurement navigation by proactively handling administrative burden, compliance requi

Help teams create written technical roadmaps aligned to business outcomes using structured frameworks. \n \n Applies the Rumelt framework to organize strategy into three parts: Diagnosis (core technical challenge), Guiding Policies (decision-making principles), and Actions (specific initiatives) \n Emphasizes documenting strategy in writing so it can be critiqued, improved, and aligned across teams rather than existing only in leadership's head \n Flags common pitfalls including tool proliferati

$22

Help users articulate problems clearly before pursuing solutions, using frameworks from 91 product leaders. \n \n Guides users through understanding current framing, identifying struggling moments, separating problems from solutions, and validating problem urgency \n Covers eight core principles including avoiding the shiny object trap, prototyping to define problems, and spending more time on problem understanding than solution design \n Includes diagnostic questions to uncover user context, wo

Guide founders through early-stage sales, from first outreach to repeatable processes. \n \n Diagnose where deals stall (lead generation, qualification, discovery, closing, or implementation) and apply stage-specific strategies based on insights from 16 product leaders \n Emphasize founder-led sales as a learning phase, not a revenue phase; stay hands-on until you've closed ~$1M ARR with a documented, repeatable process \n Cover core tactics: manual personalized outreach over AI tools, diagnosti

Framework-driven guidance for writing specs and design documents from seven product leaders. \n \n Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details \n Favor prototypes over static documentation; test the feel with real software rather than screenshots \n Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing \n Recognize that temporary design shortcuts often become permanent product decisions;

Framework-driven approach to sequencing features and allocating resources across competing priorities. \n \n Draws on 75 product leaders' frameworks including \"cannonballs vs. lead bullets\" (80/20 balance of big bets and incremental work), \"seasons\" for fast-changing markets, and growth models as common currency for cross-team comparison \n Emphasizes separating conviction from hypothesis, challenging assumptions about impact, and using roadmaps as feasibility checks rather than commitments

Framework-based guidance for building and scaling design systems from product leaders at Figma and Airbnb. \n \n Covers four core principles: separating conceptual design from production output, leveraging design systems for organizational scaling, creating self-teaching assets, and evolving beyond flat design toward dimensional interfaces \n Provides assessment questions to determine scope (component library, tokens, documentation), adoption strategy, and success metrics \n Flags common pitfall

Help teams create effective OKRs and goals aligned with company strategy. \n \n Guides users through understanding context, clarifying goal levels (company, department, team, individual), and ensuring strategy precedes goal-setting \n Emphasizes core principles: keep goals one step from company objectives, balance quantitative and qualitative metrics, use absolute numbers over ratios, and separate strategy discussions from OKR planning \n Flags common pitfalls including key results written as ta

Design product onboarding that gets users to their aha moment in the first 30 seconds. \n \n Focus intensely on the immediate post-signup experience as the primary driver of word-of-mouth growth and long-term retention \n Remove friction between signup and core value by identifying and eliminating invisible blockers that prevent users from experiencing product features \n Apply game design principles like progressive disclosure and reward mechanics to guide users toward meaningful action rather

AI-assisted software development for non-engineers building prototypes and MVPs through natural language. \n \n Guides users through iterative AI-powered development: breaking problems into smaller pieces, refining outputs through follow-up prompts, and testing generated code \n Best suited for prototypes, internal tools, and MVPs; helps users understand when professional engineering review is needed for production systems \n Teaches vibe coding as a distinct skill for product managers, marketer

Strategic AI product decision-making guided by frameworks from 94 product leaders and practitioners. \n \n Helps distinguish genuine user problems from \"AI for AI's sake\" by starting with problem definition, not technology \n Guides critical architecture decisions including build vs buy, model selection, human-AI boundaries, and multi-model systems \n Emphasizes designing for AI failure modes, non-determinism, and rapid iteration through feedback loops and evals \n Flags common mistakes like s

Craft compelling brand narratives using frameworks from 30 product leaders and storytelling experts. \n \n Guides users through understanding audience context, identifying core transformations, structuring narratives, and creating memorable moments that stick \n Emphasizes positioning the customer as the hero and your brand as the mentor providing tools, not centering the founder's story \n Covers nine core principles including leading a movement rather than solving problems, finding the singula

Strategic content marketing frameworks from 23 product leaders covering goal validation, format selection, and sustainable publishing. \n \n Validate search demand upfront and ensure content fully satisfies user intent; write for specific professional anxieties, not general information \n Prioritize consistency and daily reps over production value; treat content as an evergreen asset requiring regular updates rather than chasing news cycles \n Match content format to creator strengths and audien

Help teams write focused, actionable product requirements documents using frameworks from 11 product leaders. \n \n Start with problem and context before solutions; include \"why now\" to justify timing and urgency against competing priorities \n Choose the right format for your product type: traditional PRDs for feature specs, prototypes or prompt sets for AI features, executable evals as living requirements \n Define success upfront with clear metrics and outcomes; keep documents lightweight a