The Illusion of the Ribbon-Cutting Ceremony
The photograph of a new launch captures almost everything we want to show: the facade, the team, the investor and the brand. What gets left out is the question that matters most when the doors unlock the following morning. Who resolves the problem that nobody yet knows is coming? If the answer always relies on the goodwill of one person at headquarters, the network has expanded across the map before growing its capacity to do the actual work.
Opening a new unit is an achievement. There is investment, hired talent and difficult decisions behind that doorway. The mistake begins when the opening itself is treated as proof that the model is ready to be replicated. A contract organises commitments. A signature does not install competence, it does not prepare a team and it does not deliver the stock that fell by the wayside.
The Weight of Vanity and Responsibility
I call vanity that distance between the size we announce and the responsibility we manage to shoulder. The word makes people uneasy, but that discomfort is useful. An expansion can be both ambitious and responsible. Yet it must withstand questions that spoil the party before the problems spoil the business.
Let us imagine a network preparing to launch multiple units. It is a hypothetical example. The commercial team guides candidates, presents the concept and locks in the timeline. Training already has calendar slots. Operational support, meanwhile, is handled by the exact same people who look after existing units. Everything looks organised until two openings need help on the exact same day.
At that point, the issue is not a lack of dedication. There might be staff working late, answering calls over the weekend and saving situations with remarkable skill. The problem is having sold a capacity that only exists while nothing fails simultaneously. The exception ceases to be an exception when every launch requires a small rescue mission.
Reading the Real Capacity to Grow
Before taking on a new opening, I would ask who remains available to look after the previous one. That question forces us to look at a queue far less glamorous than the line of candidates: unanswered requests, unfinished training, repeated corrections and decisions that only one person has the authority to approve. That is where we begin to perceive real expansion capacity.
This reading does not fit into a single metric. One unit might sell well while remaining entirely dependent on extraordinary support. Another might go through a phase of sluggish sales, yet already possess a team capable of identifying the issue and executing a correction. Lumping both situations together under the banner of success or failure produces hasty and unjust decisions.
I would separate launch monitoring, operational autonomy and economic evolution. During the launch, we need to know if the conditions to welcome customers are in place. In terms of autonomy, we must check whether the team can repeat the service and resolve routine issues. In the economic dimension, we evaluate whether observed results align with the hypotheses used to make the decision. None of these questions replaces the others.
Territory, Human Care and Hard Truths
There is an important asymmetry in expansion: headquarters knows the concept and controls the presentation; the candidate brings the money, the availability and the expectation of building something. If the conversation only permits enthusiasm, useful information goes unsaid. A difficulty treated as a commercial objection might be the very first sign of operational incompatibility.
Consider someone who intends to oversee the business from afar, while the proposal demands daily presence during the initial phase. The tension does not vanish simply because that person demonstrates financial capability. It is vital to clarify who will manage the daily operations, with what experience and with what availability. Pushing that answer past the moment of signing turns a known difference into a future conflict.
The same applies to territory. A strong location in one market does not prove that another market, with a different consumer routine, holds the same conditions. Operating hours, access, buying habits, availability of people and suppliers must all enter the analysis. The model gains strength when it knows how to explain what must remain identical and what requires local adaptation.
There is a vital human element here. The candidate must feel able to say they did not understand a calculation, that they disagree with a deadline or that they feel unprepared for a responsibility. If they fear losing the opportunity by asking, the brand secures a signature but loses critical information. I prefer a well-formulated doubt before a decision rather than a rehearsed certainty designed to please the room.
Headquarters also needs the freedom to refuse an ill-fitting match. Not every candidate with capital suits every model. Not every available patch of land should be occupied right now. Rejecting an opening can protect the network, the candidate and the people who would otherwise be hired for an operation built on incompatible expectations.
Milestones, Evidence and the Morning After
The best objection to this caution is well known: if we wait for a perfect model, we never get anywhere. I agree. No team foresees every problem. A new unit brings information that never exists inside a preparation meeting. The danger lies in confusing learning with an absence of minimum conditions.
A responsible venture makes explicit what is still unproven, who provides oversight and at what point the partners decide to continue, adjust or stop. It does not demand absolute certainty. It demands that the people involved know where the uncertainty lies. When a hypothesis is presented as a guaranteed result, the partner stops participating in conscious learning and starts carrying a surprise.
Therefore, I advocate for verification milestones tied directly to actual work. Before opening, test the supply chain and service execution with the team that will actually run the site. During the initial weeks, check whether training translates into behaviour, whether support requests reach decision-makers and whether difficulties receive proper responses. Later on, compare initial hypotheses with what actually happened, without cherry-picking convenient numbers.
The timelines for these milestones depend on the business. The essential thing is that there are responsible parties, observable evidence and consequences for the next decision. A meeting where everyone agrees things are going well adds little value if the exact same problems return the following week. Monitoring must allow for a change of plan, not merely confirm that monitoring took place.
We should also review how we recognise the hard work of the expansion team. If all the merit concentrates on the signature, the rest of the organisation inherits the task of sustaining promises it did not help build. It makes complete sense that implementation, training, support and subsequent performance all factor into the evaluation. The goal is to tie commercial achievement to responsibility for continuity.
That demands uncomfortable conversations within the network itself. Whoever announces that a unit is not yet prepared cannot be treated as an enemy of growth. They might simply be protecting the brand from a problem that haste rendered invisible. True leadership shows itself in how that information is received and what is done with it.
The map is necessary to think about the future. But every point on that map contains real people who unlock the door, serve customers, crunch the numbers and return the next day. Expansion truly earns that name when the organisation increases its capacity to provide them with the right conditions to work. The ceremony ends in an afternoon. The responsibility begins the morning after.