# Tim Stuart

Tim Stuart writes about improving manufacturing operations, including making improvement cases financially defensible, extending continuous improvement beyond production, and connecting plant-floor data to useful decisions.

- Profile: https://b2binfluencer.marketing/creators/tim-stuart/
- LinkedIn: https://www.linkedin.com/in/timstuart
- Topics: operational-excellence, continuous-improvement
- Based on 11 dated posts, latest 2026-10-06

## Summary

Useful for manufacturing software and systems integration brands needing technical content or a co-presented webinar on IIoT workflows.

- Best for: Manufacturing software and systems integration campaigns on IIoT-native workflows, operational intelligence, and value realisation.
- Not for: Paid brand awareness or product launch campaigns needing rate cards, sponsorship formats, audience guarantees, or reach benchmarks.
- Check first: Ask for audience demographics and recent post performance on comparable topics and formats.

### Takeaways

- Improvement cases fail in finance review, not because the idea is bad
- Continuous improvement's problem is reach, not methodology
- Accountability is a system-design problem, not a people problem

## Main ideas

- **Improvement cases fail in finance review, not because the idea is bad**: Tim Stuart argues that improvement cases rarely die because the idea was weak; they die in finance review over three recurring questions: where a number came from, what happens if an assumption behind it is wrong, and whether several claimed savings are the same dollars counted more than once. Each question has a structural answer: trace every dollar to a finance line, break the case into claims small enough to challenge one at a time, and map who else draws on the same lines before a portfolio promises the same dollars twice. They describe a five-item pre-flight checklist to run before any number leaves the writer's desk.
- **Continuous improvement's problem is reach, not methodology**: Tim Stuart contrasts two parts of the same plant. On the production floor, continuous improvement is real: visual management every hour, tier-one meetings against takt, and standard work at every station. In planning, finance, IT, or HR, the same program exists mainly on paper: posters, a signed charter, no daily management routine, standard work in someone's head, and a backlog in a spreadsheet nobody opens. The cited root causes are structural, not cultural: incompatible system formats across functions, no prioritization framework for non-production work, gains that regress when the CI team is not watching, and A3 methods never translated to office work. The proposed fix is not another kaizen event, but applying the same method with the same rigor in the function where its absence costs the most.
- **Accountability is a system-design problem, not a people problem**: Tim Stuart says they hear "we have an accountability problem" from every function in leadership meetings, including plant managers, quality directors, operations excellence, finance, and HR. An analysis of 16 use cases across 11 departments found that the dominant root causes were structural: missing documented procedures, unassigned cross-functional KPI ownership, incomplete action follow-through, ambiguous role boundaries, and missing accountability consequences. The explanations that people do not care or that teams are undisciplined did not appear in the data. The conclusion: what looks like a people problem is a system-design problem.
- **Raw machine data matters only when it leads to action**: Tim Stuart argues that many manufacturers already have PLC signals, machine states, alarms, and production events, but traditional SCADA and MES deployments can be too rigid, expensive, or slow to deliver real-time visibility. The priority is lightweight, event-driven workflows built in Ignition: contextualize raw PLC data into meaningful machine states and events; trigger real-time alerts, notifications, and escalations; build reusable workflow templates that scale across lines and facilities; improve operator visibility with event-driven dashboards; and generate lightweight analytics for downtime, fault duration, micro-stops, and KPI tracking. A related argument identifies disconnected systems as a major barrier to real-time decision-making: plant-floor data, MES logic, and enterprise systems often operate in silos. The proposed approach is hybrid MES architecture that connects edge devices, SCADA, MES, and ERP into a unified model, defines what good production data looks like, and uses architecture patterns that scale across lines, plants, and business units.

## Work to read

