WP002

The Dana Box

What an ordinary Tuesday reveals about why small businesses stay capped

Core Question: Why do capable, growing businesses often plateau at the exact size their owner can personally hold in their head, and what does it actually take to move past that?

LEARNING GOAL

Identify a system constraint and the queue it creates.

Look for
Work cannot continue until one person performs a specific judgment-based step.
Avoid assuming
More software, another employee, or generalized delegation automatically removes the bottleneck.
Apply it
Map one job end to end and circle the step that only one person can complete.

Explore This Paper

Different ways to understand the ideas in WP002.

FEATURED CASE

The Dana Box — Illustrated Pilot

5:54

A narrated six-minute case episode combining editorial illustration, restrained character movement, and the system constraint map.

Read transcript

WP002 — The Dana Box

Dana's phone vibrated just as everyone sat down. She knew the customer's name before she looked. A quote that should have gone out Wednesday was still unfinished on the office computer. Ten quiet minutes would finish it, but there were no quiet minutes at the table. Her husband asked, gently, whether she was going to answer. Dana said no, then picked up the phone just long enough to make sure it was not an emergency. The company was approaching two million dollars in annual revenue. Fourteen people worked there. Friends called Dana successful. The public version of growth looked like arrival. The private version looked like a phone on the dinner table.

This is The Dana Box, a story about the difference between being busy and being the place where work waits. Dana, her company, and the details in this story are composites. The operating pattern is common. The result is illustrative, not a promise.

At six forty the next morning, Dana unlocked the shop. A crew lead was sick. A customer wanted the missing quote. A supplier wanted an overdue payment. By seven fifteen she had rearranged the schedule twice. Renee from the office appeared with another pricing question. The quote spreadsheet on Dana's screen was color-coded, half-finished, and three tabs deep. The colors meant something, although Dana could not remember explaining them to anyone. This dependency had not begun as a mistake. Twelve years earlier, Dana was the company: one truck, a folding table, and one person who sold, priced, built, and invoiced the job. Growth placed people around that original design. It never fully replaced it.

Marcus arrived through a mutual connection. Dana expected a sales pitch. Instead, he asked to watch. He asked where a measurement went after someone took it, what a crew waited to receive, and who could approve a change if Dana was absent. Then he asked the question that opened the case. Which of these needed you specifically, and which only needed someone? Dana's first answer was that everything came through her. Her second answer was that only some things actually required her. That gap, between work that needs the owner and work that has merely learned to route through the owner, is where this story begins.

Dana thought the answer was better software: quoting and scheduling in one place, perhaps with another manager to run it. Marcus asked what the software would do. Dana said it would let someone else send quotes. He asked what that person would use to decide the price. The spreadsheet did not merely store prices. It held twelve years of Dana's judgment: crew speed, access, terrain, material risk, and customer expectations. Software could hold the fields. It could not supply judgment nobody had made visible. So Marcus mapped one normal job from inquiry to payment. Eight boxes. Dana touched every one. You may still need software, Marcus told her, but right now it would give the waiting a cleaner screen.

The most annoying box was scheduling. The limiting box was quoting. Crews could improvise for a few days. Renee could invoice. But no job could be approved, scheduled, installed, or billed until a price existed, and only Dana could make one. Folders, emails, spreadsheet highlights, and customer follow-ups looked like separate interruptions. The map showed a single queue in different clothing. This is a constraint: not everything that is difficult, and not necessarily the task that feels worst, but the step limiting the flow of the whole system.

Dana's reaction was not relief. Her judgment protected the company. She remembered underpriced jobs. She had trained people who left. Fourteen paychecks made just delegate sound reckless. Marcus did not tell her she was wrong. Those risks were the reasons the box still had her name in it. The answer was not blind trust. It was a bounded experiment: one job type, two weeks, Dana reviewing every early quote, and anything unusual returning to her.

They chose standard fence installs: no custom gates and no unusual terrain. Renee asked an important question. Was this responsibility being added to everything else? They freed two short blocks and stopped a low-value report. Otherwise, the queue would simply move from Dana to Renee. Dana talked through examples. They listened for repeated decisions and produced six provisional rules plus an exception line. Renee's first quote contained one mistake: an eight percent material markup instead of twelve. The source was an older example with an exception Dana had remembered but never explained. They corrected the quote and corrected the rule. The mistake did not show that Renee was incapable. It showed where their shared model was incomplete. Everything else was right.

