Shipping Velocity
Help users accelerate their product development cycles by implementing high-intensity...
Install
npx skills add RefoundAI/lenny-skills --skill shipping-velocity -g -a claude-code -y- Repository
- RefoundAI/lenny-skills1.5k
- Category
- Engineering
- Updated
- 4mo ago
- License
- MIT
- Context cost
- Mediumabout 1,766 tokens
- Runs scripts
- No, instructions only
What it does
Help users accelerate their product development cycles by implementing high-intensity rituals, ruthless scoping, and technical guardrails that allow teams to ship faster without sacrificing quality.
Shipping Velocity
Accelerate execution by removing organizational friction and establishing a high-intensity shipping culture.
Help the user with shipping velocity using insights from 19 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Audit existing bottlenecks - Identify where projects get stuck in your current lifecycle and benchmark against high-performing teams.
- Implement velocity rituals - Guide the setup of daily stand-ups, demos, and single-threaded teams to maintain momentum.
- Apply scoping frameworks - Assist in cutting feature scope down to the most essential, marketable value to meet tight deadlines.
- Establish measurement systems - Set up the Core 4 metrics to track speed, quality, effectiveness, and impact simultaneously.
Core Principles
Ruthlessly cut feature scope
Gaurav Misra: "We take the design and we cut, cut, cut until we can really say that it's going to be useless if we cut anymore. We get that out and people come in."
Maintain momentum by slicing new features repeatedly until only the essential marketable value remains for a one-week deadline.
Isolate teams for single-threaded focus
Geoff Charles: "And I think the recipe for all this is constantly small teams have a single-threaded focus, give them the resources they need to execute big lofty goals, very tight timelines, and then shield them from the chaos that is the rest of the organization."
Protect development speed by shielding small teams from organizational overhead and task-switching.
Establish daily accountability rituals
Mayur Kamat: "We would pick a owner for something really urgent at the nightly leadership call. Then that owner would be expected to have all hands on deck for however long that problem is every single day and then report the updates on the daily call."
Use extreme leadership involvement and daily stand-ups to unblock decisions within 24 hours for high-stakes projects.
