Results for “metric”

Guides setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

Design rigorous A/B tests with clear hypotheses, controlled variants, appropriate metrics, and sample size calculations.

Guides SaaS pricing strategy: selecting models, value metrics, packaging tiers, and applying psychology tactics to optimize revenue.

Design value-based pricing, packaging, and monetization strategies for SaaS products, including tier structures, value metrics, and price optimization.

Transforms A/B test and product experiment data into actionable readouts with hypothesis, metrics, interpretation, and decision.

Build board and investor update decks with structured narratives, metrics dashboards, and C-suite perspectives for board meetings, quarterly reviews, and fundraising.

Generate a comprehensive product strategy using the 9-section Product Strategy Canvas, covering vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.

Reviews a video rough cut by generating deterministic metrics, critiquing the edit against brief and blueprint, and producing review_report.yaml and review_patch.json artifacts.

Provides strategic product leadership guidance for CPOs and product leaders, covering vision, portfolio management, product-market fit, org design, and metrics. Includes diagnostic questions, frameworks, and scripts for scoring PMF and analyzing portfolios.

Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.

Use only for video game projects; route research, validation, roadmap, metrics, and launch work through the game pack

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Expert product analytics advisor for Senior PMs. Use when defining success metrics for a PRD, designing an A/B experiment, setting up an analytics tracking plan, analyzing post-launch impact, or when data exists but there's no clarity on what to measure. Produces structured metrics frameworks that connect to product decisions, not dashboards.

Write a PRD or feature spec that aligns design and engineering — problem with evidence, explicit non-goals, measurable success metrics, and testable acceptance criteria.

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Identify what to measure, test, or track to de-risk a product or AI idea across internal and external risk dimensions.

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

Design pricing, packaging, and monetization strategies that capture value and align with customer willingness to pay.

Builds Quarterly Business Review decks for active clients. Pulls metrics, generates structured QBR with wins, challenges, roadmap, and recommendations. Uses crm-writer to read client data.

Provides technical leadership frameworks for architecture decisions, engineering team scaling, technology strategy, and technical debt assessment.

Build evidence and narratives that connect design decisions to measurable user, product, and business outcomes.

Drafts monthly investor updates, quarterly board decks, and high-signal stakeholder communications that surface wins, misses, risks, and asks clearly.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

Define, track, and interpret product metrics across discovery, growth, and mature product stages using frameworks like AARRR, North Star, and HEART.

Generate a Lean Canvas with sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue for testing business hypotheses.

Generates a structured Product Requirements Document (PRD) for a new feature, including clarifying questions, user stories, functional requirements, and success metrics.

Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement, using Adobe Analytics data.

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Design pricing strategies grounded in value delivery, competitive positioning, and willingness to pay. Recommends pricing models, tiers, and experiments.