Focusing on the Job-To-Be-Done with Job Stories

Focusing on the Job-To-Be-Done with Job Stories

A talk about 'Job-to-be-done' thinking, developed by Clay Christensen, author of “The Innovator's Dilemma”.

Job stories were developed by intercom: http://insideintercom.io/the-dribbblisation-of-design/
and expanded on by Alan Klement:
http://alanklement.blogspot.com/2013/09/replacing-user-story-with-job-story.html

Ba257f3320b09da4617a46b1c076344a?s=128

James Cox-Morton

November 29, 2013
Tweet

Transcript

  1. 4.

    “Customers rarely make buying decisions around what the ‘average’ customer

    in their category may do — but they often buy things because they find themselves with a problem that they need to solve” http://www.christenseninstitute.org/key-concepts/jobs-to-be-done/
  2. 6.

    People do not stumble onto your website looking for something

    to do They ‘hire’ your site to solve a problem, or accomplish a task
  3. 8.

    The job is the context Creating forms which are a

    good fit requires thorough understanding of the job
  4. 10.

    What’s the least valuable part of a user story? As

    <user> I want <some feature> In order to <reach an outcome>
  5. 12.

    I want <some feature> In order to <reach an outcome>

    Doesn’t capture why these conclusions were reached
  6. 15.

    As a project manager ! I want to track which

    organisations are visiting my report ! In order to understand the impact
  7. 16.

    When I'm releasing a report at a conference where multiple

    parties are participating ! I want to track which organisations are visiting my report ! In order to understand the impact
  8. 25.

    Summary •Focus on the “Job-to-be-done” by asking: •What are users

    are trying to accomplish? •When does that need arise? •Capture this context that drives feature design in Job Stories