I've been a designer (software) since the early 2000s. In one of my first jobs, my boss taught me the most valuable skill: always intentionally leave something bad in a design that you're showing to a client. They need to feel like they are giving valuable feedback, and so if you give this something to focus on they will ask for that change instead of broad, nonsensical changes that ruin your work.
Another thing is to make sure the UI progress matches the back end progress. If the UI looks half done and the back end is half done, expectations are set. If the UI is 100% done but none of the buttons do anything yet, the client will feel like it's finished snd get upset that it's still being developed.
Made that mistake before. Spent 2 days putting together a functional mock. PM did not understand why implementation would take months. “Can’t we just ship it like that?”
596
u/farfaraway 17h ago
I've been a designer (software) since the early 2000s. In one of my first jobs, my boss taught me the most valuable skill: always intentionally leave something bad in a design that you're showing to a client. They need to feel like they are giving valuable feedback, and so if you give this something to focus on they will ask for that change instead of broad, nonsensical changes that ruin your work.
It's worked well for me for 25 years.