7. Interviews For
Jobs To Be Done
Interview Tools:
Timeline
First thought
what happened that made that person look for a new solution;
what’s the drive?
Event 1
what triggered active looking?
Event 2
decision to switch
Buy
how did they imagine the future?
this is where expectations are set.
Satisfaction (unpacking)
PASSIVE LOOKING
ACTIVE LOOKING
8. Interviews For
Jobs To Be Done
Interview Tools:
Forces Diagram
push pull
habits anxieties
9. Interviews For
Jobs To Be Done
Conclusions
HABITS
• previous system non-existent usually
• people not willing to use tools
SITUATION WITH LAST SETUP
• no system, no overview
• a feeling of information being lost
and out of control
• some sort of change
in management or team
HOW TEAMWEEK HELPS
• visual overview (color coding!)
• very easy to use
• in a lot of cases: collaboration
ANIXIETIES
• some instability
• some additional pleas for features
• how to sell this to the management
10. Interviews For
Jobs To Be Done
Conclusions
setup
OVERVIEW
maintenance
• ease of use: making plans
• drag and drop
• adding users is easy
• learning is easy
• ease of use: drag and drop
to react to change
• making room where there’s
an incoming priority
assignment
• checklists and files to task
comments
• people taking on
assignments when someone
falls ill
• marking tasks done
• sharing timeline with clients
collaborationsetup
11. Interviews For
Jobs To Be Done
Direct Action
What Have We Done
• Rewritten Strategy and Mission
• Experimenting With Explaining
Teamweek Differently
12. Interviews For
Jobs To Be Done
Direct Action
What’s In Progress
• New Product Strategy
(Overview For Whom?)
• New Onboarding Messaging
• Achievements
13. Interviews For
Jobs To Be Done
Direct Action
What’s To Come
• Product Stories
• Opportunities For Marketing