People & Change10 min read

The Most Expensive Words in Business: "We've Always Done It This Way."

Experience should make you better at questioning decisions. Not more comfortable defending them.

Jacquelyn Mosier
Jacquelyn “Jackie” Mosier

Founder & Principal Consultant, Jack-IT Consulting

I've heard a lot of explanations for why businesses operate the way they do.

Some are thoughtful. Some are backed by years of experience, customer feedback, and measurable results. And some boil down to five words:

"We've always done it this way."

Every time I hear that, I want to ask one question.

Okay. But is it still working?

Because there's a difference between doing something consistently because it produces results and doing something repeatedly because nobody wants to challenge it.

One is discipline. The other can become a very expensive habit.

Experience Is Valuable. Until It Becomes an Excuse.

I have tremendous respect for people who have spent decades building businesses, developing teams, and learning their industries. Experience matters. It teaches you things that no software demonstration, certification, or AI-generated recommendation can replace.

But experience can also create blind spots. When you've done something successfully for years, it's easy to assume that the same approach will continue producing the same results.

Sometimes it will. Sometimes your customers change. Your workforce changes. Your competition changes. Your costs change. And the process that helped you build the business becomes the very thing preventing it from growing.

That doesn't mean the original decision was wrong. It may have been exactly right for the business at the time.

A good decision made ten years ago doesn't automatically remain the best decision today. Leadership requires being willing to revisit what you once got right.

The Cost of Staying Comfortable Rarely Shows Up on an Invoice.

When businesses consider investing in technology, they tend to focus on the cost. How much is the software? What will implementation cost? How long will training take? What happens if it doesn't work?

Those are reasonable questions. But I find it interesting how rarely organizations calculate the cost of doing nothing.

How many hours are employees spending recreating information? How much time does leadership lose trying to get accurate reporting? How many opportunities disappear because follow-up is inconsistent? How many customers become frustrated by communication gaps? How much institutional knowledge disappears when a long-term employee leaves?

Those costs may never arrive as a neatly labeled invoice. But they still affect the business.

Let's say five employees each spend three hours a week completing unnecessary administrative work. That's fifteen hours every week. Over fifty working weeks, that's 750 hours. At a hypothetical fully loaded labor cost of $35 per hour, that's $26,250 annually. And that's before considering delays, errors, missed opportunities, or the effect on employee morale.

Now imagine leadership refusing to evaluate that process because: "We've always done it this way."

The absence of a new expense doesn't mean the current approach is free.

Your Best Employees May Be Compensating for Your Worst Processes.

Here's something leaders don't always realize. A business can appear operationally successful because its employees are exceptionally good at working around broken systems.

The office manager who remembers everything. The salesperson who keeps a separate spreadsheet because the CRM doesn't reflect reality. The operations coordinator who knows which information needs to be double-checked. The employee everyone calls when something goes wrong.

Those people are valuable. But there's a difference between having talented employees and building a business that depends on employees constantly compensating for operational weaknesses.

What happens when that person takes a vacation? Gets promoted? Leaves the company? Or simply becomes exhausted from holding everything together?

Suddenly, the business discovers that the process wasn't actually working. One person was making it work.

If your operations depend on someone remembering what your systems should be managing, that's not efficiency. That's dependency. And dependency becomes a serious problem when you're trying to scale.

"My Employees Don't Like Change" Is Often a Leadership Problem.

I've heard business owners say their employees are resistant to change. Sometimes that's true. But I think leaders need to examine what they're asking employees to change and how they're introducing it.

Did anyone explain why the change was necessary? Were employees involved in evaluating the current process? Did leadership understand how the work was actually being performed? Was appropriate training provided? Did anyone consider how the change would affect existing responsibilities? Or did the company purchase software, announce a new process, and expect everyone to figure it out?

Then, when employees continued using the old system, leadership called them resistant. That's not always resistance. Sometimes it's a predictable response to poor planning.

I've worked with sales teams and business operations long enough to understand that people need more than instructions. They need clarity. They need to understand what's changing, why it matters, and how success will be measured. They also need leadership to follow through. Because if management announces a new process and then continues operating outside of it, employees notice.

You cannot expect your team to embrace changes that leadership isn't willing to model.

Innovation Doesn't Mean Throwing Away Everything That Works.

Now, here's where I think the conversation gets interesting. The opposite of "we've always done it this way" isn't "change everything." That mentality can be just as expensive.

I've watched businesses get caught up in the excitement surrounding new technology. A competitor introduces a platform. Someone attends a conference. An AI demonstration looks impressive. A vendor promises to revolutionize operations. Suddenly, leadership wants to replace systems that may already be working — without evaluating the existing processes, without understanding the cost of transition, without considering whether employees actually need the new functionality.

That's not innovation. That's reacting. And reactive decisions can create just as much operational disruption as refusing to change.

At Jack-IT, I don't believe a business should replace technology simply because something newer exists. I believe businesses should understand what they have, what they need, and where the gaps are. Sometimes the answer is a new system. Sometimes it's better training. Sometimes it's improving a workflow. Sometimes it's using capabilities the business is already paying for. And sometimes the right decision is to leave a process alone.

The goal isn't to change for the sake of change. It's to stop defending decisions that no longer serve the business.

The Questions Nobody Wants to Ask in a Leadership Meeting.

One of the most valuable things an outside advisor can bring to an organization is a willingness to challenge assumptions. Not because leadership is incapable. But because people become accustomed to the environments they operate in every day. They stop noticing the extra steps. They accept the reporting delays. They normalize the workarounds. They assume certain problems are simply part of doing business.

