Jordan B Consulting · Free Guide
10 Operational
Mistakes…that scaling businesses make — and what to do instead

These aren't rare edge cases. They're the same ten problems, in different combinations, in almost every business that's grown faster than the systems holding it up. If you recognise more than three, you're not alone — but you do have work to do.

10
What's inside
01Keeping the Process in Your Head
02Hiring Before Systems Are Ready
03Tracking the Wrong Numbers
04Making Onboarding Your Busiest Person's Job
05Fixing Symptoms Instead of Causes
06Building for Today, Not Next Year
07Delegating Tasks Without Delegating Authority
08Letting Your Tech Stack Grow Without a System
09Waiting Until It Breaks to Document It
10Confusing Busy With Productive

Every business in this guide grew quickly. That's not the problem. The problem is that growth outpaces systems — and at some point, the things that worked when you had eight people stop working when you have thirty.

These ten mistakes aren't failures of effort. They're failures of structure. Most of them were invisible until they became expensive. None of them are irreversible. But all of them get harder to fix the longer they're left.

Read through. Be honest about which ones apply. The ones you recognise are the ones to fix first.

No.
01
Process Management
Keeping the Process in Your Head
You know you're doing this when…
"Nobody does it as well as I do." "It's faster if I just do it myself." "I've explained it a hundred times and they still get it wrong." — If these are familiar, the problem isn't your team. It's that the process only exists inside you.
Why it happens
When you built the business, you were the process. It made sense to keep things fluid and in your head — writing it down felt slower than just doing it. The habit persists long after the business has outgrown it.
What it costs
Every hire takes longer to become useful. Every holiday is stressful. Every time you're unavailable, something falls apart or waits. Your knowledge is a single point of failure — and the bigger the business gets, the more expensive that failure becomes.
What to do instead
Pick your three most repeated tasks. Set a timer for 25 minutes each. Write the steps as if you're explaining to a capable person on their first week. Don't make it perfect — make it done. A rough SOP used is worth infinitely more than a perfect one never written.
No.
02
Hiring & Onboarding
Hiring Before Systems Are Ready
You know you're doing this when…
The new hire has been with you six weeks and is still asking where things are, how things work, and what the actual process is. Your most experienced person is spending half their day onboarding instead of doing their actual job.
Why it happens
Growth creates pressure to hire fast. The business is overwhelmed, the instinct is to add people, and the assumption is that a competent hire will figure it out. Sometimes they do. Usually the chaos just spreads to one more person.
What it costs
A new hire in an undocumented business costs more than the salary. It costs senior staff time, creates inconsistent quality, and often results in an early departure — meaning you pay the recruitment and ramp cost twice. A study by SHRM estimates the average cost of a bad hire at 50–200% of annual salary.
What to do instead
Before the next hire, spend one week documenting the role you're hiring for. What will they own? What does good look like? What's the 30-day plan? A role that's well-documented before it's filled onboards 3–4 times faster and retains far better. Hire into a system, not into a void.
No.
03
Reporting & Tracking
Tracking the Wrong Numbers
You know you're doing this when…
You have spreadsheets full of data, a weekly report nobody acts on, and you still can't answer the question: "Is the business on track?" You're measuring activity instead of outcomes.
Why it happens
Metrics accumulate organically. Someone added a column. Someone wanted a new report. Over time, the dashboard becomes a graveyard of numbers that made sense when they were added but no longer connect to anything the business cares about.
What it costs
Decisions get made on instinct because nobody trusts the data. Problems are caught late because the right indicator wasn't being watched. Leadership meetings become status updates instead of strategic conversations.
What to do instead
For each part of the business, ask: what's the one number that tells us if we're winning or losing? Start there. A dashboard with five meaningful metrics beats a spreadsheet with fifty ignored ones. Review them weekly at a set time. Act on them or remove them.
No.
04
Training & Onboarding
Making Onboarding Your Busiest Person's Job
You know you're doing this when…
Every time someone new joins, you pull your best person off their actual work to walk them through everything. Six weeks later your best person is behind on their own work, and the new person knows as much as your best person was willing to share while also doing their own job.
Why it happens
No structured onboarding exists, so the default is "put them with the most experienced person." This feels like a solution — it's actually a tax. You're paying your highest-value employee to do a job that could be done by a well-designed document.
What it costs
One under-structured onboarding for a mid-level hire can cost 40–80 hours of senior staff time. Multiply that by three hires a year and you've spent a month of your best person's capacity on something that could be systematised in a week.
What to do instead
Build a 30-day onboarding plan for each role. Day 1–5: access, context, culture. Days 6–15: shadowing with clear observation goals. Days 16–30: supervised doing, with defined milestones. The plan should be followed from a document, not delivered by a person in real time.
No.
05
Process Management
Fixing Symptoms Instead of Causes
You know you're doing this when…
The same problem comes back every few months with a slightly different face. You fix it, move on, and six weeks later you're fixing a version of the same thing again. It feels like bad luck. It's usually a structural issue that was never actually addressed.
Why it happens
When businesses are busy and under pressure, the instinct is to fix the immediate problem as fast as possible and move on. Root cause analysis feels slow and luxurious. It isn't — it's the difference between solving something once and solving it forever.
What it costs
Recurring problems are compounding problems. Every time the same issue returns, it costs more than the last time — in staff time, in client trust, in management energy. The businesses that grow steadily are the ones that close problems permanently, not repeatedly.
What to do instead
When something goes wrong, ask "why" five times before reaching for a fix. The first "why" almost always points to a symptom. By the fifth, you're usually at the actual cause. Fix that — not the surface event. Document the fix so the same cause doesn't resurface in a different form.
No.
06
Strategy & Systems
Building Systems for Today Instead of Next Year
You know you're doing this when…
You built a system six months ago that worked brilliantly for a team of 10. Now you have 25 people and the system is a bottleneck. You're rebuilding infrastructure while also trying to run the business that outgrew it.
Why it happens
Operational design defaults to solving the immediate problem. Nobody builds a hiring process that works for 80 people when they only have 12. But growth comes faster than expected, and the system built for today has to be rebuilt at the worst possible time.
What it costs
Rebuilding operational infrastructure mid-growth is expensive, disruptive, and demoralising. Teams that were working fine start to feel like they're always changing how things work. Trust in leadership decisions erodes. Quality dips during transitions.
What to do instead
When building or redesigning a system, ask: "Would this still work if we were twice the size?" If not, build the next version now, even if you don't need it yet. The marginal cost of building something scalable is small. The cost of rebuilding under pressure is large.
No.
07
Leadership & Delegation
Delegating Tasks Without Delegating Authority
You know you're doing this when…
"I've given them the responsibility, but I still have to approve every decision they make." Or: your manager needs to check with you before they can answer basic client questions. The task is delegated. The power to execute it isn't.
Why it happens
Trust is built slowly, and giving someone authority over something you care about feels risky. The instinct is to delegate the work but maintain the sign-off. The result is a pseudo-delegation that actually creates more work for you — not less.
What it costs
You become a bottleneck in your own business. Decisions queue up waiting for your attention. Your managers are demotivated because they have accountability without authority. Speed and autonomy — two of the most valuable operational properties — are sacrificed at the altar of control.
What to do instead
For each role, define explicitly: what decisions can this person make alone? What requires consultation? What requires approval? Write this down. Then stick to it. Delegation without defined authority is just asking someone to be busy on your behalf. Authority without accountability is also dangerous — they need both.
No.
08
Systems & Tools
Letting Your Tech Stack Grow Without a System
You know you're doing this when…
You have Slack, Teams, WhatsApp, email, Asana, Trello, Notion, and a spreadsheet all being used for roughly the same things by different people. Decisions happen in DMs. Important context lives in someone's inbox. Nobody can find anything.
Why it happens
Tools get added reactively. Someone discovers a new app. A client uses a particular platform. A problem arises and a tool gets adopted to solve it. Over time, the stack becomes a digital version of the physical chaos on a cluttered desk — everything is there somewhere, but nothing is where it should be.
What it costs
Operational information spreads across platforms that don't talk to each other. New hires have to learn six tools instead of two. Context is lost in handoffs. You pay for subscriptions that duplicate each other. Decisions are made without full information because someone didn't see the message in the right channel.
What to do instead
Audit your current stack: what does each tool do, who uses it, and does it overlap with another? Define what each type of communication or storage belongs in — one tool per job, documented policy on where things live. Fewer, better-used tools outperform a large stack used inconsistently every time.
No.
09
Documentation & SOPs
Waiting Until It Breaks to Document It
You know you're doing this when…
The only time processes get written down is after something goes wrong, someone leaves, or a client complains. Documentation is reactive, not proactive — and the business is perpetually one departure or one mistake away from losing critical operational knowledge.
Why it happens
When things are working, documentation feels unnecessary. Nobody argues for building a fire exit when the building isn't on fire. The business moves fast, the team is capable, and writing things down looks like overhead. It isn't — it's insurance.
What it costs
The true cost of undocumented knowledge only appears when it leaves. A resignation, a long-term absence, or a rapid growth phase reveals every process that lived only in someone's head. By then, the cost of capturing it is multiplied by the cost of the disruption happening simultaneously.
What to do instead
Build documentation into the workflow, not the aftermath. Every process, before it's considered complete, should have a basic SOP. Make "document as you go" a team norm, not a crisis response. Even 60% documentation across all key processes is vastly better than 100% documentation of only the things that already broke.
No.
10
Leadership & Operations
Confusing Busy With Productive
You know you're doing this when…
The team is working hard. Everyone's full. But somehow the business doesn't feel like it's moving. There's activity everywhere and progress nowhere. Full capacity, low output. The calendar is packed but nothing significant is getting done.
Why it happens
Without clear priorities and defined outcomes, effort fills available time — but not necessarily the right time. Tasks expand to fill the space. Meetings multiply. Everyone is working, but the work isn't connected to anything that moves the business forward.
What it costs
A business where everyone is busy but few things are progressing is burning payroll on motion rather than momentum. The most expensive kind of cost is often invisible: it's the strategic work that never got done because the operational noise drowned it out.
What to do instead
Define what "productive" means for each role — specific, measurable outputs, not activity levels. Run a weekly priority check: what are the three things that actually matter this week? Protect time for those things explicitly. Review at the end of the week whether they got done — and if not, why not. The answer will be instructive.
Jordan B Consulting
"Recognising the mistake is the easy part.
Fixing it without disrupting the business you're trying to fix — that's the work."

If three or more of these landed, your business has operational gaps that are costing you more than you probably realise. A free 15-minute call is the fastest way to identify which ones to fix first.

Book Your Free 15-Min Call →
jordanbconsulting.com — Chaos is just a system you haven't built yet.