Discover
Everyday Business Problems
Everyday Business Problems
Author: the Crysler Club
Subscribed: 0Played: 9Subscribe
Share
© the Crysler Club
Description
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!
212 Episodes
Reverse
Dave Crysler breaks down why cross-training so often fails right when a business needs it, starting with a company whose order entry backups were already trained but hadn't done the work in so long they couldn't step in when most of the department was out the same week. He explains the gap between being trained and being ready, how backups end up learning the expert's tacit version of the job, and why the person doing the training can feel like their job security is on the line. He also walks through the skills matrix he uses to spot gaps before they hurt and how to get backups ready ahead of planned time off. What You'll Discover: • Why having people cross-trained doesn't mean anyone can cover the work • The difference between showing up for training and practical application • How cross-training passes along tribal knowledge instead of documented best practices • Why the person doing the training can feel like they're giving away their job security • The delicate balance between backups who are ready and backups who become extra hands for daily work • How getting backups a few reps before a planned absence moves you from reactive to proactive • What preventive maintenance and cross-training have in common • How to lay out a simple skills matrix, and how detailed it really needs to be • How to audit your skills matrix against who was out last and who is out next If your team has been cross-trained on paper but the work still stops when somebody calls out, this episode is for you. With the holidays coming and a lot of people scheduled off, it's a good time to find out how much coverage you actually have.
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.



