Hidden Business Complexity. Manage It to Make It Big.

A business is often destroyed by a second good product it should never have added. Count the connections before you add.

The question I asked a CEO

I have used this example with more than one person. With one CEO it stopped a mistake that would have complicated his business many times over. His sales and marketing head was in the room.

I asked them: you know McDonald's. It is a very successful business. In India there are many other favourite foods. Chole bhature. Dosa. Idli. Paratha. Pizza. Suppose McDonald's decides to sell chole bhature as well. Assume the quality will be good, maybe even better than most. Do you think they will succeed and make money?

The answer was yes. More profitable. It will work. Would you have done it, or at least considered it? Yes.

Then dosa? Idli, which is also a fast-food business? Paratha? Pizza? Will it not succeed if McDonald's decides to do those too? Will it not attract franchisees? Yes, to all of them.

That is when I asked them to leave the launch week and look at the back end.

What the launch week hides

Of course it will look like success at the start. A global brand adding chole bhature in India creates buzz. Customers come. Sales jump. Franchisees write in. The slides look brave.

Now picture the kitchen, and the company behind the kitchen. So many new ingredients. Because it is a global company, it cannot treat those ingredients casually. Quality and hygiene have to be assured at McDonald's standard, which means supplier development, audits, cold chain, recipes, training, waste rules, and complaint handling for a second cuisine.

Then picture the store. People eating burgers and people eating chole bhature in the same room. Different smells. Different plates. Different pace. Different peak times. Walk into a house known for one kind of food and you know exactly what that house is. Walk into a McDonald's that is also trying to be that house, and you no longer know what either business is.

Very soon the team will believe they are making money on the new line. Meanwhile the burger line, the actual cash cow, starts slipping. Staff attention, equipment time, counter time, and the manager's head move to the novelty. When the cow weakens, the new lines weaken with it. You do not get two businesses. You get one confused shop.

I do not have McDonald's manual on my desk. I am still sure of this: somewhere it is written, or enforced as if it were written, that a country manager is not free to invent a new kind of food. If that bar did not exist, somebody would have added it, and the company would have been taken down from the inside.

The business is simple. That is the point.

McDonald's is not wealthy because it has the best burger in every city — plenty of chains can argue they make a better one. Quality and hygiene are the entry ticket, not the reason it wins.

What McDonald's protects is a short list of items and enough counters that food arrives almost at once. That speed is possible only because the work stays simple. Double the menu and the difficulty does not double. It multiplies. More stock, more skills, more waiting, more errors, more cost. Higher prices or slower service — usually both.

So they keep it simple, and they work at keeping it simple. Introduce an item, take one out. That habit is what allows the speed, the price, a crew that can be trained fast, a franchisee who can still make a living after the fees, and a customer who does not have to think. Break the habit and the rest goes haywire.

Give the hidden load a number

Most leaders will agree, in a room, that simplicity is better. Very few live by it — not because they haven't heard the advice, but because of the wiring. People add. Processes add. A meeting that can create a new item will create one. Saying "keep it simple" changes almost nothing unless someone is actually willing to refuse the add. And most people cannot even agree on what complexity is. It stays a feeling. One person says the company has become complicated. Another says it is still focused. Neither can point to what last year's small add actually did to the work.

This is the problem my own practice, BCS — Business Complexity Simplifier — is built to solve. Count the interaction points in the business: every place where a person must act by hand, or where something can fail or go wrong. Map those points to one another, and the total is what I call the business's BCP — Business Complexity Points. BCS is the practice. BCP is the number it produces.

It will never be one official formula that fits every firm from a distance — businesses differ too much for that. A full, paid map of a single company can be counted in real detail. What anyone can do without that engagement is walk their own operation and list the points and the connections themselves. Two honest people inside the same firm will land near the same order of magnitude, and that alone is usually enough to see that adding "one" product is never really adding one. That is enough, on its own, to stop a launch. This applies to an ongoing company and just as much to a startup — arguably more, since a young company has far fewer people to absorb a jump in the score.

