I really like the car analogy he makes: If your client asks for a car and you want to iterate, don't show them a frame with wheels on it, show them a skateboard

I really like the car analogy he makes: If your client asks for a car and you want to iterate, don't show them a frame with wheels on it, show them a skateboard. A skateboard is useful in its own right, although it doesn't have all of the features that they will want in the end. Iterate to a bike, a motorcycle, and finally a car, but at each stage you have something that works on its own. There was another article on HN a while ago about differentiating between features and core functionality, and making sure to focus on the core functionality first before you try to add the extras. Also, knowing which parts of the UI/UX are part of the core functionality is important, as is illustrated in the author's demo product fiasco anecdote. As a developer I tend to focus more on the back end functionality and supporting systems, but something can be technically beautiful and still look like useless crap to your intended users.