
Defining Product Vision
Draft and stress-test a product vision using distilled Lenny Podcast guest patterns before you scope features or roadmap bets.
Overview
Defining Product Vision is an agent skill most often used in Idea (also Validate, Build) that compiles Lenny Podcast guest insights so solo builders can articulate a credible product vision and portfolio story.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill defining-product-visionWhat is this skill?
- Aggregates defining-product-vision themes from 101 Lenny Podcast guests
- Surfaces 143 indexed mentions with quotable guest insights and tactical bullets
- Includes concrete frameworks like the solar-system core-plus-satellite product model
- Ties vision statements to UX and user action, not slogans alone
- Useful as reference material while writing positioning, PRDs, or investor narrative
- 101 podcast guests
- 143 mentions in the defining-product-vision corpus
Adoption & trust: 1.5k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know what you want to build technically but struggle to express a memorable, trustworthy product vision investors, users, and your future self can align on.
Who is it for?
Solo founders and indie PMs synthesizing vision language before scope commits, especially for content, SaaS, or multi-product portfolios.
Skip if: Teams that already have a signed vision doc and OKRs, or builders who only need API integration help with no positioning work.
When should I use this skill?
Articulating or refining product vision, portfolio narrative, or north-star language before committing roadmap scope.
What do I get? / Deliverables
You leave with guest-backed framing, metaphors, and tactical bullets you can paste into positioning docs, roadmap narratives, or validation storyboards before deeper planning skills run.
- Vision framing bullets
- Guest-backed metaphors and tactical advice excerpts
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Vision framing belongs at the start of the journey when you are still choosing what world you are building for, even though you will reuse it later in validation and PM. Guest insights and metaphors (for example solar-system portfolios) support opportunity research and narrative clarity before a locked spec.
Where it fits
Compare how media and SaaS guests describe vision so you pick a metaphor for your own one-liner.
Decide which satellite bets share DNA with your core product before running a landing-page test.
Align quarterly roadmap themes with a sun-and-satellite portfolio story for stakeholders.
Pull quotable vision language into a launch narrative without inventing new positioning from scratch.
How it compares
Use for curated podcast-derived vision patterns instead of generic one-paragraph mission generators that lack operator-tested nuance.
Common Questions / FAQ
Who is defining-product-vision for?
Solo builders and small product teams who want Lenny Podcast-derived vision patterns while drafting positioning, narrative, or early roadmap direction.
When should I use defining-product-vision?
Use it during Idea research to shape your north star, during Validate when scoping what to prove first, and during Build PM when aligning roadmap stories—before you treat the vision as final.
Is defining-product-vision safe to install?
It is editorial reference content; still review the Security Audits panel on this page and your agent vendor policies before enabling third-party skills.
SKILL.md
READMESKILL.md - Defining Product Vision
# Defining Product Vision - All Guest Insights *101 guests, 143 mentions* --- ## Alex Hardimen *Alex Hardimen* > "At the most basic level, I would say that our product is our journalism, which we then marry with a really compelling and useful user experience, in a way that helps people really act on our journalism so that they can understand and engage with the world around them." **Insight:** Product vision in media should center on the core content (journalism) enhanced by a user experience that drives real-world engagement. **Tactical advice:** - Marry core content with compelling UX - Focus on helping users 'act' on the information provided *Timestamp: 00:16:46* --- > "We have the solar system metaphor where for us news is the sun in the sense that it's why we exist. It is what gives us our brand heritage and reputation. It's what instills trust. It's also where we just have the largest audience when you think about a funnel for our portfolio, and it's also where we just have the most amount of high quality coverage. But then that sun helps you give birth to other satellite planets or products that have a lot of the same DNA." **Insight:** Use a 'solar system' model to define a product portfolio where a core 'sun' product provides the brand equity and audience for satellite products. **Tactical advice:** - Identify the 'sun' product that drives brand heritage and trust - Build satellite products that share the core DNA of the primary product - Use the primary product as the top-of-funnel for the rest of the portfolio *Timestamp: 00:19:36* --- > "One thing that's really interesting is that our impact and our business goals are in service of our mission, which is to seek the truth and help people understand the world, not the other way around. What it means is that the way that we think about impact is growing a giant subscription business. That business exists to strengthen an informed democracy." **Insight:** Align business goals (like subscriptions) as a means to fund and achieve a broader societal mission. **Tactical advice:** - Define business metrics as being 'in service' of the mission - Measure impact not just by revenue, but by mission-driven outcomes like policy changes *Timestamp: 01:08:10* ## Alisa Cohn *Alisa Cohn* > "Vision of the company. So when this company is successful, what does that look like?... What that might look like is a big venture outcome that we all read about. And if you are both assuming that you both think the same thing but aren't talking about it explicitly... then what often happens if you have differences is they come home to roost." **Insight:** Founders and leaders must explicitly align on what 'success' looks like to avoid fundamental strategic drift. **Tactical advice:** - Ask: 'What is the vision for the company when it reaches its full potential?' - Discuss the trade-offs inherent in different visions (e.g., lifestyle business vs. venture scale) *Timestamp: 01:02:01* ## Alex Komoroske *Alex Komoroske* > "You need coherence about where you're going and the way you get that is by creating a North Star for yourself. It should be in three to five years in the future, it should be very low resolution. It should describe a thing that every single person who reads it who has any kind of knowledge that might be useful or relevant agrees that it is plausible." **Insight:** A North Star should be a low-resolution, highly plausible future state that provides coherence without over-prescribing the path. **Tactical advice:** - Set a 3-5 year vision that is 'low resolution' to allow for adaptation. - Ensure the vision is plausible enough that experts across functions (legal, eng, etc.) can see how it could work. *Timestamp: 01:10:51* ## Ami Vora *Ami Vora* > "If we all agree that the feeling of something should be, I'm sitting in Dolores Park with my friends on a sunny Saturday, then people will just naturally build something that feels more consistent. You know wh