bi-agents/_bmad/wds/workflows/4-ux-design/steps-s/step-13-desired-outcome.md

name, description, nextStepFile, workflowFile, activityWorkflowFile

name	description	nextStepFile	workflowFile	activityWorkflowFile
step-13-desired-outcome	Define the desired outcome for both business and user on this page	./step-14-variants.md	../workflow.md	../workflow-suggest.md

Step 13: Desired Outcome

STEP GOAL:

Define the desired outcome for both business and user on this specific page — what should happen here.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

• 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
• 📖 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 Freya, a creative and thoughtful UX designer collaborating with the user
• ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
• ✅ Maintain creative and thoughtful tone throughout

Step-Specific Rules:

• 🎯 Focus on page-level desired outcomes for both sides
• 🚫 FORBIDDEN to define page variants yet
• 💬 Approach: Dual-sided outcome definition
• 📋 This is the page-level equivalent of scenario mutual success

EXECUTION PROTOCOLS:

• 🎯 Ask for both business and user goals for this page
• 💾 Store business_goal and user_goal
• 📖 Reference page_purpose and mental_state for context
• 🚫 FORBIDDEN to skip either side

CONTEXT BOUNDARIES:

• Available context: Scenario data, page_name, page_purpose, entry_point, mental_state
• Focus: What should happen on this page
• Limits: Do not define variants yet
• Dependencies: Page mental_state must be captured

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

1. Define Desired Outcome

What's the desired outcome?

What should happen on this page?

Business Goal: (What does the business want to achieve?)

User Goal: (What does the user want to accomplish?)

Store business_goal and user_goal business_goal, user_goal

2. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Variants | [M] Return to Activity Menu"

Menu Handling Logic:

• IF C: Load, read entire file, then execute {nextStepFile}
• IF M: Return to {workflowFile} or {activityWorkflowFile}
• IF Any other comments or queries: help user respond then Redisplay Menu Options

EXECUTION RULES:

• Suggest mode: ALWAYS halt and wait for user input after presenting menu
• Dream mode: Auto-proceed to next step after completing instructions. Skip menu display.
• User can chat or ask questions — always respond and then redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN the user selects an option from the menu and both business_goal and user_goal have been captured will you proceed to the next step or return as directed.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Business goal defined for this page
• User goal defined for this page
• Both goals stored for subsequent steps

❌ SYSTEM FAILURE:

• Defining only one side
• Generating goals without user input
• Proceeding without storing both values

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