Back to the Journal

Unsexy work wins

Under every impressive thing sits a layer of work nobody photographs. File names, alt text, backups, the follow-up email. A defense of the grunt layer.

Nobody has ever put “renamed 400 files” in a portfolio.

And yet. Every project we’re proud of sits on top of a layer of work that would bore you to describe, and the longer we do this, the more convinced we get that the boring layer is the one deciding outcomes. The case study shows the homepage. It doesn’t show the redirect map that kept twelve years of links alive, or the image compression pass that’s the actual reason the thing feels fast.

Glamour is downstream of grunt work.

That’s the whole thesis, so here’s the supporting evidence, an incomplete inventory of the unphotogenic layer:

  • File names a stranger could navigate. Future-you is the stranger.
  • Alt text written like a person describing a picture to a friend, because that’s what it is, and because the people who need it can tell when you didn’t bother.
  • Backups that actually restore. An untested backup is a mood, not a system.
  • The follow-up email that turns “great meeting” into three decisions and an owner for each.
  • DNS records documented somewhere other than one person’s memory.
  • Changelogs. Short ones. Written the day of, not reconstructed under duress.

The trap

None of this is hard, and that’s precisely the trap. Hard work announces itself and gets scheduled, praised, staffed. Easy-but-tedious work gets deferred, because any individual piece of it can be skipped today without consequence, and the consequences only ever arrive in bulk, months later, wearing a different name. Missing alt text never breaks a launch. It just quietly tells a chunk of your audience the site wasn’t built with them in mind.

December, incidentally, is when the skipped layer sends its invoices. Year-end is one long audit of small deferred decisions: the password only one person knows and that person is on a beach, the “temporary” plugin from March, the asset library that’s really a downloads folder with ambitions. Nothing on that list took skill to prevent. Each item just needed somebody to do the dull thing back when the dull thing was cheap.

The tell in every craft

The pattern shows up everywhere once you start looking. The restaurant with the best food usually has the cleanest walk-in. Great photographers spend startling amounts of time managing batteries and cards. The developer whose demos never crash turns out to have dull, disciplined habits around version control. Musicians talk about tuning; carpenters talk about sharpening. In every craft we’ve been close enough to observe, the visible excellence sat on a base of maintenance nobody applauds, and the dull verbs were the tell.

Agencies are especially prone to getting this backwards, because our industry sells the visible ten percent. Nobody wins a pitch by promising immaculate file hygiene, so the grunt layer becomes something a team either believes in privately or doesn’t do at all, and you can’t tell which agency is which from the outside. From the inside, you can tell within a week.

Belief, in practice

Here’s what belief looks like in practice. The boring work gets scheduled like real work, on the calendar, with a name attached, and the calendar entry says something unglamorous like “redirects,” and nobody smirks, because everyone here remembers a launch that went sideways for the lack of one. It doesn’t wait for downtime, because downtime is a myth invented by whoever writes project plans. And when someone spends an afternoon on the redirect map or the backup drill, that’s treated as billable craft rather than admin, because it is.

There’s a failure mode on the other side worth naming, where the unsexy work becomes an identity and everyone competes to be the most burdened. Skip that. The point isn’t that tedium is noble. It’s that tedium is load-bearing, and load-bearing things deserve respect proportional to what they hold up, not to how they look holding it.

The next time something crosses your feed looking effortless, trust that it wasn’t. Somewhere behind it is a spreadsheet, a naming convention, and a person who tested the backups on a quiet Tuesday afternoon.

That’s the whole magic trick.