A logo gets sized for the company it's made for. Somebody chose it and moved on to the next hire. Time passed, and the original file started running into a problem. The version saved for a five-person startup is still doing the job for a company running six departments. In my work that problem shows up most between 20 and 150 employees, and it arrives without anyone naming it.

Elk Antlers and the Growth Problem

Every spring a bull elk drops the old rack. A new one grows in, sized for the animal carrying it that year. Stretching last year's antlers was never on the menu. A five-person startup and a hundred-person company aren't the same animal. A logo built for the first won't fit the second. Widening the spacing or shrinking the file onto a new template changes nothing about that.

The company keeps growing. The file doesn't. Payroll adds people and the product line adds SKUs. The file that lived in one founder's folder now has to survive a hundred different hands. Most of those hands have no design background. They just need the logo to work. In Canva, on a shirt, on a booth backdrop, in a recruiting deck marketing has never seen.

The Files Are the Red Flag

It's easy to think this doesn't apply, because nobody's complained and the website still looks fine. Production is where the tell shows up. Can the file survive contact with every department that touches it, without someone rebuilding it from scratch first?

At 20 employees, one person can eyeball every file before it leaves the building. Small mistakes get caught before anyone outside sees them. At 150, marketing sees a fraction of what goes out with the logo on it. The deck a rep builds for a prospect, the recruiting slide HR pulls from a file three reorgs old. Every one of those is someone fixing the logo their own way, on their own time. Every fix adds one more version to the drift, and no one owns brand consistency at that point. The versions multiply until you stop looking like one company across every touchpoint.

The Four Operational Signs

It breaks at small sizes.
Shrink it down to a browser tab icon, an app icon, an embroidered polo, or a conference badge. If the mark turns into a smudge, the spec failed.

There's no usable dark background version.
Decks go dark, and event signage goes dark. If the fix on file is a white box someone in sales built around the logo, that's the tell.

The files are scattered across departments.
HR has one version in the recruiting deck. Sales pulled a different one off a two-year-old proposal. Ask five people for the correct file and count how many different answers you get. If the old logo keeps resurfacing, this tell has already gone external.

Nobody built it to be production ready.
A founder or an early hire made it fast, in whatever software happened to be open. It works fine as an idea. It shipped without a master file that redraws clean at any size, a locked spacing rule, a minimum size, or a spec sheet a print vendor could follow without guessing.

The Case This Builds With Leadership

All four tells are checkable, and taste never enters it. That's what makes them useful in the budget-and-buy-in room, where someone across the table asks why now. "I think we need a new logo" gets a shrug. "Four specific ways our current file fails in production, and where each one shows up" gets a different conversation. It also gets a different project. Naming a steward for the files is step one, whether or not a full system follows.

You don't need all four to make the case. One consistent, provable failure is often enough to start it.

Open your logo folder right now. How many versions are sitting in there, and could you say which one is correct without opening a single file to check?

Common Questions

What are the signs a business has outgrown its logo?

Four operational tells: smudging at small sizes, no usable dark-background version, conflicting files across departments, and a missing production spec. Each is checkable in about five minutes, and any one of them means people are already improvising versions.

Does outgrowing a logo mean the design is bad?

Often the design is fine and the file is the failure. A logo made for a five-person company ships without the sizes, variants, and specs a hundred-person company burns through weekly. The design question and the production question are separate, and the second one is checkable.

How do I check whether our logo still works?

Run the four-file test. Shrink the mark to a browser tab icon and a badge. Put it on a dark deck slide. Ask five people in different departments for the correct file. Then ask a print vendor whether the spec answers their questions without a phone call.

Do we need a rebrand, or just new logo files?

If customers still recognize you and every failure is a production failure, build a system around the existing mark. Name a steward for it. A rebrand enters the conversation when the company itself changed: new market, new offer, new size, or recognition already lost.