How to design a commission to a brief.

Designing Inside Someone Else’s Constraints

I spent most of my twenties watching people treat a client brief like a sacred text, something to be followed with a sort of fearful, religious precision. They think that if they just tick every single box on that initial spreadsheet, they’ll arrive at a masterpiece. It’s a lie. If you treat a brief as a set of instructions rather than a starting point for a negotiation, you aren’t designing; you’re just fulfilling a checklist. I’ve learned the hard way that knowing how to design a commission to a brief isn’t about compliance—it’s about understanding where the client’s words end and where the actual problem begins.

I’m not here to give you a polished, textbook workflow or a series of motivational platitudes. Instead, I want to talk about the friction. I want to share what I’ve gathered from twenty years of staring at sawdust and failed joinery to show you how to find the tension between what is asked for and what is actually needed. We’re going to look at the messy, unglamorous reality of navigating constraints, and why the most successful projects are usually the ones where you had the guts to question the premise before you ever picked up a pencil.

The Friction of Intent How to Design a Commission to a Brief

The Friction of Intent How to Design a Commission to a Brief

A brief is rarely a roadmap; more often, it’s a set of boundaries that feel like a cage until you realize they are actually the scaffolding. When I’m sitting there, staring at a client’s list of “must-haves,” the real work isn’t just following instructions—it’s interpreting client specifications through the lens of what is actually possible. I’ve learned that the most dangerous part of the creative brief development process is the temptation to say “yes” to everything. If you try to satisfy every single bullet point without question, you end up with a piece of furniture that has no soul, only a checklist.

The tension lies in the gap between what a client says they want and what the object actually needs to be. I spend a lot of my time translating requirements into visual concepts that respect the budget while still pushing the material to its limit. It’s a delicate dance of managing client expectations in design; you have to show them that the constraint isn’t an obstacle to the vision, but the very thing that gives the vision its shape. If there isn’t some friction between the intent and the execution, you aren’t designing—you’re just fulfilling an order.

The Creative Brief Development Process Finding the Hidden Conflict

The Creative Brief Development Process Finding the Hidden Conflict

When I sit down with a new set of requirements, I’ve learned to look for what isn’t being said. The creative brief development process shouldn’t be a mere transcription of a client’s wish list; if I simply follow the list, I’m not a designer, I’m a technician. I look for the tension between what they say they want and the space they actually need the object to inhabit. It’s in that gap—the space between a client’s desire for “minimalism” and their need for “warmth”—where the real work begins.

I find that the most successful projects stem from interpreting client specifications through the lens of their unspoken contradictions. A client might ask for a chair that is “sturdy yet weightless,” which is a physical impossibility until you start playing with the joinery. My job is to navigate that friction. If I don’t find the hidden conflict early on, I’m just building a beautiful solution to the wrong problem. I’ve learned that managing client expectations in design isn’t about saying “no,” but about showing them the cost of their own contradictions.

Interpreting Client Specifications Through the Lens of Near Misses

Interpreting Client Specifications Through the Lens of Near Misses

When I sit down with a stack of client requirements, I don’t see a roadmap; I see a series of boundaries that I need to push against. There is a specific tension in interpreting client specifications that feels less like following instructions and more like negotiating a peace treaty. I often find myself staring at a requirement—say, a demand for “durability” in a dining chair—and I immediately think of the elegant, spindly joint I almost used before the math told me it would fail. That rejected idea, the one that felt more “right” but lacked the structural integrity required, stays in my mind. It becomes the ghost that informs the final, stable version.

The real work of translating requirements into visual concepts isn’t about finding the easiest path to a “yes.” It’s about navigating the gap between what a client says they want and what the physical constraints of the material will actually allow. I’ve learned that the most successful pieces aren’t the ones that check every box on the initial list, but the ones that respect the spirit of the constraint while barely escaping the trap of mediocrity.

Translating Requirements Into Visual Concepts That Almost Failed

When I sit down to start translating requirements into visual concepts, I don’t look for the obvious solution. The obvious solution is usually a dead end—a polite, safe gesture that satisfies the brief but lacks any soul. Instead, I look for the tension points. I remember a dining table commission last year where the client requested “warmth” and “minimalism.” On paper, those are easy. In practice, they are a contradiction. My first instinct was a heavy, reclaimed oak slab, but that felt too loud, too much of a statement. I almost went with a thin, light ash veneer, but that felt too fragile, almost dishonest.

