north-star-vision
owl-listener/designer-skills
Define a compelling long-horizon product vision that aligns teams and anchors strategic decisions.
What is north-star-vision?
North Star Vision helps teams articulate an inspiring future state that guides direction and resolves contested strategy. Use it when product direction is unclear or teams lack alignment; for near-term project scope, use the design-brief skill instead.
- Craft a one-sentence vision statement capturing who, what experience, and why it matters
- Identify 3–5 design pillars that define strategic focus areas and differentiators
- Develop vision scenarios as concrete narrative stories of the future experience
- Establish success criteria with qualitative signals, quantitative metrics, and milestones
- Connect long-term aspiration to daily work through pillar-driven reviews and planning
How to install north-star-vision
npx skills add https://github.com/owl-listener/designer-skills --skill north-star-visionHow to use north-star-vision
- 1.Gather research on user needs, market trends, and competitive context
- 2.Facilitate an aspiration workshop with key stakeholders to explore possibilities
- 3.Draft a vision statement (one sentence) with who, what experience, and why
- 4.Define 3–5 design pillars that capture strategic differentiators
- 5.Write 2–3 vision scenarios as narrative stories of the future experience
- 6.Establish success criteria: qualitative signals, quantitative metrics, and key milestones
- 7.Validate the vision with broader teams and refine based on feedback
- 8.Communicate the vision actively in planning, reviews, and decision-making
Use cases
- Resolving competing product directions when stakeholders disagree on strategy
- Launching a new product line or major pivot with unclear long-term goals
- Aligning distributed teams around a shared future state before detailed roadmapping
- Defining 5+ year transformation goals while maintaining flexibility for unknowns
- Grounding quarterly planning and trade-off decisions in a coherent vision
- Product managers and leaders setting strategic direction
- Design and engineering teams needing alignment on long-term goals
- Cross-functional teams resolving conflicting visions or priorities
- Founders and executives articulating company or product transformation
north-star-vision FAQ
North-star vision defines long-horizon (1–5+ year) strategic direction and team alignment, while design-brief focuses on near-term project scope and immediate deliverables.
Typically near-term (1yr) for tangible improvements, mid-term (2–3yr) for major experience shifts, and long-term (5+yr) for aspirational transformation.
Root it in real user needs and market research, make it broad enough to accommodate unknowns, and ensure it connects to daily work through design pillars and active use in planning.
Review annually or when market conditions, user needs, or competitive landscape shift significantly; the vision should remain stable enough to guide decisions but flexible enough to evolve.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: north-star-vision
description: Articulate a long-horizon product vision that aligns teams and anchors strategy. Use when direction is contested or absent. For near-term project scope, use design-brief.
North Star Vision
You are an expert in articulating inspiring product visions that unite teams and guide direction.
What You Do
You help teams define a north-star vision — a compelling future state that inspires alignment and guides trade-offs.
Vision Components
- Vision Statement — Who, what experience, why it matters (one sentence)
- Design Pillars — 3-5 strategic focus areas defining differentiators
- Vision Scenarios — Concrete narrative stories of the future experience
- Success Criteria — Qualitative signals, quantitative metrics, milestones
Time Horizons
- Near-term (1yr): tangible improvements
- Mid-term (2-3yr): major experience shifts
- Long-term (5+yr): aspirational transformation
Process
Research synthesis, aspiration workshop, narrative writing, validation, communication.
Best Practices
- Inspiring but grounded in real needs
- Broad enough for unknowns
- Used actively in reviews and planning
- Connected to daily work through pillars
Related skills
More from owl-listener/designer-skills and the wider catalog.
onboarding-design
Design first-run experiences that get users to value fast and build confidence.
opportunity-framework
Identify, score, and prioritize design opportunities against impact and effort.
pattern-library
Document reusable design patterns with problem context, solution, anatomy, and related patterns.
presentation-deck
Structure design presentations that persuade your specific audience and drive decisions.
prototype-strategy
Choose the right prototype fidelity and method to answer your design question efficiently.
readable-measure
Set optimal line length (45–75 characters) for comfortable reading across devices and type sizes.