Skip to main content
GullySystem

UX Wireframing

UX wireframing draws every screen of the first journey as plain boxes and arrows. Decisions about what the customer sees first are made on paper, before anything is built.

What a wireframe answers

Wireframes carry no colour, logo or photographs. A finished look invites fewer questions about structure.

What the screen asks for

Every field a person has to fill, and whether they could reasonably know the answer at that point.

What it shows back

The confirmation, the number or the status a person sees after submitting, since what they take away matters more than what they typed.

Where they go next

The arrow out of every screen, including the path taken when something fails and the path taken when a form is left half finished.

What is not here

Features parked for later, marked as parked. Nobody assumes they are part of the first version.

Questions wireframes expose

  • Who is holding the phone at this step, and where are they standing
  • What happens when this customer has no email address
  • Whether someone in your office must approve before the next screen works
  • How many taps lead from opening the app to the task the user came for

Wireframe, mockup and prototype compared

The three terms get mixed up, so here is how they differ.

Wireframe

Shows structure and order. It answers what goes on a screen and where the user can go next. It is the cheapest to change, so it comes first.

Mockup

Adds colour, type and branding. The question it settles is how the product looks. Stakeholders who judge by appearance need this stage, and some teams skip it for an early product.

Prototype

Links screens so people can tap through. Tapping through shows whether the flow works. Wireframes can be linked directly, without a mockup stage in between.

How the work runs

Map the journey first

Before drawing a screen, the steps are listed in order, from the moment a user arrives to the moment the task is done. Gaps in the order show up at this stage.

Draw the main path, then the breaks

The happy path is drawn first. Failure paths follow, such as a declined card, a lost signal or a field left blank.

Review in short rounds

You see the drawings, comment, and the next version answers each comment. Two compact rounds settle the structure.

When to skip wireframing

If the journey is three screens and everyone agrees on them, a sketch on paper is enough. Wireframing earns its place when several people hold different pictures of the product. It also helps when an operations team works behind the screens, or when an investor or partner will see the result.

What the wireframe set contains

  • Every screen in the first journey, drawn plainly
  • The flow between screens, including failure paths
  • A parked list recording who asked for each item
  • Wording for buttons and labels, settled before visual design

A wireframe review across a working week

Wireframes move through a short series of reviews, each with a different person. A designer draws, a founder judges and a developer asks how it works. This page follows that exchange across a week. Nothing is final yet, and that is the point.

Designer sketches the first journey

The designer draws each screen as plain boxes with arrows between them. No colours, no logos. The founder receives the set on Monday and can read it in one sitting. Paper is cheaper than code.

Founder marks what is missing

The founder reads the set with a pen and marks missing steps, such as a failed payment or an empty list. These marks are the best output of the week. Gaps show up early. Code has not started yet.

Developer asks how it works

The developer goes screen by screen and asks what data each one needs. A box that shows an order total needs an answer about where the total comes from. Questions cost nothing at this stage. Answers shape the build.

Customer reads the flow

A real customer is shown the wireframes on paper and asked to say what they would tap. Wrong guesses show where the arrows are unclear. Only those two screens are redrawn. Their guesses are the data here.

What to decide before screens are drawn

Drawing screens means committing to a customer, a task and a first screen. These choices are about the business, so the founder takes them. Four questions set the frame for everything the designer draws.

Which customer the first journey serves

Choose one customer and one task. Drawing for several groups at once produces a crowded home screen. The second customer’s journey is drawn later, after the first has been tested on paper. Breadth can come later.

What the first screen shows

Decide what a returning customer should see first, such as their open order or a button to start one. The answer shapes every other screen. Write it as one sentence before drawing. Test it on a stranger.

What words the product uses

Agree the terms customers use, such as booking, order or request. Mixed words confuse people and developers alike. The designer keeps a short list of terms and applies it everywhere. Consistent words save confusion later.

Which screens are left out

Name the screens that are not drawn this time, such as settings and reports. Putting them on the parked list keeps the set short and the founder honest about scope. Leaving them out is a choice.

Make an informed decision

Questions to settle before rollout.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

UX Wireframing

Can someone correct a mistake without losing their earlier work?

Use “UX Wireframing” to test an incomplete submission with keyboard-only input. Check the error wording and retained values before signing off the screen.

Background reading: W3C: usable form validation

FAQ

Frequently asked questions

Is UX wireframing the same as design?

No. Wireframes settle structure: what goes where and in what order. Visual design follows once the structure stops moving, which avoids redrawing finished screens each time a field changes.

Can we show wireframes to customers?

Show them to people who know your trade. Plain boxes read as unfinished to most buyers, and feedback turns to how it looks. For real users, a clickable prototype works better.

Who from our side needs to be involved?

Whoever answers the awkward questions: the founder and the person who runs the operation today. Two short review rounds are the usual pattern, and the number is confirmed during scoping.

What is the difference between a wireframe and a mockup?

A wireframe shows structure in plain boxes. A mockup adds colour, type and branding to show the finished look. Wireframes settle what the screen does, and mockups settle how it feels.

How detailed should wireframes be?

Detailed enough that a developer and a customer read the same meaning from each screen. Real field names and real button words matter more than pixel positions.

Do wireframes cover the admin side too?

They can, and they should when your own team runs the product from a console. Operators have journeys of their own, and drawing them early avoids a back office built in a hurry.

Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements