agentleFS
mahirautela2020-designmahirautela2020-design/claude-skills-ux/product-ux-strategy-alignment/SKILL.md

product-ux-strategy-alignment

Skill1 starsChanged 8 months agoMITView on GitHub

Connects UX and product strategy. Use when the user needs help linking design work to product strategy, roadmaps, and success metrics, and identifying where UX can influence key outcomes like activation, retention, and satisfaction, qualitatively and with data partners, using shared metrics frameworks.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when planning UX work, proposing initiatives, or explaining how design decisions support product strategy and measurable …

    line 22
  2. Distinctive:

    Start by understanding the product strategy you need to support.[web:126][web:127][web:130][web:138]

    line 30
  3. Distinctive:

    Start and end states (e.g., “visit pricing page” → “successfully activated team”).

    line 55
  4. Distinctive:

    Write explicit links such as:

    line 83
  5. Very specific:

    Document these in a simple GSM or metric brief (Goal → Signal → Metric) using ux-product-design-metrics so expectations are …

    line 128
  6. Distinctive:

    Use UX roadmaps (for problems and journeys) that mirror and feed into product roadmaps.[web:126][web:128][web:138]

    line 162
  7. Distinctive:

    Before/after comparisons or A/B tests, if applicable.

    line 178
  8. Very specific:

    Use the same metric frameworks and dashboards defined via ux-product-design-metrics so impact is visible and comparable across …

    line 186
  9. Distinctive:

    Use journey maps and opportunity framing to show where UX can unlock value.[web:126][web:127][web:130][web:136]

    line 245
  10. Distinctive:

    Start with a small, clear set per initiative (e.g., one primary product metric, one UX metric).

    line 250
  11. Distinctive:

    Add more nuance over time with data partners.

    line 252
  12. Distinctive:

    Use shared artefacts (roadmaps, OSTs, journey maps) that are anchored in agreed outcomes.

    line 256
  13. Distinctive:

    Use this skill alongside:

    line 264

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product & UX Strategy Alignment

Purpose

This skill helps designers connect their work to product strategy, roadmaps, and success metrics, so UX is clearly contributing to outcomes rather than just delivering screens.[web:126][web:127][web:129][web:128][web:130][web:138] It focuses on clarifying product goals, mapping design work to key metrics (activation, retention, satisfaction), and working with PMs and data partners to describe and measure impact using shared frameworks like HEART, AARRR, and GSM via ux-product-design-metrics.[web:131][web:132][web:135][web:139][web:140][web:369][web:373]

Use this skill when planning UX work, proposing initiatives, or explaining how design decisions support product strategy and measurable results.


Instructions

Step 1: Clarify product vision, strategy, and goals

Start by understanding the product strategy you need to support.[web:126][web:127][web:130][web:138]

Ask:

  • "What is the current product vision and strategy for this area or time period?"
  • "What outcomes or OKRs are we aiming for (e.g., increase self‑serve revenue, reduce churn, grow active usage)?"
  • "Which user segments or journeys are most strategic right now?"

Summarize:

  • Strategic themes or bets (e.g., onboarding, collaboration, expansion).
  • 1–3 top product metrics tied to these themes (e.g., activation rate, retention, NPS, feature adoption).[web:130][web:132][web:135][web:140]

Where possible, express these outcomes using a shared metrics language from ux-product-design-metrics (e.g., map to HEART categories, AARRR stages, or GSM goals).[web:369][web:373] This forms the context for all UX work.


Step 2: Map user journeys to strategic outcomes

Connect strategy to user journeys where UX has leverage.[web:126][web:127][web:129][web:138]

For the strategic themes:

  • Identify key journeys (e.g., sign‑up and onboarding, first value, upgrade, renewal).
  • For each journey, note:
    • Start and end states (e.g., “visit pricing page” → “successfully activated team”).
    • Critical steps and handoffs (product, email, support, etc.).

Highlight where friction or drop‑offs in these journeys are likely to affect strategic metrics like activation, retention, or satisfaction.[web:131][web:139][web:140]

These are places where design can move the needle and should tie back to problem statements and opportunity spaces from ux-mindset-problem-framing and product-discovery-opportunity.


Step 3: Identify UX levers for key metrics