Within two weeks, standard quotes were moving the same day instead of waiting three or four days. One customer replied, Wow, that was fast. We're in. One message is not proof. It was a signal. Dana remained essential for custom work and difficult properties. She was still necessary. She was no longer necessary everywhere. That Friday, her phone vibrated at dinner. She checked the name, decided it could wait, and put the phone face down. There was no overnight transformation. She still answered a message later. But she heard the middle of her daughter's story.

Once Dana saw the quote queue, she began seeing the rest of the company differently. Why did every small invoice need her signature? Which scheduling decisions required judgment, and which merely used her as the middleman? Six months later, Renee handled standard quotes and escalated exceptions. Crew leads maintained a shared board. Routine invoices under one thousand dollars no longer waited for Dana. Revenue later passed two point four million dollars, but the honest claim is not that six rules caused all that growth. The structural change was that every additional job no longer required an additional piece of Dana. The constraint moved. That is what constraints do.

Choose one normal job, not the disaster and not the unusual project. Follow it from request to finished work. Draw every step as a box. Mark who performs and who approves each one. Then ask: which box makes downstream work wait? Which box truly needs you, and which boxes have simply learned to wait for you? Find the box where work waits.

Download transcript
LISTEN

The Dana Box — Narrated Story

5:54

The complete prototype narration for the expanded Dana Box case.

Read transcript

WP002 — The Dana Box

Dana's phone vibrated just as everyone sat down. She knew the customer's name before she looked. A quote that should have gone out Wednesday was still unfinished on the office computer. Ten quiet minutes would finish it, but there were no quiet minutes at the table. Her husband asked, gently, whether she was going to answer. Dana said no, then picked up the phone just long enough to make sure it was not an emergency. The company was approaching two million dollars in annual revenue. Fourteen people worked there. Friends called Dana successful. The public version of growth looked like arrival. The private version looked like a phone on the dinner table.

This is The Dana Box, a story about the difference between being busy and being the place where work waits. Dana, her company, and the details in this story are composites. The operating pattern is common. The result is illustrative, not a promise.

At six forty the next morning, Dana unlocked the shop. A crew lead was sick. A customer wanted the missing quote. A supplier wanted an overdue payment. By seven fifteen she had rearranged the schedule twice. Renee from the office appeared with another pricing question. The quote spreadsheet on Dana's screen was color-coded, half-finished, and three tabs deep. The colors meant something, although Dana could not remember explaining them to anyone. This dependency had not begun as a mistake. Twelve years earlier, Dana was the company: one truck, a folding table, and one person who sold, priced, built, and invoiced the job. Growth placed people around that original design. It never fully replaced it.

Marcus arrived through a mutual connection. Dana expected a sales pitch. Instead, he asked to watch. He asked where a measurement went after someone took it, what a crew waited to receive, and who could approve a change if Dana was absent. Then he asked the question that opened the case. Which of these needed you specifically, and which only needed someone? Dana's first answer was that everything came through her. Her second answer was that only some things actually required her. That gap, between work that needs the owner and work that has merely learned to route through the owner, is where this story begins.

Dana thought the answer was better software: quoting and scheduling in one place, perhaps with another manager to run it. Marcus asked what the software would do. Dana said it would let someone else send quotes. He asked what that person would use to decide the price. The spreadsheet did not merely store prices. It held twelve years of Dana's judgment: crew speed, access, terrain, material risk, and customer expectations. Software could hold the fields. It could not supply judgment nobody had made visible. So Marcus mapped one normal job from inquiry to payment. Eight boxes. Dana touched every one. You may still need software, Marcus told her, but right now it would give the waiting a cleaner screen.

The most annoying box was scheduling. The limiting box was quoting. Crews could improvise for a few days. Renee could invoice. But no job could be approved, scheduled, installed, or billed until a price existed, and only Dana could make one. Folders, emails, spreadsheet highlights, and customer follow-ups looked like separate interruptions. The map showed a single queue in different clothing. This is a constraint: not everything that is difficult, and not necessarily the task that feels worst, but the step limiting the flow of the whole system.

Dana's reaction was not relief. Her judgment protected the company. She remembered underpriced jobs. She had trained people who left. Fourteen paychecks made just delegate sound reckless. Marcus did not tell her she was wrong. Those risks were the reasons the box still had her name in it. The answer was not blind trust. It was a bounded experiment: one job type, two weeks, Dana reviewing every early quote, and anything unusual returning to her.

