Wireframes are one of the best tools to make the website design process more efficient. However, they can be confusing to the stakeholders. There’s a number of conventions that you need to know before diving deep.
In this article, we will shed more light on the purpose of wireframing, how to read them, why wireframes are useful before designing, and how they help you save on costly design and development iterations.
Wireframing is an exercise where you create a high-level sketch of a web page, usually in plain black and white. They are used to:
The role of a wireframe is to create a blueprint of your website. They are stripped of design cues to clearly communicate the site structure.
Here’s an example of a wireframe of a Contact Us page.
At first glance, it’s pretty unattractive. But once you realise that it encompasses almost every single interaction on that page, and clearly communicates the feature choices, it’s much easier to identify if anything is missing or misplaced.
Now that you know the purpose of wireframe and what it looks like, let’s start asking questions.
What do I need to look at?
What questions do I need to ask?
How will it help me?
Let’s find the answers.
As mentioned, the high level overview of features and layouts is crucial. You can implement every website feature in several ways, but it’s not always easy to communicate the choice using words in lengthy specifications. Wireframes can showcase future design choices and explain the essence of certain concepts.
In the example above, the wireframe clearly communicates that we will have a 2×4 grid with offices. The contents and interactions would have to be explained further, but again – this wasn’t important at this stage. Instead, we simply locked in a decision to make it a grid, rather than, say, a slider. Right away this gives us a lot more information than you might think:
As for other features in wireframes, many web agencies assume their descriptions of a column layout or a hero section are obvious to the client. In fact, just reading this is probably confusing to you.
What is a “hero section”? We can sympathise. Even within our industry, people have various names for the same sections. In this case, a hero section is the first thing you see when you land on a website. You might be familiar with its other names, like “banner” or “above the fold”. The latter has a very specific definition, but we’ve also heard people use the term “banner” to describe any section. That’s where the visualisation helps make things clear.
Wireframes can be created on a whiteboard during a meeting, on a piece of paper, or in a digital version. The latter opens up an opportunity to test the user journey at a very early stage.
Interactive wireframes include navigation links, which can be tested by both the UI designers and users. This ties into the cost-effectiveness of the project, which we’ll cover later, allowing to identify navigation issues long before design or development starts.
We are using prototypes to test the concept with real users, but wireframes work just as well – if not better. They require a bit of “mental” adjustment, as the plain look is not what people are used to. But stripping the concept of excessive colours, custom shapes and imagery prevents users from giving feedback that you don’t really need at this stage.
Whether you’re using a wireframe or the prototype, you don’t want to test the looks at such an early stage. All that matters is the usability. You want to learn about the layout and how easy it is to reach a goal. The pretty stuff will come later.
There’s a number of drag-and-drop wireframing tools that make the process easier, but we recommend taking the extra step. Once you understand the purpose and conventions, you can create digital wireframes using some of our favourite tools like InVision, Figma, or Miro.
Apart from a few conventions, wireframes aren’t as hard to read as you might think. As mentioned above, wireframes communicate the layout, features and usability aspects, such as user interface and user journey. And they’re more intuitive than you may think.
Here’s what you need to know about reading wireframes:
Designing with no idea of feature choices inflates the budget. It’s hard to put a price on the creative process already, let alone if there is no foundation in the form of wireframes.
Iterating over complex designs is much more expensive than changing a simple, black and white wireframe. It also disturbs the priorities of a web designer, who now has to evaluate both design and feature choices. And then there’s client feedback, which almost always requires additional design iterations.
Abandoning wireframes turns an exciting and creative design process into an expensive chore.
Wireframes are a great way to streamline a website build. Communicating their purpose is the only challenge. If you can get that out of the way, they will be beneficial to both the stakeholders and the web agency. It seems too good to be true, but it’s really a win-win situation.
They might seem like an added cost at first – in the end, you’re adding another step to your process. But if you consider that the exercise will ensure the site converts better and meets the expectations, while also saving money on costly design and development iterations, you’ll see that it’s incredible value for money.
Originally published Sep 26, 2019 8:57:14 AM, updated July 23 2021.