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

## Executive summary

The video argues that as AI agents level the implementation playing field, the most valuable skill for engineers is product judgment—the ability to build the *right* thing. It introduces frameworks like Jobs to be Done (JTBD) and the Kano Model to guide product decisions, emphasizing that technical effort must be directed toward solving fundamental user problems rather than implementing requested features. Engineers must understand the functional, social, and emotional dimensions of a product to inform architectural decisions, prioritizing reliability and reversibility.

## Key takeaways

- Jobs to be Done (JTBD): People 'hire' products to help them make progress in a specific situation. Instead of accepting feature requests, engineers should ask 'Why?' repeatedly (the 'problem tree') to uncover the underlying job statement (e.g., 'Help me get into the workshop quickly so I can learn about product engineering without missing the first 20 minutes.') [8:52].
- Functional, Social, and Emotional Dimensions: When defining a job, consider three dimensions: Functional (does it work?), Social (who is involved when using it?), and Emotional (how do users feel?). These dimensions must inform technical decisions, such as whether to use facial recognition or a simpler NFC chip [11:34].
- Kano Model for Prioritization: The Kano Model classifies features into Basic Needs (must-haves, e.g., reliable order confirmations), Performance Needs (measurable gradients, e.g., ETA accuracy), and Delighters (unexpected extras, e.g., surprise discounts). Focus must first be on nailing the basics, as delighters are useless if the foundations are weak [15:00].
- The Product Engineering Mindset: The job of the product engineer is to translate the identified 'job' into technical requirements, determining the necessary reliability, performance constraints, and architectural effort, rather than simply implementing a feature request [17:29].

## Technical details

- System Architecture & Data Modeling: When solving a problem (like speeding up workshop entry), engineers must consider the necessary state and data, such as maintaining a database of faces (if using facial recognition) or implementing NFC chips in badges. The architectural impact must be weighed against the core job statement [17:29].
- Incident Response and Reliability: Understanding the system's code and architecture is critical for incident response, especially when business losses are measured in millions of dollars per minute. While AI agents can assist, deep system knowledge is required to guide the fix and diagnose the problem quickly [22:00].
- AI and Future Development: The increasing capability of AI agents means that the differentiator in product development will be the ability to define and solve the *right* problems, not just the ability to implement solutions. This requires strong product judgment and system thinking [29:00].

## Practical implications

- When receiving a feature request, immediately pivot to asking 'Why?' to uncover the core user problem (the 'job').
- Use the Kano Model to prioritize development, ensuring Basic Needs are fully implemented before investing heavily in Delighters.
- When designing a system, map the solution across functional, social, and emotional dimensions to anticipate technical and user impacts.
- Always evaluate the cost of maintenance for features that users actively dislike or that fall into the 'Indifference' or 'Reverse' categories.

## Topics

Product Management, Product Engineering, System Design, User Experience (UX), Product Strategy, AI Development, Jobs to be Done Theory, Kano Model, Competing Against Luck

Source: https://www.youtube.com/watch?v=s0hFne6EeOI