Ben Wightman

Before I tell you about myself, I'd like to know why that unusual campaign setting is there.

There may be a good reason. There may be a bad reason. There may be a note from somebody who already investigated the question we're about to spend an afternoon investigating again.

I'm Ben Wightman, a PPC specialist with a fairly patient approach to accounts and a fairly impatient approach to ceremonial busywork. Search Without Noise is where I keep the questions, recollections and occasional grumbles that come out of that combination.

I like an account with a history you can read. Not necessarily a tidy history. A useful one. A record of what changed, why somebody changed it, what happened and what they still weren't sure about.

That record can save the next person from assuming every strange decision was a mistake.

When I look at an established campaign, I start by understanding the offer and the business's working arrangements. The person receiving enquiries may explain a setting faster than an hour of staring at it. The change history may reveal a problem that has since disappeared. The page may tell us a service operates differently from the way the account suggests.

I would like to know those things before recommending a rebuild.

This is not an oath to preserve old accounts forever. Some do need substantial work. I just want the intervention to solve a described problem, rather than provide a dramatic entrance for the newest consultant.

A few small habits

I keep context beside unusual weeks. A promotion, a stock change or a holiday can make a report look exciting. It may also make the following ordinary week a poor comparison.

I save the relevant setup before a substantial change. Memory becomes surprisingly creative when someone asks you to put a setting back late on a Friday.

I name the review point. A test without one has a habit of becoming an established arrangement simply because everyone got used to seeing it.

I write uncertainty down. The absence of an answer is useful information if the next person can find it.

The notes don't need to become a second job. If maintaining the record takes longer than understanding the change, we may have made another little system too elaborate.

I enjoy the ordinary investigative work: reading a search phrase in context, following the destination, asking why a certain enquiry is unsuitable, checking what the business actually promised.

There is plenty of interest in a small account when you let the details speak. I don't need every observation to become a universal principle for the internet.

You'll find some scepticism here about best-practice language. A sensible convention can be helpful. Shouting its name at a working system doesn't explain which problem it solves.

I also think quiet periods can be respectable. If the account is doing a clear job, the page is accurate and the business can handle the work, a review doesn't need to create six new tasks to justify itself.

The writing will sometimes sound grumpy. That is partly a style preference and partly a consequence of knowing how easily avoidable confusion gets passed to the next person.

I want colleagues to inherit understandable decisions. I want customers to find an offer that fits the business's actual arrangement. I want the report to distinguish a useful observation from a flattering story.

And, when somebody suggests rebuilding everything before reading the notes, I reserve the right to put my tea down and ask one more bloody question.