Every operator says they want to be more efficient, and Dave Crysler argues that's exactly the wrong goal. In this solo episode he unpacks the one-word distinction that quietly holds most operations back, the difference between efficiency and effectiveness, and why nearly 30 years on the shop floor taught him that the two are not the same thing. He walks through why the localized efficiency we're all trained to chase can look like progress on the inside while the customer never feels a thing, and shares a recent custom manufacturing client that cut lead times from 30 to 45 days down to 5 to 10, with no additional resources. What You'll Discover: • Why the word efficiency may be the reason your operation stays stuck • The difference between efficiency, utilization, and effectiveness, in plain language • How chasing efficiency inside every department quietly sabotages the whole system • The rowing team analogy that makes effectiveness click in ten seconds • Why increasing flow means some parts of your business should be less efficient on purpose • How a custom manufacturer cut lead times from 30 to 45 days down to 5 to 10 with the same, and eventually fewer, resources • The teeter totter effect, why fixing one bottleneck just moves the constraint somewhere else • Why buying scheduling software almost never fixes a scheduling problem • The real cost of solving at the symptom level, in margin and in cash If your team feels busy but the numbers won't move, you're probably measuring the wrong thing. Start by looking at where the work actually waits, not at how busy everyone is. That's where your next real gain is hiding, and it usually doesn't cost a dime.

Every business is already running on a system. The only question is whether anybody actually designed it. In this solo episode, Dave Crysler breaks down the difference between running by design and running by default, and why the problems that keep coming back are not bad luck or bad people. They are the designed output of a system nobody chose. Dave explains how default systems quietly accrete over time, why you can't see yours from the inside, and the order you have to follow to rebuild it on purpose, without buying anything new. What You'll Discover: • Why firefighting is a system problem, not a discipline problem, and why you can't out-discipline your way out of it • What a "default system" actually is and how it accretes one shortcut and one bolt-on at a time • Why your recurring problems are the system working exactly as it was unintentionally built to work • How your "lens of experience" keeps the real problem invisible from the inside • Why swapping one CRM or ERP for another just extends the same broken system • The hidden tax a default system charges your people, and why your best ones leave first • Why the order matters: planning, then people, then process, then technology • How to use a Cost of Chaos calculator to put a real dollar number on the problem • The crawl, walk, run path from default to design you can start Monday morning If you feel like you are running the same fire drill every week, watching your capacity stall every time you try to grow, and asking your team why the output isn't there, the problem probably isn't your effort or your tools. It's the system underneath, and it's fixable. Start by making it visible, then design it on purpose.

Dave Crysler sits down with Greg Harrod, a 30-year manufacturing leader and Certified Working Genius facilitator, to unpack a pattern that quietly drains operations teams: the most dependable person on the floor is often the closest to burnout. Because leaders trust their best people, they keep handing them more, until reliable becomes overloaded and the resignation nobody saw coming lands on the desk. Greg and Dave dig into why it happens, the early warning signs most leaders miss, and how to redistribute ownership without lowering standards or sacrificing accountability. What You'll Discover: • Why the people you trust most are the ones you unknowingly push toward burnout • The difference between being good at the work and being energized by it, and why it matters • A simple two-question check that surfaces burnout before a resignation does • How "just because you can doesn't mean you should" reshapes the way you assign work • The early warning signs that a dependable person is running out of road • Why overload is almost always a clarity problem, not a people problem • How to redistribute work across a team without lowering standards or accountability • The story behind the Working Genius model and what it reveals about overloaded leaders • What to actually do Monday morning if you recognize one of these people on your team If you've got a go-to person who never drops the ball, this conversation is your early warning system. Greg and Dave give you the language and the questions to spot the strain before it costs you your best person. Greg's Leadership Clarity Scorecard is a ten-minute starting point you can find at leadershipclarityscorecard.com.

Before anybody on your team makes a sale, builds a product, or delivers a service, they are logging into tools, running reports, and trying to piece together what to do next. Dave Crysler calls this admin overhead, the hidden time tax of figuring out what the work is before anyone can actually do it. In this solo episode, he breaks down how to flip the model: instead of making people pull information out of your systems, you push the contextualized action straight to them. It is technically a push, but as Dave explains, it is still working at the demand of the customer, and it is one of the cheapest ways to get capacity back without hiring anyone or buying anything. What You'll Discover: • Why the first hour of your team's day disappears before real work even starts • What admin overhead actually is, and why it never shows up on a report • The push versus pull reframe, and why pushing information is not the same as pushing work • How the full kit discipline from Theory of Constraints applies to office and sales work • What a pushed quote follow up looks like in practice, and the time it saved a two person team • The difference between automation and AI, and why accuracy is the trap most people miss • Where pushing goes wrong, and how to avoid creating a new firehose nobody reads • Why this is a process problem, not a software purchase, and where technology actually belongs • The one thing you can do Monday to start cutting admin overhead without spending a dime If your best people are buried in busywork and you keep thinking the answer is more headcount or another tool, this episode offers a different lever. Stop making your team hunt for the work. Push it to them, and let their time go where it actually matters.

