Why a branding studio started a newsletter

Thinking Cap, Issue #1 from Bluecap Studio

Every agency has a newsletter. You’ve seen them. A hero image, three portfolio pieces, a “we’re thrilled to announce,” and a subject line written by someone who was late for lunch.

We didn’t want to make another one of those. So for years, we just didn’t. Bluecap’s been heads-down on 2,000+ projects across 12+ industries, and somewhere in there we accumulated a warehouse of opinions, scar tissue, and stories that don’t fit in a case study. Case studies are the highlight reel. The interesting stuff, the near-misses, the lessons that cost real money, the argument about kerning that got weirdly personal, never makes the cut.

That felt like a waste. Hence: Thinking Cap. Every week, one or two stories from the studio floor, told the way we’d tell it to you over coffee. Here’s the first one.

The two identical files that weren’t

A while back, a client sent us two versions of the same printed announcement. Same layout, same copy, same everything, allegedly. Our job was to confirm they matched before one of them went to press.

Here’s the thing about “identical” files: they never are. If two versions of a document exist, something happened between version one and version two, and somebody’s forgotten what. So we don’t skim for differences. We hunt for them, line by line, element by element, the boring way.

We found four.

Three were the kind you’d expect. A word here, a spacing shift there. Annoying, fixable, the ordinary sediment of revision rounds.

The fourth was a QR code.

Two of them, actually, visually indistinguishable, same size, same position, same little pixelated squares, pointing to two different URLs. One went where the campaign was supposed to send people. The other went somewhere else entirely.

A QR code is the one element on a page that nobody actually proofreads. Your eye checks that it’s there, confirms it’s square-ish, and moves on. It’s a picture of a link, and pictures of links all look the same. Print it wrong and thousands of copies ship, every scan lands in the wrong place, and nobody notices until someone in the field holds up their phone and frowns.

In their industry, “the wrong URL” isn’t an oops. It’s a compliance conversation.

The takeaway you can steal

The lesson isn’t “proofread harder.” Everybody proofreads. The lesson is that proofreading is a design discipline, not a spelling check, and it has to cover the stuff that can’t be read, only scanned.

QR codes, embedded links, phone numbers, job codes, color values, barcodes: this is the invisible copy on your page. It carries meaning, it can be wrong, and your eye is useless against it. So we test it the only way that works; we scan every code, click every link, dial the number if we have to, on every version, every round, even when the file is “just a resupply” or “identical to the last one.”

Especially when it’s identical to the last one. That phrase is where mistakes go to hide.

If you take one thing from this issue: next time a file comes back from anyone; vendor, client, your own team with the words “same as before, just one small change,” treat it like a brand-new document. The small change is never alone. It brought friends.

What happens next

That’s the shape of this thing. A story, a lesson, no trend roundups, no “5 Things You Can’t Ignore.” We’ll be back next week.

Until then: the studio lives at bluecapstudio.com, the case studies are worth a scroll, and this inbox goes to actual humans. Hit reply, we read everything.

Dave & Deb
Bluecap Studio