Frame problems using JTBD Job Stories, HMW questions, and persona validation
Frame problems effectively using Jobs-to-be-Done, How Might We questions, and persona validation from Notion.
Create a Job Story in this format:
When [situation/context],
I want to [motivation/action],
So I can [expected outcome/benefit].
Example:
When I'm managing multiple client workspaces,
I want to switch between them quickly,
So I can respond to urgent requests without losing context.
Reframe the problem as an opportunity question:
How might we [opportunity that addresses the job story]?
Guidelines:
Example:
How might we help users navigate between workspaces seamlessly?
Fetch relevant personas from Notion database:
Search for personas database:
API-post-search with query "Personas" or "User Personas"
Query the database:
API-query-data-source with database_id from search results
Get persona details:
API-retrieve-a-page + API-get-block-children for each relevant persona
Extract these fields:
Validate the problem addresses all three job dimensions:
| Dimension | Question | Example |
|---|---|---|
| Functional | What task are they completing? | "Switch between workspaces" |
| Emotional | How do they want to feel? | "In control, not overwhelmed" |
| Social | How do they want to be perceived? | "Responsive, professional" |
After running this skill, output:
## Problem Framing
### Job Story
When [situation],
I want to [motivation],
So I can [outcome].
### How Might We
How might we [opportunity]?
### Relevant Personas
| Persona | Role | Goals | Pain Points |
|---------|------|-------|-------------|
| [Name] | [Role] | [Goals] | [Pain Points] |
### Three Dimensions
| Dimension | Definition |
|-----------|------------|
| Functional | [Task] |
| Emotional | [Feeling] |
| Social | [Perception] |
Invoke manually with "use problem-framing skill" or follow Ask mode DIVERGE loop which references this skill's phases.
design-context - Run after problem-framingcompetitor-scan - Research how others solve this problem