For each strategic metric, identify UX levers—aspects of the experience that can influence that metric.[web:126][web:129][web:131][web:139]

Examples:

  • Activation:
    • Clarity of value proposition and next steps.
    • Onboarding flow usability and guidance.
    • Time to first value.
  • Retention:
    • Ease of completing core tasks repeatedly.
    • Discoverability and usefulness of key features.
    • In‑product feedback loops and support experiences.[web:131][web:132][web:135][web:139]
  • Satisfaction / NPS:
    • Perceived reliability and responsiveness.
    • Emotional resonance, trust, and sense of control.
    • Resolution of major pain points in critical journeys.[web:132][web:135][web:140]

Write explicit links such as:

  • “Improving onboarding clarity and reducing steps should improve activation rate and early satisfaction (HEART: Task Success + Happiness).”[web:369]
  • “Making recurring workflows more efficient should improve retention and customer effort scores (HEART: Engagement + Task Success; CES).”

This makes the connection between UX decisions and metrics from ux-product-design-metrics explicit.


Step 4: Translate design work into strategic initiatives

Group design activities into initiatives that clearly support product strategy.[web:126][web:127][web:130]

For each initiative or project:

  • Name it in outcome‑oriented terms (e.g., “Reduce onboarding confusion”, “Improve billing transparency”), not just “New UI”.
  • Specify:
    • Which journey(s) it affects.
    • Which strategic metric(s) it aims to move (primary and secondary).
    • How it supports roadmap themes or OKRs.[web:126][web:127][web:129][web:138]

This makes UX work show up on roadmaps as outcome‑linked items, not isolated design tasks.[web:128][web:130][web:134]


Step 5: Define UX and product metrics together

Collaborate with PMs and data partners to define metrics and signals, using shared frameworks.[web:131][web:132][web:135][web:140][web:369][web:373]

For each initiative, identify:

  • Primary product metrics (often at HEART/AARRR/GSM level):
    • Activation and conversion rates, time to first value.
    • Retention, churn, engagement (DAU/MAU, feature usage).
    • Revenue, expansion, or other business KPIs where relevant.
  • UX‑specific metrics:
    • Task success rate, time on task, error rate.
    • Customer Effort Score (CES), CSAT, NPS for key journeys.
    • Qualitative indicators from research (e.g., reduced confusion, improved trust).

Agree on:

  • Which metrics are directly impacted by design changes.
  • Which are influenced indirectly but still worth monitoring.

Document these in a simple GSM or metric brief (Goal → Signal → Metric) using ux-product-design-metrics so expectations are explicit.[web:369][web:373]


Step 6: Formulate testable UX hypotheses

Frame design work as hypotheses linked to metrics.[web:126][web:129][web:131][web:139]

Examples:

  • “If we simplify the onboarding from 7 steps to 4 and clarify required vs optional fields, new users will reach first value faster, increasing activation rate and reducing early churn.”
  • “If we make billing history and upcoming charges transparent and easy to find, we will reduce billing‑related support tickets and improve satisfaction for admins.”
  • “If we surface collaboration features in the primary workflow instead of hidden menus, more teams will adopt shared workspaces, driving higher retention and expansion.”

Each hypothesis should tie:

  • A design change → user behaviour change → metric impact (using metrics defined in Step 5).

You can reuse hypothesis patterns from product-discovery-opportunity and connect them directly to HEART/AARRR/GSM targets.


Step 7: Align with roadmaps and planning cadences

Embed UX work into roadmap discussions and planning cycles.[web:126][web:127][web:128][web:130][web:138]

Practices:

  • In roadmap meetings, talk about UX initiatives in terms of:
    • Which strategic outcomes and metrics they serve.
    • Where they sit in the journey map and opportunity space.
  • Collaborate with PMs to:
    • Bundle UX work into roadmap themes and epics.
    • Reserve capacity for discovery, prototyping, and iteration tied to key bets.
  • Use UX roadmaps (for problems and journeys) that mirror and feed into product roadmaps.[web:126][web:128][web:138]

This keeps UX from being a separate track; instead it becomes part of how the roadmap achieves outcomes.[web:127][web:130][web:134]


Step 8: Describe and measure impact with data partners

Work with analytics and research to estimate and measure design impact.[web:131][web:132][web:135][web:139][web:140]

