Do We Really Need a Work Instruction for Every Little Thing?

Dave Crysler breaks down why a growing backlog so often gets mistaken for a capacity problem, starting with a client whose estimating queue hit 40 lines while everyone assumed the answer was another hire. He explains how one static process ends up carrying several different types of work, what he learned the hard way training an entire new customer service team, and why an express lane changed how fast the business felt to its customers. He also covers where this idea goes wrong, from batching jobs to save a setup to putting one person in charge of sorting every inquiry. What You'll Discover: • Why a growing queue can look like a capacity problem when it isn't • How first in, first out leaves simple work sitting behind complex work • What it looks like to work a backlog from both ends • How categorizing your workload and your team gets the right work to the right people • Why an express path can feel lightning quick to customers • How batching to save a setup can leave three jobs shipping late today • Why a full-time "traffic cop" reading every inquiry is the wrong fix, and what a hybrid looks like • How to tell when a lane is worth building and when overtime or a temporary shuffle will do • Why the way you measure a backlog matters, and how a win rate can mislead you If your team is buried and the next idea on the table is another hire, take a closer look at what's actually sitting in the pile first. This episode gives you a practical way to sort your work and decide whether you have too much of it, or just too much of it standing in one line.

In this episode, Dave Crysler breaks down why most software purchases fail to deliver on their promise. Drawing from a recent conversation with a sub-million-dollar business owner evaluating an $8,000 MIS, Dave unpacks the Tool Trap: the pattern of buying technology to fix problems that are actually process problems in disguise. The software cannot create clarity, and if the underlying process is not defined, the tool will not automate anything. It will just spread the confusion faster. What You'll Discover: • Why no leader, at any revenue band, is ever fully in love with their ERP or MIS, and what that tells you about the tool itself • The fastest diagnostic to tell whether you have a process problem or a technology problem, using the tools you already own • Why "I want to automate the process" almost always means something different than it sounds • How the Clarity, Consistency, Accountability sequence maps directly onto every software buying decision • What a $4,000 configuration fee is actually buying, and why you can get the same output on a whiteboard for free • The honest exception: when buying the tool early still makes sense, even if the ROI does not pencil out • The 2026 wrinkle: why AI coding assistants and vibe-coded custom tools are the Tool Trap wearing cheaper clothes • Why the homegrown software cycle has already played out once, and what history tells us about where this one ends • A concrete Monday morning exercise you can run with your team before you spend another dollar on software Whether you are a sub-million-dollar business deciding on your first MIS, a mid-market leader looking at an ERP upgrade, or anyone tempted to have an AI build you a custom tool this weekend, this episode will change how you evaluate the decision. The tool can execute a clear process. It cannot create one.

Ask most leadership teams what they're working on and you get the whole list: an ERP optimization, a new CRM, a quality initiative, process documentation, maybe a rebrand. Every one of them is in progress, and none of them ever seem to finish. Dave Crysler explains why that's rarely a project management problem and almost always a clarity and leadership problem, and why the real unlock is having the strength to look at a good idea and say "not yet." He walks through how he connects a 12 to 18 month mission to strategic objectives and then to a short list of initiatives, the metrics that quietly reward the wrong behavior, and two simple ways to decide what moves first. What You'll Discover: • Why leadership's list of priorities and the front line's list almost never match, and what that gap tells you • Why a better project management tool or prioritization method won't fix a list that was never edited • How to layer mission, strategic objectives and initiatives so every active project traces back to something • How to park good ideas on a shared board without losing them or letting them crowd the active list • The fine line between a strategic pivot and plain inconsistency • Why 50 phone calls to companies outside your ICP count as activity, not progress, and how to measure effective volume instead • Two ways to sequence what's left: the natural order of enablers, or a simple impact, effort and cost scoring matrix that lets the math do the work • Why some ideas are one-off tasks, not initiatives, and why treating them all the same overloads the team • What a dot matrix banner and a wall of sticky notes taught Dave about building a culture of continuous improvement • Why trust and change management decide whether a business being disrupted by AI makes it through If your team is pushing ten initiatives forward and finishing none of them, start Monday by getting every one of them in one place where you can see it. Then get clear on the mission, cut the active list to the few things that matter now, and move the next one up only when something actually finishes.

