Success Criteria Workshop Facilitation

Purpose

Collaboratively define comprehensive success criteria across functional, emotional, and social dimensions through structured workshop that synthesizes validated need, root causes, boundaries, and stakeholder perspectives into measurable indicators of solution success. Success criteria enable objective evaluation (A5 portfolio prioritization, A6/A7 validation) and prevent subjective "I like it" assessments.

Many innovation teams define success too narrowly (functional only) or vaguely ("improve user experience"). Workshop ensures three-dimensional criteria that are specific, measurable, and traceable to validated need.

When to Use:

• After completing Steps 1-4 (need validation, framing, root cause, boundaries)—success criteria are synthesis
• Multi-stakeholder projects requiring alignment on what "success" means
• Before solution ideation (A2)—criteria guide design, not evaluate after-the-fact
• Governance requirement (A5 portfolio decisions need objective criteria)
• Validation planning (A6/A7)—criteria define what to measure

When NOT to Use:

• Haven't completed Steps 1-4—premature to define success without understanding need, causes, boundaries
• Solo practitioner without stakeholders—informal criteria definition sufficient
• Obvious success metrics (rare—usually more complex than initially apparent)

Prerequisites:

• Completed A1.3 Steps 1-4: itemize
• Validated need statement
• POV framing (Step 2)
• Root cause analysis (Step 3)
• Boundaries defined (Step 4) itemize
• A1.2 empathy maps or emotional data (for emotional criteria)
• Cross-functional stakeholders available (product, design, engineering, business, operations)
• 3-hour workshop time
• Success Criteria Matrix template (3-column poster: Functional, Emotional, Social)

Quality Criteria

1. Three-dimensional completeness: Criteria span functional, emotional, social (not just functional)

2. Specificity and measurability: Each criterion has clear target and measurement method

3. Root cause alignment: Criteria address identified root causes (traceability)

4. Evidence-based: Criteria derived from A1.2 data (especially emotional—tied to empathy maps)

5. Prioritized: Must-have vs. nice-to-have distinction clear (Tiers 1-3)

6. Conflict-free: No contradictory criteria (or conflicts acknowledged and resolved)

7. Validated by stakeholders: Workshop participants confirmed criteria capture their definition of success

Complete Workshop Facilitation Script

Preparation (1-2 weeks before workshop)

Materials preparation:

• Success Criteria Matrix poster (3 columns: Functional | Emotional | Social)
• Sticky notes (3 colors for 3 dimensions)
• A1.2 empathy map printouts (for emotional dimension)
• Root cause summary (Step 3 output)
• Boundary canvas (Step 4 output)
• Validated need statement (large print, visible throughout workshop)

Pre-read packet (send 3 days before):

• Validated need + POV framing
• Root cause summary (1 page)
• Boundary canvas (1 page)
• Success Criteria explainer (what are 3 dimensions, why each matters)

Scheduling:

