goal-setting

name	goal-setting
description	Define measurable outcomes, KPIs, success criteria, acceptance thresholds, and decision criteria for software products, features, projects, or initiatives. Use when establishing what success looks like.

Purpose

This skill helps convert product intent into measurable outcomes that guide scope, prioritization, delivery, and review.

Use this skill when:

• Defining project outcomes
• Selecting KPIs
• Setting acceptance criteria
• Establishing launch success criteria
• Aligning stakeholders on goals
• Creating decision thresholds

Inputs

Expected inputs:

• Candidate or validated direction
• Target user
• Business objective
• User outcome
• Baseline metric
• Constraints
• Decision that the goal must support

Inputs usually come from validation or ideation. If the desired outcome is unclear, use ideation to clarify the intent and validation to confirm it matters.

Goal-Setting Principles

Always optimize for:

1. Outcome clarity
2. Measurability
3. Decision usefulness
4. Alignment with user and business value
5. Clear review timing

Avoid optimizing solely for:

• Easy-to-measure activity
• Vanity metrics
• Ambiguous success language
• Too many KPIs
• Goals disconnected from user behavior

Process

Step 1: Define the Desired Outcome

Clarify:

• What should change
• Who benefits
• Why it matters
• What decision the goal will inform

Flag goals that describe outputs instead of outcomes.

---

Step 2: Select Metrics

Choose a small set of indicators.

Metric Type	Questions
User Outcome	Did users accomplish the intended job?
Adoption	Are target users using the feature?
Quality	Is the experience reliable and usable?
Business Impact	Does this support revenue, retention, cost, or strategy?
Guardrail	What must not get worse?

Prefer metrics that can change because of the work being planned.

---

Step 3: Set Thresholds

For each goal, define:

• Baseline
• Target
• Timeframe
• Owner
• Measurement source
• Success threshold
• Failure threshold

---

Step 4: Produce Success Criteria

Generate:

• Primary outcome
• Supporting KPIs
• Guardrail metrics
• Review cadence
• Decision rules

Anti-Patterns

Avoid:

• Using delivery completion as the only goal
• Setting goals without a baseline
• Mixing strategic goals with task checklists
• Selecting metrics nobody can measure
• Ignoring guardrails
• Defining success after launch

Reviewer Checklist

Before finalizing goals:

• Is success measurable?
• Is the target realistic and time-bound?
• Is there a baseline or plan to establish one?
• Are guardrails included?
• Can scoping use these goals to define boundaries?

Escalation Guidance

Escalate when:

• Stakeholders disagree on the primary outcome
• Metrics are unavailable or unreliable
• Business and user goals conflict
• The target is impossible given constraints
• Success criteria would incentivize harmful behavior

Example

Input:

• Validated idea: Guided onboarding checklist
• Business objective: Reduce manual setup calls

Expected goals:

1. Reduce onboarding-related support tickets by 25% within 60 days
2. Increase setup completion from 62% to 80%
3. Keep time-to-first-value under 15 minutes

Recommended next skill:

• Use scoping to define the minimum feature that can achieve these goals.