Most design projects don’t fail because the designer wasn’t talented. They fail because the collaboration broke down. A clear brief, timely decisions, and feedback that actually helps: these are the things that separate a project that ships something great from one that limps to a mediocre finish.
What “Working With a Designer” Actually Means
Working with a designer is not the same as placing an order. Design is a problem-solving process, and the client is part of that process. You bring domain knowledge, business context, and the ability to make decisions. The designer brings craft, systems thinking, and the ability to give ideas visible form. Neither party can do the other’s job, and the quality of what ships depends heavily on how well the two of you exchange information.
The fastest way to understand this: think of a designer less like a vendor executing specifications and more like a specialist you’ve hired to think alongside you. The more honestly and precisely you can communicate what you’re trying to solve, the better the work will be.
Write a Brief That Does the Job
The brief is the most undervalued document in any design engagement. A good brief doesn’t constrain the designer; it focuses them. A bad brief (or no brief at all) forces the designer to guess, which wastes cycles and produces work that misses the mark.
A brief for most design projects should cover:
- The problem. What are you actually trying to solve? Not “we need a new website” but “our site doesn’t communicate what we do to enterprise buyers, so we lose them before they reach the contact page.”
- The audience. Who is this for? What do they care about? What do they already believe?
- The constraints. Budget, timeline, technical environment, legal requirements, things that cannot change.
- The measures of success. How will you know this worked?
- What you’ve already tried. What didn’t work, and why.
- References and direction. Examples of work you admire, with notes on why you admire them, not just “I like this.”
That last point matters more than people expect. “I like how this feels confident but not aggressive” is useful. “I like this” is not.
For a deeper look at the document that sets every project up, see The Creative Brief That Actually Briefs.
Give Feedback That a Designer Can Use
Feedback is where most client-designer relationships go wrong. The two failure modes are opposite ends of the same problem.
Too vague: “It just doesn’t feel right.” “I’d know it when I see it.” “Can you make it more exciting?” These tell the designer nothing actionable. They invite a guessing loop that burns time and goodwill.
Too prescriptive: “Move that logo 10 pixels to the left. Use this exact shade of blue. Make the headline bigger.” This treats the designer as a pixel-pusher rather than a problem-solver. It also tends to produce incoherent work, because you’re making dozens of micro-decisions without the systems context the designer holds.
The most useful feedback sits in the middle: it describes the problem with the current design, not the solution. “The headline isn’t landing the key benefit quickly enough” is better than “make the headline bigger.” “This color feels too corporate for our audience” is better than “change it to green.”
When you receive a round of work, try to answer these questions before responding:
- Does this solve the stated problem?
- Is anything factually wrong (wrong product name, missing element)?
- What would your audience think or feel seeing this?
- What specific things aren’t working, and why?
“The goal of feedback isn’t to tell the designer what to do. It’s to tell them what isn’t working so they can figure out how to fix it. That’s the job you hired them for.”
Consolidate Before You Send
If multiple stakeholders are reviewing work, consolidate feedback before it goes to the designer. One set of prioritized notes is infinitely more useful than five individual email threads with conflicting opinions. Decide internally which feedback reflects a genuine problem versus a personal preference. Not all feedback is equal, and the designer should not be adjudicating internal disagreements.
Build Trust Early
The best designer-client relationships feel collaborative because trust was built quickly. Trust doesn’t appear from nowhere. It’s built through small consistent actions on both sides.
From the client side, trust-building looks like:
- Sharing context generously. The more the designer understands about your business, your customers, and your competitive landscape, the better decisions they make. Don’t hold back.
- Respecting the timeline. If the designer needs a decision by Thursday to hit the next milestone, give them a decision by Thursday. Latency compounds. A one-day delay early can cascade into a two-week slip later.
- Being honest about constraints. If the budget is fixed, say so upfront. If a deadline is immovable, say so upfront. Discovering constraints midway through a project forces rework.
- Giving direction, not consensus by committee. Designers can work with a single strong point of view. They struggle with five conflicting ones. Identify the decision-maker before work begins and stick to that structure.
If you’re working with a boutique studio on a full brand or digital engagement, reading What to Expect Working With a Boutique Agency will set expectations well before kickoff.
Make Decisions on Time
This deserves its own section because it’s the single most common reason projects stall.
Design projects have a rhythm. Concepts lead to refinement, which leads to build, which leads to delivery. When a client sits on a decision for two weeks, it doesn’t just delay that one step. It breaks the rhythm. The designer’s context has cooled. Other projects have filled the gap. The momentum that produced good thinking in the first place has dissipated.
A few practical principles:
Define the decision-making structure upfront. Who has final say? Who gets input? What’s the escalation path if stakeholders disagree? Answering this before work begins prevents the worst delays.
Separate “needs more thinking” from “I don’t like it.” If you need time to reflect, say “I need a few days to think about the strategic direction,” and that’s legitimate. “I don’t like the colors but I’m not sure why” is a feeling that can be worked through in a conversation, not by waiting.
Trust the process on executional decisions. You hired a designer because they know things you don’t. On decisions that are primarily craft judgments (kerning, hierarchy, micro-animation timing), defer unless there’s a genuine strategic or audience reason not to.
Understand What You’re Buying
Design is often misunderstood as a service category. Clients sometimes expect certainty (“show me the final output before we start”), fixed scope at variable output (“add these five things, same budget”), or unlimited revision (“we’ll know it when we see it”). None of these expectations match how good design actually works.
What you’re buying is a process with a defined scope, a skilled team applying judgment within that scope, and a deliverable that solves the stated problem. The output depends partly on your inputs. If your brief is fuzzy, the first round of work will be exploratory. If your feedback is clear and timely, the refinement rounds will be focused.
Understanding how much branding work costs and how to scope a web project before you engage a studio helps align expectations in both directions. Scope creep (the most common source of friction) almost always traces back to an underspecified brief or a client who didn’t understand what was and wasn’t included.
The Strategic Dimension
The best design engagements aren’t just executional; they’re strategic. A designer working on your brand or site should understand your positioning, your audience, and the competitive space you’re operating in. If they don’t, they’re applying craft without context, and the work will show it.
Clients who get the most from a design engagement treat it as an opportunity to sharpen strategic thinking, not just produce assets. Come with a point of view on your audience, your category, and what you want people to feel when they encounter your brand. Be willing to have that point of view challenged. The tension between what a client knows (domain, business) and what a designer sees (perception, pattern, form) is where the best work comes from.
If you haven’t done the strategy work yet, it may belong earlier in the process than you think, before design starts and not after it stalls. Explore our services to see how Strynal structures strategy and design as an integrated sequence.
How Strynal Approaches This
Every engagement at Strynal starts on a blank page. No templates, no recycled frameworks adapted to fit. That means the brief and discovery phase is genuinely important: we need to understand your problem well enough to design against it, not around it.
We work best with clients who are willing to engage in the process: share context openly, give clear feedback, and make decisions with appropriate speed. In return, we bring senior thinking to every stage, and the team that scopes the work is the team that builds it.
If you’re getting ready to start a design project and want to understand how we’d approach it, start a conversation with us; we’re straightforward about fit, scope, and what the process actually looks like.