Case Study: Building Stronger Systems for Small Business Growth
A Systems-Thinking Approach to Scaling Beyond a One-Person Bakery Operation
HIGHLIGHTS:
Challenge: Rapid growth exposed both financial strain and operational pressure. Revenue was down while labor, purchasing, training, menu complexity, and dependency on one person were increasing.
Response: Used ICAR principles to connect those issues, simplify processes, transfer knowledge, standardize repetitive work, and use data to better align time, labor, and spending with the value being created.
Result: Improved cost control, reduced dependence on one person, redirected labor away from low-return work, and gave the business a stronger foundation for making growth decisions with the resources already available.
CONTEXT:
This particular bakery business began as a one-person operation working from home, where most of the knowledge, decision-making, production, and quality control naturally lived with the owner. As demand grew, the business expanded into a storefront, added employees, and eventually introduced additional revenue streams through a café and catering operation within the same space.
That growth created more opportunity, but it also changed what the business needed behind the scenes. Once I gained visibility inside the business, I started to see how many parts of the operation were connected, from catering purchasing and food-prep standards to menu structure, labor, training, and revenue, and how pressure in one area could quickly show up somewhere else. The business had grown quickly, but many of the systems supporting that growth were still operating as if one person were carrying most of the work load.
CHALLENGE:
The first signs of strain were financial. Revenue was down, the owner felt like the business was not making enough money, and the natural response was to look for more ways to bring revenue in. More menu items, more offerings, and additional business ideas can feel like growth, but they also create more purchasing, prep, labor, inventory, and operational complexity behind the scenes.
For example, Once we started looking more closely at the numbers, it became clear that some of those growth ideas were creating very little return. One offering, for example, represented only about 0.1% of total revenue. Even under the most generous assumption that every dollar of that revenue were profit, the contribution was still too small to materially change the financial position of the business. Once ingredients, labor, waste, and overhead are considered, holding onto or expanding an offering like that can create more cost and workload than value.
That was an important signal. The problem was not simply, “How do we make more money?” It was also, “Where is the business already losing time, labor, inventory, and attention without enough return?” As the café and catering sides continued to grow, those questions became increasingly important because every additional product or service affected the rest of the operation.
The larger challenge became how to move from a business built around one person’s knowledge and constant hands-on involvement into an operation that multiple employees could support without simply adding more cost, more complexity, and more risk. Before adding more, the back-office structure needed to be strong enough to show which parts of the business were actually helping move it forward.
SOLUTION:
Starting with my core 'ICAR' principles, I treated the business as one connected operation rather than a series of separate problems.
Interconnectedness helped me see how front-end decisions around products and revenue were directly affecting back-kitchen labor, purchasing, training, and quality. That made it easier to spot where pressure in one area was creating unnecessary strain somewhere else. For example, adding more menu items increased prep and back-kitchen workload. Once the revenue data showed that those offerings were not creating enough return to justify the added effort, changing the menu structure became part of the solution. Instead of offering three or four items every day, the menu was simplified to one unique item per day. That allowed the workload to better match demand, while still giving customers variety without carrying the same level of cost, prep, and operational complexity.
Clarity became especially important around knowledge transfer. A large amount of operational knowledge still lived with one person, which created a bottleneck as more employees were added. To make that information easier to use and share, I helped create clearer training materials, more consistent recipe quality, and a recipe book employees could fall back on instead of relying only on a single person or observation or memory.
Alignment meant looking closely at where time, labor, and money were actually going. On the catering side, a significant amount of effort was tied up in manually recreating grocery lists for different event sizes. Building a calculator helped standardize that process, freeing up time for higher-value work while still keeping human judgment where it was needed. It also helped control grocery costs by keeping purchasing closer to what each event actually required and reducing unnecessary overbuying.
Menu structure became part of that same conversation. Creating more consistency in the menu could support quality control, purchasing, training, and labor at the same time, making it easier to match the amount of work and resources being used with the value the business was actually getting back.
Resilience was really the larger goal behind all of it: creating tools, information, and processes that could continue to support the business as it grew without depending so heavily on one person to hold everything together.
For example, I created catering training materials so anyone could step in and recreate the same quality of platter without needing one specific person there to explain every step. My rule of thumb was simple: if the person who normally does the work suddenly could not be there, would someone else have the resources they needed to do the job well?
That is what resilience means to me. Growth brings change, and changes in employees, demand, workload, or responsibilities should not automatically create a drop in quality or put the whole operation under strain. Building clearer tools and transferable knowledge helped create a stronger structure that could better absorb those changes over time.
*See examples of deliverables below
RESULTS:
The strongest results came from reducing three areas of exposure: unnecessary cost, wasted labor, and dependence on one person to keep the operation moving. What made those changes possible was applying the ICAR principles together.
Interconnectedness made it easier to see how purchasing, labor, training, menu decisions, and revenue were affecting one another instead of treating them as separate problems. Clarity turned informal knowledge and repeated judgment into tools and standards people could actually use. Alignment helped match time, labor, and spending more closely with the value being created. And resilience reduced how heavily the business depended on one person by making knowledge and processes easier to transfer.
Those principles led to practical changes: the catering calculator helped control grocery spending and reduce repetitive planning, training materials made quality standards easier to carry across employees, and revenue analysis led the owner to reduce labor dedicated to an offering that represented only about 0.1% of total revenue.
The result was not just a few better processes. The business had more clarity around where resources were going, better alignment between effort and value, less dependency on one person, and a stronger understanding of how one decision could affect the rest of the operation.
Just as important, the process gave the owner an opportunity to see how the business could work differently with the resources already available. Instead of assuming growth always meant adding more, it opened up new ways to strengthen the business through better use of time, labor, information, and existing processes while still keeping the work meaningful.
Pictured Above: Examples of Deliverables
Comments