Hacker News Reader

Comment by everdev | Hacker News Reader

The points all make sense, but anytime I've tried to show clients anything less than a high fidelity mock-up (wireframes, design palette, b/w mockups, etc.), I've been meet with something been indifference and guarded acceptance.

Most of my clients (who have marketing but not design backgrounds) want that "wow" factor when they see the first mockups. By easing into the designs I felt like I lost that.

As a designer I realized I wasn't just delivering a JPG, but a design experience. My clients seemed to equally enjoy putting their mark on the design and imaging the same "wow" factor their CEO would feel when they saw the latest iteration.

So, while I love this process for personal projects or for companies familiar with the design process, for the average marketing team I'm still going full color mockups.

View on HN

Designer myself. It very often helps to visually communicate this as a draft. That means: show them a drawing, or a nice rendering with Copic markers – even if you designed on the computer.

When they see some cleanly designed draft printed out (or worse: on the screen), most people cannot see that it is a draft, even if you tell them.

I firmly believe that communicating the right thing in a strategic way to the customer giving them what they need and making them realize that they want it, is what seperates a good designer from a bad one.

Another way than actually drawing is to give them many drafts, so they focus on the differences. This however depends on the job (sometimes multiple drafts are not a thing you can afford time wise).

>Most of my clients (who have marketing but not design backgrounds) want that "wow" factor when they see the first mockups. By easing into the designs I felt like I lost that.

When I got started in marketing the best designers I had the pleasure of working with educated me as to the different kinds of decisions design needs to make.

The finished product is the amalgamation of many different, distinct, decisions. Those decisions include things like: what is the objective of this page? If there's more than one objective which one is more important? If there are several objectives how do they compare in terms of importance to the end user? How does that contrast with the goals of the business? How do we want the user to feel? What do we want them to think? What action do we want them to take?

Some of these questions require high fidelity design while others do not. The lower fidelity designs typically help answer the strategic questions that the higher fidelity designs will build upon and execute. Using sketches and wireframes facilitates separating these conversations.

If a client is looking for a 'wow' factor with the first mockup then they've confused themself with the end user.

That was indeed brilliantly put. I'm saving this. So many questions get answered if you explain this right at the very beginning of the design process.

This kind of approach should also apply to good requirements gathering in my opinion.

> As a designer I realized I wasn't just delivering a JPG, but a design experience.

Yes, a lot of "craft" oriented people don't realize that until they have a few painful experiences with clients. They spend hours and hours poring over every single pixel, and then do not spend anywhere near the same amount of effort on communicating with and presenting to the client.

The article is correct that designing without color at first can be a fine approach, encouraging you to focus on weight, layout, etc. But showing these intermediary, exploratory outputs to the client is just asking for wasted time at best, and trouble at worst.

It depends on whether you're designing for your clients, or for your clients' customers. It sounds like you're doing the latter.

I understand that focusing on pleasing your client is the easiest way to gain acceptance and possibly business, but if it's at the expense of delivering a product that actually serves your client (which pandering to clients on purely aesthetic grounds very often is), you're effectively selling snake-oil. It may be lucrative, but it's bad design. Doing good design requires managing your clients' expectations and selling them on quality.

Setting correct expectations is a generally hard problem. As a designer myself, I try to outline the whole process with my clients before work begins and I emphasize “wireframes” vs “mockups.” It’s worked for me so far, but YMMV.

Reply on news.ycombinator.com