Many years ago, before I worked in business systems, I worked as a personal trainer after completing an undergraduate degree in recreation administration.
What I learned back then tells a similar story to my work now. In personal training, clients who succeed are not the ones who overhaul everything at once. The ones who achieve their goals set realistic and achievable goals, make incremental changes, and stay honest about where they are starting from.
I designed programs around each person, recognizing their season of life, their obstacles, what would build long term success and their readiness for change at that point in time. Cookie-cutter programs wouldn’t work. They never do, and not because people aren’t capable, but because the program wasn’t built for the unique individual and circumstances.
Business systems work the same way.
Every Established Business Already Has Systems In Place
An original system in a start-up, if not evaluated and intentionally updated, takes on a life of its own over time. It has adapted based on how a team communicates, how work gets tracked, and how decisions get made. It wasn’t chosen to look like it does now. It formed alongside the work, one workaround at a time, and now it’s “just how things get done around here”.
What happens when you want to update or design a new system?
When a new system gets introduced without accounting for any of those established habits, the team and founder will, in time, default back to what’s familiar if the system is not the right fit. It is one of the most common small business workflow problems I see in established businesses.
Before anything gets built or redesigned, those habits need to be visible. That’s what this blog article is about.
4 Key Habits Already in Motion
Every established business is already running on workflow habits, from how information moves, how work gets tracked, and how decisions get made. Before any new system is designed, these need to be seen.
A system built without accounting for habits will be working against the grain from day one.
Below are the four most common habit patterns I see, and what to look for in each one before you build anything new.
1. People-Dependent vs. System-Dependent
The habit: key knowledge resides with specific people, not in any documented process. This is one of the most persistent people-dependent business problems in established teams.
Have a favorite assistant who has been with you for years? A project manager who leads your team with ease? More often, it is the business owner who has all the information in their head, and it isn’t written down.
What it looks like in practice: the person who knows how something works is the system; when they’re on vacation, become ill or leave employment, things stall or stop.
Why it persists: asking a person is faster than building a process; in an established business, this unconsciously happens more and more over the years without anyone noticing.
What to look for before you build a system: map where knowledge actually lives, specifically who holds it, whether it’s documented anywhere, and what happens when that person isn’t available.
In effect: systems can be trained, updated, and don’t miss work; people can’t make that promise. Documenting your work systems and processes is critical for consistent and measurable workflow.
2. Email as Project Management
The habit: the inbox functions as the task list, decision log, and follow-up system. It is a habit that starts early and is a very common small business workflow problem.
What it looks like in practice: email threads become the record; searching email is how people find what was agreed; new team members have no way to access the information in an organized way. Need to reference decisions previously made with no system? That is trouble in the making and a lot of time wasted.
Why it persists: email is already open, already familiar, already where communication happens; it requires no new behaviour or learning curve. Easy short-term, with long-term consequences.
What to look for before you build a system: identify where decisions and tasks actually live right now; if the answer is “in email,” any new system needs to give those things a real home or it won’t be used. The default will gradually occur one email at a time. Clear instructions and agreed-upon workflows are a must.
In effect: the inbox isn’t a project management system, but it’s filling that role until something better is put in place to manage team communication over projects and events. It starts innocently in the early years, but the habit gets embedded over time.
3. Starting Before Defining
The habit: work begins before scope, responsibilities, and success criteria are agreed. You don’t need a polished, detailed system at the start if it just needs to get moving fast, but you will need a basic structure in place. It is very important in that case that time is set aside in the near future to map out a solid system to work from, or it will grow out of scope and become disorganized quickly. Then it’s harder to build repeatable business processes.
What it looks like in practice: the team moves fast without foundational decisions and a basic system put in place, and it becomes a runaway train. The project can get out of hand, expectations alter mid-project; scope expands without anyone deciding to expand it.
Why it persists: momentum feels productive and stopping to define the structure of the work feels like slowing down. In an established business, moving fast is often how things got built in the first place. As businesses evolve they tend to become more complex structurally, therefore it is important to pause and make decisions about how the work will proceed.
What to look for before you build a system: identify whether your team has a consistent method for creating structure before project execution begins. If this process is actually used or if it is routinely skipped, it is time to create one.
The effect: scope creep doesn’t start mid-project; it starts before the project gets going.
4. New Software, Same Habit
The habit: modern tools get used exactly like the manual systems they replaced. If you purchased a new system, ensure your staff is trained to use its functions that serve its purpose.
What it looks like in practice: a project management platform becomes a shared to-do list; a CRM becomes a contact spreadsheet. What happened is the tool changed, but the habit did not.
Why it persists: nobody chose how to use the tool; they defaulted to what was familiar, which was the old system in a new interface.
What to look for before you build: understand how the team will actually use a tool before committing to it, and whether the habit the tool needs to work alongside has been accounted for.
The effect: buying new software doesn’t change the habit; it just gives the habit a more expensive home.
Conclusion
The goal here isn’t to make change feel harder than it is. Systems can be very simple, and they can also be very complex depending on what structure is needed for the work to flow.
Keeping it as simple as possible is the key.
When you know what habits are already running your business, how your team communicates, where work gets tracked, and how decisions move, then you have something to build from. That’s how you build repeatable business processes that work and get used. You avoid the small business workflow problems that come from designing without looking first.
The businesses that get the most out of new systems aren’t the ones that replace everything at once.
They’re the ones who looked honestly at what was already in motion, kept what was working, and built the new system around the rest.
Same principle as that fitness program: assess first, start where you are and build something that fits the business you have.
That’s where the work begins. If you’re ready to look at what’s already running before you build anything new, that’s exactly what I help with.