Product Engineering: Jobs to Be Done and Feature Tradeoffs

AI Engineer52m 9s
Kent C. Dodds against a black background beside the blue and white headline “JOBS NOT FEATURES”.
0 comments · 0 votesOpen discussionClose discussion
Sign in to join the discussion

    Kent C. Dodds reframes product requests around the progress a person wants to make in a particular situationJobs to be done is a product research framework that describes the progress people want 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, privacyData privacy governs how personal, confidential, or sensitive information is collected, used, shared, retained, and protected in AI systems. 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 judgmentHuman judgment in AI is the accountable interpretation and decision-making people contribute when setting goals, evaluating evidence, and managing consequences., arguing that AI-assisted implementation does not remove the need to understand a critical system or its failure modes.

    Original YouTube thumbnailWatch on YouTube

    Video topic coverage

    • Agents & workflows0
    • Coding & tools80
    • Models & learning0
    • Infrastructure & compute0
    • Research & evaluation15
    • Safety & security35
    • Business & productivity100
    • Creative & media0
    • Robotics & perception10
    • Society & policy10

    Share this video

    Kent C. Dodds against a black background beside the blue and white headline “JOBS NOT FEATURES”. 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.