tezvyn:

How do you adapt contextual inquiry for internal API and tool design?

Source: nngroup.comadvanced

This tests applying ethnographic methods to API design by observing engineers at work, surfacing invisible habits, and mapping findings to endpoint granularity and docs. A red flag is treating internal users as unlike external customers or using only surveys.

This tests whether you can adapt ethnographic methods to internal tools and translate observed workflows into API design decisions. A strong answer outlines contextual inquiry inside an engineer's actual workflow, watching them code and debug to uncover invisible habits and workarounds. It then connects insights directly to API contract choices like endpoint granularity, resource naming, error clarity, and documentation structure. A red flag is claiming internal users need no generative research or substituting surveys for direct observation.

Read the original → nngroup.com

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

How do you adapt contextual inquiry for internal API and tool design? · Tezvyn