shipping-products
This skill helps users accelerate product launches and releases by applying frameworks from 47 product leaders. It guides users through identifying shipping blockers, challenging timelines, and balancing speed with quality through core principles like shipping smaller changes frequently, getting early feedback, and maintaining relentless focus until completion. Use it when planning a product launch, trying to increase release velocity, struggling with quality concerns before shipping, or establishing better release practices.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/shipping-products && cp -r /tmp/shipping-products/skills/shipping-products ~/.claude/skills/shipping-productsSKILL.md
# Shipping Products Help the user ship products effectively using frameworks and insights from 47 product leaders. ## How to Help When the user asks for help with shipping: 1. **Understand the blocker** - Ask what is preventing the ship: scope, quality concerns, dependencies, or organizational friction 2. **Assess the context** - Determine if this is a new product, feature iteration, or infrastructure change 3. **Challenge timelines** - Apply the 'maximally accelerated' principle to identify the critical path 4. **Guide quality tradeoffs** - Help balance speed with appropriate quality standards for the product type ## Core Principles ### Speed is a signal of competence Nan Yu: "If you look at people at the pinnacle of their craft, you can tell how good the output is going to be by how fast they're going." High speed combined with quality indicates mastery, not sloppiness. Use speed to increase iterations and variations tested. ### Ship to get feedback Dylan Field: "Get it out as fast as you possibly can. The faster you get it out, the more feedback you get." Prioritize shipping speed to accelerate the feedback loop, which is the most valuable asset in early product development. ### Speed and stability move together Nicole Forsgren: "When you move faster, you are more stable. You're pushing smaller changes more often with a smaller blast radius." Push smaller changes more frequently to reduce complexity and make failures easier to debug. ### 99% done is 0% done Dmitry Zlokazov: "If something is 99% done, it's closer to 0% rather than 100%." A product provides zero customer value until fully finished and launched. Maintain relentless focus until shipping is complete. ### Ask why you can't ship tomorrow Nick Turley: "Why can't we do this now? If this was the most important thing and you wanted to truly maximally accelerate it, what would you do?" Use this question to strip away non-essential blockers and identify the critical path. ### Use quality checklists Matt MacInnis: "We have a Product Quality List that articulates the standards we want you to meet when you ship." Create a PQL checklist of quality standards that must be met before release, and iterate on it when bugs slip through. ### Ship to learn, then polish Nick Turley: "You won't know what to polish until after you ship." In emergent products like AI, ship early to discover which areas actually require polish based on real-world usage. ### Tempo matters more than org design Patrick Campbell: "Your tempo framework is more important than your org design. If a team is always planning but doesn't ship, you don't have alignment on what good tempo looks like." Define shipping frequency expectations for every department. ### Perfect execution validates strategy Naomi Gleit: "Only with perfect execution can we reevaluate whether the strategy is right or wrong." Poor execution leaves the cause of failure ambiguous. Ship properly to learn whether your strategy was correct. ### Small consistent gains compound Keith Yandell: "If you continuously push up what you ship by a week, you'll end up lapping competitors because you start the next thing a week sooner." Small velocity improvements create massive competitive advantages through compound interest. ## Questions to Help Users - "What would it take to ship this tomorrow - what's actually blocking you?" - "Is this a mission-critical product where reliability matters, or can you ship raw and iterate?" - "What is the smallest version that would let you learn something from real users?" - "Who is the single person with authority to make the final trade-off decisions?" - "What quality bar must be met, and what can be polished after launch?" - "When did you last have a working, testable version of this product?" ## Common Mistakes to Flag - **Over-polishing before launch** - You can't know what needs polish until you see real usage patterns - **Waiting for pixel-perfect designs** - Early versions don't need pixel perfection; they need working software you can interact with - **Feature flag sprawl** - Excessive feature flags create technical debt and hidden failure points during launches - **No single decision maker** - Coherent product design requires one person with moral authority to make trade-off decisions - **Confusing activity with shipping** - High-quality ideation and documentation are useless without the velocity to actually release ## Deep Dive For all 55 insights from 47 guests, see `references/guest-insights.md` ## Related Skills - Writing PRDs - Stakeholder Alignment - Setting OKRs & Goals - Usability Testing
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.