Whether you’re a one man shop, designing and coding your projects all by yourself, or a small business with a pool of talent, you will always face a challenge: how much design and UI work is needed before the mockups are passed on to the developer? To take it a step further, how much visual work needs to be done to communicate the project to the client? In this article we’ll talk about best practices for clear communication, the tools used, and resource management on both small and large projects.
The Deciding Factors of Mockup Quantity
As an owner of a small business myself, I have watched our company grow from a part time, basement dwelling, under-the-radar operation to a small business with an office, chairs, desks, and staplers (aren’t staplers an indication of your legitimacy?). During this process of hacking out of our eggshell we have birthed a company culture, a set of best practices, and gained valuable experience in the field of web design and development. One of these nibbles of knowledge is the ability to save time and money by creating just the right amount of visual material to communicate clearly with both your client and your web developer.
I’m not even going to ask if you’ve ever had a project where you create a custom web application with an intricate UI and your client pretty much freaks out and tells you that it’s completely the opposite of what they’ve had in mind. And let’s be real – it’s not because they’re web infants who drool every time a flash intro pops up…it’s because you failed at communicating the project and it’s functionality.
Don’t get me wrong, your UI is probably slick: it runs fast, the scripts are minified, it uses sprites for all button and UI elements and from a technical and design standpoint – it’s as hot as the BMW MINI Cooper in 2007. What you have failed to communicate is that your client was looking for a pickup truck.
Our approach to web design and quantity of mockups is usually based on the size of the project. For the purpose of this article I’ll break projects into two categories: the brochure site (a content managed site about the company / individual / business, etc.), and the web application site.
A Brochure Site
For small websites I recommend that you sit down with the client and spend a good hour just learning about the business. Before this meeting all you probably had to start with was an email from your cousin saying something like “Listen, Mike over at Gadget Inc. wants a cool site that will be #1 in Google”. After this meeting, however, you will be amazed at the quantity of relevant information that your client will share with you. Don’t be afraid to ask questions – information that no one would share with you is a question away when you’re sitting in front of a person. Your inquisitive attitude will also get your client comfortable because it’s indicative that you’re genuinely interested in solving his business problem.
Now that you have a wealth of information you should be able to deduct what the client really wants (and it might not be exactly the same as you originally thought). You now should know the sites they like, the reasons why they like them, the colors, logo, and other visual cues that should help you get started on the design. If your client has not yet committed to the project and is waiting for a proposal, you need to decide if providing a single mockup with your proposal will be a worthy investment. I can guarantee you that on larger projects it is an absolute must, as clients get emotionally attached to this initial mockup and it is much easier to win the bid. This more or less sums it up for small sites – clear communication with the client will help you establish a good base to start work from and the quantity of mockups should be kept to a minimum if you’re good at listening. In case you get stuck on a minute detail that the client doesn’t like, you can always post up your mockup on ConceptFeedback.com and get some feedback from other designers. Most of the time, peer opinion will sway the client to your side if you know what you’re doing.
Web Applications
Larger projects or web applications are a completely different beast and should be dealt with accordingly. Your requirements for the project will arrive in a Request for Proposal gold coated envelope scented with the smell of money which will be put together by a project lead. There will be a committee of people responsible for the content, functionality, and goals for the site and all of their opinions will be slightly different. It will be the job of the designer and/or team lead to interpret and communicate the requirements between the client and your development team in a visual manner.
I have learned that written technical specifications are only as good as the person reading them. Your developers will understand it, but your client committee will interpret it in as many ways as there are people. It is your responsibility, then, to visually illustrate the project for both teams. All items mentioned in the small website section still apply, but in addition to that you will need to build an information architecture map, functional flow, interactions mockups, and more. As you’re working through these visual elements, you should consider using some of the tools available on the web to get feedback from a wider audience.
While detailed functionality mockups are a costly venture, they are simply the best thing you can do before a line of code is written because a visual illustration will set correct expectations for your client. As a web development company you are also very lucky if you have web designers who understand markup, limitations of AJAX, accessibility and readability implications, and more. We have had some curious interactions with designers who make fantastic brochures but can’t mock up a single screen of a website UI.
This approach might seem wasteful to you at first, but you will save hundreds of development hours when your application behaves and looks in exactly identical way to your mockups and clients expectations. Your established information hierarchy and functionality mockups will also allow your developer to work completely independently from the designer with minimal interruption and questions.
Recommended Tools:
- Concept Feedback for idea-sourcing
- Basecamp for project management
- Photoshop + Illustrator for mock-up creation
- Balsamiq for functionality mock-ups
- Gridding
- Using a grid as background
- Freshbooks for time tracking
- Paper & pen for initial mock-ups
Red Flags
Even if you are following these guidelines and wield a creative stylus you will have conversations or emails which should set off alarms ringing in your head. These types of communications usually start with "This is not as hip as I wanted it", "I was expecting something unexpected", and "we really want it to look social". There are a couple of problems with these types of statements, first being you having a limited budget and time frame set for the design and having already spent some of this time. The second issue is that those statements are as ambiguous as Ricky Martins sexuality (not anymore, huh?).
Well, just like with requirement gathering, your focus here should be to drill down to the bottom of those statements and find out exactly what is meant by each. A lot of times the work you have already done can be salvaged and the client wants nothing more than a different illustration, color combination, or font stack. I suggest approaching this with items that require little effort: start with small tweaks, send mockups; continue with medium complexity changes, send mockups; rinse and repeat. What you will find through communication and these small mockup adjustments is that sometimes the negativity expressed in their email is actually an over exaggeration of a small issue.
Lessons Learned
You can probably tell that the route you take to a successful project will depend on the size and composition of your team and your ability to communicate with your client. The more projects we complete the more strongly we believe in visual communication which lies strictly on the designer’s shoulders. It is also safe to say that a web designer is a mixed and intricate breed of a professional: an individual who must understand business, be able to read customers, stay creative and fresh with visual solutions, and be technical enough to understand web technology limitations and best practices.