Skip to content
Strategy

Research before design, always

The cheapest hour in a project is the one spent not designing the wrong thing. A short, honest inquiry — even in a tight timeline — changes what gets built.

Noura Al-Harbi Head of Design
6 min read
Share

The temptation to open the design file on day one is understandable: everyone wants to see something. But an hour spent drawing a solution that is not yet understood is an hour you will pay for later in rework, and in meetings that explain why the page “did not feel right.” Research before design is not academic luxury, and it is not a separate project to postpone until there is time. It is the cheapest way to avoid building the wrong thing.

By research we do not mean a months-long encyclopaedia. We mean specific questions, and answers from real sources: a conversation with someone who uses the product, a review of support and complaints, or a watch of someone trying to complete a task on the current site. On tight timelines, short inquiry is more honest than pretending the team “knows the market” because the last deck looked convincing.

What you lose when you start with form

When a project starts with screens, hypotheses harden into fact with surprising speed. A headline a stakeholder liked becomes the product message. A layout borrowed from a visual reference becomes the information structure. After a few days, critique turns cosmetic, because admitting the direction is wrong looks expensive. Form has acquired political weight.

Early research lightens that weight. It does not forbid beauty. It delays commitment until we know who we are serving in this phase, which task must succeed, which language people actually use, and where the current path stumbles. Design then becomes an answer, not an elegant guess.

If the team cannot write one sentence about whom it serves and what must succeed, any screen it draws will be an expensive guess.

Short research is enough when it is honest

The honesty of the research matters more than its size. Five conversations with real users, if they are well listened to, are worth more than a file of general summaries. A review of ten recent support tickets may reveal a clearer pattern than a loose survey. The point is to look where real friction lives, not where impressions are easy to collect.

Questions we ask before any visual mood

We decide in advance what we need to know in this cycle, and we stop when the answer is enough for a decision. Good questions narrow the field: who is trying to do what? Where do they stop? What do they trust? What do they ignore? And which sentence do they use, not the sentence we wish they would say.

Those questions protect the team from decorative research: interviews that confirm what was already decided, or competitor references used to justify a look we already liked. Research that cannot change a decision is not research. It is procedural décor.

Practical sources that do not require a wide budget

Many teams delay research because they imagine a costly lab. In practice, a disciplined start can rely on sources already at hand if they are asked well. These are some of the sources we return to early on most projects.

  • Short conversations with people who sell or answer customers: they hear objections before design ever does.
  • Watching someone outside the team try to complete a task on the current site or app, without early intervention.
  • Support messages, reviews, and repeated questions in mail or chat, treated as an archive of misunderstanding.
  • The language the audience already publishes: how they name the problem, not how we name it on a slide.
  • A review of the current path: where a form runs long, and where an important fact is buried under ornament.
  • A narrow comparison with real alternatives the audience uses, looking for expectations rather than for something to copy.

The aim is not to fill a binder. It is to extract three to five notes capable of changing the first screen. If a note changes nothing, it may not yet be a note — or we may not have been ready to hear it.

Steps for bringing research into a tight schedule

The usual objection is time. Our answer is that research here does not postpone design indefinitely. It precedes the first formal commitment by a few days, and it saves later weeks. This sequence fits a real project that has a date.

  1. Name a decision you need to make: the message, the path, or the content priority on a specific page.
  2. Choose only two or three sources tied to that decision, and refuse to scatter effort into a general survey.
  3. Hold the conversations or observations on close days, and summarise on the same day, not a week later.
  4. Write one page: what you learned, what is still a hypothesis, and what you will not build now.
  5. Share the summary with stakeholders before drawing, and get agreement on the problem, not on the colours.
  6. Then start design as a test of that summary, and return to users if the bet changes.

After this path, reviews become shorter. Disagreement moves from “do I like it” to “does it serve what we agreed we heard.” That alone justifies the few days spent listening.

Design after research is, in truth, faster

Research looks like delay to anyone who reads a calendar as a straight line. In practice, teams that design from something they have heard reduce cycles of rejection, reduce pages rebuilt from zero, and arrive at more honest content. Real speed is not who drew first. It is who reached a solution that holds.

We stay modest: short research does not remove risk, and it does not grant full certainty. It reduces costly ignorance. After launch, listening continues, because the product changes and the audience speaks again.

Do not design until you have listened

Design is honourable work, and it is more expensive than it looks when it is aimed at the wrong question. Research before screens — even a few days of it — is professional courtesy toward a client’s budget and a user’s time. Always, even when the calendar is tight, there is room for one honest question before a guess becomes an interface.

If you are about to redesign a path or a site, we can start with you on this short pass before any screen. Write to us, and together we will save the design hour that would have been spent in the wrong direction.

Want an article that turns into work?

We will review your site or campaign and build a clear plan for the next step.