Dave Crysler starts with a loop every operations leader knows: something goes wrong, the team runs a five whys, everybody gets retrained, and you're sure it's solved until it happens again. In most shops he walks into, the tool has very little to do with why the problem keeps coming back. Dave walks through a recurring finished goods problem that came back for nearly a decade and got solved with the same tools the company already had, used in a different order. He also shares how he decides which root cause problems deserve a full investigation, why so many of them end at "operator error, retrained," and how he defines human error differently than most people. What You'll Discover: • Why the five whys so often stops at a symptom or at operator error, and what the real skill behind it is • How a recurring problem that lasted nearly a decade got solved without a single new tool • Why not every problem deserves a full root cause investigation, and how to scale the response to the risk • What happens to a review step when people get fatigued from double checking everything • When to reach for a fishbone diagram or a Pareto chart instead of starting with a five whys • A custom manufacturer's order errors, and the options that beat retraining the team again • Dave's three types of error (equipment, system and human) and why he sees so few true human errors • Why most people who skip a process are doing it for a reason, and why finding that reason is leadership's job • How a plant making mission critical documents got returns and allowances down to 0.04% by making mistakes impossible • What to pull from your files on Monday to see how many of your fixes were really just bets If the same problem keeps showing up on your floor no matter how many times you fix it, start here. The tools you already have are probably fine. What usually needs to change is which one you pick up first, and where you stop looking.

Dave Crysler takes on one of the most repeated lines in business, what got you here won't get you there, and argues the other side. The quoting, scheduling, purchasing, making and shipping that built a $1 million company are the same work a $100 million company does. There's just a lot more of it, and the handoffs between people are what break. Dave walks through a custom manufacturer that ran every customer inquiry through a shared inbox, why "if we were ten times bigger, this would go away" never holds up, and why the software vendor telling you to rip and replace probably isn't telling you the whole story. What You'll Discover: • Where the phrase "what got you here won't get you there" comes from, and why Dave disagrees with how it gets applied to growing companies • Why growth is just more of everything: more transactions, more people, more risk, with the same core work underneath • What the "everyone's in the same room" stage looks like, and why informal works so well until it doesn't • How a shared inbox with no audit trail let customer inquiries fall through the cracks, and what designing a real system changed • The phrases that tell you work is falling between people, starting with "I thought you were dealing with that" • Why "Dave just knows" turns into rework, scrap, delays and upset customers the day you hire someone new • Why getting ten times bigger swaps your problems for different ones, with cash flow as the example • What a company under $1 million and a company over $1 billion have in common, and the game of telephone that separates them • Why QuickBooks can handle far more volume than software vendors want you to believe • A crawl, walk, run approach that starts with tracing a single order through your business If your company keeps stalling at the same size, or the same problems keep showing up a little bigger every year, start here. The work that got you here will get you there. What has to change is getting that work out of people's heads and into systems designed for where you're going.

Dave Crysler walks through a client call that started with one boring question, what happens when you click new invoice, and ended up exposing a couple thousand customer records with no payment terms at all. Every decision that led there made sense the day it was made, from the net 30 default to a finance team adjusting terms to quiet a noisy aging report. Dave uses it to show how a default system gets built out of good intentions, why localized efficiency creates confusion everywhere else, and why a cleanup that works can still be undone a week later. This is the episode for anyone who suspects their software is making decisions nobody on the team actually made. What You'll Discover: • What one question about a default setting uncovered in a client's accounting system • Why a net 30 default was a reasonable choice when it was made, and how it quietly stayed in charge for years • How a blank field and a real decision can look identical on screen • The difference between localized efficiency and overall effectiveness, and why good intentions drive the first one • Why adjusting a customer's terms to match how they actually pay distorts your cash picture and your view of that customer • The customer who burned the company for thousands of dollars and still showed payment terms in the system • Why the cleanup worked, and why thirty-some new accounts had recreated the problem a week later • How to design around non-negotiable systems so the tool carries the rule instead of the operator's memory • Why the words you choose on a job ticket or status can create clarity or confusion • A crawl, walk, run approach to finding the blanks and defaults running your business today If your team keeps cleaning up the same mess, or you inherited settings nobody remembers choosing, start here. The fix is rarely more discipline from the people doing the work. It is deciding on purpose what the system should do when nobody is choosing.

Dave sits down with Wes Temple, Director of Growth at Gorilla 76, a B2B agency that works exclusively with manufacturers and industrial technology companies. Wes owns the marketing strategy for every client they sign, which means he has traced a lot of lead flow end to end and found out exactly where it stops. In one case, the leads were arriving, they were logged, they had real six figure values attached to them, and nobody was touching them. This conversation goes at the part of the funnel most manufacturers have never mapped: what happens between a lead landing in the system and somebody actually owning it. What You'll Discover: • Why the fight between marketing and sales exists at all, and what Wes says is really underneath it • What he found when he traced a client's lead flow end to end, and the value that was sitting untouched in their CRM • How a few changes to a sales process can be worth one, two, or three more closed deals a quarter • The difference between owning a CRM and actually using it to sell • Why so many manufacturers pay for sales software they never configured to match the way they sell • The exact sentence a marketing leader can use to open the conversation with their sales leader • How to route leads, trigger follow up, and run a weekly review that makes dropped opportunities visible • Why three to five priorities beat thirty, and what happens to the companies that refuse to choose • Where the cheapest growth in most manufacturing businesses is already sitting, and the exercise that finds it • What Wes tells people to go do Monday morning, which has nothing to do with marketing at all If your quotes go out and follow up happens sometimes, or you are about to spend more money generating demand that your current process cannot hold, this conversation is about a gap you have probably never measured. The fix is rarely more leads. It is almost always knowing what happens to the ones you already have.

