Oct 17, 2026

6 min read

The Brief Is a Symptom: Reframing Enterprise Requests Before You Design

Most briefs arrive as a solution. Here is how I work out what a request is actually evidence of, and why that one step has changed more of my shipped work than any screen I have drawn.

Introduction

Almost every brief I have received arrived as a solution.

  • “Simplify the Create Client API.”

  • “Build a better project management tool for enterprise teams.”

  • “Make software for dietitians.”

Each one was reasonable. Each one, built as written, would have produced the wrong product.

That is not because the people writing briefs get it wrong. A brief is written from where the pain is felt, which is rarely where it starts. It is a symptom report. My job is to work out the diagnosis before anyone starts drawing.

Here is the process I use, with the projects where it mattered most.

1. Ask what the request is evidence of

On Tracker I-9, the brief was to simplify the Create and Update Client API. Partners had to send about 50 configuration arguments for every new client, and support kept getting setup tickets. Shorter API, fewer tickets. Simple.

So I went to the evidence instead of the request. I rebuilt the existing admin and client screens in Figma, which meant walking every tab a setup touched. I read the partner tickets. I sat with the PM to understand how setups actually moved between clients.

The partners were not confused by the API. They had mastered it. What hurt was that they were setting up the same configuration again and again, with nowhere to keep one that was already right. A shorter form would still have meant building every setup from scratch.

The product did not need to be simpler. It needed a memory.

We shipped Distributor Packages: build a complete setup once, save it, and assign it to any client in one step. One package ID replaced about 50 arguments. Three months after release, onboarding a client took about 40% less time and partner setup tickets dropped by about 70%.

2. Check where the request puts you

Some briefs are not wrong about the problem. They are wrong about the fight.

On Dunio, the client asked for “a better PM tool for enterprise teams.” Taken literally, that puts a small company head to head with Jira, Asana and ClickUp. A small team’s product loses that fight.

Research showed something else. Teams were not short of tools. They used 8 to 12 of them, and the failure lived in the space between those tools, where nobody owned anything. So the brief became “build the layer that connects what teams already use.” Same users, same budget, but a place in the market where nobody was selling.

3. Treat workarounds as the real spec

The most honest requirements document in any company is the workaround people build when the product lets them down.

  • A delivery lead who rebuilt a Notion page every morning because the PM tool could not tell her what was going on.

  • Distributor admins keeping a Google Doc of “standard setups” outside the product.

  • Dietitians acting as the glue between Excel, WhatsApp, Canva and their UPI app.

None of these showed up in a brief. All of them told me exactly what the product had to absorb. When I find a workaround, I design to delete it, and I use “they stopped doing the workaround” as the success signal.

4. Name the thing carefully

Distributor Packages changed names three times: from Distributor Configuration Templates, to Templatized Client Packaging, to the name that shipped.

That was not cosmetic. A template is a blank document you fill in. A package is a complete thing you hand over. Once the team started saying “package”, the conversation moved from simplifying a form to delegating a setup, and that shaped every decision after it, from how inheritance worked to how a package could be switched off safely.

If the name of a feature describes the old problem, the team will keep designing for the old problem.

5. Reframe out loud, and keep the goal

Reframing is not ignoring the brief. The goal behind the brief still has to be met. The partners still needed fewer tickets and faster go-lives. Dunio’s client still needed a product that could sell.

I write the reframe in one line and share it before designing anything:

“We were asked to X. The evidence says Y. So we propose Z, which still achieves the goal of X.”

That sentence does two things. It shows the people who wrote the brief that I heard them. And it makes the reframe something we can disagree about with evidence, rather than a designer’s opinion.

When not to reframe

Sometimes the brief is right. Sometimes the evidence is thin. A reframe built on a hunch costs trust, and you only get a few of those before people stop listening.

My rule is simple. I reframe when I can point to the evidence: tickets, workarounds, behaviour I have watched. When I can’t, I build what was asked, measure it, and bring the evidence next time.

Closing thoughts

The most valuable design work I have done happened before I opened Figma. Not because the screens did not matter, but because the right screens only exist once you know what problem they are solving.

Key Takeaway

A brief tells you where it hurts, not what to build. Read it as evidence, find the workaround people already rely on, and propose a reframe that still meets the brief’s goal. That is the job, long before the first frame.

Be the first to know about every new letter.

Stay ahead in the world of web design with expert insights, industry trends, and practical tips.

No spam, unsubscribe anytime.