# Why a campaign that worked was logged as a failure

[Home](https://theonlyaxelj.com/en) › [Study](https://theonlyaxelj.com/en/study) › [Articles](https://theonlyaxelj.com/en/study/articles)

author: [Axel Jedlitschka](https://theonlyaxelj.com/en/about)  
published: 2026-10-13  
updated: 2026-10-13  
language: en  
reading time: 5 min  
topic: Organization  
source booklet: [What Breaks When You Grow](https://theonlyaxelj.com/en/shop/introduction/growth-breaks)

A campaign that brought in more people than the business could take was logged as a failure, and what it lacked was a plan decided in advance for exactly that moment.

There are moments when something in a small business works better than expected, and that is exactly when it gets recorded as a failure. According to the booklet, the cause is a jump in pace that no process survives unless someone decided in advance what to do when it arrives. The source calls that decision a programme.

## A campaign that succeeded too well

The source tells a story, and the booklet calls it the most complete example in the whole source material. A small office in London ran a health campaign built on handing out leaflets, and people stormed into the office. Within about an hour a hundred and twenty-five of them had crowded in, and they all wanted to know everything.

The receptionist had not been briefed for a situation like that. She panicked, pushed everyone out through the front door into the street and shut the door. In the end only two of those people signed up for the major services, and the campaign was recorded as a failed crusade.

Stop on the word failed, because it hides what happened. The campaign itself succeeded completely, drawing a hundred and twenty-five people in a single hour. It went into the books as a failure because the side that had to take them in was not built for it.

The same thing happens in small businesses all the time. Suppose an owner whose campaign succeeded beyond expectations. He answered half the people who got in touch, and the rest told others about the experience. In his report it went down as a campaign that did not work.

Or a shop owner after a feature in the local paper. Thirty new customers came in on one day, and two of them came back.

Or an installer who appeared in a large neighbourhood group. Forty enquiries arrived, and he answered eight.

## From one a day to a hundred and twenty-five in an hour

The source gives the numerical comparison, and it is the point of the whole chapter. The office was used to one person a day, maybe three. Then, within an hour and a bit, a hundred and twenty-five walked in.

According to the booklet, no process survives a jump like that. Call it a **change of pace**: volume that multiplies tenfold or more within one day. That is what happens to a small business on the day something finally works.

Suppose a clinic owner used to three enquiries a day. Then a review went viral and thirty arrived, and she answered none of them for three days.

## You cannot prepare for every scenario

The source lifts the blame from the receptionist. She did behave badly, it says, but she went into a total panic: a small office, and a hundred and twenty-five people in front of her.

Then it adds a defence worth remembering: “you couldn't establish a receptionist for every possible contingency or emergency.”

That is an important admission. You cannot prepare an answer in advance for every scenario. What you can do, according to the booklet, is know that it will happen and decide in advance what to do when it does. You write that decision in a quiet time, when there is no pressure.

Suppose an owner who decided in advance that above a certain number of enquiries a day, everyone goes onto a declared waiting list. He made that decision while things were quiet.

And the case the other way round: the same clinic owner next time, with an automatic message telling every person when they will hear back. The volume is the same, and nobody walks away.

## A programme is the bridge

The source names what was missing in the London office: “Program is the bridge between the establishment and the production.”

In the same case it explains exactly what that means. The receptionist may have been established in her post, but nobody had programmed her for what to do with these people.

The distinction is very useful. **Establishment** is what already exists: a role, a person trained for it and a desk to work at. **Production** is the work itself. The connection between them is the **programme**, the decision about exactly what to do in this situation.

In a small business, according to the booklet, that is usually the missing part. There are good people and there is work, and there is no written decision about what happens when ten arrive instead of one.

Suppose an office with an excellent employee and not one rule for what comes first when three urgent things land together. Most of the time she chose well, and each wrong choice was costly.

Or a garage that decided in advance that a car off the road comes before one that is still driveable. It is a single line, and every argument about priorities disappeared.

This chapter of the booklet has two exercises, one on a tenfold jump and one on the bridge. The next chapter turns to the owner, and the moment he becomes the bottleneck himself.

The success of the London campaign was real. It was recorded as a failure only because nobody had decided in advance what to do on the day it arrived.

- [What Breaks When You Grow](https://theonlyaxelj.com/en/shop/introduction/growth-breaks): A name for the failure, a sequence that shows you where you stand in it, and one answer to the question of what comes first.

---

[עברית](https://theonlyaxelj.com/he/study/articles/when-success-overwhelms-the-front-door) · [Español](https://theonlyaxelj.com/es/study/articles/when-success-overwhelms-the-front-door)
