Embed Notice

@inthehands @crazybutable I think we often forget that part of the job is learning the space we're working in. If we refuse to learn anything about our client's experiences, we cannot deliver them good software. No amount of checklists will fix that.

A common example I've used is a car. You expect any car you buy will have a steering wheel, brakes, headlights, and the like. You expect the car manufacturer to know you need them even if you don't ask. They can't say "I don't know your use case."