HIDE
We help female founders bring their
with
built around
with
built around
and
business —
and
with
business —
I think one of the reasons business owners get so frustrated with trying to improve their operations is that we’re often trying to solve the problem we see without taking the time to understand what’s actually causing it.
Your projects are consistently running behind schedule, so you assume you need a better project management system. Your team keeps coming to you with questions, so you figure you need to document all of your SOPs. You’re overwhelmed by everything on your plate, so naturally, you start thinking about hiring someone to help.
Sometimes, those are exactly the solutions that would be most helpful. But I’ve also seen how easy it is to invest time, energy, and money into fixing something, only to discover that the original problem hasn’t really gone away.
Maybe your projects are still running behind because nobody knows who has final say in the approval process. Maybe your team has plenty of documentation but doesn’t feel like they have the authority to make decisions independently of you. Or maybe you’ve hired someone to manage a process that’s unnecessarily complicated to begin with, and now you’re paying another person to maintain it.
Which is why, before we start talking about what needs to change, we need to understand WHY something isn’t working that great in the first place. Because the thing slowing your business down isn’t always the thing that looks like the problem, and figuring out the difference can save you a whole lot of time and unnecessary work.
A business process bottleneck is a point in a workflow where work consistently gets delayed, backed up, or requires more time and attention than it should. Bottlenecks can happen in just about any area of your business — from client inquiries and onboarding to project management, internal communication, approvals, and day-to-day operations.
For example, maybe your team can prepare client deliverables on time, but everything sits waiting for your review before it can be sent. Or perhaps your onboarding process involves so many manual steps that every new client creates another lengthy to-do list. You might even have a project management system that everyone technically uses but important information still gets buried in Slack messages, emails, and conversations that never make it into the actual project.
Individually, these things might seem like relatively minor inconveniences. But when the same delays and workarounds happen across multiple clients, projects, and team members, they can have a pretty significant impact on how efficiently your business operates and how much of your mental capacity is required.
Your business doesn’t have to be falling apart for bottlenecks to exist.
You can have happy clients, a profitable business, a capable team, and systems that. technically work while still spending an enormous amount of time keeping everything moving behind the scenes. In fact, some of the most frustrating operational challenges are the ones you’ve gotten so used to managing that you barely recognize them as “problems” anymore.
(If that sounds familiar, I talked more about how to evaluate what you’re already using in How to Audit Your Business Systems (Without Overhauling Everything).)
One of the first things I want to understand when a founder tells me something in her business isn’t working is what she’s actually experiencing. What feels frustrating? Where is she spending more time than she wants to? What keeps getting delayed, forgotten, or brought back to her attention?
But I also want to understand what she believes is causing those frustrations because those aren’t necessarily the same thing.
Let’s say you own a creative agency and your team is constantly missing internal deadlines. You might assume that the problem is that people aren’t managing their time well or that your current project management system isn’t doing its job. So you start researching new platforms, creating more detailed task lists, and scheduling additional check-in meetings to make sure everyone stays on track.
But what if the team isn’t actually struggling to complete their work? What if they’re getting stuck because they need your sign-off before moving on to the next stage, and you’re so busy managing everything else that those approvals sit in your inbox for days?
Suddenly, we’re looking at a very different problem.
The issue might have very little to do with your software or with your team’s productivity. It could be that your approval process no longer makes sense for the size of your business, that your team doesn’t have clear decision-making authority, or that you’ve remained involved in decisions you no longer need to personally need to be part of.
And if we don’t identify the underlying issue, we could spend weeks rebuilding your project management system only to end up with the same exact bottleneck in a much prettier dashboard. That’s why I think understanding how work actually moves through your business is so important. We need to look beyond the frustration itself and figure out what’s happening that allows the same problem to keep occuring.
Before you open up Asana, start researching automations, or decide that your entire backend needs an overhaul, I’d encourage you to think about the things that consistently make running your business feel harder than it needs to.
When I’m working with a founder, I start with a questionnaire that helps me understand her business, the challenges she’s facing, and what she’s hoping to change. From there, we talk through her answers together because I want to understand the context behind them. Something that looks like a straightforward systems issue on paper can become a very different conversation once we start talking about how she works, what her team needs, and the experience she wants to create for her clients.
You can approach your own business in a similar way by paying attention to the things you repeatedly find yourself thinking, “There HAS to be a better way to do this.”
Maybe it’s the onboarding process that requires you to manually send six different emails. Maybe it’s the fact that your team comes to you with the same questions every week, even though you’ve already explained the process multiple times. Or maybe it’s a project that keeps getting pushed back because no one’s quite sure who’s responsible for moving it forward.
I wouldn’t worry about figuring out the solutions quite yet. Instead, make a note of what’s happening, how frequently it happens, who is involved, and what the consequences are when it doesn’t go smoothly. You might be surprised by how much you start noticing once you actually pay attention to the things you’ve been working around for years!
Once you’ve identified something that consistently creates friction, the next step is to understand how that process works. And I mean how it actually works because that might be different than how it’s technically supposed to work.
Let’s use client onboarding as an example. You probably have a general idea of what happens when someone completes their proposal, but have you ever sat down and walked through every step involved in getting that person completely onboarded?
Think about what happens immediately after they sign the contract or pay. Who received the notification? Who sends the welcome email? Where does their information go? Who creates the project, assigns the tasks, schedules the kickoff call, and makes sure everything is ready before work commences?
Then look at how those steps connect. Does someone have to wait for another person to complete something? Is information being added in multiple places? Are there decisions that only you can make? Are there steps that happen automatically, or are you still relying on yourself to remember when something needs to happen?
This is where the “little” things start to become more visible.
Maybe the process itself is perfectly fine but there’s no clear handoff between sales and delivery. Maybe you’re manually entering information that could be transferred automatically. Or perhaps the entire process is dependent upon you noticing that a contract has been signed and then remembering what happens next.
Each of those situations calls for an entirely different solution, which is why I wouldn’t recommend changing anything until you understand where the process is actually getting stuck.
One of the biggest operational bottlenecks I’ve noticed in established businesses is how much still depends on the founder. But trust me, I get it! You’ve spent years building this business. You know your clients, you know your standards, and you’ve probably developed a pretty good instinct for the things that need your attention.
The problem is that, as your business grows, all of that knowledge and decision-making can become increasingly difficult to manage on your own.
When you’re looking for recurring business process bottlenecks, I’d pay particular attention to how often work stops because someone (or something) is waiting on you. And then I’d ask whether your involvement is absolutely necessary.
Sometimes it is. There are strategic decisions, sensitive client situations, and creative choices where your experience and judgment are incredibly valuable. But there may also be dozens of decisions that your team could confidently make with a little more clarity about expectations, responsibilities, and what they’re empowered to handle independently.
There’s a pretty important distinction between delegating a task and giving someone complete ownership of it. If you’re still the person assigning every step, reviewing all of the details, and deciding what needs to happen next, you’re still carrying the weight of the responsibility.
(I explored this further in What to Systemize Before You Hire Your Next Team Member, including how to create the structure your team needs to take on more ownership.)
Now that you have a clearer understanding of where things are getting stuck, we can start digging into what’s behind the problem. This is the part I find especially interesting because there isn’t always one obvious answer, and I don’t think we should be assuming that every business needs the same solution.
For example, if your team is constantly coming to you with questions, I’d want to understand the kinds of questions they’re asking. Are they asking about completing a task because the process hasn’t been documented? Are they asking about responsibility because ownership isn’t clearly defined? Or are they asking for permission because they don’t feel comfortable making decisions without your approval?
Those might all look like the same problem from your perspective because you’re the person being interrupted, but they’re actually three different challenges
The first might benefit from clearer documentation or training. The second could require a conversation about roles and responsibilities. The third might mean taking a closer look at your leadership structure and whether you’ve unintentionally created an environment where everyone feels like they need to check with you before moving forward.
I’d also consider whether the problem is happening because the process itself has become more complicated than it needs to be. Because sometimes a workflow accumulates too many steps, tools, approvals, or workarounds over the years that nobody stops to question whether all of them are still necessary.
One helpful way to explore this is to keep asking why something happens until you reach an explanation you can address. If a project is delayed because a deliverable is waiting for approval, ask why that approval is required, why it has to come from a particular person, and whether that decision could happen differently without compromising the quality of the work. The goal is to understand what needs to change so that the same problem doesn’t keep happening.
Once you understand what’s causing a bottleneck, you can start deciding what to do about it. And this is where I think it’s really important to remember that the most efficient solution on paper isn’t necessarily the best solution for your business.
I want to know what the process needs to accomplish, how the people involved naturally work, what resources are available, and what kind of experience you’re trying to create for you, your team, and your clients.
If your onboarding process involves too many manual steps, automation might make a huge difference. If your team is waiting on you for decisions, clearer ownership and decision-making authority could be more valuable than another softwar platform. If your projects are getting stuck because information is scattered across multiple places, you might need to simplify how work is organized and communicated.
And yes, sometimes the answer really is to hire someone. If you’ve streamlined the process, clarified responsibilities, and eliminated unnecessary work but still have more to do than your current team can reasonably manage, additional support may be exactly what your business needs in this stage.
I just wouldn’t want you to make that investment before understanding what problem you’re asking this new person to solve.
One of the frameworks I like to use when evaluating recurring tasks is to consider whether they should be elimiated, simplified, automated, or delegated. Often, a process benefits from a combination of those approaches, and the order in which you consider than can make a pretty significant difference.
(You can read more about that decision-making process in Automate, Delegate, Simplify, or Eliminate? How to Decide What to Do With a Recurring Task.)
A great example of how this all comes together is the work I did with Ashley, the founder of Out of Office Social, a growing social media agency. When she first reached out, her business was doing well — she had happy clients, steady inquiries, and some exciting plans for the future, including hiring her first team member and increasing her pricing.
But as the agency grew, more and more of the day-to-day operations were depending on her to keep everything moving. She was manually following up with inquiries, managing client information across different places, and using Notion to organize parts of the business without having the project management structure she needed for the next stage of growth.
The important thing was understanding what those systems needed to accomplish before deciding which tools to implement. We looked at her client journey, how work was being managed, where Ashley was spending her time, and what another team member would eventually need in order to step into the business successfully.
From there, we implemented HoneyBook to manage the client relationship, including inquiries, proposal, contracts, invoicing, and onboarding, and Asana to manage the actual execution of client work. We also created repeatable workflows, clearer task ownership, and more visibility into what was happening across the agency.
The result was a business that relied less on Ashley remembering all of the details and next steps, and gave her a more consistent way to manage both the client experience and the work happening behind the scenes. She shared that after our work together, she was experiencing less stress, saving time, and feeling more confident in the systems supporting her business.
What I love about this example is that the work wasn’t simply about implementing new platforms. We chose those tools after understanding how the business operated, where it was creating unnecessary work, and what Ashley needed in orfer to support her plans for the future.
(You can read the full breakdown in Case Study: Building Better Business Systems for a Growing Social Media Agency.)
Now, we can’t talk about bottlenecks without talking about something that can be a little…uncomfortable. Especially when you’ve spent years building something that you’re incredibly proud of (as you should be!).
Sometimes we have to acknowledge that we are contributing to the very bottlenecks that we’re frustrated by,
And I say that with a whole lot of understanding because I know how personal running a business can be. You’ve put your time, money, creativity, and probably more than a few sleepless nights building something that matters to you. Of course you care about how things are done, how your clients are treated, and whether the work reflects the standards you’ve worked so hard to establish.
But there’s apoint where holding onto every decision, process, and responsibility can start limiting what your business is capable of doing.
Maybe you feel comfortable personally reviewing every client deliverable because it’s what you’ve always done. Maybe you haven’t fully delegated onboarding because you’re worried the experience will feel less personal or heartfelt. Or maybe you’ve had a hard time giving your team decision-making authority because you’re afraid things won’t be done exactly the way you would do them.
Those concerns are worth acknowledging, but they’re also worth examining.
What would your team need in order for you to feel comfortable handing over more responsibility? What standard or expectations could be communicated more clearly? Where could you create a process that allows someone else to deliver a great experience while still leaving room for their own judgment and personaility?
I also think we need to get away from the idea that creating systems and automations automatically makes a business more rigid or less human.
I’m a HUGE believer in creating thoughtful, personal client experiences, and I’ve learned that doing everything manually isn’t necessarily what makes an experience meaningful. Sometimes automating the administrative pieces gives you more time and attention for the conversations, relationships, and creative work that truly benefit from your involvement.
The same goes for your team! Giving people clear responsibilities and decision-making authority can help them feel more trusted, more capable, and more invested in the work they’re doing. And it gives you the opportunity to spend more of your time leading the business rather than managing every little thing happening within it.
Getting out of your own way can be uncomfortable, especially when your business has been your baby for so long. But I’d encourage you to consider whether the level of control you’ve gotten used to maintaining is actually supporting the business you want to run today.
Once you start paying attention to the things creating friction in your business, you might discover that there are quite a few areas you’d like to improve. And while I love a good operational improvement project, I would resist the urge to tackle everything at once. Instead, I’d start by considering which bottlenecks are having the biggest impact on your time, your team, your clients, and your ability to move the business foward.
Something that causes a five-minute interruption every single day might deserve more attention than a process that takes an extra hour every quarter. A recurring delay that affects multiple team members could be a higher priority than something that’s mildly inconvenient but doesn’t really affect anything else.
I’d also consider what becomes possible once the problem is addressed.
Maybe improving your onboarding process gives you the capacity to bring on more clients without adding more administrative work to your plate. Maybe clarifying your team’s responsibilities means you can finally spend your mornings focused on strategy instead of answering questions. Maybe improving the way projects move through your business creates enough room to pursue an idea you’ve been excited about for months.
That’s where I think the conversation becomes much more interesting! Because we’re no longer looking at business operations solely through the lens of efficiency. We’re looking at how the way your business runs influences what you actually have the time, enery, and capacity to do. And that should definitely be part of how you decide what deserves your attention first.
If there’s one thing I’d love for you to take away from this, it’s that the frustrations you’ve gotten used to managing don’t necessarily have to remain part of running your business.
You might have spent the last two years working around a process that technically works, answering the same questions, manually handling tasks that could happen more easily, or feeling like everything needs to pass through you before it can move forward.
And because you’re incredible capable, you’ve probably gotten pretty good at making it all work. But I wonder what running your business could feel like if you weren’t spending quite so much of your time and mental energy keeping those things moving.
Maybe you’d have more capacity to lead your team, spend more time with your family, explore a new opportunity, or simply finish your workday without a running list of things you still need to remember to do.
You don’t necessarily need a complete business haul to start making that happen either. Sometimes one thoughtfully designed (or redesigned) process, one clarified responsibility, or one system that finally works the way you need it to can making a huge impact in your day-to-day experience.
And if you’ve already identified a few bottlenecks that you’d love to address but haven’t had the time or capacity to actually do something about them, my Business Intensives give us dedicated time to work through those challenges and implement solutions that make sense for you and your business.
I’d also just love to hear what you’ve been working around and what you’d like to change! You can explore the ways to work together or get in touch here. You’ve already put SO much into building this business. You deserve to have the way it runs support you too!
A business process bottleneck is a point in a workflow where tasks, decisions, information, or approvals consistently get delayed, slowing down the rest of the process. Common examples include work waiting for founder approval, unclear team responsibilities, manual administrative tasks, and inefficient handoffs between people or systems.
Start by identifying recurring delays, interruptions, and frustrations. Then map how work actually moves through the process, including who is responsible for each step, where information lives, and what needs to happen before work can continue. Look for patterns and investigate why those delays keep occurring before deciding which changes to make.
Common causes include manual processes, unclear ownership, unnecessary approval steps, scattered information, inconsistent workflows, limited team capacity, and decisions that depend too heavily on the founder. Bottlenecks can also develop when a business grows but its systems and responsibilities haven’t evolved to support that growth.
Automation can help reduce bottlenecks caused by repetitive, predictable tasks, such as sending onboarding emails, transferring information, or creating recurring tasks. However, automation won’t necessarily solve problems caused by unclear responsibilities, unnecessary steps, or decision-making delays. It’s important to understand the root cause before automating a process.
Depending on the cause, you may be able to simplify a workflow, eliminate unnecessary steps, document a recurring process, clarify responsibilities, give team members more decision-making authority, or improve how information moves through your business. Hiring may still be appropriate when the actual issue is insufficient capacity, but it’s worth evaluating your existing operations first.

learn more about our services
We help female founders bring their
with
built around
with
built around
and
business —
and
business —