Files
sar/.agents/skills/wds-4-ux-design/data/scenario-init/05-mutual-success.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

70 lines
1.3 KiB
Markdown

# Question 4: What's the End Goal (Mutual Success)?
**Define winning for both business and user**
---
## The Question
```
Agent: "What does success look like for both sides?
For the business: [what outcome?]
For the user: [what state/feeling/outcome?]"
```
---
## Why This Matters
Success must be mutual:
- Business gets value
- User gets value
- Both are happy
**If only one side wins, the relationship fails.**
---
## Example: Dog Week
```
Designer: "Business: Active subscription
User: Family harmony restored, dog gets walked consistently,
no more nagging needed"
```
**Why both matter:**
- Business needs subscription (revenue)
- User needs harmony (problem solved)
- Subscription only works if harmony is real
- Harmony only happens if product delivers
**Mutual success = sustainable business.**
---
## What Agent Captures
```
MUTUAL SUCCESS:
Business Goal: Active subscription (recurring revenue)
User Goal: Family harmony + consistent dog care + no nagging
Success Metric: User stays subscribed because harmony is real
Failure Point: User cancels if product doesn't reduce conflict
```
---
## Next Question
[What's the shortest path to get there?](05-shortest-path.md)
---
[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)