Every operations leader has heard the advice: capture your tribal knowledge before it walks out the door, write the SOP, get it out of people's heads. Dave Crysler breaks down why that advice keeps failing, and it is not the part you think. The hard part was never writing the document. It is pulling the knowledge out of the person in the first place, and that is the gap nobody talks about. Dave walks through a real story of a lab that solved a problem they had lived with for over a decade in a single conversation, then lays out the workflow that actually gets the knowledge out: capture, observe, synthesize. What You'll Discover • Why most SOPs end up as documents nobody uses, and what the format gets wrong • The real reason your best people can't just write down what they know • How experience makes your own knowledge invisible, even to you • Why a blank screen kills knowledge capture before it starts • The kinds of questions that actually pull tribal knowledge out of someone's head • How "how deep is deep enough" works the same way a five whys does • The capture, observe, synthesize workflow and why skipping a step breaks it • How one captured insight can travel far past operations into sales and marketing • Why technology comes last when you are documenting what your team knows • What to do Monday morning to start capturing tribal knowledge with no tools at all If you have a team where one person holds the knowledge everyone else depends on, this episode is for you. Stop telling people to "go document it" and start asking the questions that actually surface what they know. The knowledge that runs your shop already exists. The work is pulling it out the right way. To get a running start, the Operations Workbench we built walks you through this exact flow, capture, observe, synthesize, and it is free to use. The tool is optional. The questions are not.

Dave Crysler built his own AI email tool. He also tells clients not to build their own software. In this episode, he resolves the contradiction and lays out the honest skill ledger behind a build that costs three dollars a month to run, processes fifty to a hundred marketing emails a day, and required twenty years of self-taught coding background plus the one skill almost everyone underestimates: process clarity. What You'll Discover: • The four-part test for whether building beats buying for a specific tool in a specific context • Why the real maintenance bill on a homemade tool does not come due in month one • What actually leaves a Microsoft tenant on each AI API call and how to think about the data egress • Why commercial tools cost ten times what bespoke tools cost (and what the premium is actually funding) • How to evaluate an AI agent proposal sitting on your desk using Claude or ChatGPT in an afternoon If you have an AI vendor pitch on your desk, an inbox you cannot keep up with, or a build-versus-buy decision you have been putting off, this episode gives you the framework to think it through honestly. Process clarity is the operational skill you already have. The technology has finally caught up to it.

A couple of weeks ago Dave Crysler sat in on a monthly leadership meeting where a metric on the dashboard was lying. The team caught it in fifteen minutes and changed how they measured. That moment is the entire problem with most manufacturing leadership dashboards. In this solo episode, Dave breaks down the difference between metrics that report the news and KPIs that drive action, why most weekly leadership meetings feel like theater, and the one question every KPI has to pass before it earns a spot on your weekly board. What You'll Discover: • Why most of your dashboard is probably decoration, and the one test that cuts it down to what actually matters • How to tell if a metric is "reporting the news" versus telling you what to do tomorrow • The reason consensus design fails when leadership teams try to build dashboards together • Why the dashboard should be built between meetings, not inside them, and how to do that • The version-five story: how one client moved from cycling-through-metric-ideas to a working dashboard in about five weeks • How to spot meeting theater in your own organization and what to do about it • The gaming risk every metric carries, and how to track behaviors and outcomes together to catch it • What to do Monday morning if your weekly leadership meeting has stopped driving action If your weekly leadership meeting feels like an interrogation about numbers nobody can change, you are not alone. Most of the dashboards I see in mid-market manufacturing are stacked with metrics that tell you what already happened with no way to influence what comes next. The fix is not to add more discipline to the meeting. It is to cut the dashboard down to metrics that trigger specific actions and to do the design work in the right room.

