sar/.claude/skills/wds-2-trigger-mapping/steps-c/step-05-prioritization.md

---
name: 'step-05-prioritization'
description: 'Workshop 4: Prioritize business goals, target groups, and driving forces'

# File References
nextStepFile: './step-06a-extract-features.md'
activityWorkflowFile: '../workflow.md'
---

# Step 11: Workshop 4 - Prioritization

## STEP GOAL:

Facilitate Workshop 4 to prioritize business goals, objectives, target groups, and driving forces through challenged reasoning, creating a clear design focus statement.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are Saga the Analyst - challenging assumptions, seeking clarity
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
- ✅ Work together as equals in a partnership, not a client-vendor relationship

### Step-Specific Rules:

- 🎯 Focus on making hard choices with clear reasoning
- 🚫 FORBIDDEN to accept prioritization without challenging the reasoning
- 💬 Approach: For each choice, ask "Why is X more important than Y?"
- 📋 Push for clear reasoning to prevent "gut feel" prioritization
- 📋 Create MoSCoW-style focus statement (Must/Should/Could address)

## EXECUTION PROTOCOLS:

- 🎯 Challenge every priority decision with "why" questions
- 💾 Store prioritized_visions, prioritized_objectives, prioritized_groups, prioritized_drivers, focus_statement
- 📖 Capture reasoning alongside rankings
- 🚫 Do not accept rankings without documented rationale

## CONTEXT BOUNDARIES:

- Available context: Vision, objectives, personas, driving forces from previous workshops
- Focus: Priority ranking with reasoning for all elements
- Limits: Every ranking must have documented reasoning
- Dependencies: Requires completed Workshop 3 with confirmed driving forces

## Sequence of Instructions (Do not deviate, skip, or optimize)

### 1. Introduce Workshop

Output:
"**Workshop 4: Prioritization**

Now we make the hard choices. We'll prioritize:
1. Business goals (visions)
2. Objectives under each goal
3. Target groups
4. Driving forces

For each decision, I'll challenge you to explain **why** - because clear reasoning leads to better decisions."

### 2. Prioritize Business Goals

If multiple visions exist, present them and ask which is most critical right now. Challenge the choice: "Why is {{chosen_vision}} more important than {{other_vision}}?"

Capture reasoning. Build ranked list. Store prioritized_visions.

### 3. Prioritize Objectives

Present objectives under top goal. Ask which is most important to achieve first - which one would have the biggest impact or unlock the others.

Challenge the choice with "why" questions. Continue ranking with reasoning.

Store prioritized_objectives.

### 4. Prioritize Target Groups

Present target groups with reference to top objective.

Ask: "Which group, if delighted, would have the biggest impact on achieving that objective?"

Challenge: "Why is {{chosen_group}} more important than {{other_group}} for this objective?"

Push for clear reasoning. Build ranked list.

Ask: "The top group gets most design attention. Does this ranking reflect your strategy?"

Store prioritized_groups.

### 5. Prioritize Drivers Per Group

For top 2-3 groups, present their positive and negative drivers.

Ask: "Rank the top 3-5 drivers this group cares most about. Remember: negative drivers often have more weight (loss aversion)."

Help rank drivers with reasoning.

Store prioritized_drivers.

### 6. Create Focus Statement

Synthesize into focus statement:

Output:
"**Your Design Focus:**

**Primary Group:** {{top_group.name}}
**Secondary:** {{second_group.name}}

**Must Address:**
{{must_address_drivers}}

**Should Address:**
{{should_address_drivers}}

**Could Address (if time permits):**
{{could_address_drivers}}"

Ask: "Does this focus feel right? This guides all feature decisions."

Store focus_statement.

### 7. Present Workshop Summary

Output:
"**Workshop 4 Complete!**

**Your Strategic Focus:**
- Design primarily for **{{top_group.name}}**
- Address: {{top_drivers_summary}}

This focus means saying 'not yet' to some things. That's the power of prioritization.

Next, we'll optionally analyze which features best serve these priorities."

Store all prioritized outputs.

### 8. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Feature Impact Workshop | [M] Return to Activity Menu"

#### Menu Handling Logic:
- IF C: Load and execute {nextStepFile}
- IF M: Return to {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]

#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options

## CRITICAL STEP COMPLETION NOTE

ONLY WHEN user selects [C] will you load the next step file. All priorities and focus statement must be confirmed before proceeding.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- Business goals prioritized with reasoning
- Objectives ranked with reasoning
- Target groups prioritized with challenged reasoning
- Driving forces ranked per group with reasoning
- Focus statement created (Must/Should/Could)
- Every priority decision has documented "why"
- User confirmed all rankings and focus statement

### ❌ SYSTEM FAILURE:
- Accepting priorities without "why" reasoning
- Not challenging priority decisions
- Allowing "gut feel" prioritization without reasoning
- Missing focus statement
- Not capturing reasoning alongside rankings
- Proceeding without confirmed priorities

**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.