A McDonald's store, counted roughly

Take one small store. Four counters. Ten products. Thirteen ingredients. Ten pieces of hardware — a fryer, a microwave, a coffee machine, a cold-drink machine, and the rest. One supplier if a single firm sends everything, five or ten if it doesn't.

Now draw the connections. The till is a point: billing, cash change if it's a cash business. Special orders are a point. The counter talking to the kitchen is a point. Five suppliers talking to two employees is five times two. Every machine that can fail is a point. Every product that must be known to every person on shift is a set of points. Keep mapping, and you will land on a number that feels too large — for one small McDonald's store, it can already sit between two hundred and five hundred BCP. That's before the country, the distribution centre, and the head office even enter the picture.

Add one product, and the score does not rise by one. You add ingredients, you add what every person on a ten-person shift must now know, you add a supplier path, a quality path, a waste path, a complaint path. A store sitting at five hundred points can move to five hundred fifty or six hundred on a single item, in a single store.

Now picture a company with hundreds of products and tens of thousands of people. The score is no longer in the hundreds — it's in the hundreds of thousands. Add one product there and the jump is enormous. Remove one product, or one process, and the fall is just as large. That fall is the prize. That jump is the warning.

Before you add an employee role, a process, a product, a brand, or a channel: look at the BCP. If you cannot say how many new connections you are creating, you are not looking at an addition. You are looking at a fog.

A second picture, if a kitchen is too familiar

Imagine you are offered a fifty percent share in one of two businesses, for the same price. Both have the same revenue, the same profit, similar balance sheets.

The first has two products and a thousand customers. The second has five hundred products and ten thousand customers.

Which one do you buy? And the day after you buy it, what's the first thing you try to do to it?

The second looks like a bigger life. It is a heavier one — more suppliers, more exceptions, more training, more ways to miss a delivery, more arguments in every meeting. The first can still be improved. The second is already spending its management just holding the pieces together.

People already know this. They add anyway.

You've heard the old lines. If you can't explain it to a child, you don't understand it. Simplicity is a form of sophistication. The greatest ideas are usually the simplest. All true, and all easily agreed with in a room that will still approve the add the next morning.

Complexity is cheap to start and expensive to keep. Simplicity is costly to protect and valuable once protected. Complexity confuses the team. Simplicity opens the next decision. Complexity cripples a growing company. Simplicity is what lets it arrive.

Almost every leader will nod along to this in a meeting, then approve a product, a channel, a brand, and a "small exception" the very next morning. That is the wiring. Humans complicate what they touch. Processes do the same even when no single person intends it. Time does the rest. A leader's real job is to push the other way — cut connections, automate what can be automated, and design what remains so the score doesn't creep up on its own.

Why the adds keep winning the meeting

Ask any senior person what they achieved this year. Most will list an add: I launched, I opened, I introduced, I built a new range. Very few will say, I added this only because I removed that, and I can show you the new one is better than the old one on a clean comparison. Almost nobody says that, because almost nobody did the removal.

Ask a product manager or a marketing manager, honestly, whether they want to create a new brand. Of course they do — a new brand is a line on a CV. "I launched X" travels. "I refused Y and deleted Z so the first line could live" almost never makes the CV, even in the year it was the better decision.

Ask a plant manager what a good year looks like. More items through the same line often sounds like utilisation. It is also more changeovers, more settings, more ways to make the wrong thing well.

Ask a product designer. New variants are the work. Killing a variant feels like killing the work.

If every function is measured on adds, the score rises even while the CEO gives speeches about focus — because the company is doing exactly what it pays people to put on a CV. A startup is no safer. A founder's own story to investors is often just a list of launches, and that story has to be rewritten too: what we refused, what we killed, why the thing that remains can actually be delivered at once.

What a "profitable extra line" often is

