AI and contentBoth sides

Taste is the bottleneck now

When execution is free, the scarce skill is choosing. What taste actually is, why it's mostly not innate, and how to build it deliberately.

Adam Murray6 August 20269 min read
On this page

Generate fifty concepts in an afternoon and you'll discover something uncomfortable: having fifty options is worse than having five, unless you can tell which of the fifty is good.

Most of them will be competent. Several will be genuinely fine. Two or three will be right. And the skill that separates those (knowing which) didn't get cheaper when generation did.

That skill is taste, and it's now the constraint.

Taste isn't mystique

The word carries a lot of unhelpful baggage: innate, ineffable, you-have-it-or-you-don't. Almost none of that survives contact with people who demonstrably have it.

Taste is three things, and all three are learnable:

A model of who you're for. Not a demographic: an actual understanding of what a specific person already believes, what they're sceptical of, and what would move them. Most bad creative choices are a failure here rather than a failure of craft.

Enough reference to recognise the derivative. You can't tell that an idea is the fourth version of something if you've never seen the first three. This is why people with deep exposure to a field pick better within it: not innate sensibility, just a larger comparison set.

The willingness to reject something adequate. This is the hard one, and it's more temperament than skill. Adequate is comfortable. When you've generated fifty options, forty of them are adequate, and shipping one is frictionless.

Why AI made it the bottleneck

Two mechanisms, and the second is nastier.

Options went up. Choosing between five things a week is a background task. Choosing between fifty is a job.

The signals that used to help you choose stopped working. Historically, effort correlated with quality: a well-structured, cleanly-written, confidently-argued piece was probably made by someone who knew what they were doing, because producing it took skill. That correlation is broken. Generated work clears the competence bar every time.

So the surface cues you'd been using without noticing (is it polished, is it coherent, does it sound authoritative) have gone quiet. What's left is the actual question: is this right, for this audience, now? That question was always the real one. It was just previously masked by a correlation you could lean on.

Building it deliberately

Taste responds to deliberate practice more than people expect. Four things that work.

Study your own outliers, not the internet's

The most-shared industry examples are a badly biased sample: they got enormous distribution for reasons largely unrelated to their craft, and their style is at least as much a consequence of their scale as a cause of it.

Your own outliers are a far cleaner instrument. Same audience, same brand, same era. Something about that specific post was different. Finding out what is how you build a model of what your people respond to, rather than what the internet's people do.

And do the step everyone skips: check whether the pattern in your winners is absent from your losers. If it's present in both, you've found a habit, not a signal.

Build the comparison set on purpose

You can't recognise derivative work without a reference library. Spend deliberate time on the best work in adjacent fields: not to copy, to calibrate.

Adjacent matters. Studying only your own category teaches you your category's conventions, which is how everyone in a category ends up making the same thing.

Write the rejection down

When you kill an option, write one sentence saying why. "Too close to what X did." "Assumes they already believe the thing we're trying to prove." "Good idea, wrong quarter."

Do this for a few months and you'll have an explicit model of your own judgement, which you can then check, argue with, and hand to someone else. Most taste stays tacit and therefore unteachable and unauditable.

Make the criteria external

The best defence against being persuaded by an adequate option is having written down what you were looking for before you saw the options. That's what a creative brief is for, and it's why the brief matters more now: it's the fixed reference point that stops fifty plausible options from dragging you around.

The team version

Individual taste is one problem. Getting a team to choose well is a different and harder one.

Name a decider. A group of people with good taste and no decision rights produces an average, and averages are exactly what you're trying to avoid. This is why briefs name a final approver.

Separate generating from choosing. Different modes, different meetings, ideally different moments. A room that's generating gets enthusiastic; a room that's choosing needs to be able to say no. Doing both at once reliably produces the enthusiastic option.

Make the standard explicit. "Would we be embarrassed if this was the only thing someone saw of us this month?" is a real bar. "Do we like it?" is not.

What taste is not

It isn't preference. "I don't like it" is a legitimate reaction and it isn't taste. Taste is a judgement about whether something will work for someone who isn't you.

It isn't contrarianism. Rejecting the obvious option because it's obvious is not discernment. Sometimes the obvious thing is right.

It isn't a substitute for measurement. This matters. Taste tells you what to try; it does not tell you what worked. People with excellent judgement are wrong regularly, and the ones who stay good are the ones who measure honestly and update. Taste unchecked by evidence calcifies into style.

Where Acumin fits

The product is built for exactly this bottleneck. It doesn't generate your content. It's pointed at the choosing.

Outlier Studio and Content Analysis are instruments for building the model of your audience from your own results rather than from the internet's. A Concept Read gives an idea a confidence band before you shoot it: genuinely useful for killing options cheaply, which is most of what taste does in practice. And Experiments is the correction mechanism that stops judgement drifting away from reality.

The consistent design decision underneath: it will tell you when the evidence is thin rather than producing a confident-sounding recommendation. A tool that always has an opinion is a tool that will happily replace your judgement with a plausible one. When judgement is the scarce input, that's the opposite of helpful.

How to use this tomorrow

Next time you have a set of options, write down the criteria before you look at them.

Then, for the ones you reject, write one line each on why. Keep the file. In three months it's the most honest description of your own taste you'll own. It's also the first thing you can actually hand to someone else.


Related: What AI cannot tell you about your own content is the limit on delegating this. Outliers, not virality is the method for building the model.

Written by
Adam Murray
Founder, Acumin

Adam builds Acumin. He spends his days on the same two problems this library is about: working out what a piece of content is actually worth, and getting a brief through production without it turning into something else.

Want this done on your own channel?

Acumin reads your public content and your category and hands back what to make next. Every call comes with its confidence and the evidence it rests on. The first Snapshot is free.