The real work happens in that uncomfortable middle ground. It’s about managing client expectations in design by presenting the version that almost failed. I find that showing a client the “near miss”—the concept that was just a bit too daring or a bit too quiet—helps them understand the why behind the final choice. It turns the design project scope and constraints from a set of handcuffs into a framework for actual discovery.

Managing Client Expectations in Design the Courage to Pivot

There is a specific kind of vertigo that sets in when you realize the path you’ve mapped out is leading toward a mediocre result. In my studio, this usually happens mid-prototype. I’ll look at a joint or a silhouette and realize that while it technically meets every line of the original document, it lacks the soul of the initial spark. This is where managing client expectations in design becomes less about polite nodding and more about the uncomfortable necessity of the pivot. It requires the courage to tell a client that the very thing they asked for might be the thing that prevents the piece from working.

I’ve learned that true effective communication for freelance designers isn’t just about confirming requirements; it’s about explaining why a deviation is actually a fulfillment of their deeper intent. When I suggest a change, I don’t present it as a failure of the initial plan, but as a refinement born from the friction of the work. I show them the “near miss”—the version that satisfied the brief but failed the design—so they can understand why the new direction is the one that actually holds weight.

I have a shelf in the back of my studio filled with what I call “the ghosts”—half-finished joints, bent plywood curves, and failed joinery that never made it to the showroom. Most people see these as mistakes, but to me, they are the most honest parts of the process. They represent the exact moment where the design project scope and constraints began to squeeze the life out of an idea. When a brief arrives, it feels like a set of walls closing in. You start with a wide, airy concept, and then the budget, the material limitations, and the client’s specific requirements start to tighten the perimeter.

The trick isn’t to fight these walls, but to use them as a fulcrum. I’ve learned that true intentionality comes from leaning into the friction rather than trying to smooth it over. When I am interpreting client specifications, I don’t just look for what they want; I look for where their needs collide with the physical reality of the craft. That collision is where the real design happens. It’s the tension between a beautiful, impossible silhouette and the stubborn reality of a load-bearing leg that forces you to find a third, better way.

Effective Communication for Freelance Designers Choosing the Hard Path

There is a seductive ease in saying “yes” to a client’s every whim. It feels like progress, but in my experience, it’s usually just a slow surrender. I’ve spent enough time in my studio looking at the graveyard of prototypes in the corner to know that a project without tension is a project without a soul. Effective communication for freelance designers isn’t about being a polite mirror; it’s about being a filter. It’s about having the grit to pause a conversation when you realize the client is asking for a solution that contradicts the very problem they hired you to solve.

The hard path involves leaning into the discomfort of a disagreement. When I’m interpreting client specifications, I often find that the most productive moments happen right after a “no.” You aren’t rejecting their vision; you are defending the integrity of the object. If you spend the entire creative brief development process merely translating their words into shapes, you aren’t designing—you’re just transcribing. True design happens when you find the courage to push back against the initial impulse, forcing the conversation toward the decision that actually matters.

The Ghost in the Blueprint

A brief isn’t a set of instructions to be followed; it’s a boundary to be tested. The real work happens in that tense, quiet space where you acknowledge the client’s requirements, but keep one hand on the version of the design that almost failed—because that’s where the soul of the object actually lives.

Jonathan Marin

The Ghost in the Machine

Ultimately, designing to a brief isn’t about checking boxes or following a roadmap to a predictable destination. It is a process of negotiating with tension—the tension between what is asked for and what is actually needed, between the rigid constraints of a budget and the fluidity of a good idea. We’ve looked at how to find the hidden conflicts and how to communicate the hard truths when a concept begins to veer off course. But the real work lies in recognizing that the brief is not a cage; it is a set of boundaries that forces you to make meaningful choices. If you aren’t constantly weighing one direction against another, you aren’t designing; you’re just executing.

As I look at the shelves in my studio, filled with those rejected prototypes I can’t bring myself to toss, I realize that the most successful commissions are rarely the ones where everything went smoothly. They are the ones where we stood on the edge of a mistake and decided, with great difficulty, to turn back. Don’t aim for a seamless process that leaves no trace of doubt. Instead, aim for a design where the weight of the decisions is visible in the final form. The goal isn’t to avoid the near miss, but to ensure that every choice you make is a conscious departure from the path of least resistance.

About Jonathan Marin

The interesting part of a finished object is the decision that nearly went the other way.