• Duration: 3 hours (don't attempt shorter—quality suffers)
• Participants: 6-10 people (product owner, designer, tech lead, business stakeholder, user researcher, operations rep)
• Required: Product owner, design lead (decision-makers)
• Optional: Customer success, sales (voice-of-customer)

Workshop Script (180 minutes)

SECTION 1: Context Setting (30 minutes)

[0-10 min] Welcome and objectives

Facilitator script:

"Welcome. Today we're defining success criteria for [problem]. By end of workshop, we'll have specific, measurable indicators across three dimensions: Functional (what solution must do), Emotional (how users should feel), Social (team/organizational impact).

These criteria will:

• Guide solution design (A2 ideation)
• Enable portfolio prioritization (A5 governance)
• Define validation measures (A6/A7 testing)

Success criteria are NOT features or solutions—they're outcomes. We're defining what success looks like, not how to achieve it."

[10-20 min] Root cause and boundary summary

Display validated need statement (keep visible entire workshop).

Present 2-3 slides:

• Slide 1: Validated need + key A1.2 evidence (3-4 compelling quotes)
• Slide 2: Root causes identified (Step 3)—"We discovered problem exists because [causes]"
• Slide 3: Boundaries (Step 4)—"We're focusing on [in-scope], accepting [constraints], deferring [out-of-scope]"

Emphasize: Success criteria must address root causes within boundaries—can't succeed if criteria require solving out-of-scope causes.

[20-30 min] Three-dimensional framework introduction

Explain each dimension with examples:

Functional Success: Observable behaviors, tasks completed, measurable outcomes

• Example: "Users spend <30 minutes on forecast preparation (vs. current 2 hours)"
• Example: "Forecast accuracy within ±10% of actual, 80%+ of quarters"

Emotional Success: User feelings, psychological states, subjective experience

• Example: "Users feel confident defending forecast (self-reported confidence score >7/10)"
• Example: "Reduce Sunday evening anxiety (sleep quality improvement)"

Social Success: Team dynamics, organizational impact, relationship effects

• Example: "Sales reps report reduced micromanagement pressure"
• Example: "Cross-functional trust in forecasts improves (CFO/ops satisfaction)"

Key point: All three matter. Functional without emotional = works but feels bad (low adoption). Emotional without functional = feels good but doesn't work (not sustainable). Social shows broader value beyond individual user.

SECTION 2: Functional Success Criteria (45 minutes)

[30-45 min] Brainstorm functional criteria

Prompt: "What observable outcomes or behaviors would indicate solution is functionally working?"

Participants write criteria on sticky notes (green)—one criterion per note. Work individually, then share.

Guidance:

• Think: time saved, error reduction, task completion, output quality, process efficiency
• Trace to root causes: If cause is "lack of structured signals," functional criterion is "deal health signals visible and actionable"
• Be specific: "Reduce time" → "Reduce forecast prep time from 2 hours to <30 minutes"

Generate 15-25 candidate criteria.

[45-60 min] Share and cluster

Participants place notes on Functional column of matrix. Facilitator clusters similar criteria.

Example clustering:

• Time efficiency: "Prep time <30 min," "Real-time updates (not batch weekly)," "One-click forecast submission"
• Accuracy: "±10% quarterly accuracy," "Deal-level confidence scores," "Early warning for at-risk deals"
• Adoption: "80% weekly active usage," "Replace manual spreadsheets"

[60-75 min] Refine and specify

For each cluster, create specific measurable criterion.

Refinement progression example:

• ✗ Vague: "Improve forecast accuracy" (no baseline, no target)
• ⚠ Better: "Increase forecast accuracy" (directional but not specific)
• ✓ Specific: "Quarterly forecast accuracy within ±10% of actual, achieved 80%+ of quarters (vs. current 60%)"

Format: "[Metric] reaches [target] by [timeframe], compared to [current baseline]"

Document 8-12 functional criteria (top priorities from clustering).

SECTION 3: Emotional Success Criteria (30 minutes)

[75-90 min] Extract from A1.2 empathy maps

Distribute A1.2 empathy map printouts (if created in A1.2; if not, use interview emotional quotes).

Prompt: "What emotional states did users describe? What did they say they FELT about the problem?"

Review empathy map quadrants:

• Pains: Anxious, frustrated, overwhelmed, uncertain → Emotional success = alleviate these
• Gains: Confident, relieved, in-control, respected → Emotional success = achieve these

Participants identify emotional criteria on sticky notes (yellow)—reference specific A1.2 evidence.

Examples from sales forecast case:

• Current: "Anxious Sunday evenings, difficulty sleeping before Monday call" → Criterion: "Reduced pre-meeting anxiety (self-reported)"
• Current: "Don't trust my gut, feel uncertain" → Criterion: "Increased confidence in assessments (confidence score >7/10)"
• Current: "Defensive, fear of being wrong" → Criterion: "Feel safe committing to forecast (psychological safety score)"

Generate 8-15 emotional criteria.

[90-105 min] Refine for measurability

Challenge: Emotions subjective—how to measure?

Measurement approaches:

1. Self-reported scales (validated instruments or custom):

• "Rate your confidence in this forecast, 1-10"
• "How anxious do you feel about Monday's forecast call? (Not at all / Somewhat / Very)"

2. Behavioral proxies:

• Anxiety → Sleep quality (wearable data), time spent on forecast (reduced rumination)
• Confidence → Willingness to defend forecast in meeting (observed), fewer hedging statements

3. Indirect indicators:

• Sentiment analysis of forecast review meeting transcripts (shift from hedging to assertive language)
• Reduced "checking in" behavior (anxious managers check 3x/day → confident managers trust and check 1x/week)

For each emotional criterion, specify measurement method.

Document 5-8 emotional criteria (prioritize based on A1.2 prevalence—which emotions most commonly expressed).

SECTION 4: Social Success Criteria (30 minutes)

[105-120 min] Explore social dimensions

Prompt: "Beyond individual user, how does solving this need affect teams, relationships, organizational dynamics?"

Reference POV workshop (Step 2)—who else is affected?

Social criteria categories:

1. Team dynamics:

• How does solution affect user's relationship with team members?
• Example: "Sales reps report reduced micromanagement pressure (weekly check-ins decrease from 3 to 1)"

2. Cross-functional trust:

• Do other departments trust/rely on outputs?
• Example: "CFO confidence in forecast reliability increases (satisfaction score >8/10)"

3. Organizational reputation:

• Does user feel recognized/valued?
• Example: "Managers perceived as more competent by leadership (promotion rates, performance reviews)"

4. Knowledge sharing:

• Does solution improve collective capability?
• Example: "Deal health insights shared across team (best practices dissemination)"

Participants brainstorm social criteria on sticky notes (blue). Generate 8-12 criteria.

[120-135 min] Synthesize

Cluster social criteria. Common categories: Trust (internal/external), Team dynamics, Organizational value, Reputation/identity.

Refine to 4-6 social criteria (social dimension often fewer than functional/emotional—less central but important for comprehensive assessment).

SECTION 5: Validation and Prioritization (30 minutes)

[135-150 min] Completeness check

Review all three columns (Functional, Emotional, Social). Test completeness:

Test 1: Root cause coverage

For each addressable root cause (from Step 3), is there corresponding success criterion?

Example: If root cause is "lack of structured signals," functional criterion should include "deal health signals defined and accessible."

If cause addressed but no criterion → add criterion.

Test 2: Three-dimensional balance

Count criteria per dimension:

• Functional: 8-12 typical
• Emotional: 5-8 typical
• Social: 4-6 typical

If imbalanced (e.g., 15 functional, 2 emotional), revisit underrepresented dimension—likely incomplete.

Test 3: Specificity and measurability

For each criterion, answer:

• Is it specific? (clear definition, not vague)
• Is it measurable? (how will we know? data source identified)
• Is it traceable? (connects to validated need and root causes)

If not, refine.

Test 4: Conflicting criteria check

Do any criteria conflict? (Optimizing one degrades another)

Example conflict: "Fastest possible forecast prep" vs. "Thorough deal-by-deal assessment"—speed and thoroughness may trade off.

If conflict identified, clarify priority or balance point: "Forecast prep <30 min while maintaining deal-level assessment (not blind aggregation)"

Test 5: Minimum viable success

Ask: "If we achieve 80% of these criteria, is that success? Which 20% are must-have vs. nice-to-have?"

Prevents criterion creep (100 criteria impossible to achieve).

[150-165 min] Must-have vs. nice-to-have prioritization

Use dot voting:

• Each participant: 10 votes total (can distribute across criteria)
• Place dots on criteria most critical for success
• Top criteria (>50% of votes) = Must-have
• Medium (20-50%) = Important
• Low (<20%) = Nice-to-have

Create tiered list:

• Tier 1 (Must-have): Solution must achieve these or not viable (8-12 criteria typical)
• Tier 2 (Important): Significantly enhance value (6-10 criteria)
• Tier 3 (Nice-to-have): Incremental improvements (remaining criteria)

SECTION 6: Wrap and Next Steps (15 minutes)

[165-180 min] Document and close

Facilitator summarizes:

• Total criteria count per dimension
• Must-have criteria (Tier 1) highlighted
• Measurement approach for each criterion
• Next steps: Document in Problem Definition Brief (Step 6), use for ideation (A2), validation planning (A6)

Closing script:

"We've defined comprehensive success criteria—functional (what works), emotional (how feels), social (broader impact). These criteria are north star for solution design. In ideation (A2), we'll generate solutions that address these criteria. In validation (A6/A7), we'll measure against these.

Next: I'll create detailed Success Criteria document and circulate for feedback within 48 hours. Review and confirm we captured accurately."

Post-Workshop Documentation (Day 1-2 after workshop)

Create Success Criteria document (5-8 pages):

Section 1: Overview

• Validated need statement (context)
• Workshop participants and date
• Summary of criteria counts (X functional, Y emotional, Z social)

Section 2: Functional Success Criteria

Table format:

Section 3: Emotional Success Criteria

Section 4: Social Success Criteria

Similar table format (criterion, measurement, priority).

Section 5: Validation Plan Preview

For each Tier 1 criterion, note how will validate in A6/A7:

• A6 (concept validation): Survey, clickable prototype with self-reported confidence
• A7 (pilot): Time tracking (prep time), forecast vs. actual comparison (accuracy), longitudinal survey (confidence over 8 weeks)

Tools and Resources

Success Criteria Matrix poster:

• Large format (36"×48") with 3 columns labeled
• Sticky notes in 3 colors (Functional = green, Emotional = yellow, Social = blue)
• Markers for annotations

Digital alternative:

• Miro/Mural board with 3-column template
• Color-coded cards for each dimension

Documentation template:

• Success Criteria Document (Word/Notion template with tables)
• Export to PDF for Problem Definition Brief (Step 6)

Sample Size / Duration

Participants: 6-10 people (cross-functional, decision-makers)

Duration:

• Pre-work: 30 min (review packet)
• Workshop: 3 hours (do not shorten—comprehensive criteria require time)
• Documentation: 4-6 hours (facilitator creates detailed document)
• Total: 7-9 hours (workshop facilitator effort)

Common Challenges and Solutions

Challenge 1: Functional dominates, emotional/social neglected

Symptoms:

• 20 functional criteria, 2 emotional, 0 social
• Team more comfortable with measurable functional metrics
• Emotional/social dismissed as "soft" or "nice-to-have"

Solutions:

• Time allocation: Enforce 45 min functional, 30 min emotional, 30 min social—don't let functional consume entire workshop
• Frame importance: "Functional without emotional = low adoption, eventual abandonment—emotional success predicts sustainability"
• Evidence grounding: Return to A1.2 empathy maps—users expressed strong emotions, ignoring that dimension means ignoring user reality

Challenge 2: Criteria embed solutions (not outcomes)

Symptoms:

• Criterion: "Solution includes dashboard with 10 widgets" (describes feature, not outcome)
• Criterion: "Uses AI for prediction" (describes technology, not success)

Solutions:

• Outcome test: "Is this what solution does (feature) or what user achieves (outcome)?" If former, reframe.
• Reframing: "Dashboard with 10 widgets" → "Deal health visible at-a-glance (user scans in <10 seconds)"
• Facilitator challenging: "Why do we want dashboard? What outcome does it enable?" → Focus on outcome.

Challenge 3: Vague emotional criteria not measurable

Symptoms:

• Criterion: "Users feel better" (how much better? how measure?)
• Criterion: "Improved satisfaction" (satisfaction with what? baseline?)

Solutions:

• Force specificity: "Feel better about what? Confident? Relieved? Calm? Be specific."
• Measurement requirement: "How will we measure this? Self-report survey? Behavioral proxy? If can't measure, refine criterion."
• Validated instruments: Use established scales (System Usability Scale for usability, validated confidence scales) rather than ad-hoc

Challenge 4: Conflicting criteria unaddressed

Symptoms:

• "Fastest forecast prep" vs. "Most thorough deal analysis"—trade-off not resolved
• Team avoids discussing conflicts, hopes solutions magically resolve both

Solutions:

• Explicit trade-off discussion: "These criteria conflict—which is more important, or where's the balance point?"
• Constraint framing: "Fastest prep subject to maintaining deal-level analysis (not blind aggregation)"
• Prioritization: If must choose, vote on which criterion Tier 1 (must-have) vs. Tier 2 (important but flexible)

Challenge 5: Criteria creep (too many, unrealistic)

Symptoms:

• 40+ total criteria (impossible to achieve all)
• No prioritization—"everything is must-have"
• Risk of building solution that satisfies none well vs. some comprehensively

Solutions:

• Force prioritization: Dot voting (limited votes) forces choices
• 80/20 framing: "If we achieve top 10 criteria, is that success? Which 30 criteria are incremental?"
• Tier enforcement: Limit Tier 1 (must-have) to 8-12 criteria maximum—if more, not truly "must-have"