All frameworks and cheat sheets

Framework

Why continuous discovery stalls: three frictions

Framework of three frictions that stall continuous discovery: the scheduling burden, the synthesis lag and the gap between research and decisions.
A stack that only fixes the third friction still stalls. It has to remove all three.

A framework of the three operational frictions that stop weekly customer interviews from lasting: the time it takes to schedule each call, the lag between a call and its synthesis, and the missing handoff from findings to roadmap decisions. Use it to audit a continuous discovery program, or to check whether a new tool removes the friction that is actually stopping you. Koji runs interviews from one link and builds themes as they complete, which takes care of the first two.

Where this appears

What's in this framework

  1. The scheduling burden: Recruiting, booking, rebooking and chasing even one interview a week eats hours of PM or researcher time.
  2. The synthesis lag: Transcripts and tags arrive days after the call, and by then the best quote is forgotten.
  3. The research-to-decision gap: Findings sit in a doc nobody reads, with no clear line from what you heard to what changes on the roadmap.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/why-continuous-discovery-stalls-three-frictions"><img src="https://www.koji.so/visuals/why-continuous-discovery-stalls-three-frictions/why-continuous-discovery-stalls-three-frictions.png" alt="Framework of three frictions that stall continuous discovery: the scheduling burden, the synthesis lag and the gap between research and decisions." width="1200" height="630" /></a>
<p>Source: <a href="https://www.koji.so/visuals/why-continuous-discovery-stalls-three-frictions">Why continuous discovery stalls: three frictions</a>, Koji</p>