- [Why improvement cases die in finance review—and how to pre-check them](https://www.linkedin.com/posts/timstuart_improvement-cases-rarely-die-because-the-activity-7492535247885172736-YY7i)
- [Continuous improvement has depth on the floor and only a charter elsewhere](https://www.linkedin.com/posts/timstuart_continuousimprovement-lean-manufacturing-activity-7457028760442142720-VcM8)
- [The accountability problem is usually a system-design problem](https://www.linkedin.com/posts/timstuart_manufacturing-operationalexcellence-leadership-activity-7454986906058248192-YoVb)
- [Designing IIoT-native workflows in Ignition](https://www.linkedin.com/posts/timstuart_iiot-ignition-smartmanufacturing-activity-7465412059179032576-EfL_)
- [Hybrid MES architecture: connecting edge, SCADA, MES and ERP](https://www.linkedin.com/posts/timstuart_manufacturing-smartmanufacturing-mes-activity-7454942215753224192-yNMN)

## Brand relationships

- **Visual Decisions Inc** (disclosed_partnership)
- **Sandalwood Systems Integration Services** (disclosed_partnership)
- **Worth Doing** (mention)
- **Manufacturing Value Platform** (mention)

## Partnerships

Tim Stuart’s posts do not offer partnerships, sponsorships or paid placements directly. They focus on education and vendors, not commercial pitches, and include no rate card, media kit, sponsorship policy or inquiry route. One recurring collaboration format is a webinar presented jointly by Visual Decisions Inc and Sandalwood Systems Integration Services. The posts describe free, practical sessions: 30 minutes on IIoT-native workflows in Ignition and a separate session on hybrid MES architecture. Both target process engineers, controls engineers, IIoT developers, data engineers and manufacturing IT/OT teams. This is a co-presented educational format, not a disclosed sponsorship: the posts do not say which company Tim represents, how the sessions are funded or whether either company pays for placement. For a content collaboration or speaking engagement, the visible template is a short joint technical webinar with a co-presenter, not a sponsored post or brand endorsement. Ask directly whether paid opportunities are available and who funds the sessions; five posts are available here, with no official partnership pages, specifications or contact pages.

## Alternatives

- Eric Ciampoli (MBA): Choose Eric Ciampoli when the buyer is a plant or operations leader and the message is operational intelligence, ERP alignment and knowledge continuity rather than event-driven engineering detail. Both posts put ECIC's OPSIDIAN platform at the centre of that story: plant data, documentation and knowledge brought together so operational knowledge stays accessible and current, alongside a warning that procedures fall behind as equipment, processes and teams change. The Manufacturing Day post adds the buying language — operational improvement, ERP alignment, process optimization and plant visibility — drawn from a booth conversation with manufacturers. A collaboration focused on documentation, procedures or knowledge systems, or aimed at an ERP-adjacent audience, fits this material better than a session about turning raw PLC signals into machine events.
- Nilesh Samel: Choose Nilesh Samel when the audience is Indian manufacturing and the problem sits at the control layer: PLC logic, interlocks, SCADA alarms and edge systems. The posts are specific and execution-level: never start a pump without flow feedback, tag every trip cause in PLC logic, insert timers between heavy loads, log OEE batch-wise with timestamps, wire SCADA alarms to actions instead of beeps, enable remote access and train operators on signal interpretation. They draw on a stated base of 50+ plant audits and quantify downtime, energy and fault-resolution improvements. The year-end post sets out a direction for AI-driven edge systems and an execution platform for Indian manufacturing. A partner selling PLC, SCADA or edge products into Indian plants and seeking list-form practical tips with ROI framing will find a closer match here than in a 30-minute co-presented IIoT workflow session.
- Jay Byam: Choose Jay Byam when the specific problem is downtime-data collection on older equipment. The aluminum mill post works through one plant in detail: roughly $800,000 of material moving through the plant every hour, an ambition to run 24/7/365, capital decisions that require proof, and operators on 1940s machines logging stoppages on paper for someone else to enter later. Details get lost, leaving a weak case for a fix. The post names the counter-intuitive failure mode plainly: plants losing the most money from downtime often have the weakest downtime data. The OEE post argues that tracking decays because the system does not return value fast enough, not because operators do not care. The fix, it says, is logging that fits the way work flows and feeds visible improvements back. A partner selling data collection, OEE tooling or operator-facing capture into plants with legacy machines gets a sharper problem statement here than from an architecture-led session.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/