Most leaders feel capacity tight and immediately start writing a job description. Dave Crysler pushes back on that reflex in this solo episode, drawing on a recent client engagement where synchronizing manufacturing flow more than doubled throughput, cut lead times from weeks to four days, and dropped work-in-process to almost nothing. The team got smaller during this period, not larger, because natural attrition was not backfilled. The capacity was already there, hidden behind a system nobody had ever synchronized. Dave breaks down why the hiring reflex is so strong, why most "capacity problems" are actually synchronization problems wearing capacity problems' clothes, and why the constraint does not migrate between departments on a weekly basis the way most leaders think it does. If your bottleneck has been moving for six to twelve months, that pattern itself is the diagnosis. What You'll Discover: • Why the hiring reflex is older than the problem it tries to solve, and how operations training reinforces a local lens that misses system-level constraints • The three kinds of problems every "capacity-constrained" company actually has, and why synchronization is by far the most common • The bottleneck-chasing trap, and the conversation Dave had recently with a leader who had been moving people around for over a year without ever synchronizing flow • The counterintuitive reality that every touchpoint outside the constraint needs to be deliberately less efficient by design • A real client case where throughput at the control point doubled (and then doubled again) while the team got smaller through natural attrition • What the shop floor feels like when chaos becomes calm, and why the operations leader at this client said "I don't even know what to do. It's so quiet." • The three conditions where hiring really is the right call, instead of synchronizing first • Why this is not a job you can self-diagnose from a book, and what to actually do this week before writing another job description If you are about to write a job description because capacity feels tight, this episode is the conversation worth having first. The lens of experience says you have a hiring problem. The lens of experience is almost always wrong about that.

Two customers ordered the same bolt. The ERP treated both as custom-engineered transactions, kicking off two full procurement loops that never needed to happen. The team built spreadsheets to compensate. Leadership wanted a new system. In this solo episode, Dave Crysler walks through a real mid-market manufacturing case study where the ERP was doing exactly what it was configured to do, and the configuration was wrong for the business model the division was actually running. He breaks down the audit conversation, the reconfiguration that fixed it without replacing the system, and the structural pattern that makes this misconfiguration so common after acquisitions and growth. What You'll Discover: • Why the impulse to replace your ERP is almost always the wrong first move, even when the frustration is real • The financial incentive behind the "you need a new ERP" conversation that vendors and consultants don't always disclose • The reframe of what an ERP fundamentally is, and why no software is "smart" on its own • The two-customers-one-bolt case study and what it reveals about configuration mismatch • How a custom-manufacturing ERP configuration crippled a spare parts and service division • The audit conversation that surfaces the structural mismatch in the first couple of hours • The reconfiguration work that fixed the system without replacing it • Three versions of the configuration-vs-business-model mismatch every mid-market manufacturer should know • When replacement actually is the right call, and the markers that signal it • Why this pattern repeats so often in mid-market manufacturing after acquisitions and growth Most mid-market manufacturers don't need a new ERP. They need to go back to the configuration with fresh eyes and ask whether the system is set up for the business they are actually running today. If you're seeing the workaround layer build up around your existing system, this is the conversation to have before you start shopping for a replacement.

Dave Crysler unpacks why most change initiatives die on the shop floor and the sequence that makes them actually stick. Most rollouts answer one of three questions, sometimes two. Almost never all three, in the right order. Why, What, and How aren't just questions to cover in a kickoff deck. They're a non-negotiable sequence, and most leaders run them backwards. In this solo episode, Dave breaks down the failure mode he sees every week: a trained team that reverts in six weeks, a leader who assumes resistance, and a rollout that started with How and never circled back to Why. He walks through what each layer of the sequence actually requires on the floor, and what to do Monday morning if you've already rolled something out that didn't stick. What You'll Discover: • Why leaders consistently default to How and skip the first two questions, and the leadership-perspective trap underneath that pattern • What the Why actually sounds like when it's done well, including a real example from a $100M services business facing an AI-driven survival window • Why the What isn't the description of the new process, it's the answer to "what about me" from the operator's perspective • How to build the How with the people who have to live in it, instead of handing it down, anchored in a recent LinkedIn post that nailed the move • Why skipping Why turns the What into a mandate, and skipping What turns the How into a punishment • The exact admission script to use when you need to re-anchor a rollout that's already off the rails • Where this sequence fits with Clarity, Consistency, Accountability, and why CCA is the universal diagnostic but Why/What/How is the change-specific instrument If you've ever watched a well-trained team revert to the old way six weeks after launch, this is the episode. The fix isn't more training. It's running the rollout in the right order.