In this episode we examine the true financial impact of staff turnover within the automotive workshop environment. AndrewUglow reveals why losing a productive technician is the most expensive event a business can face, often costing betweenone and a half to two times their annual salary. The discussion explores the hidden costs that fail to appear on standardreports and why the industry must move beyond the myth that technicians only leave for higher pay.Andrew explains the critical importance of the net promoter score for technicians and why current industry trends represent anuclear fire on the front lawn for workshop owners. The episode emphasises the three pillars of retention, recognition,reward, and resource, and reveals why people ultimately leave managers rather than businesses. By shifting the focus fromthe visible tip of the iceberg to the underlying cultural issues, Andrew demonstrates how workshops can begin to solve theirown skills shortage through better engagement.What You Will Learn:• Why staff turnover is the most expensive event in your workshop• How to calculate the true cost of losing a foreman or service manager• What the plummeting industry net promoter score means for your business• Why the excuse of more money is often a myth in departure interviews• How to implement the three pillars of technician retention• Why technician satisfaction is the real solution to the skills shortageKey Takeaways:• Staff turnover costs between 1.5 and 3.5 times a salary off the bottom line• People leave managers, they do not leave businesses• 70 percent of technicians in some surveys are detractors of the industry• Measuring staff satisfaction should be as rigorous as measuring customer satisfaction• Recognition, reward, and resource are the foundations of a stable teamNotable Quotes:• "The most expensive event in a workshop is technicians leaving, and more expensive than that is foreman leaving."• "We know the reality is that people leave managers, they don't leave businesses."• "If the technicians were satisfied, I doubt we'd have the skills shortage that we do."• "We've been stuck playing at the tip of the iceberg... and we've missed the really important things that are less visible."Andrew has a variety of free downloads and tools you can grab.Discover if your workshop is Retention Worthy here or visit his website, https://www.solutionsculture.com(https://www.solutionsculture.com) where the focus is on bringing reliable profitability to automotive workshop owners andworkshop management through the Retention, Engagement and Development of their Technical Professionals.This podcast was produced by 'Podcasts Done for You' https://commtogether.com.au (https://commtogether.com.au) .
May 13, 202622 min
How to Stop Repeating Your Instructions to Technicians
In this episode, we examine the common frustration of workshop leaders who feel they have to repeat instructions athousand times without seeing results. Andrew Uglow reveals why the issue is rarely the information itself, but rather thedelivery and the emotional state of the person receiving it. He introduces the TATS framework, which stands for Triage,Action, and Test, as a structured way to ensure that instructions are not only heard but correctly understood andimplemented.Andrew explains the critical importance of the triage phase, where the emotional state of both the foreman and thetechnician must be managed before any meaningful communication can occur. He shares personal stories from his time asa technician to demonstrate how a lack of clear instruction and testing can lead to embarrassment, stress, and repeatedmistakes. The discussion also covers the hidden costs of inaction and the importance of closing the capacity gap forworkshop foremen to prevent burnout and improve overall flow.What You Will Learn:• Why the meaning of a conversation depends entirely on the hearer's understanding• How the TATS framework can eliminate the mechanical butt kicking machine• What the triage phase involves and why it is the most skipped step in communication• Why technicians need to know the why behind an action to be successful• How to use the verbal test to ensure instructions are correctly installed in a technician's mind• What the hidden cost of inaction looks like on your workshop's bottom lineKey Takeaways:• The importance of building respect and rapport before giving instructions• How to identify if a technician is in a state to actually process information• The role of the Quality Information Model in improving service advisor to foreman handovers• Why blaming technicians for mistakes is often a sign of poor communication delivery• How to move from a reactive cycle to a proactive, friction-less workshop environmentNotable Quotes:• "The meaning of any conversation is on what the hearer understands, not what the speaker said."• "If my instructions are bad, my results are gonna be bad."• "We want to test that what you heard and what I said are the same thing."• "Meaning gets installed when they have to make sense of it internally before they can explain it externally."Andrew has a variety of free downloads and tools you can grab.Discover if your workshop is Retention Worthy here or visit his website, https://www.solutionsculture.com(https://www.solutionsculture.com) where the focus is on bringing reliable profitability to automotive workshop owners andworkshop management through the Retention, Engagement and Development of their Technical Professionals.This podcast was produced by 'Podcasts Done for You' https://commtogether.com.au (https://commtogether.com.au)
April 29, 202622 min
The Foreman Bottleneck: Why Your Best Technicians Are Burning Out and Breaking Your Workflow
Information Breakdown: Why Service Advisors Get Blamed for Communication Failures
n Episode 35 of the Friction-less Workshop Podcast, host Anthony Perl and automotive trainer Andrew Uglow tackle one of the most common sources of workshop friction: the complaint that service advisors don't provide enough information to technicians. But is this really about lazy advisors, or is there a deeper systemic problem?Andrew reveals why this complaint is actually a symptom of broken communication systems, not individual failures. He explores how technicians and service advisors literally speak different languages - one technical, one customer-focused - and why neither side fully understands what the other needs. The episode exposes how workshops inadvertently create information bottlenecks by failing to establish clear communication protocols.Key topics include the shared responsibility model for information flow, why technicians need to ask better questions instead of waiting for perfect information, and how service advisors can translate customer concerns into actionable diagnostic data. Andrew shares practical frameworks for creating effective communication systems that eliminate 80% of workshop friction.Listeners will discover why the "us versus them" mentality between front and back of house destroys efficiency, how to implement simple communication protocols that work, and why both technicians and advisors need training in each other's roles. The episode also addresses how modern workshop management systems can help or hinder communication, and why face-to-face interaction still matters in a digital age.Perfect for workshop owners tired of communication breakdowns, service advisors feeling caught in the middle, technicians frustrated by incomplete information, and anyone responsible for improving workshop efficiency. This episode provides actionable solutions for one of the automotive industry's most persistent problems.Keywords/Tags#ServiceAdvisor #WorkshopCommunication #TechnicianCommunication #WorkshopEfficiency #AutomotiveWorkshop #CommunicationBreakdown #WorkshopManagement #ServiceDepartment #TechnicianFrustration #InformationFlow #WorkshopSystems #AutomotiveIndustryCategoriesPrimary: Business > ManagementSecondary: Business > CommunicationTertiary: Technology > AutomotiveTarget AudienceWorkshop owners dealing with communication issuesService advisors feeling blamed for information gapsTechnicians frustrated by incomplete job informationService managers trying to improve efficiencyDealership fixed operations managersWorkshop communication trainers3. SHOW NOTESEpisode SummaryWhy do technicians always complain about service advisors not providing enough information? Andrew Uglow reveals it's not about lazy advisors - it's about broken systems. Discover how to create effective communication protocols that eliminate workshop friction and improve efficiency for everyone.Main Topics CoveredThe "service advisors don't give us enough information" complaintWhy technicians and advisors speak different languagesThe shared responsibility model for communicationHow workshops create information bottlenecksWhy waiting for perfect information wastes timeThe importance of technicians asking better questionsHow to translate customer concerns into diagnostic dataCreating effective communication protocolsThe "us versus them" mentality and its costsModern workshop management systems: help or hindrance?Why face-to-face communication still mattersTraining advisors and technicians in each other's rolesKey Insights & LearningsSystemic Problem, Not Personal Failure - When communication breaks down consistently, it's not about individual incompetence - it's about missing systems and protocols that should exist but don't.Different Languages - Technicians speak technical language (codes, systems, specifications) while advisors speak customer language (symptoms, concerns, experiences). Neither is wrong, but translation is essential.Shared Responsibility - Information flow isn't just the advisor's job. Technicians must actively seek clarification and ask diagnostic questions rather than passively waiting for complete information.The 80/20 Rule - Simple communication protocols can eliminate 80% of information-related friction. You don't need perfect systems, just consistent ones.Cross-Training Value - When advisors understand basic diagnostics and technicians understand customer communication, the entire workshop operates more smoothly.Stories & Examples SharedThe Translation Problem - Real examples of how customer descriptions like "it makes a funny noise" need to be translated into diagnostic questions about when, where, and under what conditions.The Waiting Game - How technicians waste time waiting for "complete" information instead of proactively gathering what they need to start diagnosis.The Blame Cycle - Why the "us versus them" mentality between front and back of house creates a self-perpetuating cycle of poor communication and mutual frustration.Simple Protocol Success - Workshops that implemented basic communication checklists saw dramatic improvements in first-time fix rates and reduced comebacks.Communication protocol templatesWorkshop management system best practicesCustomer interview frameworksDiagnostic questioning techniquesAction Items for ListenersFor Workshop Owners/Managers:Audit your current communication systems - do they actually exist or are they informal?Create simple, written communication protocols for common scenariosImplement regular front-of-house and back-of-house meetingsInvest in cross-training: advisors shadow technicians, technicians shadow advisorsStop blaming individuals and start fixing systemsFor Service Advisors:Learn basic diagnostic questioning techniquesUnderstand that "the customer said..." isn't enough - dig deeperTranslate customer language into technical language before passing to techniciansDon't be afraid to go back to customers for clarificationBuild relationships with technicians -...
January 15, 202623 min
Shared Responsibility: Why Workshop Success Depends on Everyone Playing Their Part