4 ms·
The second point is that most people don't know what they want until you show it to them. Designing what you're told only works with people who have done the ex
by davidivadavid 4y ago
The second point is that most people don't know what they want until you show it to them. Designing what you're told only works with people who have done the exploration themselves, which tends to be a tiny minority (because it essentially requires the design skills that they're expecting from the designer themselves).
- duxup 4y agoMy very first application that was all mine was demoed to the customer. They hated it, had tons of changes demanded. I told them I would update it in a week. I didn't get to it. I go to the next meeting and before I can apologize for not making the changes. "We love the changes! Keep it like it is now!" I think they just needed to see it twice...
- meerita 4y agoWell, one of the traits of a designer is being able to master draft anything in couple of hours, max. Also, PMs should help on teorizing what would a product be like. That helps to create expectations, but also, helps the designer to see what's the idea they want. The designer in the end will make all the needed changes in order to deliver a performant design.
- davidivadavid 4y agoYou're coming at it from a different context than the original article, which is more about what an agency would do, where there won't be PMs and designers have to figure out requirements themselves (often precisely by challenging what the client is asking for).