Listen on Spotify // Listen on Apple podcasts
I was on the phone with a friend recently, and somehow we ended up talking about her gym membership.
I don’t even remember how we got there. But we were talking about the difference between buying a tool and actually having a system, and the gym turned out to be a pretty good example.
You can join a beautiful gym. You can have access to every machine, every class, and a locker room that makes you feel like you have your life together.
But the membership can’t decide what you’re training for. It can’t fit workouts into your actual schedule. And it definitely can’t tell you what to do when your knee is bothering you. Ask me how I know. I’d had two knee surgeries by the time I was 20.
I’ve done the business version of this, too.
I spent years hopping between tools. Asana. ClickUp. Evernote. I’d see what the next app could do and get convinced that the right one was somehow going to fix how the work felt.
Eventually, I committed to Notion. I learned it, built around the gaps, and stayed long enough to develop a way of working with it.
That doesn’t mean everyone should use Notion. It also doesn’t mean you should stay with a tool that genuinely doesn’t fit. But the experience taught me something I keep coming back to:
Buying access to a tool and having a system you can use are two different things.
The difference between a business tool and a business system
A business tool gives you a place to do something. A project management app can store tasks. A calendar can hold appointments. A CRM can hold contacts. Notion can connect a lot of information in one place.
All useful. I love a good tool.
But none of those things can answer these questions for you:
What are you trying to accomplish?
What happens next?
When are you actually going to come back to it?
That distinction matters because it’s easy to treat the purchase as the solution. Then Monday still feels like Monday, the follow-ups are still scattered, and you’re looking at yourself going, “Well, I bought the thing. Why can’t I make myself use it?”
Maybe there’s a part of the system that hasn’t been designed yet. Maybe the tool is an awful fit for the work. Either way, shame is a pretty useless troubleshooting method, even though it’s the one a lot of us reach for first.
The four pieces that make a system work
I resisted making this sound like a framework because the second I do, someone’s going to screenshot it and miss the whole damn point. Stay with me.
When I’m looking at a system, I look for four connected pieces: the tool, the process, the ritual, and the outcome.
The tool is where the work lives. It could be Notion, a notebook, an inbox, or a spreadsheet. The right choice depends on what you’re doing, who needs access, and whether the tool is affordable and usable for the people involved.
The process is what happens. How does information get into the tool? What do you do with it? What happens next, and who needs to know? A database full of contacts doesn’t tell you how an inquiry moves from a first message to an actual conversation.
The ritual is how you return to it. And no, I don’t mean a candle and a 45-minute routine. I mean the cue that makes it likely you’ll see the thing and use it. That might be checking a list after Monday planning or opening it when you sit down for follow-ups.
The outcome is the specific result you want. Can you see who’s waiting on a reply? Can you find the next step without searching through five apps? Can you make a decision with the information you’ve collected?
All four matter. You can have a beautiful list and no reason to open it. You can update that list religiously and still have no idea what to do next.
And trust me, I know how easy it is to spend hours building something that looks like work. I love building things. I have a whole personality about building things.
What this looks like with client follow-ups
Say someone reaches out through email, Instagram, or the form on your website. You have a lovely conversation, then you get busy.
Three weeks later, you remember that person was interested. But where did you talk? What did you say you’d send? Were you supposed to follow up, or were they?
You might decide you need a CRM. And maybe you do. But before you pull out the credit card, get specific about the problem.
In this example, the next step is scattered across multiple conversations with no reliable place to land. So let’s start there.
Pick one place to see your follow-ups. For each person, capture:
Their name
A way to find the original conversation
The next action
When you want to revisit it
Your tool could be a simple list. Your process is adding the next step after a meaningful inquiry. Your ritual is checking that list during time you’ve set aside for follow-ups. Your outcome is being able to see who needs a response without searching through five places.
That’s already a system. It doesn’t need 17 automations or a design award.
Use it for two weeks and pay attention. Did you remember to add things? Could you find the original conversations? Did you actually review the list, or did you schedule the review during a meeting that always runs long?
In my case, I’ll put a block of time on my calendar and then move it to wherever it’s more convenient. Time blocks and I are not friends. I honestly don’t know why I still try sometimes.
That’s useful information. The point of testing a system is to learn what happens when a real human uses it.
When is the tool actually the problem?
Let’s go back to the gym.
If it’s 40 minutes away, you hate being there, and the hours don’t work with your life, more discipline might not be the answer. Maybe you need a different gym. Maybe equipment at home or a walking routine fits better.
The same goes for business tools. A tool might be the wrong fit if it can’t support a necessary workflow, doesn’t work for your team, costs more than you can reasonably spend, or makes the work less accessible.
You’re allowed to leave.
I do believe there’s value in choosing something, learning it, and resisting the urge to hop every time a new app launches. But persistence and stubbornness are not the same thing.
The question I’d ask is: Am I leaving because this tool genuinely doesn’t fit, or because building a process around it got uncomfortable and someone else’s template looks easier?
No prize for either answer. We’re trying to get honest about the problem before buying another subscription.
Build your business systems for an actual Tuesday
A lot of us build for a fantasy version of the week. The version where we check every notification, have uninterrupted mornings, and apparently have a fun little romance with admin.
And then Tuesday arrives.
While recording this episode, I misread a client’s text about rescheduling a session and spent 45 minutes scrambling to find a time that worked for both of us. I was the one who screwed it up. That wasn’t on my ideal schedule for the day.
A system that only works when everything is perfectly caught up will be hard to trust on the days you need it most.
That’s why I want you to make the return point obvious. If you miss a review, where do you go to start again? Can you see the next action? Can you pick it back up without rebuilding the entire dashboard?
A system should help you come back. It shouldn’t turn a missed day or a client fire into a referendum on your character.
Try this one-system audit
Pick one thing you’re trying to manage. Follow-ups. Content ideas. Appointments. Invoices. The group chat you’ve meant to respond to since July.
One thing. Please don’t turn this into a full backend rebuild.
Ask yourself:
Where does it live? Identify the tool or place where the information belongs.
What moves it forward? Write down the next steps in the process.
When do I come back to it? Choose a cue you’re likely to notice and use.
What outcome do I want? Name the result you need the system to support.
If you can’t answer one of those questions, start experimenting there. If you have a tool but no process, write down the next two steps. If you have steps but never see them, find a better cue. If you keep updating a list but can’t make a decision, reconsider what information you actually need.
And if the tool itself is creating friction, take that seriously. Look at its cost, whether it connects to what you need, and whether the people using it can access it.
Your system should support the human doing the work
When I’m thinking about a system, I don’t start with the dashboard. I want to know what the thing is for and how a human being, on a real Tuesday, is supposed to use it.
A lovely dashboard can absolutely be part of the answer. But I’d rather have a slightly ugly list that helps you follow through than a gorgeous space that makes you feel bad every time you open it.
Your business deserves support that fits the human doing the work.
Want more conversations like this? Follow The Burnout-Proof Podcast.
