All frameworks and cheat sheets

Guide

Five research mistakes DevTools teams make

Listicle of five research mistakes developer tools teams make, from asking engineers marketing questions to never synthesizing the feedback.
The workaround question alone often tells you who you really compete with.

Five ways developer tools teams spoil their own user research: marketing-style questions, long shallow surveys, interviewing only fans, skipping the workaround and leaving transcripts unread. Use it as a check before you send the next developer survey or interview invite. Koji's AI interviews ask follow-ups on every answer and theme the transcripts automatically, which covers the last mistake.

Where this appears

What's in this guide

  1. Asking engineers marketing questions: Ask where the setup broke, not how delighted they are.
  2. Going wide instead of deep: Five sharp questions with follow-ups beat twenty-five flat ones.
  3. Only talking to champions: Also reach the developers who bounced in onboarding and the ones who chose a competitor.
  4. Ignoring the workaround: The real competitor is often a homegrown script, not a funded rival.
  5. Letting feedback rot in a spreadsheet: Interviews nobody synthesizes never reach 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/devtools-research-mistakes"><img src="https://www.koji.so/visuals/devtools-research-mistakes/devtools-research-mistakes.png" alt="Listicle of five research mistakes developer tools teams make, from asking engineers marketing questions to never synthesizing the feedback." width="1080" height="1080" /></a>
<p>Source: <a href="https://www.koji.so/visuals/devtools-research-mistakes">Five research mistakes DevTools teams make</a>, Koji</p>