Everyday Business Problems

Hosted by the Crysler Club

BusinessExplicit

Website RSS feed LinkedIn Facebook Instagram YouTube

Episodes

190

Latest episode

Jun 2026

Language

About the show

When it comes to your business, you know everything – except what you don't. Hosted by David Crysler, each episode we dive into finding and solving everyday business problems. Learn from business leaders and subject matter experts about the challenges they've overcome, and the challenges they still face. Join us for fresh insights, real talk, and inspiration to grow your business!

Listen to episodes

60 recent

June 16, 202625 min

Your Team Wastes the First Hour of Every Day

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.

June 9, 202621 min

Everybody Says "Capture Tribal Knowledge." Nobody Tells You How.

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.

June 2, 202625 min

The AI Skill No One Talks About (It's Not Coding)

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.

May 26, 202619 min

Most of Your Dashboard Is Decoration

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.

May 19, 202627 min

How a Client Doubled Throughput With Fewer People

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.

May 12, 202624 min

Two Customers, Same Bolt: How a Misconfigured ERP Trapped a Spare Parts Division

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.

May 5, 202625 min

Most Change Rollouts Start at the Wrong End

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.

April 28, 202632 min

Why Owner Dependency Is a Today Problem, Not an Exit Problem

Most of the conversation around owner dependency in manufacturing happens through the lens of an exit. Buyers discount your business, your valuation suffers, your retirement plans take a hit. In this solo episode, Dave Crysler reframes the conversation. For founder-led manufacturers, owner dependency is a today problem first, an exit problem second. He breaks down what it actually looks like up close, why documenting your processes won't fix it, and the practical move you can run on yourself this week, without hiring anyone. What You'll Discover: • Why most of the advice on owner dependency is missing the point, and what changes when you frame it as a today problem instead of an exit problem • The diagnostic patterns that show up before a meeting even happens, including "today it's blue, tomorrow it's green" and the favoritism trap • Why documenting your SOPs won't fix owner dependency, and the keystone problem nobody talks about • How Clarity, Consistency, and Accountability work in sequence, and why most owners try to skip straight to the third one • The "hold up a mirror" conversation and what it actually looks like when an owner faces what their day-to-day behavior is doing to the business • A practical exercise any founder can run this week with a sheet of paper and tally marks • What changes when an owner actually does this work, including the strange feeling of calm that catches most of them off guard • Why bringing people up doesn't remove your stress, it shifts it • The reason information is not the bottleneck and readiness is, and why the people who need this work the most are the least likely to hire someone to help The work of fixing owner dependency goes deeper than documenting your processes. It's about Clarity, Consistency, Accountability, and the leadership development underneath all three. If you're tired of being the bottleneck in your own business, the right time to start is this week, while you're still in the building. Start with paper and tally marks. Track your time. Track your decisions. The size of the dependency you're sitting on will reveal itself.

April 21, 202651 min

Transforming the Healthcare Supply Chain: Building the Bridge to What's Next (Part 3 of 3)

Dave Crysler wraps the three-part series with Cody Fisher, President of Concordance Innovations, on transforming the healthcare supply chain. This episode zooms out to the bridge between today's operations and what's next, the leadership mindset required to stay nimble in a landscape changing by the hour, and why the real constraint on innovation isn't capability anymore. It's prioritization. What You'll Discover: • Why "can we" is no longer the hard question, and how "should we" and "how do we" are replacing it • The shift from great employees who do it all themselves to great employees who build virtual teams around them • Why three-year plans are getting completed in 60 days, and what that means for how leaders should plan • How the journey itself uncovers bigger problems than the ones you set out to solve • Why not innovating isn't standing still, it's falling behind, and how to reframe the conversation with your team • A tactical reframe for the vendor conversation: tell them the problem and what you can spend, not what you want them to build • Why the leaders winning right now are defining outcomes, not destinations, and staying flexible on the route Whether you lead supply chain operations in healthcare or any industry navigating this level of change, this conversation gives you a practical framework for moving forward when the ground keeps shifting under you.

April 14, 202649 min

Transforming the Healthcare Supply Chain: The Reality of the Day-to-Day Operations (Part 2 of 3)

Dave Crysler welcomes Cody Fisher back for part two of their three-part series on transforming the healthcare supply chain. This episode gets tactical, digging into why supply chain teams stay stuck in firefighting mode, how leaders can build a culture of innovation without mandating it from a distance, and what it actually looks like to adopt AI and automation when your data is far from perfect. What You'll Discover: • Why most firefighting isn't caused by too many problems, but by no way to prioritize them • How Cody built a personal "shadow team" of AI agents to scale his own productivity • Why the gap between organizations embracing innovation and those resisting it widens by the hour, not by the quarter • The leadership principle that nobody is above the need to be more productive, and why it starts at the top • Why expecting AI tools to be 100% perfect is the fastest way to never use them, and how a 90/10 mindset changes everything • How to use automation to clean your data and leverage it simultaneously instead of waiting for perfect • Why the organizations thinking five steps ahead are stacking blocks in a different order than everyone else Whether you lead supply chain operations or any team stuck in reactive mode, this conversation offers a practical roadmap for moving from firefighting to forward progress.