Before launch:

  • Estimate potential impact where possible (e.g., “If we reduce onboarding drop‑off at step 3 by X%, we expect Y additional activations per month.”).
  • Define what data you’ll collect:
    • Funnels and events.
    • Surveys or in‑product feedback.
    • Before/after comparisons or A/B tests, if applicable.

After launch:

  • Review metric changes alongside qualitative feedback.
  • Attribute shifts where reasonable (e.g., improvement in task success, reduction in specific support ticket categories, better retention in affected cohorts).
  • Capture stories and examples to supplement numbers (e.g., user quotes, smoother support interactions).

Use the same metric frameworks and dashboards defined via ux-product-design-metrics so impact is visible and comparable across initiatives.[web:369][web:373]


Step 9: Communicate alignment and learnings to stakeholders

Make the connection between UX work and strategy visible and ongoing.[web:126][web:127][web:130][web:132][web:136]

For key initiatives, prepare simple artefacts that show:

  • The strategic goal and metrics (HEART/AARRR/GSM framing where helpful).
  • The user journeys and problems targeted.
  • The UX hypotheses and design changes.
  • The observed results (metrics + qualitative insights).
  • What you’re doing next (double down, iterate, or pivot).

Use these to:

  • Align with PMs, engineering, marketing, and leadership.
  • Advocate for UX work that clearly supports strategy.
  • Refine future strategy based on what you learned.

Examples

Example 1: Onboarding UX aligned to activation target

  • Strategy:
    • Increase new customer activation in self‑serve channel.
  • Journey focus:
    • Sign‑up → onboarding → first successful task.
  • UX levers:
    • Clarify value proposition at sign‑up, simplify steps, and add guidance.[web:126][web:129][web:131]
  • Metrics:
    • Activation rate, onboarding completion, time to first value (HEART: Adoption + Task Success), CES.[web:131][web:140][web:369]
  • Result (hypothetical):
    • Activation up, fewer support tickets about setup, improved early CSAT, demonstrating UX impact on a core strategic goal.[web:131][web:132][web:135][web:139]

Example 2: Billing UX aligned to retention and satisfaction

  • Strategy:
    • Reduce churn due to billing friction and confusion.
  • Journey focus:
    • Billing settings, invoices, plan changes.
  • UX levers:
    • Clearer pricing and billing information, easier access to invoices, better error and success messaging.[web:126][web:127][web:139]
  • Metrics:
    • Churn in affected segments, billing‑related support contacts, CSAT/NPS for admins, task success in billing flows.[web:131][web:132][web:135][web:140]
  • Result (hypothetical):
    • Downward trend in billing‑related churn and support, improved admin satisfaction, supporting the product strategy for healthier recurring revenue.[web:131][web:139][web:140]

Troubleshooting

Stakeholders don’t see UX as strategic

  • Frame UX work explicitly in terms of product outcomes and metrics, not only design quality.
  • Use journey maps and opportunity framing to show where UX can unlock value.[web:126][web:127][web:130][web:136]
  • Bring data and examples that show how UX changes have influenced engagement or retention, using shared metrics language.[web:131][web:132][web:135][web:139][web:369]

Metrics feel overwhelming or not actionable

  • Start with a small, clear set per initiative (e.g., one primary product metric, one UX metric).
  • Focus on metrics directly connected to the journey you’re changing.
  • Add more nuance over time with data partners; avoid perfectionism at the start.[web:132][web:135][web:140][web:369]

UX and product teams are misaligned on priorities

  • Use shared artefacts (roadmaps, OSTs, journey maps) that are anchored in agreed outcomes.
  • Facilitate short alignment sessions where you connect user problems and design ideas to roadmap items and metrics.
  • Revisit alignment regularly as data and strategy evolve.[web:126][web:127][web:130][web:134][web:136]

Notes for use with other skills

  • Use this skill alongside:
    • product-discovery-opportunity to define and size opportunities tied to strategy.[web:372]
    • ux-mindset-problem-framing and ux-user-research to ground strategy in real user problems and evidence.
    • ux-prototyping-validation to test design hypotheses and connect outcomes back to metrics and roadmaps.[web:362][web:370]
    • ux-product-design-metrics to define HEART/AARRR/GSM metrics and measurement plans for each strategic initiative.[web:369][web:373]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.