<?xml version="1.0" encoding="utf-8"?>

Wireframes should focus on a team's plan and goals

Wireframes should focus on a team's plan and goals

The way you style your wireframes depends on a few things: the goals for your product, the costs associated with developing the wireframes, and the time and effort available to focus on the wireframing process. So how do you decide?

First, think about how the wireframe will be used. Is it purely an internal document? In that case, you can likely get by with low-fidelity, or even hand-drawn, wireframes. Will they be shown to clients, potential users, or high-level stakeholders? You’ll probably want to create something more polished, include actual wireframe text, use colors, and add relevant imagery. You’ll likely need to strike a balance between creating high-fidelity wireframes and not spending too much time styling them.

Remember that the higher-fidelity your wireframes are, the less creative feedback stakeholders may offer.[1]

Improve your UX & Product skills with interactive courses that actually work