The Manufacturing Edge - For Ops Leaders

The episode covers legitimate SIOP fundamentals with some useful frameworks - data centralization, capacity modeling, bottleneck identification - but relies heavily on abstract explanations and general principles. While there are practical ideas (switching product mix, outsourcing, equipment investment decisions), they lack depth and specificity. The guest repeats key points across multiple exchanges without drilling into novel territory, and much of the conversation consists of reframing rather than new insight.

“if you think about it, uh, in the past, with less complexity, people were able to quickly respond to changes or to variations, the order patterns that were coming. So being reactive was a little bit easier today”

“you could try to shape the demand. You might be able to look at opportunities to outsource some of the business throughout periods of year to alleviate that constraint”

The core message - that disconnected spreadsheets, poor data discipline, and siloed functions hurt manufacturing planning - is not novel and is widely discussed in operations circles. The recommendation to centralize data, build capacity models, and use Power BI reflects standard industry practice. There are no contrarian insights, counterintuitive frameworks, or first-principles arguments that distinguish this from dozens of other SIOP-focused consulting pitches.

“if your SIOP process still runs on disconnected spreadsheets, conflicting numbers from different systems, and forecasts that no one fully trusts, it's not really a planning system”

“So throughout everybody has migrated to Excel. So we have these powerful ERP systems that MRP functionalities that people believe are going to be the one all end all”

Brian Cromer holds a meaningful title (Managing Director of Global Supply Chain at TBM Consulting) and references hands-on client work. However, the transcript offers no evidence of personal execution at scale - no founder-level P&L ownership, no personal operational turnarounds, no specific companies led or metrics personally achieved. He speaks as a consultant synthesizing patterns rather than a practitioner who has lived the complexity. His experience is real but the episode does not establish him as a standout operator.

“Brian Cromer is TBM's managing director of Global Supply Chain”

“So we do a lot of assessments of SIOP processes”

The episode includes two brief client examples (global multi-plant expedited freight problem, siloed sales-to-manufacturing communication failure) but lacks concrete numbers, company names, timelines, or quantified impact. Recommendations are vague: 'shift production between sites,' 'build inventory,' 'invest in equipment,' without any specific case metrics or financial outcomes. The Power BI discussion mentions the tool but no actual before/after performance data.

“a global business that had multiple plants on different ERP platforms. Each one of the businesses was really siloed, looking at their own capacity constraints, their own capabilities, and they wouldn't react quick enough. So the result of that was having to shift some of the production between the different sites where the capabilities would be the same. But because they didn't plan far enough ahead, it ended up costing a lot of freight expense”

“so we typically will see, uh, a drop in inventory because we're able to plant better, set the right inventory levels”

The host (Will Merriman) asks competent, logical follow-up questions that build on previous answers (e.g., 'Are there constraints on data before considering SIOP?' 'What does that empower internally?'). However, the conversation lacks genuine push-back, challenge, or productive disagreement. The guest is never questioned on vague claims, asked to defend a position, or invited to resolve contradictions. This reads as a polished but fundamentally softly-conducted consulting interview rather than adversarial probing.

“Yeah, and I was about to say too. Are there any warning signs? Seems like you covered them on what companies might be able to look to and say, okay, this is, um, a red flag”

“And once you get all that information together, you know, it can be a long process to synthesize and summarize, but also detail all that data.”