Using Jobs to Guide Strategy and Design

Public group
Location image of event venue


#JTBD·CPH — Meetup #4


🔌 17.20 - Mads Kristensen, Partner at FURTHER (

How do you make Jobs operational in a corporate setting? What is the potential, and how do you go about it to make sure that Jobs guides your most important strategic as well as design decisions?

FURTHER shares key learnings from working with enterprise and public/private partnerships.

🔀 17.40 - Recap from last meetup: Job Mapping

April and June Meetups looked at interviewing customers with the Switch framework, then understanding current behavior with Job Maps, respectively.
A huge topic last time, so it seems fitting to reiterate the main points of Job Maps and the JTBD Canvas

🍤 17.55 - Snack break

🔬 18.30 - Intro to Job Stories

To wrap it up, we’re taking a look at how Job Stories can be used to describe a Job to be done, in plain, simple language everyone can understand (words customers actually use), from developer to executive.

A Job Story is a great way to introduce Jobs thinking to your team and coworkers, as both a workshop/intro tool and as a format to keep insights visible over time.

Learn how to model the bigger picture of a design, in terms of the functional, social and emotional goals your users have, and use Job Stories to guide design and product development.

⚒ 18.45 - Group exercise: Creating Job Stories

We’ll pair up and try working out a Job Story together. Templates will be provided, but bring a pen.

💡 19.30 - Wrap-up, drinks and shared discussions

See you!



- How Intercom use Job Stories,
- Designing Features using Job Stories, Alan Klement
- Products are Functions, Ryan Singer (Basecamp)