Our Cabinet Shop Is a Mess — Where Do We Start?

"We're disorganized. We're struggling to get stuff through the shop. We're late on orders. We know we're not lean, and we don't know where to start."

That's close to word-for-word how owners describe it when they first call. If that's you, two things worth saying up front. You're not behind — most shops that grow past a few people hit exactly this wall, because the habits that worked for four people don't work for fourteen. And the fix isn't a big reorganization or a big software purchase. It's four small things, in order, over four weeks.

Week 1: pick one number

Not five. One. Throughput: what the shop completed today against what it needed to complete.

Choose the unit — cabinet boxes, doors, cabinet-equivalents, dollars shipped, whatever you'd naturally answer if someone asked "how much did we get done today." Set tomorrow's target from what a normal crew produces on a normal day. Write target and actual on a board at end of every shift.

That's the whole week. Don't add anything else. By Friday you'll know something you probably don't know today: how far off you actually are, and which days you miss.

Week 2: log every defect

Keep the throughput board going and add a clipboard at each area with six columns: date, where found, where caused, what happened, rework hours, scrap. Log everything for the whole week. Tell the crew it's about the process, not the person.

By Friday you'll have a list. Price it roughly (rework hours × what an hour costs you, plus scrap) and sort by cost. The number at the top is your first improvement project, and it's usually not the problem everyone complains about — it's the one that quietly costs the most. The defect log template has the exact columns.

Week 3: put a Kanban card on the ten things you run out of

Ask the crew: what do we run out of? You'll get the list in a minute — a hinge, a slide, edgebanding colors, screws, a sheet good, a finish. Take the top ten. For each, make a card: item, where it lives, supplier, how many to order, and the reorder point (the level at which the card comes off the bin and goes to purchasing).

Laminate them, put them in the bins. When someone hits the card, it goes on the "order" hook. That's it. Ten cards won't fix everything, but they'll usually end the stockouts that cost the most, and the crew will notice within a week that they're waiting less. The Kanban card template walks through reorder points.

Week 4: write the SOP for your top defect

Take the number-one defect from week 2 and write the standard way to do that job. One page. Photos of the steps. The check at the end that would have caught it. Put it where the job happens — a QR code at the workcell works. Train whoever does that job on it, and note who's been trained.

One SOP. Not forty. Forty is how the SOP project dies. One SOP aimed at your most expensive defect pays for itself immediately and shows the crew what an SOP is for.

What you'll know after four weeks

• Your real throughput gap and which cell is the bottleneck.
• Your most expensive defect and where it comes from.
• Your top ten stockout items, with cards on them.
• One standard job, documented and trained.
• Whether the shop can sustain a daily routine — because you've been running one.

That last one is the real outcome. The four things aren't the point; the habit is. Every improvement after this runs on the same routine: measure, find the top issue, fix it, repeat.

What not to do first

• Don't reorganize the whole shop. A big cleanup feels productive and lasts three weeks. Fix the flow first; organize around it after.
• Don't write forty SOPs. Write one, for the defect that costs the most.
• Don't assume an ERP is the answer. Before buying a system, know whether the problem is scheduling, accounting, job costing, inventory control, or daily shop-floor management. Most shops at this stage need the last one, and it doesn't come from an ERP. Here's how the categories differ.
• Don't try to fix everything the crew complains about. Fix what the numbers say costs the most. Complaints are data; the log is the ranking.

If you don't have time to do any of this

That's a real answer and it's the most common one. If the honest situation is "we would do this if someone set it up with us," that's the whole reason our done-for-you program exists: we come in, build the throughput targets, the defect log, the Kanban cards, and the first SOPs with your team, and leave you running the routine. If you'd rather see the whole system before deciding, the eight-minute overview walks through it.

Frequently asked

Where should a disorganized shop start? With one number — daily throughput against a target — for one week. Everything else follows from what that shows you.

Do we need software to get organized? No. A whiteboard, a clipboard, and ten laminated cards are enough for the first month. Software matters when the routine works and you want it to run itself.

How long until we see a difference? Most shops feel it in the first month: fewer stockouts, one expensive defect fixed, and a daily target the crew can see. The routine compounds after that.

What if the crew won't buy in? Start with the throughput number and the huddle. Two minutes a day. When people see the target and see themselves hit it, buy-in follows. Don't launch five things at once.