Michael Curtis Broughton

An industrial engineer who came up through military logistics on testing systems under stress, why design and execution are different skills, and the projects he will not take.

Michael Curtis Broughton works at the intersection of industrial engineering, supply chain operations and military logistics — designing and improving the systems that move goods, people and resources. That covers distribution centres, transportation networks and logistics control systems, across both military environments and large-scale commercial supply chains, particularly retail distribution.

The method he describes is unsentimental about paper design. He tests systems under peak demand, disruption scenarios and failure points, on the principle that anything holding up under pressure will hold up in normal conditions. That instinct comes from a setting where a logistics failure has immediate consequences.

Designing Systems That Move Things

Please introduce your work in industrial engineering and logistics, and describe the role you play in shaping operations and long-term systems.

I work at the intersection of industrial engineering, supply chain operations, and military logistics. My role is to design and improve systems that move goods, people, and resources efficiently. That includes distribution centers, transportation networks, and logistics control systems. I focus on execution. I look at how a system performs under real conditions, then adjust it to improve reliability, cost, and speed over time.

How do you approach building teams and systems to execute complex logistics operations?

I start with the system, not the org chart. You define the process flow first. Then you identify constraints. After that, you build teams around those constraints. Some work remains internal if it requires tight control, such as core logistics planning. Other parts can be external, like specialized automation or software integration. I usually use a hybrid model. The goal is to keep decision-making close to the operation while using external expertise where it adds speed.

From an operational perspective, how do you ensure your work stands out in a crowded field?

I focus on execution quality. Many people can design a system on paper. Fewer can run it at scale. I test systems under stress. That includes peak demand, disruption scenarios, and failure points. If it works under pressure, it works in normal conditions. That approach comes from military logistics. If a system fails there, the consequences are immediate.

Where He Works, and What Breaks

Which industries or environments do you primarily serve, and how has that focus evolved?

I work across military logistics and large-scale commercial supply chains, especially retail distribution. Over time, the focus shifted from tactical execution to system-level design. Earlier in my career, I was operating inside systems. Now I design and improve them. The common factor is scale and complexity.

What problems do organizations most often bring to you, and how do you decide what to take on?

Most problems relate to inefficiency, cost pressure, or lack of visibility. That could be slow warehouse throughput, poor inventory placement, or inconsistent delivery performance. I take on work where the problem is clearly defined and measurable. If there is no baseline or no way to measure improvement, it’s difficult to execute.

How do you stay ahead of changes in supply chain and logistics systems?

I rely on a mix of direct observation and structured learning. I study system performance, not just trends. I also stay engaged in academic research and applied engineering work. The key is to connect theory to execution. If a new approach cannot be implemented in a real operation, it has limited value.

Trust, Success and Handover

What does long-term trust look like in your work, and how do you build it?

Trust comes from consistency. You deliver results, and you communicate clearly. I focus on transparency. If a system has limitations, I state them upfront. Over time, that builds confidence. Most long-term relationships come from repeat execution, not one-time success.

How do you define success in logistics and operations?

Success is measurable. It includes throughput rates, cost per unit, delivery accuracy, and system uptime. You set targets at the start. Then you track performance against those targets. If the system consistently meets or exceeds them, it is successful.

What responsibility do you have after a system or project is delivered?

The system has to sustain performance. That means follow-up, monitoring, and adjustment. I stay involved long enough to confirm the system is stable. After that, the internal team needs to own it. A system that only works with constant external input is not well designed.

Value and Fit

How do you think about pricing and value in your work?

Value is tied to measurable outcomes. If a system reduces cost or improves throughput, that value is clear. Pricing needs to reflect the complexity of the problem and the impact of the solution. I avoid models where the value is unclear or subjective.

How do you balance accessibility with maintaining high standards?

Not every operation is a fit. I focus on environments with sufficient scale to justify system-level improvements. Smaller operations may not need that level of engineering. Fair value means both sides understand the scope, the effort, and the expected outcome.

Have you turned down opportunities, and why?

