Skip to main content
Growth System Design

  • Operational problems we fix (when systems don’t match reality)

    If you’re constantly chasing stock, fixing mistakes, and working around the system, you’re not alone. Most owner-operated manufacturing and warehousing businesses don’t have a “software problem”, they have a gap between the system, the process, and what people actually do day to day.

    Below are the most common problems we see (and the practical first steps to fix them).
    Let's Talk

    Prefer examples?Read the case studies →

Stock problems (inventory accuracy)

If you can’t trust your stock numbers, everything downstream gets harder (purchasing, production, and fulfilment).

Why do we keep running out of stock, even when we think we’re organised?

Stockouts are often caused by a mix of unreliable stock numbers, unclear reorder triggers, and lead times that aren’t realistic.

Good first steps:
  • Identify the top repeat stockouts (20% causing 80% of issues)
  • Fix the reorder trigger (not just “buy more”)
  • Confirm lead times based on what actually happens

Why does the system say we have stock, but we can’t find it?

This usually happens when stock moves without being recorded, receiving isn’t controlled, locations aren’t maintained, or people are forced into workarounds.


Good first steps:
  • Tighten receiving (what “done” looks like, every time)
  • Make locations real (where stock is allowed to live)
  • Start cycle counting the items that cause the most pain

Why are stock adjustments happening all the time?

Frequent adjustments are a symptom: the business is correcting errors after the fact instead of preventing them.

Good first steps:
  • Track adjustments by reason (so you can eliminate the cause)
  • Fix the transaction points that create the errors (usually receiving, picking, or production issues)
  • Put a simple approval/check on high-impact adjustments

How do we make cycle counting stick?

Cycle counting fails when it has no owner, no rhythm, and no consequence when it’s skipped.

Good first steps:
  • Assign ownership (one person accountable)
  • Set a weekly cadence that’s realistic
  • Use a simple rule: count → investigate variance → fix the cause

Related case studies: Master data cleanup, BoM cleanup in ERP


Purchasing problems

When purchasing is always urgent, it’s usually because reorder triggers and lead times don’t reflect reality.

Why is our purchasing always urgent?

If purchasing is always urgent, it’s usually because the business has no reliable trigger for what to buy and when, so everything becomes a rush.

Good first steps:
  • Define what triggers a purchase (not “someone noticed”)
  • Set basic reorder levels for your critical items
  • Clean up supplier lead times (even roughly is better than fantasy)

Why are we always chasing suppliers and rushing freight?

This is often caused by unreliable ordering cadence, unclear priorities, and lead times that aren’t maintained.

Good first steps:
  • Create a weekly purchasing rhythm (even if small)
  • Confirm real lead times and minimum order constraints
  • Reduce last-minute orders by stabilising the top repeat items first

Why do we buy too much of the wrong stuff and still run out of the right stuff?

That’s usually a classification + planning signal problem (not a “people problem”).

Good first steps:
  • Split items into critical vs non-critical
  • Set simple stocking rules for each group
  • Stop treating every item the same

Related case studies: Master data cleanup


Order fulfilment & warehouse workflow problems

If dispatch is slow or error-prone, it’s often a workflow and system-step issue, not just a people issue.

Why does picking and packing take so long?

This is usually layout + process + system steps not matching how people work.

Good first steps:
  • Map the pick path (where time is actually lost)
  • Fix locations and item labelling
  • Reduce exceptions (the “weird cases” that slow everything down)

Why does everything rely on one person who knows how it really works?

That’s a risk issue. If one person is away, the business slows down or mistakes spike.

Good first steps:
  • Document the real process (not the ideal one)
  • Simplify steps so the process is teachable
  • Coach the team until it’s normal

Why are we getting so many picking mistakes / wrong items shipped?

Most errors come from unclear identification, poor bin discipline, and no verification step at the right point.

Good first steps:
  • Improve item identification (labels, barcodes, descriptions)
  • Add a simple verification step where it matters
  • Fix the top SKUs causing repeat errors

Related case studies: Master data cleanup


Production & planning problems (manufacturing)

When planning keeps changing, it’s usually because the plan isn’t based on real constraints, times, and priorities.

Scheduling is a mess, we’re constantly reshuffling.

This usually happens when the plan doesn’t reflect reality (times, constraints, priorities), so the team stops trusting it.

Good first steps:
  • Identify the real constraint (the bottleneck)
  • Validate times for your highest-volume work
  • Build a simple planning rhythm (weekly plan + daily control)

Why can’t we meet promised lead times?

Lead times fail when WIP isn’t visible, priorities change constantly, or the plan ignores capacity limits.

Good first steps:
  • Make WIP status visible and consistent
  • Define priority rules (so everyone isn’t guessing)
  • Align what sales promises with what ops can deliver

Related case studies: Production scheduling systemisation, Routing and work centres, BoM cleanup in ERP


We can’t trust the numbers

If reports don’t match what you see, the issue is almost always the inputs and process discipline feeding the system.

Why don't the reports match what we see in the business?

If the inputs are messy, the outputs will be too. This is usually data + process discipline, not “better reporting”.

Good first steps:
  • Decide what decisions you need the numbers for (stock, staffing, purchasing, capacity)
  • Fix the upstream steps that feed those numbers
  • Clean the few data fields that drive the most downstream issues

Why do we need so many spreadsheets? 

Spreadsheets usually appear when the system doesn’t match reality or is too hard to use consistently.

Good first steps:
  • Identify which spreadsheet is “mission critical”
  • Work backwards: what’s missing from the system/process that forces the spreadsheet?
  • Replace the root cause, not just the spreadsheet

Related case studies: Master data cleanup, Routing and work centers, BoM cleanup in ERP


Do we need a new system?

Most businesses don’t need a replacement; they need their current system set up to match how the business actually runs.

Do we need to replace the system, or fix how we use it?

Most of the time, replacement isn’t the answer. The system is often capable, it’s just not aligned to how the business actually runs.

If it genuinely isn’t fit for purpose, we’ll tell you plainly.

Related case studies: Master data cleanup, Production scheduling systemisation


Not sure where to start?

If one of these problems sounds familiar, start with a short intro call. No sales pitch, just a straightforward conversation about what’s happening and whether we can help.

Let's Talk