Dave Crysler answers the question a client asked him in the middle of a gap review, the one everybody in the room was already thinking. There is no clean line between tribal knowledge and a work instruction, so most teams stall at the question and write nothing. Dave lays out the two questions that break the tie, the cost of leaving a gap undecided that almost nobody counts, and why a step that is already documented can keep failing anyway. This is the episode for anyone staring at a list of process gaps trying to work out which ones are actually worth doing something about. What You'll Discover: • Why nobody will give you a straight rule about what to document, and who benefits from that • The two questions that decide it: would this work at double the headcount, and what does it cost every time somebody gets it wrong • Why exposure decides what gets documented, not completeness • The hidden cost of a gray area, and the private calculation your team runs several times a day because of it • Why the person who knows the process best is the worst judge of what needs writing down • The billing step that was in the work instruction the whole time, and still kept getting missed • Why writing it down does nothing when the step depends on somebody remembering • The difference between a training problem and a system problem, and the one question that tells them apart • Why operator error, operator retrained is a prediction rather than a resolution • What designing it out actually means, and why building the tool first just automates the wrong process faster • The third answer nobody talks about, and why deciding to write a document is not the same as fixing anything If your team keeps working around the same thing, or somebody just told you the fix is a new SOP, start here. You have more than two options, and the one everybody reaches for first is usually the third best. Dave closes with four questions you can run against a single process on Monday morning.

Dave Crysler sits down with Glen Antwiler, founder and CEO of Right Fit PEO, who built, ran, and sold his own PEO before moving to the buy side of the market. Glen explains what a professional employer organization actually is, where the savings really come from, and why only about 50 of the roughly 600 operating in this country carry the IRS certification that determines who is liable when payroll taxes get misfiled. The conversation gets into admin fee spreads, the widely repeated myth that PEOs stop making sense at 100 employees, and a renewal timing play most owners have never heard of. What You'll Discover: • What a PEO actually is, and why the shared benefit pool, not the bundled services, is where the savings come from • The difference between a certified PEO and a non-certified one, and why the IRS treats the two completely differently • Why only about 50 of roughly 600 PEOs carry that certification, and what Glen found when he pulled the report on who recently lost it • How admin fees range from $85 to close to $300 per employee per month for the same 25 person company • Why the rule that PEOs stop making sense at 100 employees does not survive a simple follow up question • How carve outs let a company keep an existing broker or workers comp policy inside a PEO relationship • Why one bad year on a level funded plan can quietly close the door on the option you would want next • What actually changes for multi state hiring, state unemployment accounts, and compliance when your people are spread across the country • Why switching providers is half of Glen's business, and what that says about how the first decision usually gets made • The renewal timing move Glen calls a double dip, and why the weeks before a January renewal are the leverage point Most owners inherit their payroll and benefits setup from a warm referral and never look at it again until the renewal shows up. If you are heading into Q4 with a renewal on the desk and no real idea whether what you have is competitive, properly certified, or priced anywhere near the middle of the market, this conversation gives you the questions to ask before anyone tries to sell you anything.

Dave Crysler breaks down Overall Equipment Effectiveness, the traditional manufacturing KPI that gets sold as a solution far more often than it gets used as a diagnostic. After a call with a machine monitoring vendor, Dave lays out what OEE actually measures, why two plants with identical scores can have nothing in common, and why a high number can sit right next to a growing backlog and shrinking profitability. This is the episode for the operator who has never tracked OEE and is being told they should. What You'll Discover: • What OEE actually measures and the three factors that multiply together to produce the score • Why the metric follows the problem, and what goes wrong when you pick the metric first • How two plants can both hit 85% while having completely unrelated issues driving the number • Why a metric that can be influenced without solving anything becomes a vanity metric • The blind spot nobody mentions: OEE never asks whether anybody ordered the parts • What happens when you drive up efficiency on a machine that is not your constraint • Why elevating a constraint usually takes ingenuity and conversations, not capital • The three conditions that make OEE genuinely worth tracking • How your lens of experience decides which solution you reach for, including Dave's own bias • The legal pad exercise you can run Monday morning without buying anything If your backlog is growing, your capacity feels constrained, or somebody just put a capital request for new equipment on your desk, this episode will save you from measuring the wrong machine. Before you buy sensors and software, there is a two week exercise with a notepad that will tell you more about your operation than a dashboard will. Dave walks through exactly how to run it.