Exit Algorithms

The episode contains solid operational principles (visual management, flow, data-driven decision-making) and specific examples (60% of products at loss, 103-to-51 person turnaround, 36% YoY growth), but much of the advice is foundational rather than novel - walking factory floors, having good processes, and understanding financials are well-established operational practices. The AI section adds some tactical value (Notebook LM, markdown documents for prompt consistency) but remains surface-level.

“if you walk into a maintenance area and that maintenance area isn't well maintained and cleaned and organized, then right away that raises the question: what are you doing with the equipment that's out on the floor?”

“at one company, 60% of the products we made were at loss. You know, we wrap dollar bills around everything we sent out the door.”

Wayne's approach is pragmatic and operationally sound, but not particularly contrarian or first-principles thinking. The core ideas - principles over playbooks, hiring the right people, financial discipline before exit - are standard in operations and PE circles. His observation about listening to complainers as proxy for organizational health is somewhat fresh, but the overall framework is conventional operational wisdom.

“I really like principles, you know, over people that say, Hey, well, we have a playbook. Because if that something changes, that playbook may not function as well. But the principles will still carry forward.”

“whoever I've gone into a company, I've always asked like, like, who's the biggest complainer in the company? ... I found is about 70, 80% of the time, you know what, everybody else is kind of shut down.”

Wayne is a highly credible practitioner: three-decade operations leader, four successful PE portfolio turnarounds, Air Force background with Toyota exposure, and currently active in PE operating roles. He has direct, hands-on experience with the subject matter (not a theorist or career podcaster) and speaks with authority earned from executing complex operational transformations at scale.

“He's a private equity operating executive with four successful portfolio company turnarounds under his belt. He's a US Air Force veteran and three decade operations leader.”

“the biggest turnaround I did, I walked in, you know, on day one and there was a hundred and three people, day two or I'm sorry, day forty five. We were down to fifty one people.”

Wayne provides concrete numbers and examples: 60% products at loss, 103-to-51 headcount reduction, 36% YoY revenue growth, triple-digit bottom-line growth, $385 profit after 17 years of losses, 45-day timeline for major layoffs. He names tools (Notebook LM, ChatGPT, Claude, Perplexity) and gives specific metrics (material costs at 48-50%). However, he avoids naming actual companies and some advice remains somewhat vague ("walk the factory floor").

“at one company, 60% of the products we made were at loss.”

“the biggest turnaround I did, I walked in, you know, on day one and there was a hundred and three people, day two or I'm sorry, day forty five. We were down to fifty one people.”

Pete asks reasonable follow-up questions and probes specific areas (first 30 days, integration challenges, team building, AI usage), but rarely pushes back or challenges Wayne's claims. The conversation is friendly but surface-level; Pete doesn't dig into contradictions, ask for more evidence, or challenge assumptions. Follow-ups are generally straightforward rather than incisive (e.g., 'what are some things have you seen examples of it going wrong?' instead of pushing on a specific claim).

“what are some of those those things that you look at in in the first thirty to days you know, take a private equity acquisition example.”

“as a you know, business owner potentially selling to to private equity, are is there any advice you you might give someone in in those shoes?”