Product Engineering: Jobs to Be Done and Feature Tradeoffs

AI Engineer52m 9s
0 comments · 0 votesOpen discussionClose discussion
Sign in to join the discussion

    Video summary

    Kent C. Dodds reframes product requests around the progress a person wants to make in a particular situation. A conference-entry example shows why a proposed facial-recognition feature should be questioned against the actual job, including speed, privacy and operational constraints, rather than treated as the inevitable solution.

    The workshop introduces functional, social and emotional dimensions of a job, then uses the Kano model to distinguish basic expectations, performance improvements and delighters. Dodds connects these choices to feedback, reversibility and engineering judgment, arguing that AI-assisted implementation does not remove the need to understand a critical system or its failure modes.

    Original YouTube thumbnailWatch on YouTube

    Share this page

    Kent C. Dodds against a black background beside the blue and white headline “JOBS NOT FEATURES”. Framed in blue with WWW.ARTIFICIAL-INTELLIGENCE.VIDEO, 5 October 2026 and duration 52m 9s.

    Kent C. Dodds uses jobs to be done and the Kano model to evaluate features by user outcomes, distinguishing essential reliability from attractive but unnecessary complexity.