They chose standard fence installs: no custom gates and no unusual terrain. Renee asked an important question. Was this responsibility being added to everything else? They freed two short blocks and stopped a low-value report. Otherwise, the queue would simply move from Dana to Renee. Dana talked through examples. They listened for repeated decisions and produced six provisional rules plus an exception line. Renee's first quote contained one mistake: an eight percent material markup instead of twelve. The source was an older example with an exception Dana had remembered but never explained. They corrected the quote and corrected the rule. The mistake did not show that Renee was incapable. It showed where their shared model was incomplete. Everything else was right.

Within two weeks, standard quotes were moving the same day instead of waiting three or four days. One customer replied, Wow, that was fast. We're in. One message is not proof. It was a signal. Dana remained essential for custom work and difficult properties. She was still necessary. She was no longer necessary everywhere. That Friday, her phone vibrated at dinner. She checked the name, decided it could wait, and put the phone face down. There was no overnight transformation. She still answered a message later. But she heard the middle of her daughter's story.

Once Dana saw the quote queue, she began seeing the rest of the company differently. Why did every small invoice need her signature? Which scheduling decisions required judgment, and which merely used her as the middleman? Six months later, Renee handled standard quotes and escalated exceptions. Crew leads maintained a shared board. Routine invoices under one thousand dollars no longer waited for Dana. Revenue later passed two point four million dollars, but the honest claim is not that six rules caused all that growth. The structural change was that every additional job no longer required an additional piece of Dana. The constraint moved. That is what constraints do.

Choose one normal job, not the disaster and not the unusual project. Follow it from request to finished work. Draw every step as a box. Mark who performs and who approves each one. Then ask: which box makes downstream work wait? Which box truly needs you, and which boxes have simply learned to wait for you? Find the box where work waits.

Download transcript
WATCH

Concise Video Overview

1:20

The original short visual overview of the Dana Box pattern.

EXPLAIN

Explorer Explainer

1:33

The original concise explainer built from WP002 and its system map.

Visual Overview

The operating chain and the point where work waits.

EIGHT STEPS. ONE BOX ONLY DANA CAN FILL. Customer calls Takes down the details Builds the quote ONLY DANA CAN DO THIS Sends the quote Customer approves Schedules the crew Job runs Invoices, chases payment Five of the eight boxes could survive without her. One could not.

Key Ideas

  • Identify a system constraint and the queue it creates.
  • The constraint is rarely where the owner is looking. It hides inside the step that “only I can do.”
  • Primary signal: Work Waits for One Person.
  • Pattern: owner dependent knowledge.

▣   Field Exercise

Pick one normal job, start to finish, and draw the chain. Mark who touches each step. Circle the one box only you can fill.

Core Question

If you got hit by a bus tomorrow, which single step in your business would stop everything cold?

READ ONLINEThe Dana BoxOpen full paper +

Why This Matters

Most small business owners assume growth is capped by demand, capital, or hiring. Often it is not. It’s capped by one, or just a few, undocumented steps: usually judgment-based, usually invisible, and something only the owner can perform. This paper follows a composite owner, built from patterns observed across dozens of conversations, through the process of finding that step.

Dana, her business, and the specific details below are a composite, not a real company. The pattern is real.


I. The Symptom

Dana unlocked the shop at 6:40 a.m., same as always, coffee in one hand, phone already buzzing in the other.

Message one: a crew lead calling in sick. Second one this month. Message two: a customer asking why their quote from Tuesday still hadn’t shown up. Message three: the supplier, reminding her that last month’s invoice was overdue.

She had built this business from a single truck and a folding table twelve years ago. Now it was fourteen employees, a warehouse, and on most days, a sense that she was the only thing holding it together.

By 7:15, she had already rearranged today’s job schedule twice, texted three different guys to see who could cover the sick crew lead, and still hadn’t looked at the late quote her customer was asking about. That quote was sitting in a spreadsheet on her desktop, the one only she really understood, because it was color-coded, half-finished, and three tabs deep.

Revenue was good. Better than good, actually: it hit just under $2M last year, up from $1.6M the year before. On paper, Dana was doing everything right.

So why did every morning feel like triage?

She used to think it was a busy season problem. Then a busy quarter problem. Now, if she was being honest, it just felt like how the business operated.

“I need better software,” she told her husband over dinner one night. “Or another manager. Or both.”