Until someone asks: Why does this approval require four people? Why is this information being entered twice? Why can't your sales team see what operations is doing? Why does one employee have to manually create a report that the system should already provide? Why are you paying for three tools that perform overlapping functions? Why is nobody measuring whether this process is actually effective?

Those questions can be uncomfortable. Especially when the answer reveals that a long-standing process is creating unnecessary costs. But discomfort isn't necessarily a bad thing. Sometimes it's the beginning of a much better decision.

If nobody in your organization is allowed to question how things work, don't be surprised when nothing improves.

Growth Exposes What Small Teams Can Hide.

When a business is small, informal processes can work surprisingly well. The owner knows every customer. Employees communicate directly. Decisions happen quickly. Everyone understands who handles what. And if something goes wrong, somebody fixes it.

But as the company grows, that same informal structure can become a bottleneck. More employees. More customers. More projects. More financial responsibilities. More systems. More handoffs. Suddenly, the owner can't personally oversee everything. The spreadsheet that worked for five employees doesn't necessarily work for fifty. The verbal approval process that worked for ten transactions may become unreliable at a hundred. And the person who used to remember every customer detail can no longer keep up.

This is where businesses often mistake growing pains for staffing problems. They assume they need another employee. Or another manager. Or another software platform. Sometimes they do. But sometimes the real issue is that the organization has outgrown the way it operates.

You can't always scale a business by asking more people to work inside the same limitations. At some point, the operating model itself needs to evolve.

The Most Dangerous Phrase Might Actually Be "It's Working Fine."

"We've always done it this way" is easy to recognize. But there's another phrase I pay attention to: "It's working fine."

Fine according to whom? Leadership? Employees? Customers? The financial statements? And what does fine actually mean? Does it mean the business is profitable? Does it mean employees aren't complaining? Does it mean nobody has experienced a major failure? Or does it mean the organization hasn't measured whether a better approach is possible?

A process can function without being efficient. A system can produce results without producing reliable information. A business can be profitable while absorbing unnecessary operational costs. And a team can meet its goals while operating under avoidable pressure.

That doesn't mean everything needs to be redesigned. It means leaders need to define what success looks like beyond simply getting through the day.

"It's working" and "it's working well" are two very different statements.

What Forward-Thinking Leadership Actually Requires.

I don't believe the best leaders are the ones constantly chasing the next big thing. And I don't believe they're the ones who refuse to change because their existing approach once worked. I believe strong leaders are willing to evaluate both.

They ask whether current processes still support the business. They listen to employees who experience operational problems firsthand. They challenge vendors who promise results without understanding the organization. They examine the financial and operational consequences of their decisions. They invest in training and accountability. And they're willing to acknowledge when something needs to change — even when they were the person who originally created it.

That's an important part of leadership. Your job isn't to defend every decision you've ever made. Your job is to make the best decisions you can with the information available today. Then remain willing to reevaluate them tomorrow.

Why This Matters to Jack-IT Consulting.

I started Jack-IT because I saw a gap between what businesses were being sold and what they actually needed. Too many technology conversations begin with a product. A platform. An integration. An AI solution. A promise of efficiency.

But before any of those recommendations mean anything, somebody needs to understand how the business operates. What is working? What isn't? What has changed? What is costing money? What is preventing growth? What are employees struggling with? And what would actually improve the organization's ability to serve its customers?

Those are the conversations we prioritize. We're not here to tell businesses that everything they're doing is wrong. We're here to help them recognize where their existing approach still creates value and where it may be holding them back.

Sometimes that means technology. Sometimes that means process improvement. Sometimes that means training, organizational alignment, or a completely different strategy. And sometimes it means challenging an assumption that nobody has questioned in years.

Because the most expensive business decisions aren't always the ones you make. Sometimes they're the ones you refuse to reconsider.

Think about one process in your organization that nobody questions anymore. Maybe it's how you manage customer inquiries. Maybe it's how you approve purchases. Maybe it's how you schedule projects. Maybe it's how you track performance. Maybe it's how your employees communicate between departments.

Now ask yourself: If we were starting this business today, knowing everything we know now, would we build this process the same way?

If the answer is yes, great. You have a reason to keep it. But if the answer is no, why are you still defending it?

Experience should give you the confidence to make better decisions. Not the obligation to keep making the same ones.

"We've always done it this way" explains your history. It doesn't justify your future.

Your Business Has Evolved. Have Your Operations?

Jack-IT Consulting  |  Strategy Before Software. Always.

Jacquelyn Mosier — Founder and Principal Consultant, Jack-IT Consulting
Jacquelyn “Jackie” Mosier

Founder & Principal Consultant, Jack-IT Consulting

Technology Strategy  ·  AI Advisory  ·  Business Operations  ·  Executive Leadership

Jacquelyn Mosier is the Founder and Principal Consultant of Jack-IT Consulting. With a background in national sales leadership, team development, and business operations, she built Jack-IT on a straightforward premise: technology decisions should start with the business, not the software. She works directly with leadership teams to evaluate investments, identify operational gaps, and build strategies that connect people, processes, and systems before recommending what comes next.

Your Business Has Evolved. Have Your Operations?

If your organization has grown, your technology has changed, or your employees are spending more time working around systems than benefiting from them, it may be time to question the processes you've accepted as normal. Jack-IT Consulting helps businesses evaluate operational challenges, technology investments, employee workflows, and growth strategies without pushing unnecessary software or chasing trends. We'll help you identify what deserves to stay, what needs to change, and where the right investment can create meaningful results.