HomeServicesPricingWorkFAQCareersHiringContact
ProcessMar 28, 2025 · 10 min read

What 600 client projects taught us about design

600-plus brands is enough volume to stop seeing individual projects and start seeing patterns. Here's what actually held up across all of them — the lessons that changed how we operate, not just the ones that sound good in a retrospective.

The brief is never actually the brief

Almost every project starts with a stated problem that isn't the real problem. "We need a better logo" is usually "we can't articulate what makes us different." "We need a redesign" is usually "our product outgrew a visual system built for a different stage of the company." Taking the stated brief at face value and executing it literally produces technically correct, strategically useless work.

The highest-leverage thing we do at the start of any engagement isn't design — it's figuring out what's actually being asked for underneath what's actually being said.

Fast clients and slow clients ship equally good work — for different reasons

We used to assume client speed predicted project quality. It doesn't. What predicts quality is decisiveness at the right moments: fast, clear decisions on strategic questions (positioning, priorities, what's in scope), paired with patience on execution (letting craft take the time it needs). Clients who are fast everywhere often rush craft decisions that needed more time. Clients who are slow everywhere stall strategic decisions that needed to be fast. The best clients are fast where speed doesn't cost quality, and patient where it does.

Every design system fails at the same point: month four

Design systems built to launch a v1 almost universally start fraying around month four — not because the initial system was wrong, but because nobody planned for the components that would need to exist for use cases that didn't exist yet at launch. The fix isn't building a bigger system upfront (that's over-engineering against a use case you can't predict yet). It's building the system with explicit extension points and a clear governance owner, so month-four additions extend the system instead of forking it.

Startups underestimate how much brand affects fundraising

We've watched two founders with comparable products and comparable traction get very different reception from the same investors, and brand clarity was a real, if unspoken, factor. A founder who can articulate a sharp, differentiated story in the first ninety seconds of a pitch reads as more in control of the business — even when the underlying metrics are similar. This isn't the primary driver of a raise. It's a real multiplier that founders systematically underrate.

The revision requests that matter are rarely about the thing being revised

When a client asks for a fourth round of logo tweaks, the real issue is almost never "the S-curve isn't quite right." It's usually an unresolved strategic question — about audience, positioning, or ambition — that's manifesting as visual indecision because it hasn't been named yet. We've learned to stop iterating on visuals past the second or third round without stepping back and asking what unresolved question the visual iteration is actually standing in for.

Good work and fast work are not in tension — but good work and rushed strategy are

We can execute fast. What we can't do — what nobody can do well — is skip the strategic groundwork (positioning, audience, what "done" means) and still land on strong creative output on the first try. Every project that felt "slow" in retrospect wasn't slow because of execution; it was slow because the strategic foundation was still being figured out live, mid-execution, instead of upfront.

What changed in how we operate because of this

We now spend more time up front — before any visual work starts — clarifying the actual problem, the actual audience, and the actual definition of success for a given engagement. It feels, in the moment, like it's costing time. Across 600-plus projects, it's the single change that most consistently prevented the expensive kind of rework: the kind that happens after a client has already seen and reacted to work built on a wrong assumption.

If you're evaluating a design partner, ask how they handle the gap between what's asked for and what's actually needed. That answer predicts the quality of everything downstream. See our work or book an intro call.