Neither felt quite right. They tried a scheduling app two years ago, but it lasted six weeks before everyone quietly went back to using group texts. She didn’t have room in the budget for another manager, and even if she did, she wasn’t exactly sure what she would actually be hiring them to fix.

She just knew that somewhere between the truck-and-folding-table days and now, the business had gotten bigger than any one person could hold in their head, and nobody had told her what to do about that part.

II. The Outside Observer

Like most businesses, Marcus found Dana’s through a mutual connection who said, “you should talk to her, she’s got a lot going on.”

He wasn’t a contractor and didn’t know the trade, but he reached out the next day anyway. He’d learned a long time ago that knowing the specifics of an industry was rarely really the issue.

Dana agreed to fifteen minutes, mostly to be polite.

He showed up at 7 a.m., which surprised her. No polo shirt with a logo. No slide deck under his arm. Just a notebook in a worn leather case and a pen.

“I’m not here to sell you anything,” he said, before she could ask. “I just like understanding how different businesses actually work. Would you mind if I walk around a bit and ask some questions?”

She gave him the tour out of habit. She started with the warehouse, the trucks getting loaded, the whiteboard in the office where next week’s jobs were scrawled in three different colors of marker. He didn’t take notes on any of that. What he wrote down was smaller, stranger things.

He asked how a job went from “customer calls” to “invoice paid,” wanting every step. He asked who touched it at each stage. He asked what happened when someone was out sick, and who covered for whom, and whether that was written down anywhere or just… known.

“Walk me through what happened this morning when you got here,” he said.

So she told him about the sick crew lead, the reshuffled schedule, the quote still sitting unsent, the overdue invoice from the supplier. She expected him to nod along and start pitching an app.

Instead he asked: “How many of those four things needed you specifically, versus needed someone?”

She started to answer, then stopped.

“All four went through me,” she said slowly. “But only… two of them actually needed to.”

He didn’t say anything else about it. Just wrote something down, thanked her for her time, and asked if he could come back next week and see how the quote situation played out.

She said yes, mostly out of curiosity about what he had written.

Recognition Checkpoint

Before Marcus returns, stop with the evidence already available. Quotes wait in Dana’s spreadsheet. Scheduling changes route through her. The office can complete several administrative steps, but work cannot begin without a price.

What appears to be the symptom, and which single step might be limiting the whole system?

Keep your answer in mind. The next sections test it against the work itself.

III. The Wrong Diagnosis

Marcus came back the following week, notebook and pen in hand.

Dana had already decided what she wanted to tell him. She was thinking about it all week.

“I know what the problem is,” she said, before he even set his coffee down. “I need better software. Something that actually handles scheduling and quoting in one place, so it’s not all stuck in my head or in my spreadsheet.”

Marcus nodded slowly, like he was actually considering it. “Maybe. What would the software do, exactly?”

“Take the scheduling off my plate. Let someone else send quotes without waiting on me.”

“Okay. And who’s ‘someone else’?”

Dana paused. “I don’t know yet. I’d need to hire for that.”

“So the plan is: buy software, then hire a person to use it.”

”…Right.”

“You tried that two years ago,” he said. Not as a gotcha, just a fact he’d written down on the last visit. “The scheduling app. What happened?”

She sighed. “Everyone went back to texting within six weeks. It wasn’t the app’s fault, really. It just didn’t fit how we actually work.”

“That’s what I want to understand,” Marcus said. “Not whether you need software, but whether we know what’s actually broken yet.”

He flipped to a blank page and drew a line across it.

“Walk me through one job, start to finish. Not the exception, just a totally normal one. Customer calls Monday. What happens Tuesday? Wednesday?”

Dana started talking, and he wrote as she went: not bullet points, but a chain, each step connected to the next with an arrow. Customer calls, she takes the details, she builds the quote in her spreadsheet, she sends it (when she has time), customer approves, she schedules the crew (often by texting three people to see who’s free), job runs, she invoices, she chases payment if it’s late.

Eight steps. Every single one ran through her.

Marcus looked at the chain for a long moment.

“You don’t have a software problem,” he said. “You have a Dana problem. The software would just be a faster way to make you the bottleneck.”

She opened her mouth to argue, then looked at the eight arrows on the page, all pointing back to the same box.

She closed it again.

IV. The Real Constraint

Marcus tapped the paper. “Eight steps. All through you. But if we’re being precise, which one is actually the bottleneck?”

