Technology-first approach

"How can we include AI into our product? "Let's digitalize our product offering." "We need a mobile app - let's build one." "We need to become more innovative - let's brainstorm some ideas."

These quotes are quite typical of what we see in our practice at companies. We call it a solution-first or technology-first approach. Starting with the technology, building a product or strategy and only then looking for a customer need or a customer problem to solve.

We believe this is incredibly wasteful and lessens the likelihood of success. It leads to many iterations and might even miss the sweet spot of customers all together.

CFI goes the opposite way. If you follow the CFI process in this course, you will discover the unmet needs and problems of your future customers upfront and in a data-driven way, allowing you to select the right need opportunities in the market and tune your technology or solution towards those opportunities. CFI is a needs-first approach and thus tries to prevent you falling into the technology-first trap.

Become a Growth Architect: Measure needs with Jobs-to-be-done

Buy nowLearn more

Let's meet!

  • Hi, I'm Beat
  • Hi, I'm Yann

Jobs-to-be-done

  • Jobs-to-be-done is a way to think
  • What is a Job?
  • Job example: Public transport
  • Job example: Ed-tech
  • Job example: Car manufacturer
  • Lesson summary and outlook

Pitfalls in designing growth initiatives

  • Technology-first approach
  • Ocean of ideas
  • Biases in decision making

The CFI process

  • CFI in a nutshell
  • Frame
  • Discover
  • Spin
  • Action
  • Summary

Framing

  • Case study
  • The purpose of Frame
  • Business intention
  • Get inspired: Other business intentions
  • Target group in B2C
  • Target group in B2B
  • Brainstorm a Jobs-to-be-done hypothesis
  • The Jobs-to-be-done Hierarchy
  • Finding the right Focus Job
  • Get inspired: Framing examples
  • Jobs-to-be-done Hierarchy template
  • Lesson summary and outlook

Qualitative Discovery

  • Purpose of qualitative interviews
  • Get ready!
  • JTBD interview excerpt
  • Start the Jobs-to-be-done interview
  • Validating the JTBD hierarchy
  • Structure of a Job Metric
  • Get Job Metrics from participants
  • Try to find Job Metrics
  • Job Metrics we heard
  • More Job Metric extraction techniques
  • Why do Job Metrics have to be precise?
  • Consolidate Job Metrics into one long list
  • Interview plan and guide
  • I can't quantify: What can I do?
  • Value Map template and workshop instructions
  • Lesson summary and outlook
  • FAQs on qualitative interviews

Quantitative Discovery

  • Purpose of quantifying Jobs-to-be-done
  • Select Job Metrics for quantification
  • Structure of a CFI survey
  • Run a Jobs-to-done survey
  • Analyzing Jobs-to-be-done data
  • The Value Map
  • The Journey Navigator
  • Datafile Template to analyze and visualize the data
  • Drawing conclusions from data
  • Lesson summary and outlook

Spin

  • Purpose of Spin
  • Vendbridge Value Proposition canvas
  • Value Proposition workshop
  • Pain Matching
  • Pain Matching tool template
  • Lesson summary and outlook

Action

  • Keep the customer at the table!
  • New idea? Only when it solves a Pain Point
  • More cases and Info

Q&A

  • Q&A Session

Glossar

  • List of terms and definitions