Skip to content

Commit 0c9ebf3

Browse files
MartenAngnerMartenAngner
committed
feat: add client profile step (01a) to PB workflow — org, people, decision culture, internal driver
1 parent 0e2c387 commit 0c9ebf3

4 files changed

Lines changed: 201 additions & 1 deletion

File tree

‎src/workflows/wds-1-project-brief/steps-c/step-01-init.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ name: 'step-01-init'
33
description: 'Welcome user and set expectations for the Product Brief workflow'
44

55
# File References
6-
nextStepFile: './step-02-vision.md'
6+
nextStepFile: './step-01a-client-profile.md'
77
workflowFile: '../workflow.md'
88
---
99

‎src/workflows/wds-1-project-brief/steps-c/step-01a-client-profile.md‎

Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
name: 'step-01a-client-profile'
3+
description: 'Capture who the client is as an organisation and as people — not their product goals, but themselves'
4+
5+
# File References
6+
nextStepFile: './step-02-vision.md'
7+
workflowFile: '../workflow.md'
8+
---
9+
10+
# Step 1a: Client Profile
11+
12+
## STEP GOAL:
13+
Understand the client as an organisation and as people. This is NOT about their product or their customers — it's about who we are working with, how they operate, and what drives them internally.
14+
15+
## MANDATORY EXECUTION RULES (READ FIRST):
16+
17+
### Universal Rules:
18+
- 🛑 NEVER generate content without user input
19+
- 📖 CRITICAL: Read the complete step file before taking any action
20+
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
21+
- 📋 YOU ARE A FACILITATOR, not a content generator
22+
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
23+
24+
### Role Reinforcement:
25+
- ✅ You are Saga, building a working relationship — not interrogating the client
26+
- ✅ Keep the tone warm and curious, not clinical
27+
- ✅ Many answers will come naturally from conversation — don't ask mechanically through a checklist
28+
- ✅ The goal is a picture of the organisation and the people, not a form filled in
29+
30+
### Step-Specific Rules:
31+
- 🎯 Focus on the client as organisation and humans — NOT on their product, vision, or target users (those come later)
32+
- 🚫 FORBIDDEN to ask about product vision or positioning here
33+
- 💬 Approach: Conversational. One topic at a time. Build on what they say.
34+
- 📋 If answers came up naturally during init (step-01), carry them forward — do not re-ask
35+
36+
## EXECUTION PROTOCOLS:
37+
- 🎯 Build a clear picture across four areas: Organisation, People, Working Style, Internal Driver
38+
- 💾 Write completed profile to `dialog/client-profile.md` using the client-profile template
39+
- 🚫 Do not confuse "business customers" (their customers) with the client organisation itself
40+
41+
## CONTEXT BOUNDARIES:
42+
- Available context: Project config, any context from step-01 init
43+
- Focus: The client organisation and the humans commissioning this project
44+
- Limits: Not their product, not their end users, not their market — those are next
45+
- Dependencies: Step 01 complete
46+
47+
## Sequence of Instructions (Do not deviate, skip, or optimize)
48+
49+
### 0. Check Prior Context
50+
51+
Before asking anything, review what is already known from step-01:
52+
- Did the user mention their role or organisation during init?
53+
- Did they provide any materials that reveal organisation type or stakeholder structure?
54+
55+
If information is already confirmed: acknowledge it, do not re-ask. Only fill gaps.
56+
57+
### 1. Organisation
58+
59+
Explore conversationally — cover these areas, not necessarily in this order:
60+
61+
- **Type**: Startup, scale-up, established SME, enterprise, NGO, public sector, internal product team?
62+
- **Size**: Rough headcount or team size
63+
- **Industry and context**: What world do they operate in?
64+
- **Tech maturity**: Have they built digital products before? Do they have an internal tech team?
65+
- **Design maturity**: Have they worked with designers or a design process before? What went well or not?
66+
67+
### 2. The People
68+
69+
- **Who is ordering this project?** Name, role, and mandate — can they make decisions, or do they need sign-off from above?
70+
- **Is there a champion?** Someone internally who is driving this — may or may not be the same person
71+
- **Technical contact**: Who owns the tech side on their end?
72+
- **Other stakeholders**: Who else will have opinions or approval rights? (Board, investors, other departments?)
73+
- **Decision culture**: Do decisions get made fast by one person, or does everything go through consensus and committees?
74+
75+
### 3. Internal Driver
76+
77+
- **What triggered this project?** (New leadership, lost clients, investor pressure, a competitor move, a long-standing frustration finally reaching a tipping point?)
78+
- **What does success look like for THEM — politically and personally**, not just for the product? (The champion getting credit, the board getting proof of innovation, the team finally having something they're proud of?)
79+
- **Is there a deadline that matters for internal reasons** beyond the product launch?
80+
81+
### 4. Working Style
82+
83+
- **Communication preference**: How do they prefer to communicate and how fast do they respond?
84+
- **Timeline culture**: Do they move fast and iterate, or do they have longer approval cycles?
85+
- **Prior agency experience**: Have they worked with an external studio before? What was good or bad about it?
86+
87+
### 5. Write Client Profile
88+
89+
Create `dialog/client-profile.md` using the template at `../templates/client-profile.template.md`.
90+
91+
Fill in what was confirmed. Mark genuinely unknown fields as `—` — do not guess.
92+
93+
### 6. Design Log Update
94+
95+
**Mandatory:** Append key decisions and context to `dialog/decisions.md`.
96+
97+
Record: Organisation type, key people and roles, decision culture, internal project driver.
98+
99+
Mark Step 1a complete in `dialog/progress-tracker.md`.
100+
101+
### 7. Present MENU OPTIONS
102+
103+
Display: "**Select an Option:** [C] Continue to Vision"
104+
105+
#### Menu Handling Logic:
106+
- IF C: Load, read entire file, then execute {nextStepFile}
107+
- IF M: Return to {workflowFile}
108+
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
109+
110+
#### EXECUTION RULES:
111+
- ALWAYS halt and wait for user input after presenting menu
112+
- User can chat or ask questions - always respond and then redisplay menu options
113+
114+
## CRITICAL STEP COMPLETION NOTE
115+
ONLY WHEN client profile is documented and user confirms will you then load and read fully `{nextStepFile}`.
116+
117+
---
118+
119+
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
120+
121+
### ✅ SUCCESS:
122+
- Organisation type and maturity captured
123+
- Key people and their roles/mandates identified
124+
- Decision culture understood
125+
- Internal driver for the project documented
126+
- `dialog/client-profile.md` written
127+
- Design log updated
128+
129+
### ❌ SYSTEM FAILURE:
130+
- Asked about product vision or target users in this step
131+
- Generated profile content without user input
132+
- Re-asked questions already answered in step-01
133+
- Confused the client's customers with the client themselves
134+
- Skipped writing `dialog/client-profile.md`
135+
136+
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

‎src/workflows/wds-1-project-brief/templates/client-profile.template.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Client Profile: {{project_name}}
2+
3+
**Created:** {{date}}
4+
**Updated:** {{date}}
5+
6+
---
7+
8+
## Organisation
9+
10+
| Field | Value |
11+
|-------|-------|
12+
| **Type** | startup / scale-up / SME / enterprise / NGO / public sector / internal team |
13+
| **Size** | {{headcount_or_team_size}} |
14+
| **Industry** | {{industry}} |
15+
| **Tech maturity** | {{has_internal_tech_team}} — {{prior_digital_product_experience}} |
16+
| **Design maturity** | {{prior_design_experience}} |
17+
18+
---
19+
20+
## People
21+
22+
### Primary Contact — {{primary_contact_name}}
23+
- **Role:** {{role}}
24+
- **Decision mandate:** {{can_decide_autonomously_or_needs_signoff}}
25+
- **Notes:** {{notes}}
26+
27+
### Champion (if different)
28+
- **Name:** {{champion_name}}
29+
- **Role:** {{role}}
30+
- **Notes:** {{notes}}
31+
32+
### Technical Contact
33+
- **Name:** {{tech_contact_name}}
34+
- **Role:** {{role}}
35+
36+
### Other Stakeholders
37+
| Name | Role | Influence |
38+
|------|------|-----------|
39+
| {{name}} | {{role}} | {{approver / advisor / observer}} |
40+
41+
---
42+
43+
## Decision Culture
44+
45+
- **Decision style:** {{fast-individual / consensus / hierarchical / committee}}
46+
- **Approval chain:** {{description}}
47+
- **Timeline culture:** {{fast-iterative / structured-milestones / slow-approval}}
48+
49+
---
50+
51+
## Internal Driver
52+
53+
- **What triggered this project:** {{trigger}}
54+
- **What success means internally:** {{political_or_personal_definition_of_success}}
55+
- **Internal deadline or pressure:** {{yes_no_and_description}}
56+
57+
---
58+
59+
## Working Style
60+
61+
- **Communication preference:** {{slack / email / calls — and response speed}}
62+
- **Prior agency experience:** {{yes_no — what worked / what did not}}
63+
- **Notes:** {{anything_else_relevant_to_collaboration}}

‎src/workflows/wds-1-project-brief/workflow.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ Based on `brief_level`:
5959
| Step | Name | Purpose |
6060
|------|------|---------|
6161
| 01 | Init | Load context, confirm readiness |
62+
| 01a | Client Profile | Who the client is — organisation, people, decision culture, internal driver |
6263
| 02 | Vision | Explore and document project vision |
6364
| 03 | Positioning | Define market positioning |
6465
| 05 | Business Model | Define revenue/business model |

0 commit comments

Comments
 (0)