Dana stared at the chain. “All of them, kind of.”

“Maybe. But not equally. Let’s test it. If you got hit by a bus tomorrow, bad example, sorry, which of these eight steps stops the business cold?”

She thought about it for real this time.

“Crew scheduling, my guys could figure out between themselves for a few days. They know the jobs. Invoicing is annoying, but Renee in the office could learn it in an afternoon. Chasing payments, same thing.”

“So five of the eight could survive without you. What about the other three?”

Dana’s finger landed on one box: she builds the quote in her spreadsheet.

“This one. Nobody else can do this one.”

“Why not?”

“Because the pricing isn’t really written down anywhere. It’s in my head. Labor hours per job type, what we can push on materials, which customers negotiate and which don’t, what we quietly build in for the jobs that always run long. I know all of it. Nobody else does.”

Marcus circled that single box on the page.

“This is it,” he said. “Not the scheduling. Not the software. This one step is the actual constraint on your whole business. Every other step is downstream of it: nothing gets scheduled, run, or invoiced until a quote exists, and only one person on earth can make a quote exist.”

Dana looked at the circle for a long time.

“So even if I hired someone tomorrow,” she said slowly, “for scheduling, for invoicing, none of it matters, because they’d still be waiting on me for the quote.”

“Right. You’ve been trying to fix the five easy boxes. The business has been quietly waiting on you to fix the one hard one.”

She sat back. It wasn’t the answer she expected. Not a system to buy, not a person to hire. Just one box, with her name effectively written inside it, that nothing else could move past.

“I don’t even know how I’d write that down,” she admitted. “Half of it isn’t rules. It’s just… judgment. Years of judgment.”

Marcus closed his notebook. “That’s the real question, then. Not ‘what software do you need.’ It’s: can that judgment ever leave your head, and if so, how?”

V. The Resistance

Dana didn’t sleep well that night.

By the next morning, the clarity from the day before had curdled into something closer to defensiveness. When Marcus called to check in, she found herself talking faster than she meant to.

“I’ve thought about it, and honestly, I don’t think that’s really the problem,” she said. “The quoting works. It’s fast, because it’s in my head. If I had to write all that judgment down, it’d take me weeks. Months, maybe. I don’t have that kind of time.”

“Fair,” Marcus said. “What else?”

“And even if I did write it down, what happens when someone underprices a job because they didn’t understand the nuance? That’s real money. That’s my name on the invoice.”

“Also fair.”

“And who would I even hand it to? Renee’s got enough on her plate. I’d have to hire someone, train them for months, and there’s no guarantee they’d get it right, or that they’d even stay. I’ve had people leave after I invested all that time.”

Marcus let the silence sit for a second. “Dana, can I say something, and you tell me if it lands wrong?”

She braced. “Go ahead.”

“Every reason you just gave me is true. And every one of them is also the reason this hasn’t changed in twelve years.”

She didn’t say anything.

“You’re not wrong that it’s risky to hand off,” he continued. “You’re not wrong that it took years to build that judgment. But right now, the entire business, fourteen people, $2M a year, is capped by how many hours are in your day. Not your revenue. Not your demand. Just your hours.”

“So what, I just hand it over and hope for the best?”

“No. I’m not saying blow it up tomorrow. I’m saying, what if we didn’t try to solve all of it at once? What if we just tested whether any piece of that judgment could live outside your head, on one type of job, for two weeks?”

Dana rubbed her eyes. Part of her wanted to end the call right there and go back to the version of this where she was just busy, not stuck. That version was uncomfortable, but it was familiar. This new version asked her to admit that the thing making her business run was also the thing keeping it from growing past her.

“Fine,” she said finally. “One job type. Two weeks. But I’m watching every quote that goes out.”

“Deal,” Marcus said. “That’s exactly how it should start.”

VI. The Small Experiment

They picked the simplest job type to start: standard fence installs, no unusual terrain, no custom gates. Dana ran maybe six of these a month, routine enough to have a pattern, but not so high-stakes that a mistake would be a disaster.

Marcus didn’t ask her to write a manual. “Just talk,” he said. “I’ll write it down.”

So for two hours one afternoon, Dana talked through every fence quote she could remember, not the exceptions, just the normal ones. How many labor hours per hundred feet, depending on the crew. What she padded in for older properties where they usually hit something in the ground. Which materials she marked up more, and which she kept tight because customers price-checked those. How she adjusted, without quite realizing she did it, for customers who’d been referred by someone versus strangers off the website.

