Back to Insights

    Your Second Location Audits Your First One

    Opening a second site does not break your process. It reveals whether you had one. What to write down in the week before you sign the lease.

    August 29, 20267 min read
    multi-location
    expansion
    process documentation
    operations
    workflow design
    smb growth

    The second location is supposed to be a copy of the first one. That is the plan on the spreadsheet, and it is why the first ninety days are harder than anyone budgets for. What actually happens is that the second site runs an audit on the first one, and the results arrive as customer complaints.

    Why is opening a second location harder than expected?

    Because the first location runs on proximity, and proximity is doing work that everyone credits to the process. Someone has a question, walks twelve feet, and gets an answer. That exchange happens dozens of times a day. Nobody counts it, because it does not feel like a system. It feels like working.

    Open forty miles away and every one of those exchanges has to become something else: a written rule, a form, a phone call, or a mistake.

    Does the process break when you expand?

    No. That framing is the reason the usual fix does not work. The process did not break, because at one site there was never a process in the sense the word implies. There was a group of experienced people within earshot of each other, and that arrangement was load-bearing.

    Distance removes the arrangement. Nothing else changed, which is why the failures feel random and personal rather than structural.

    What should you write down before opening a second site?

    The questions, not the answers. Spend one week at the existing location and write down every question that gets answered out loud. Who to call about a damaged shipment. What to do when a customer wants a change after the order is in. Which discount needs a signature.

    That list is how the company actually runs and it has never existed on paper. It is also, unlike a manual, something you can produce in a week without stopping the business.

    Why does writing a manual usually fail?

    Because a manual describes the work as leadership pictures it, and that version is the one that was already fine. It documents the well-lit path, not the ninety seconds of confusion that precede every exception.

    The other failure is timing. Manuals get written after the second site opens, which is the point at which the people who could write them are covering two locations.

    What are the three things that never travel?

    Across most multi-site openings, the same three things fail to make the trip:

    • The question that used to get answered by walking over to somebody's desk.
    • The exception your longest-tenured employee handles without mentioning it, often for years.
    • The rule everybody knows and nobody has written, which the new crew has no way of inferring.

    None of them are in a manual. All three are visible if you spend a week listening for questions instead of documenting procedures.

    Does this only apply to opening a location?

    No, and this is the useful part. The same gap opens whenever distance or time gets inserted into the operation. A second shift has it, because the night crew cannot walk over to anyone. A first remote hire has it. So does the week the owner is unreachable, which is why that week goes badly in a way nobody can quite explain afterward.

    If you are not opening a second site this year, you can still run the test. Have someone list every question they had to ask out loud during one normal week.

    What is the cheapest version of this?

    One week, one notebook, before the lease is signed. The list is cheapest to build while there is still only one place to build it from, and it gets much more expensive to reconstruct once half the answers live in a building you are not standing in.

    Then take the messiest item on that list and turn it into a written rule with a name attached to it. That is a single afternoon, and it removes an entire category of the first-ninety-days problem before it starts.

    Curious how we think about operations work?

    Our alignment framework shows where strategy, work, and systems drift apart — and how to close the gap.

    See the framework

    Related Insights

    Yes, There Is an API. Does It Carry the Numbers You Need?

    The software has an API. The numbers you want may not be in it. What to ask before anyone promises an integration, and what an honest scope looks like.

    Why Can't We Use the Feature the Demo Showed?

    The demo showed it working. Your account does not. The three forms the demo gap takes, and the checks to run before you plan anything on a system.