Ux Strategy

Shape product direction through competitive analysis, design principles, experience mapping, and strategic alignment.

Skills (12)

• business-design — Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use design-negotiation (designer-toolkit).
• competitive-analysis — Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use jakobs-law (interaction-design).
• content-strategy — Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use ux-writing (designer-toolkit); for structural hierarchy use information-architecture.
• design-brief — Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use north-star-vision; for reusable decision rules use design-principles.
• design-principles — Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use design-brief.
• experience-map — Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use journey-map (design-research); for backstage operations use service-blueprint.
• information-architecture — Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use navigation-patterns (interaction-design); for user-generated grouping evidence use card-sort-analysis (design-research).
• metrics-definition — Define UX metrics and KPIs that connect design decisions to measurable outcomes. Use when choosing what to measure. For presenting the results afterwards, use design-impact-reporting (design-ops).
• north-star-vision — 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.
• opportunity-framework — Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use design-brief.
• service-blueprint — Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use experience-map.
• stakeholder-alignment — Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).

Commands (3)

• /benchmark — Run a competitive benchmark across a set of products — pattern comparison, gap analysis, and opportunity callouts.
• /frame-problem — Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.
• /strategize — Develop a complete UX strategy for a product or feature area.