Marcus turned it into six rules. Not perfect, not covering every case, but just enough to handle the standard version of the job.

Renee took the six rules and, the next time a fence inquiry came in, built the quote herself. Then she showed it to Dana before it went out.

Dana read it over, tense, waiting to find the thing Renee had gotten wrong.

She found only one thing, a materials line that should’ve been marked up 12%, not 8%. Small, fixable, five minutes to correct.

Everything else was right.

Not “close enough.” Right.

By the second week, Renee was sending fence quotes same-day instead of them sitting in Dana’s spreadsheet for three or four days waiting on a free hour. One customer, who’d emailed twice the previous month asking where their quote was, texted back within the hour: “Wow, that was fast. We’re in.”

It was one job type. Six rules. Two weeks. It hadn’t touched the custom jobs, the tricky properties, the judgment calls that still lived only in Dana’s head.

But for the first time in longer than she could remember, a quote had gone out the door without her.

VII. The Shift

Three weeks after the fence experiment started, Dana caught herself doing something strange: standing in the warehouse, watching a crew load a truck, and instead of thinking about the ten things she needed to do that hour, she was thinking about the invoicing process.

Not because anything was wrong with it. Because she was starting to notice it the way Marcus had noticed the quoting: as a chain of steps, with a question underneath it: how much of this actually needs to be me?

Renee was still just handling fence quotes. Everything else, the custom jobs, the tricky properties, the negotiated pricing, still ran through Dana. But something had cracked open that she couldn’t quite close back up. Dana had spent twelve years thinking of the business as a hundred different fires that happened to need her personally. Now she kept seeing it as a series of chains, most of them with her name jammed into a box that didn’t actually require her.

She started asking her own questions, unprompted. Why did every invoice route through her for approval, even the routine ones under $500? Why did she personally text crew leads about scheduling instead of crew leads just knowing the week’s plan in advance? Half the “urgent” texts she got weren’t urgent, they were just undocumented.

When Marcus checked in that week, she got to the point before he did.

“I want to do the same thing with scheduling,” she said. “Not the software. The judgment part, like we did with quoting. What actually needs deciding versus what’s just… me, being the middleman.”

Marcus smiled, but didn’t say told you so. “What do you think would happen if we mapped it the same way?”

“Honestly? I think I’d find three more boxes with my name in them that don’t need to be there.”

It wasn’t fixed. Fourteen employees, a full board of jobs, a business still capped in places by hours in her day. But for the first time, Dana wasn’t looking for a piece of software to save her.

She was looking for the next box.

VIII. The Pattern Named

Six months later, Dana’s business looked mostly the same from the outside. Same warehouse. Same fourteen trucks, then sixteen. Same 6:40 a.m. unlocks.

But the eight-step chain from that first week didn’t look the same anymore. Quoting on standard jobs ran through Renee, with Dana reviewing exceptions only. Scheduling ran on a shared board the crew leads updated themselves, with Dana stepping in maybe twice a month instead of daily. Invoicing under $1,000 didn’t need her signature at all.

Her name was still in a few boxes: custom jobs, difficult properties, the handful of long-standing customers who wanted to talk to her. But it wasn’t in all of them anymore. And the business had grown past $2.4M that year, not because she worked more hours, but because for the first time, growth didn’t require more of her.

Marcus asked her, near the end of their last conversation, what would she tell another owner in her position.

She thought about it longer than he expected.

“I’d tell them the problem is never really what it looks like,” she said. “It looked like I needed software. It looked like I needed to hire someone. What I actually needed was to find the one box with my name jammed into it that didn’t belong there, and I couldn’t see it myself. I was too close.”


The Pattern

That’s the pattern, more than any single fix: the constraint is rarely where the owner is looking. It hides inside the step that “only I can do,” and that step is almost never written down, which is exactly why it’s never questioned.

Observe. Watch the work as it actually happens, not as it’s described. Listen. Let the owner talk through a normal day, not the highlight reel. Understand. Map the chain: every step, every hand it passes through. Find the pattern. One box usually explains more than the other seven combined. Improve. Test the smallest possible change against it before reaching for a system.

Every business has a Dana box. Most owners have never drawn the chain that would show them where it is.

If you think yours might have one, let’s take a look.


The Explorer Method

Observe  →  Listen  →  Map  →  Find Patterns  →  Experiment

Learn the Method