Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer

This post introduces two key frameworks for product engineering: Jobs-to-be-Done (JTBD) and the Kano model. For JTBD, it demonstrates how to move beyond superficial feature requests (e.g., facial recognition for workshop entry) to understand the underlying user need (e.g., efficient workshop entry without missing content). This involves dissecting needs into functional, social, and emotional dimensions, which then inform engineering decisions about system design and user experience. For the Kano model, it illustrates how to categorize user requests (e.g., for a food delivery app) into basic needs (reliable confirmations), performance gradients (delivery estimates), delighters (discounts), and unexpected features (GPS tracking). This categorization guides architectural effort, prioritizing reliability for basic needs, measurement for performance, and reversible experiments for delighters. The post also touches on handling feature prioritization, validating ideas, and the relationship between technical expertise and product judgment.