north-star-vision

Define a north-star product vision with pillars, scenarios, and success criteria.

2.0k|325|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill north-star-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: north-star-vision
Source: https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/north-star-vision
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill north-star-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align teams around a single, aspirational north-star vision to reduce strategic drift and improve decision clarity.

Core Features & Use Cases

  • Vision Statement: a one-sentence articulation of the future user experience and value.
  • Design Pillars: 3–5 strategic focus areas guiding roadmap decisions.
  • Vision Scenarios: concrete narratives of how the product evolves and users interact.
  • Success Criteria: qualitative signals and quantitative metrics to track progress across near-, mid-, and long-term horizons.
  • Use Case: align product strategy during planning reviews and stakeholder updates.

Quick Start

Draft a concise Vision Statement and 3 Design Pillars to start your north-star vision.

Frequently Asked Questions about north-star-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a north-star vision to align stakeholders and reduce strategic drift?

To create a north-star vision, draft a concise Vision Statement articulating future user value, then define 3–5 Design Pillars to anchor roadmap decisions. This reduces strategic drift by giving stakeholders a single aspirational reference point for product strategy.

What should a product roadmap vision include for cross-functional planning reviews?

A product roadmap vision should include a Vision Statement, Design Pillars, Vision Scenarios, and measurable success criteria. These elements align cross-functional teams by translating aspirational strategy into concrete narratives and tracked metrics across near-, mid-, and long-term horizons.

When do I need to define design pillars and vision scenarios for my product?

You need design pillars and vision scenarios when aligning product strategy during planning reviews and stakeholder updates. Pillars guide roadmap decisions while scenarios provide concrete narratives of how user interactions evolve, ensuring teams share a unified strategic direction.

How do I set measurable success criteria for a product vision across different time horizons?

Set measurable success criteria by defining qualitative signals and quantitative metrics tracked across near-, mid-, and long-term horizons. This approach grounds the vision statement in verifiable progress, ensuring strategic alignment translates into objective evaluation.

Can I use this north-star vision approach for cross-functional alignment without prior strategic planning experience?

Yes, you can start by drafting a concise Vision Statement and 3 Design Pillars. This quick-start approach requires no prior strategic planning experience, allowing you to gradually generate scenarios and success criteria to anchor product decisions.

What is the difference between a vision statement and design pillars in product planning?

A vision statement is a one-sentence articulation of future user experience and value, while design pillars are 3–5 strategic focus areas guiding roadmap decisions. Together they prevent strategic drift by separating aspirational goals from actionable execution priorities.