HIDE
We help female founders bring their
with
built around
with
built around
and
business —
and
with
business —
One of the very first things I want to know when a business owner tells me that she’s feeling overwhelmed by everything happening behind the scenes in her business is what she’s actually currently spending her time doing. Not because I’m looking for what we could immediately start to delegate or automate, but because it’s important to understand WHY those things are happening and WHY she’s currently feeling overwhelmed by them.
And you might be surprised how often that question leads us somewhere completely different than where we started or what she thought she needed.
I’ve seen businesses hire team members to manage processes that could have been simplified, invest in a new software to “solve” problems that weren’t actually a software issue, and spend hoursss attempting to build out automations for things that didn’t really need to be happening in the first place.
And trust me, I get it! When you’re running a business, there are a million things concurrently competing for your attention, so finding someone (or something) to take some of those things off of your plate seems like a pretty straight-forward solution.
But in my working in businesses and now working with business owners directly, I’ve learned something pretty important: before you figure out how to get something off of your plate, you need to figure out whether it belongs on anyone’s plate at all. Because sometimes the solution is automation or delegation, but sometimes it’s recognizing that a process you created years ago no longer makes sense for the business you are running today.
So before you hire someone, invest in another platform, or spend your entire day trying to figure out how to connect a bunch of things through Zapier, I want to walk you through how I think about recurring tasks and how to decide what actually needs to happen with them.
When you first start a business, you get REALLY good at figuring things out as you go. You manually send the emails, start a spreadsheet to track client info, build a process for onboarding new clients, and create little workarounds for all of the things you don’t have a formal system for…yet.
But your business today probably looks a lot different than it did when you originally made a lot of those decisions.
Maybe you started manually following up with every inquiry because you were only receiving a handful each month. Maybe you create a monthly (or quarterly) reporting process because you wanted to stay informed about what was happening in your business. Maybe you added an extra approval step after a project went sideways to “learn from your mistake” but now every single deliverable has to pass through you before it can move forward.
None of those things are inherently “wrong” or “bad.” They’ve served a purpose, and might have been exactly what your business needed at the stage you implemented them. But a process that worked well when you have five clients, no team, and a relatively simple business model isn’t necessarily going to make nearly as much sense now that you have twenty clients, a team/contractors, and several projects happening simultaneously.
When we continue operating our business based on the decisions that made sense for a previous version of our business but haven’t allowed our operations to evolve alongside our business, we can end up creating A LOT of unnecessary work for ourselved.
This is why I don’t typically start a business systems audit by asking what we can automate or delegate. I want to understand what the process is supposed to accomplish, how it currently works, where things have a tendency to get stuck, and whether everything you’re doing still serves the business you’re running today. I also want to know whether the founder needs or wants to be involved, or whether she’s remained responsible simply because nobody ever stopped to consider that there might be another way of doing things.
Once we understand all of those things, we’re able to make much more informed decisions about whether to automate, delegate, simplify, or eliminate the task altogether. And while all four approaches can help you streamline your business operations, the order in which you consider them can make a pretty significant difference.
I know. We’re diving right in here. Answering this question can sometimes feel a little uncomfy, especially if you’re someone who’s spent years building your business, refining your processes, and putting SO much thought into the way things are done.
Before I recommend making a recurring task more efficient, I want to know whether it needs to continue happening at all.
I think this is something that gets overlooked in a lot of conversations about productivity and business systems. We’re so quick to ask how something can get done faster, how we can take it off our plate, or how we can make it happen automatically that we sometimes forget to ask whether or not it’s actually worth doing in the first place.
You can make a process incredible efficient while still having it be a completely unnecessary use of your business’ resources. Maybe your team prepares a detailed monthly report that nobody actually reads. Maybe you’re still maintaining a spreadsheet that was created before you implemented your current CRM or project management software. Maybe you have a recurring meeting that originally served an important purpose, but now everything is simply resharing info that’s already available somewhere else.
Or maybe you’re still offering a service that requires an enormous amount of administrative work but no longer aligns with the direction you want to take your business.
In those situations, automating or delegating the task might save you some time, but it doesn’t address whether the task deserves to continue taking up space in your business at all.
One of my favorite questions to ask when evaluating a business process is: if we stopped dong this tomorrow, what would actually change?
Would your clients notice? Would your team be affected? Would you lose important information or create additional risk? Would it negatively impact your revenue, operations, or ability to deliver your services? Or would everyone continue going about their day without even realizing that something had changed?
If the task no longer contributes to a meaningful business outcome, duplicates work happening elsewhere, or supports a process that is no longer necessary, it might be a good candidate for elimination.
Of course, there are some things that need to happen regardless of whether or not they feel valuable in the moment. Legal, financial, regulatory, and other essential business requirements aren’t things we eliminate just because they feel tedious. But I think it’s worth questioning the things we’ve continued to do out of habit, especially when they’re taking up time and resources that could be better used elsewhere.
And if you’re unsure whether something is still essential, you don’t necessarily have to make a permanent decision right away. You could decide to pause it for thirty days, see what changes, and then make a more informed decision from there.
Sometimes a business owner will tell me that she needs help keeping up with something, and after we talk through it, we realize that she doesn’t actually want or need to keep doing it. She’s just been so focused on figuring out how to manage everything that she hasn’t stopped to consider whether some of those things could go away… and that’s a pretty important distinction to make before you invest in another tool or team member to help you manage them
This might be my favorite category because sometimes the solution is SO much more simpler than what we expect it to be.
I’ve worked with businesses where a single process involved multiple platforms, several handoffs, and a whole slew of workarounds. And the funny thing? Nobody thought that the process was complicated. It was “just how things were done,” and everyone had gotten so used to working around the parts that didn’t quite make sense that no one even questioned it anymore.
Maybe your team updates a project in Asana, sends a message letting everyone know it’s been updated, and then adds that same information to a spreadsheet so you can review it during your weekly meeting. Maybe you’re manually copying information from your SRM to a separate client racker because the original setup no longer gives you the visibility you need. Or maybe your onboarding process includes three different questionnaires because each one was created at a different stage of your business, and nobody every went back to consolidate them.
Individually, none of this looks like a big deal. But collectively, they create a lot of unnecessary work. The more moving pieces you have, the more opportunities there are for something to get missed, duplicated, or delayed. And when a process becomes unnecessarily complicated, adding another person or another tool isn’t always the answer. Sometimes we need to simplify the process itself.
When I’m evaluating an existing workflow, I pay attention to how many times the same information is being entered, how many people a task passes through, and how many different places someone has to look to understand what’s happening. I also want to know where people tend to get stuck — whether they’re waiting on approvals, constantly asking the same questions, or switching between multiple platforms to complete something that should be relatively straightforward.
Those are the kinds of things I pay attention to because they help me understand where we’re creating unnecessary work and what we might be able to do differently.
Let’s say you own a wellness practice, and every new patient has to complete an intake form, a health history questionnaire, and a separate consent form. Your administrative team manually reviews everything, transfers that information into your EHR, and follows up with patients who missed something.
Before hiring someone to manage that process or investing in additional automation, I’d want to look at how the information is being collected in the first place. Could the forms be consolidated where appropriate? Could required fields prevent incomplete submissions? Could information flow directly into your existing system? Are there questions you’re collecting that nobody actually uses or needs?
You might discover that the process doesn’t need more support; it needs fewer steps.
And while this may not sound nearly as exciting as implementing a sophisticated new system, I would much rather help someone create a simple process that works rather than an elaborate one that requires constant maintenance.
When simplifying a recurring task, the question I want you to ask yourself is whether or not you can accomplish the same outcome with fewer steps, fewer handoffs, or less unnecessary work without compromising the quality of what you’re delivering.
If the answer is yes, I’d generally recommend simplifying the process before investing in another solution.
Now, I love a good automation as much as the next ops girly — especially when it allows a business owner to create a more consistent client experience without having to personally manage every single little detail. But I also think we’ve reached a point where automation has become the default recommendation for just about everything…yet not everything needs to be automated.
In fact, one of the things I want to understand before automating a process is whether or not the process itself actually works. Because if a workflow is inconsistent, unnecessarily complicated, or constantly changing, automating it can make those problems harder to identify and correct. And sometimes, the time you spend building, troubleshooting, and maintaining an automation is significantly greater than the time you’d spend just doing the actual thing.
This is why I like to understand how a process works manually before I recommend potentially automating it. I want to know what triggers it, what needs to happen next, what information is required, and whether there are any circumstances that would change the way the task needs to be completed.
Once those things are clear, it’s much easier to identify which parts of the process could happen automatically and which parts still need human involvement.
Automation is particularly helpful when a task is predictable, repeatable, follows clear rules, and doesn’t require much human judgment. Things like sending appointment reminders, delivering onboarding questionnaires, creating recurring project tasks, or notifying a team member when a project moves into a new phase are all great examples of things that need to happen consistently but don’t necessarily require someone sitting down and manually making them happen every time.
Let’s say you’re a photographer who manually sends every client an email after their session, reminding them to schedule their ordering appointment. You open your email, find the template, personalize it, add the scheduling link, and hit send. It might only take five minutes, but if you’re doing that twenty times a month, you’ve just spent over an hour and a half on something that could have happened automatically — and that’s before accounting for the mental energy of remembering to do it in the first place.
By creating an automation that sends the email when a session is marked complete, you can ensure every client receives the information they need at the appropriate time without having to keep track of it yourself. That’s a GREAT use of an automation.
But what if your clients regularly need personalized follow-up based on what happened during their session? What if the next step changes depending on the type of service they received, or there are circumstances that require someone to review the information before moving forward?
You might still be able to automate portions of that process, but automating the entire thing could create more complications than it solves. And that’s the distinction that has to be made, especially for service-based businesses where relationships, personalization, and client experience are central to what makes the business successful. Automation doesn’t have to replace an entire process in order to be valuable. In fact, there are plenty of situations where automating the more predictable parts while still leaving room for human involvement is going to create a much better experience for everyone involved.
I never want to recommend an automation simply because we CAN automate something. I want to understand whether doing so actually improves the way the business operates and supports the experience the founder wants to create.
This is where I see a lot of business owners get stuck. They know they need help, and they’ve maybe even taken the step to hire someone to provide it. But they’re still the person responsible for remembering everythinggg — what needs to happen when, explaining how to do it, checking whether it gets done, and answering any and all questions that come up along the way.
It’s no wonder that delegation feels daunting when it ends up feeling like a full-time job in and of itself.
I think part of the problem is that we tend to talk about delegation as though handing someone a task automatically means we’ve taken it off our plate. But if you’re still the personal responsible for managing everything else pertaining to that task, you haven’t necessarily created that much more capacity for yourself.
This is what I pay attention to whether we’re delegating an actual responsibility or simple handing someone a list of tasks to complete.
Let’s say you own a creative agency, and every Monday morning, you spend an hour reviewing project timelines, checking in with your contractors/team, and making sure all of the upcoming deliverables are on track. You could delegate the individual tasks of updating Asana, sending reminders, and preparing status reports. But if you’re still the one noticing when something is falling behind, deciding what needs attention, and making sure everyone knows what to do next, you haven’t actually transferred much of the responsibility. You’re still managing the process…now you just have another person to manage along with it.
A more effective approach might be to give a project manager ownership of keeping projects moving forward, with clear expectations around when they should make decisions independently and when something needs to be escalated to you. Instead of managing every moving piece, you’re now able to stay informed and involved where your leadership is actually needed, while someone else takes responsibility for ensuring the day-to-day work continues moving forward.
I do want to be very clear on this though: that does NOT mean you need (or should) remove yourself from every part of your business. There are probably aspects of your client experience, creative process, or leadership that you genuinely want to be involved in — and that’s okay! The goal in delegating is to be intentional about where your involvement adds value, rather than remaining involved simply because nobody else knows how to do it.
This is something that I feel pretty strongly about — it’s actually one of the reasons I often recommend evaluating your existing business systems before expanding your team.
I’ve seen businesses bring in additional support when what they really needed was to address the systems and processes that were making the work difficult in the first place. And while hiring someone can absolutely create more capacity, adding another person to an unclear (or unnecessarily complicated) workflow can also create more questions, more handoffs, and more things for the founder to manage.
Before I recommend delegating something, I want to know whether the expected outcome is clear, whether there’s an established process for creating the work, and whether the person taking it on has access to the information and tools they need. I also want to understand what decisions they can make independently, when something needs to be escalated, and whether the founder actually has the capacity to onboard and support this person.
Because hiring someone and handing them a list of tasks isn’t going to create the kind of support you’re looking for. And if you’re still the person responsible for managing all of the details, you might find yourself wondering why you feel just as overwhelmed as you did before you hired help.
When I’m evaluating whether something should be delegated, I want to understand what it would look like for someone else to truly take ownership, not just complete the individual tasks. Because that’s where delegation starts to create shifts in capacity for you as a business owner.
Now I know what you might be thinking: what if a task could fit into more than one category? And that’s a great question because a lot of them will!
You might have a process that could be simplified, partially automated, and then delegated to someone on your team — or you might discover that a task you were planning to delegate could actually be eliminated altogether. That’s why I don’t recommend looking at these four options as entirely separate solutions. Instead, I like to think of them as a framework for making more intentional operating decisions, starting with whether the task needs to happen and then working towards what needs to be done, how it needs to happen, and who needs to be responsible for it.
The order matters because each decision changes what needs to happen next. If you eliminate an unnecessary task, there’s nothing left to automate or delegate. If you simplify a process, you might discover that you need significantly less support than you originally thought. And if you automate the predictable portions, you give your team more capacity to focus on the work that actually requires their judgment, expertise, and attention.
Of course, this isn’t a rigid formula, and automation and delegation often work together. Someone might own an entire process while automations handle several of the steps within it, or you might simplify a workflow and realize that the remaining work is something you actually enjoy doing yourself. The point is to make those decisions intentionally rather than automatically assuming that the next step is another platform, another person, or another process.
The best operational solution isn’t always the most sophisticated one. It’s the one that makes the most sense for you and your business.
I want you to think about one recurring task that’s been taking up more of your time or attention. (Not necessarily the biggest thing on your plate, but something like consistently frustrates you or causes you to think “there HAS to be a better way.“) Maybe it’s preparing for client meetings, managing project updates, following up on unpaid invoices, onboarding new clients, or keeping track of everything your team needs from you.
Whatever it is, I want you to take a few minutes to evaluate the process before jumping into finding a solution. Start by identifying what the task is actually meant to accomplish and where it still needs to happen. If it does, look at the steps involved and consider whether any of them could be removed, combined, or made more straightforward. From there, think about which parts could happen automatically and which parts require someone to be involved. And finally, consider whether or not that person absolutely has to be you.
Use this questions to work through one recurring responsibility in your business:
Now before you jump into implementing a solution, I want you to consider what that change might mean for the rest of your business. If you automate a process, does someone still need to monitor it? If you delegate something, does that person have the information and authority they need to take ownership? If you simplify a workflow, will it affect another process down the line? And if you eliminate a task, is there anything important that needs to be accounted for elsewhere?
These are the kinds of questions that help you create improvements that actually stick, rather than solving one problem only to create three more.
I also wouldn’t recommend trying to overhaul every recurring task in your business at once. Start with something that’s consistently creating friction, make an intentional improvement, and pay attention to the ripple effects. You might discover that one relatively small tweak created more capacity than you expected or that the process you were evaluating is connected to a much bigger operational issue.
And if you’re starting to notice that the same kinds of problems keep showing up across different areas of your business, it might be worth taking a look at your systems as a whole. (I walk through how to approach that in How to Audit Your Business Systems).
Here’s where I think this conversation gets really interesting. Sometimes when we start looking at one recurring task, we discover that the task itself isn’t actually the problem. Maybe your team keeps coming to you with questions because nobody has clear decision-making authority. Maybe you’re constantly following up on projects because there’s no consistent process for managing them. Maybe you’re spending hours on administrative work because your systems haven’t evolved alongside your business.
And sometimes, you’re doing allll of those things because your business has grown into something that required an entirely different level of operational support than it did when you first started.
That’s why I don’t believe in looking at your business systems in isolation. I want to understand where your business is today, where you want it to go, what it (and you) currently have the capacity to support, and what needs to change to make that next chapter possible.
Because the right solution for a founder who’s preparing to grow her agency from three contractors to ten might look very different from the right solution for a founder who has built a successful business but wants to work fewer hours and spend more time with her family. Both deserve systems and support that makes sense for the businesses they’re actually trying to build.
And sometimes, the most valuable thing we can do isn’t to immediately implement another system, hire another person, or take on another project. It’s to create enough clarity to understand what actually needs to happen next, what can wait, and what needs to change behind the scenes in order to make the founder’s vision executable.
Inside the Vision-to-Execution Accelerator, we take a comprehensive look at your business, identify what needs to change, and create a strategic roadmap for building the systems, structure, and support that your business actually needs. Whether you’re preparing for your next stage of growth or simply want to create a business that feels more sustainable to run, we’ll look at how everything works together so you can make infomred decisions about where you can best focus your time, energy, and resources.

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