使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/owl-listener/designer-skills --skill jobs-to-be-done開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Jobs-to-Be-Done
Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.
Context
You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.
Domain Context
- JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
- Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
- Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].
Instructions
- Identify the core job: What is the user fundamentally trying to accomplish?
- Map the job dimensions:
- Functional: The practical task or outcome
- Emotional: The feeling they seek or want to avoid
- Social: How they want to be perceived by others
- Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
- Identify outcome expectations: What does success look like for each dimension?
- Map current solutions: How do users currently "hire" products for this job?
- Find opportunities: Where are current solutions underserving the job?
- Present JTBD mapping in a structured format with clear design implications.
