Saltar al contenido
Marketplace

jobs-to-be-done

de owl-listener

Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.

Resumen

SKILL.mdLeída en 9a6930c

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

  1. Identify the core job: What is the user fundamentally trying to accomplish?
  2. 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
  3. Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
  4. Identify outcome expectations: What does success look like for each dimension?
  5. Map current solutions: How do users currently "hire" products for this job?
  6. Find opportunities: Where are current solutions underserving the job?
  7. Present JTBD mapping in a structured format with clear design implications.

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add owl-listener/designer-skills --skill jobs-to-be-done

Más de owl-listener

  • presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,800 instalaciones en skills.sh0
  • typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,300 instalaciones en skills.sh0
  • visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,300 instalaciones en skills.sh0
  • color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,200 instalaciones en skills.sh0
  • dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,200 instalaciones en skills.sh0
Todas las skills de owl-listener