I once joined a manufacturing company that looked, from the outside, like a focused plant. Ask most people how many finished items a firm like that might carry and they'll guess fifty, a hundred, two hundred if they want to sound extreme. This one had well over five thousand. It had also drifted into another line of business that nobody in the building treated as a real business. No dedicated team. Stock sat. Meetings didn't happen.

The sales team pointed out they still got orders for the long tail. Of course they did. An order is not a reason to keep a factory and a warehouse organised around five thousand names. We cut the list hard. In a short time the live range was under a third of what it had been. Orders for what we'd dropped still trickled in. The answer was simple: you can order it. You will not get it.

There was also an adjacent line people called profitable. Margin on a sold unit looked fine. The company was holding about two years of inventory against it. Profit on a sale that sits in a shed for two years is not profit — it is cash wearing a costume. We sold what we could and exited the line.

The plant also had a process that "could not be stopped." Restart waste, crack risk, hours of fuel to bring it down and back up. All true, and none of it a reason to run for a month making something that wasn't selling. If the fuel tap can be closed, the process can be closed. Spend a few hours of fuel shutting it down in a controlled way — that is cheaper than a month of output nobody wants. "We cannot stop" is very often a sentence protecting complexity, not production.

None of this depends on the industry. A software firm, a hospital, a trading company, and a two-person startup all grow tails, "profitable" sideshows, and processes that insist they cannot pause. Mapping the connections is what makes those tails visible before they start to feel like the company itself.

Where the load actually hides

It hides in the work most CEOs never put a rule around — the quiet accumulation of items, suppliers, sub-brands, side channels, one-off deals only a single salesperson understands, systems patched together because the last project never quite closed, and exceptions the founder still has to personally sign off. A startup whose founder is the exception machine is already complex, whatever the pitch deck shows.

What the score does to money

Revenue can rise when you add — that is why the trap works. Cost arrives later: training, waste, working capital, quality failures, slower service, discounts to fix the slower service.

Profit is what's left after that lag. Growth stalls once the cash cow gets neglected. For a startup the lag is deadly — there is no old, established brand funding the experiment. The new line runs on the same people who were supposed to be making the first line excellent.

A rule for Monday

Before you approve a new item, role, process, brand, or channel, write two lists. List A: what the customer will see in the first thirty days — buzz, samples, extra sales. List B: every new ingredient, supplier, skill, machine, station, complaint type, and weekly meeting the company must now run, forever.

Then look at what List B actually adds to the BCP, not the SKU count. If List B is longer than List A, you are not looking at a product. You are looking at a new company living inside the old one.

Then apply the swap: if we add this, what do we remove? If the honest answer is "nothing, we have spare capacity," check whether that spare is real or only a hope. Spare capacity in a startup is very often just the founder's sleep.

If you cannot name what will be removed, you are choosing a higher BCP. Say that sentence out loud in the meeting. The launch will sound a good deal less romantic.

Guard the score on purpose

Reduce complexity even when it costs a salesperson their favourite order. Guard against any rise, because every person in the company is wired to add, and every process is wired to grow extra steps on its own. Automate what can be automated. Redesign the rest so fewer people have to touch fewer things by hand.

"Focus on core strength" is this same rule in older words. Protect the conditions that make what you already do well continue to work well. Whatever would force a second kitchen, a second supply chain, a second training school — you don't add it just because a room said yes.

McDonald's core strength was never "food." It is a short menu, delivered at once, at a price the customer has already accepted. Chole bhature can be genuinely excellent food and still be an attack on that strength. A startup's strength is usually narrower still — one job done well enough that a stranger repeats the name.

See the addition. See the back end. See the cow. Count the connections. If McDonald's sold chole bhature, dosa, idli, paratha, and pizza because each one "would work," it would stop being McDonald's fairly quickly. A company that copies that appetite does not become McDonald's. It becomes the meeting where somebody finally has to ask you to stop.