2 ms·
This sort of expectation management is also why it is a terrible idea to show a client a slick UI mockup that kinda works (but is missing the underlying app log
by georgemcbay 13y ago
This sort of expectation management is also why it is a terrible idea to show a client a slick UI mockup that kinda works (but is missing the underlying app logic).
As far as they are concerned, you're pretty much almost done because all the stuff they will ever see is there and looks good. No matter how much you try to rationally explain to them that it is just a superficial shell of an app and is a long way from done, a lot of them just aren't capable of internalizing this concept meaningfully.
- nknighthb 13y agoWhat's the best way you've found to manage that particular issue? Line-art slide decks instead of interactive demos?
- georgemcbay 13y agoIn my experience, yeah that's basically it. If it helps to have an interactive demo to communicate things, keep it ugly when showing it to the client, and show them the final UI designs separately as static image files. Even if you've already done the work to bring the assets into the demo, avoid showing this to the client as long as is reasonably possible to manage their expectations because they will almost universally have a hard time separating the UI/UX functionality completeness from everything else. Obviously there are situations where the client will, in fact, understand the distinction, but I assume they won't until proven otherwise.
- Tloewald 13y agoBecause it's so easy to make slick mockups a lot of developers have forgotten that lo fi prototypes are a Good Idea, but obviously you're also selling against folks who will show clickable prototypes that look finished, so it's a matter of building a relationship where you can avoid this kind of silliness.