The Logo Brief Red Flags I've Learned to Spot

After a decade of logo and brand identity work, I've developed a set of pattern-recognition instincts about project briefs. Not pessimism — I go into every project intending to produce the best work possible. But certain signals in a brief reliably predict certain challenges, and recognizing them early allows me to address them before they become problems.

"I Need Something Timeless"

This phrase appears in almost every logo brief and means something different to every client. Usually it means "I don't want to update this often" which is a legitimate and achievable goal. Sometimes it means "I want something that looks like it has always existed" which is a more difficult ask and requires discussion about what "timeless" formally means.

The red flag is when "timeless" is paired with very specific trend-forward references: "I want something timeless, like this current trend I've seen." These goals are in tension. I address it by separating the durability goal (how long do you want this to serve the brand?) from the aesthetic reference (what do you like about those examples?) and working from the durability goal.

"I Want Something Simple Like Apple or Nike"

When a client points to Apple or Nike as examples of the logo they want, what they often mean is: "I want something minimal and recognizable." That's a useful direction. What they sometimes mean is: "I want a simple design that doesn't require much work." These are very different asks.

Simplicity in logo design is extremely demanding. The Apple logo and the Nike swoosh look simple because decades of design refinement and enormous brand investment have made them feel inevitable. A mark that achieves apparent simplicity through genuine formal rigor is harder to produce than a complex mark.

I align around the goal (a mark that's clean, distinctive, and flexible) while being honest about what achieving that requires in terms of design process.

"Can We See 10 Concepts?"

When a client asks for a large number of concepts upfront, it usually signals one of two things: they don't trust the design process and want to exercise maximum control, or they've been burned by a designer who showed one concept that didn't work.

Ten concepts isn't better than three — it's worse. It disperses the designer's effort across too many directions and gives the client too many options to compare, leading to mixing and matching elements across concepts. I explain my rationale for showing two or three well-developed directions and address the underlying concern directly.

"We Want to Look Like Specific Competitor"

This is a brief I decline or redirect. Designing toward a competitor's aesthetic is a legal risk (trademark) and a strategic failure (you want differentiation, not resemblance). I redirect by asking what the competitor's brand communicates and whether that's what they want to communicate — and usually the conversation moves to more productive territory.

No Clear Decision-Maker

If a brief arrives and I can't identify who has final approval authority, the project has a structural problem before it starts. I ask directly. "Who has final sign-off on the identity?" If the answer is "the committee" or "everyone on the team," I discuss how that process works and what it means for scope and timeline.

Projects without clear decision-making authority tend to produce work by consensus, which produces generic work. I'd rather address this in the brief than in the fifth round of revisions.