Work better.
Lead stronger.

Every small manufacturer I've worked with has the same inventory story. Someone reaches for a part, it isn't there, and suddenly we're paying for overnight shipping and pushing a job back. The fix usually proposed is a spreadsheet with reorder points. The problem is that nobody on the floor is looking at a spreadsheet when they grab a part.

So we made the reorder point physical. For each item, we set a safety stock level and taped it off with red tape. Above the tape, use what you need. Break the tape, and it's an emergency: that item gets reordered now.

Simple, visual, and nobody has to remember a number.

The tape was only half of it. The other half was training. Everyone who touches inventory was trained to own the restock, not just the purchasing person. If you break the tape, you flag it. Ninety days after we put the system in place, emergency orders and stockouts were down 40%.

The lesson isn't really about tape. The best systems put the information where the work happens, and they make the right action the easy one.

Lean has a word for it: Gemba, the place where the work actually happens. Before I recommend a single change, I go there. I watch the work, ask questions, and let the people who do the job every day show me where it hurts.

That matters for two reasons. First, processes don't exist on paper. They exist in practice. The written procedure and what really happens are rarely the same, and you can't fix what you haven't seen.

I never want to implement a process that makes anybody's life harder.

Second, people support what they help build. When the team designs the new process with you, they own it. When it's handed to them from an office, they work around it. The second version always loses, no matter how good it looked on the whiteboard.

When something goes wrong, the instinct is to find the person responsible. In my experience, that almost never fixes anything. The same mistake comes back with a different name attached to it.

I treat every mistake as one of two things: a process gap or a training gap. Either the process allowed the error, or the person was never properly shown how to avoid it. Both are fixable, and neither requires blame.

Once you know the root cause, error-proof it. Lean calls this poka-yoke: design the step so the mistake is hard or impossible to make. A part that only fits one way. A checklist built into the form. A visual cue right where the decision happens.

Fix the process, not the person, and the mistake stays fixed.

Do this consistently and something bigger happens. People stop hiding problems, because reporting one leads to a fix instead of a reprimand. That's the beginning of a real continuous improvement culture.

Most small businesses run on what's in a few people's heads. It works fine until one of those people is out sick, retires, or leaves. Then everyone discovers how much was never written down.

I've been on the receiving end of that. At one company, the administrator who held all the knowledge of how the business and its finances ran was stepping back. My job was to capture it before it walked out the door. We wrote what the team called "the bible": how the business actually runs, step by step, and built processes where none had existed.

If it only lives in one person's head, it isn't a process. It's a risk.

You don't need a binder that nobody opens. Start with the tasks that would hurt most if they stopped. Write them click by click, test them with someone who has never done the job, and treat every conversation with staff as a training moment.