UX Wireframing That Settles Structure Before Style
Low-fidelity, grey-box layouts that decide what appears on each screen and in what order of priority, without colour or imagery to distract from that decision. GullySystem wireframes new products and screens being redesigned.
What a Wireframe Is For
A wireframe is deliberately plain. Boxes, labels and grey tones stand in for content, so a review stays about structure — what's on the screen and in what order — instead of turning into a conversation about colour.
- Comes after journeys and structure are agreed, and before any visual design begins
- Used for every screen in a new build, or targeted at the specific screens being redesigned
- Built with real content and field names wherever they're known, not filler text
- Reviewed and approved before visual design starts, so structural changes stay cheap
What Goes Wrong Without a Wireframing Stage
Skipping straight to a polished screen feels faster and usually costs more later.
Feedback Arrives About the Logo Colour, Not the Layout
Show a finished-looking screen too early and every review turns into an opinion on the palette, while the actual structural problem sails through unnoticed underneath it.
The Important Field Isn't the Biggest One
Without a structural pass first, hierarchy gets decided by accident — whatever looked good in the mockup — rather than by what the person doing the task actually needs to see first.
Every Screen Reinvents Its Own Layout
One screen puts the primary action top-right, the next puts it bottom-left, because nothing settled the pattern before visual design started screen by screen.
Real Content Doesn't Fit the Layout Built for Sample Text
A screen designed around short placeholder names breaks the moment a genuine customer name, three times as long, is typed into it — a problem a wireframe stage using real content would have caught early.
How We Wireframe
The process is kept deliberately unglamorous, because that's what keeps the conversation on structure.
Priority Before Layout
For each screen, we rank what the person needs to see first, second and only if they go looking, before a single box is drawn.
Grey-Box First
Screens are laid out in outline form — boxes, labels, placeholder counts — so structural review happens without the distraction of finished visuals.
Static and Dynamic Marked Separately
What's fixed on the screen and what changes with the data are annotated distinctly, so nobody mistakes a wireframe's example numbers for a real rule.
Review Kept to Structure
Sessions are framed around one question — does this screen have the right things, in the right order — and colour discussion is explicitly deferred to the next stage.
Sign-Off Before Visual Design
Structure is approved on its own before visual design begins, so a later structural change is a redrawn wireframe rather than a rebuilt screen.
What a Wireframe Set Gives You
The output looks unfinished on purpose, and that's the value of it.
- A screen inventory validated against real content and realistic data volumes, not placeholder text
- Structural decisions made while they're still cheap to change — a redrawn box, not a rebuilt screen
- A shared agreement everyone can review without being pulled off-topic by aesthetics
- The direct foundation the visual design and clickable prototype are then built on
What Shapes a Wireframing Engagement
Wireframing effort tracks the number and complexity of screens, and how settled the content behind them already is.
- The number of screens being wireframed
- How much of the structure is genuinely new versus reused from an existing pattern
- Whether the real content driving each screen — field names, list lengths, exceptions — is already known
- How many rounds of structural review are wanted before visual design begins
- Whether responsive layouts for other screen sizes are wireframed at this stage or handled later
After the Wireframes Are Approved
Wireframing settles structure. The next stage adds visual design and turns the approved layout into something people can click through.
Frequently asked questions
Do wireframes use real content or placeholder text?
Real content wherever it's available — your actual field names, sample record lengths and realistic list sizes — because placeholder text hides exactly the problems a wireframe stage is meant to catch, such as a column that can't hold a genuine value.
Can we skip wireframing and go straight to visual design?
For a handful of simple, low-risk screens, sometimes. For anything with real complexity — dense tables, multi-step forms, several roles seeing different things — skipping this stage usually means the structural argument happens later, on a screen that's expensive to redraw, instead of now, on one that isn't.
Will I be asked to approve colours or fonts at the wireframe stage?
No. Wireframes are deliberately grey and plain so the review stays on what's on the screen and in what order, not on how it looks. Colour, type and imagery are decided in the visual design stage that follows, once structure is settled.
What drives the cost of wireframing?
The number of screens and how much genuine structural novelty each one has. A form similar to five you've already wireframed goes quickly; a dense new report screen with several conditional states does not.
How many revision rounds are included?
We agree a number of structured review rounds up front, based on how many decision-makers need to sign off. What matters more than the count is that each round reviews structure specifically, so revisions stay quick rather than reopening decisions already made.
Do wireframes cover every screen, or only the important ones?
Whichever you need. A new build usually wireframes every screen so nothing is left to be invented mid-build. A redesign can target only the screens generating the most confusion, leaving the rest of the product untouched.
What do you need from us for wireframing?
The approved journey map and screen list from the previous stage, real sample content wherever you have it, and access to someone who can answer questions about an edge case quickly rather than after a week's delay.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private