Introduction
Growth has a way of exposing the cracks in a business. What worked when five people sat in the same room can quickly become a bottleneck at twenty-five. Emily Falk, founder of EF Operations, helps growing companies align their people, systems, and technology so they can scale without losing what makes them unique. In this interview, she shares the signs that your operations have fallen behind, how to approach technology choices, and why structure doesn't have to kill culture.
Build Your Ops Blueprint
This is for general guidance only, not professional consulting advice.
Meet our featured expert from EF Operations. Complete this quick quiz to get a personalized operations roadmap.
Question 1: What signs indicate a growing business has outgrown its current operations setup?
Emily sees a clear pattern when a business outgrows its operations. "Usually, the first sign is that people are working harder just to keep the business functioning." The owner becomes the answer to every question, employees build their own workarounds, and the same issues keep resurfacing because no one has time to fix the root cause.
She also points to burnout among top performers. "The highest performers are working extremely long hours, suffering from burnout, and feel like they can never truly take time off." For Emily, the real question is whether the business has grown faster than the way it operates. If so, it's time to examine the structure underneath—process and accountability.
Question 2: How do you approach choosing the right technology stack for a scaling company?
Emily's approach is refreshingly practical: "I don't start with the technology. I start with the business." She first understands how the team actually works, where time is lost, and what information needs to move between people. Only then does she look at tools.
With the explosion of AI tooling, she sees both opportunity and risk. "There are incredible opportunities for businesses to use AI to improve efficiency, reduce repetitive work, and give employees more time to focus on higher-value work." But she cautions that a new tool layered onto a broken process rarely helps. "The technology is only one part of the equation. Whether it is AI, an off-the-shelf platform, or a custom application, the underlying process still has to make sense." She also notes that custom internal tools are becoming more accessible, but "I don't believe in forcing one solution just because it is newer or more exciting." The best results come when process and technology evolve together.
Question 3: What is the most common operations mistake you see in companies going from 10 to 50 employees?
Emily's answer is direct: "Trying to run a 50-person company the same way you ran a 10-person company." In a small business, informality works—everyone knows who to ask, and problems get solved in quick conversations. But as the business grows, that breaks down.
"If you don't intentionally create structure, the founder becomes a bottleneck, employees start filling in the blanks differently, and important knowledge stays with individual people instead of becoming part of the company." She's not advocating for bureaucracy. "Defining processes and people's roles does not mean the death of informality. It simply means clarity has become necessary for efficiency." The goal is to ensure growth doesn't depend on everyone remembering everything.
Question 4: How do you balance standardizing processes with keeping a company's unique culture intact?
This is a topic Emily cares deeply about. "I don't believe a growing company must sacrifice its personality to become more organized. I think good operations help protect the things that made the company successful in the first place."
The key is understanding why something is done a certain way. "If it is different because it reflects the company's values, the way they care for customers, or something meaningful about their culture, I want to understand and preserve that." But if it's different simply because no one has ever decided how it should work, that's a different problem. "Structure should remove unnecessary confusion. It should not remove humanity from the business." Her role is not to impose a template but to help build a version of the company that works better.
Question 5: What does a typical operations alignment engagement look like from start to finish?
Emily is clear that there's no one-size-fits-all model. "Business is personal, and every relationship starts with a conversation." She begins by understanding the company, its people, and where leadership feels things are no longer working. Then they decide together on the level of involvement—from near full-time to a few weeks of intensive assessment followed by periodic check-ins.
During the initial work, she looks across the whole business: people, responsibilities, workflows, technology, documentation, vendors, and financial processes. But she also spends a lot of time observing. "Being in the background and seeing how a company functions naturally is fundamental to understanding its operations." She emphasizes that she's not there to tear things apart. "There is usually a reason a business operates the way it does, and I want to understand that before anything changes." Ultimately, her goal is to leave the company stronger and more self-sufficient. "If I have done my job well, they should not need me forever."
Key Takeaways for Founders and Operators
- Watch for the warning signs: If your best people are burning out and the owner is the bottleneck, your operations haven't kept pace with growth.
- Start with the work, not the tools: Understand how your team actually operates before choosing technology. A new tool won't fix a broken process.
- Create clarity without bureaucracy: Define roles, decision-making, and where information lives. This doesn't kill informality—it makes growth sustainable.
- Preserve what makes you unique: Standardize the how but protect the why. Understand the difference between a process that reflects your values and one that exists only by default.
- Engage flexibly: Operations alignment isn't a rigid consulting model. It should adapt to your company's needs and change over time.
For more insights on process design and improvement, check out this guide on business process design and best practices for process development.