A boutique commercial photography studio spends three years earning one relationship. The founder, a photographer by training, personally scouts every room in a boutique hotel group’s flagship property, builds each shot list around what the listing actually needs to sell, and does the final color grading on every image before it goes anywhere near a booking site. The hotel’s occupancy improves. The marketing director notices, and mentions it to her counterparts across the group.
Then the call comes: the group wants to make the studio its exclusive photography partner across the entire portfolio, twelve properties, starting with three in the next six weeks.
The founder says yes before she’s finished the sentence in her head. Most people would. Driving home afterward, though, a quieter question arrives, one that has nothing to do with whether the opportunity is good. It’s whether the business, as it currently exists, can actually survive saying yes to it.
The Instinct to Answer With a Resourcing Plan
Ask most founders what would happen if demand for their business doubled, and the answer arrives fast: hire someone, extend the hours, rent more space, spend more on the tools already in use. It’s not an unreasonable first instinct. Growth does often require more of something.
The trouble is that this answer treats every kind of strain as the same kind of strain, as if a business under pressure simply needs more of itself, applied faster. It skips the actual question, which isn’t whether more resource would help. It’s what, specifically, would fail first if nothing else changed.
That distinction matters more than it sounds like it should, because the two answers point at completely different problems.
What the Question Is Actually Asking
*The Designed Business* frames this directly as one of two diagnostic tests worth running before chasing more demand: what breaks if demand doubles? The book is specific that “we’d need more people” doesn’t count as an answer, because it’s too vague to act on. The real question is which part fails first, and why. The founder’s calendar. The accuracy of a quote. How fast a new client actually gets started. The consistency of the finished work. Whether cash arrives in time to cover what delivery costs before the invoice clears.
Most businesses have never actually answered this with any precision, because until growth forces the question, there’s rarely a reason to sit with it. Revenue looks fine. Customers keep showing up. The strain, if it exists, stays private and manageable, the kind of thing a founder absorbs quietly rather than diagnoses. A sudden jump in demand removes that shelter fast. Whatever the business was quietly compensating for becomes visible to everyone, usually at the worst possible moment to discover it.
A Break About Capacity, and a Break About Design
Not every point of failure means the same thing, and collapsing them into one category is exactly what leads founders toward the wrong fix.
A capacity break is a genuine resourcing shortfall. There simply isn’t enough of something: hours, hands, inventory, equipment, working capital. The method for doing the work is sound. There just isn’t enough of it to go around at the new volume. More resource, applied to a capacity break, actually solves it.
A design break is different. It’s a point where the business has never actually decided how something should work once it’s not the founder personally handling it. No amount of additional resource fixes a design break, because the missing thing was never quantity. It was a decision, a standard, or a boundary that nobody has yet made explicit. Hiring a second person to make an undefined judgment call doesn’t remove the dependency on judgment. It just adds a second person waiting for permission.
Most founders run straight past this distinction because both kinds of break feel identical from the inside: too much to do, not enough time to do it. They only look different once you ask, specifically, what would actually happen first.
The Studio Runs the Numbers
Back to the photography studio, now facing three properties in six weeks instead of one property a year. The founder sits down and forces herself past “we’d need another shooter” to ask what would genuinely fail first.
The first candidate is her own calendar. Every property still needs her personally to scout it, because the shot list depends on judgment she’s never described to anyone else: which rooms actually drive bookings, which angles flatter a space that photographs poorly in person, when a property’s real selling point isn’t the room at all but the view or the light at a certain hour. That’s a design break. A second shooter with a camera doesn’t inherit an eye that’s never been taught.
The second candidate is final quality control. Every image currently passes through her personal color grading before a client sees it, and “good” has only ever lived in her own judgment, never written down as anything another editor could apply consistently. Also a design break.
The third is onboarding. Each new property needs its shot list built from scratch around what that specific property is trying to sell, and right now that process exists only as something she does, not something anyone else has been shown how to do. A third design break.
The fourth is cash flow. Three simultaneous shoots mean equipment hire, contractor day rates, and travel costs land well before the client’s invoice clears. That one actually is a capacity break: a real, quantifiable gap that more working capital, arranged in advance, would close.
Of the four points most likely to fail, three have nothing to do with how many people are on the roster. Hiring a second shooter, the obvious first move, would have addressed exactly one of the four, and not the one most likely to break first.
Where to Look Before Saying Yes
None of this means turning down the opportunity, and it isn’t an argument for over-preparing before every reasonable next step. Early growth almost always outruns perfect readiness, and that’s normal. The value of the question isn’t caution for its own sake. It’s finding out, before the pressure arrives, which parts of the business are genuinely ready to carry more weight and which parts have simply never been tested.
A useful way to run the exercise honestly: look at the last time volume actually rose, even briefly, a busy month, a seasonal spike, a single large client. Notice the first thing that felt like it was about to give way. That’s rarely random. It tends to be the same point every time, because it’s the same structural gap, not a new one each occasion.
What the Honest Answer Looks Like
A few questions worth answering specifically, not in general terms:
If the next surge of demand arrived this month, what is the first thing that would fail, not eventually, but within the first two weeks?
Is that failure point a shortage of resource, or a decision, standard, or judgment call that currently exists only in one person’s head?
If it’s the second kind, what would need to become explicit, a written standard, a decision rule, a documented method, before more resource would actually help rather than just multiply the confusion?
The specificity matters more than the answer. “We’d struggle” isn’t useful information. “The third property’s shot list would get built at midnight by someone guessing what I’d want” is.
The Answer Is Information, Not a Verdict
Running this diagnostic honestly doesn’t produce a pass or fail grade. It produces a map: which parts of the business would hold, and which one would give way first, and why. That’s worth knowing before the opportunity arrives, not while it’s already underway and there’s no room left to fix anything quietly.
The photography studio still said yes. It just said yes knowing precisely which three things needed to change before the first new property was shot, instead of finding out live, on the worst possible week to learn it.
Run the exercise on your own business before the next opportunity arrives: if demand doubled tomorrow, what would actually break first, and is that a shortage of resource or a decision nobody has made explicit yet? Reply and tell me what you found. The specific answer tends to be more useful than the general shape of the question.