Process
How to run developer research that gets completed

Five steps for running user research with software developers that they actually finish: keep it short, frame questions in technical terms, probe specifics with follow-ups, reach them inside the product or community, and pair structured questions with open ones. It is meant for product, DX and growth teams at developer tools companies. Koji runs this as a short AI-moderated interview with adaptive follow-up questions.
Where this appears
What's in this process
- Respect their time: Short and conversational. A two-minute adaptive interview beats a 20-question form they will quit.
- Lead with technical credibility: Ask in their language: stacks, workflows and failure modes, not marketing abstractions.
- Probe, don't interrogate: When the API was confusing, ask which endpoint, doing what, expecting what.
- Meet them where they are: In-product, in CLI onboarding, after a docs visit or in a developer community, not a generic email blast.
- Mix the what and the why: Pair scale and single choice questions with open questions that explain the pattern.
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/developer-research-steps-that-get-completed"><img src="https://www.koji.so/visuals/developer-research-steps-that-get-completed/developer-research-steps-that-get-completed.png" alt="Process showing five steps for user research with developers: respect their time, sound technical, probe, meet them where they work and mix what with why." width="1200" height="792" /></a>
<p>Source: <a href="https://www.koji.so/visuals/developer-research-steps-that-get-completed">How to run developer research that gets completed</a>, Koji</p>