Yes. If the problem is not clearly defined, or if there is no alignment on execution, I do not take it on. I also avoid situations where decisions cannot be implemented. A good design without execution authority does not create value.

Pressure, Innovation and Culture

What challenges have shaped how you operate today?

Early combat experience had the biggest impact. In those environments, logistics failure has immediate consequences. That changes how you think about risk and planning. It also reinforces the importance of redundancy and adaptability in systems.

How do you create space for innovation while maintaining discipline?

Innovation comes from controlled testing. You isolate a variable, test it, and measure the outcome. At the same time, the core system remains stable. You do not change everything at once. That balance allows improvement without disrupting operations.

What role does culture play in performance?

Culture determines how people respond under pressure. In logistics, pressure is constant. I focus on accountability, clear communication, and problem-solving. I model direct communication and attention to detail. Those behaviors tend to scale across teams.

Looking Ahead

Looking ahead, what impact do you want your work to have?

I want to improve how large systems operate under stress. That applies to both military and commercial environments. The goal is reliability. If systems perform consistently in difficult conditions, they create long-term value.

How has your approach to leadership and operations evolved?

It moved from task execution to system design. Early on, the focus was on completing the mission. Now it is about building systems that allow others to execute effectively. The principles are the same, but the scope is larger.

What emerging changes in logistics or engineering are most important to you?

Automation and data integration are important, but only when they improve execution. Tools like robotics and advanced slotting systems can increase efficiency. The challenge is integrating them into existing operations without creating new constraints.

What advice would you give to someone entering this field?

Focus on fundamentals. Understand how systems actually work. Spend time in operations, not just analysis. One key lesson is that design and execution are different. A system is only as good as its performance in real conditions.

Key Learnings

• Design the process flow and identify constraints before building the org chart — teams should be shaped around the bottleneck, not the other way round.
• A system tested only under normal conditions has not been tested; peak demand and disruption scenarios are where the design is proven.
• Without a baseline there is no way to demonstrate improvement, which makes measurability a precondition for the work rather than a reporting detail.
• A system that only functions with constant external input is a design failure, however well it performs while the consultant is present.
• A good design without execution authority creates no value — which is why alignment on implementation matters more than the quality of the recommendation.

Supply Chain Optimization: Where the Gains Actually Come From

Supply chain optimization is often sold as a technology purchase. In practice it is closer to a diagnostic discipline: finding where a network’s time, cost and inventory are genuinely being consumed, and then deciding which of those constraints is worth relieving. The software matters, but it is downstream of that judgement.

The recurring gains tend to come from a short list. Inventory placement — holding the right stock at the right node — usually beats holding less stock overall, because service failures are more expensive than carrying cost. Warehouse throughput responds to slotting, pick-path design and labour scheduling long before it responds to automation; the advanced slotting systems Broughton mentions work precisely because they attack travel time, which is the dominant cost inside a distribution centre. Transportation gains come from consolidation and routing rather than rate negotiation. Visibility is the enabler for all of it: you cannot optimise a flow you cannot see.

What separates programmes that deliver from those that stall is rarely analytical sophistication. It is the presence of a baseline. Broughton’s refusal to take work where there is no way to measure improvement is not caution — it is the recognition that without a starting measurement, any change becomes unfalsifiable, and the organisation cannot tell an improvement from a reshuffle.

The second failure mode is optimising a network for conditions that do not persist. A supply chain tuned tightly for steady-state demand tends to be brittle when demand spikes or a node fails, and the last several years have made that trade-off vivid for most operators. This is the argument for stress-testing rather than efficiency-maximising: a system that is 5% less efficient but degrades gracefully under disruption will usually outperform one optimised to the edge, measured over any period long enough to include a bad quarter.

Scale is the practical qualifier. System-level engineering carries fixed costs in analysis and implementation that a smaller operation may never recover — which is why Broughton screens for operations large enough to justify the work rather than treating every network as a candidate.

More REVERB Interviews

• Jonathan Kniss — on execution discipline across aerospace, energy and industrial operations
• John Charrier — on sourcing, freight and building a supply chain you can see
• Constantine Koliopoulos — business strategist, on scaling before the systems are ready