A Different Approach to Complex Manufacturing Problems
Andy Watkins LLC provides unbiased fact-finding and structured manufacturing analysis for complex production challenges — separating facts from assumptions, identifying causal relationships, and developing an accurate Situational Analysis.
We begin by understanding the problem.
How Do We Determine What Is Actually Happening?
Complex manufacturing problems rarely belong to one department or one technical discipline. The information needed may be distributed across machine behavior, CNC programs, tooling, workholding, Engineering, Quality, Operations, suppliers, historical decisions, and the experience of the people closest to the process.
Andy Watkins LLC uses a disciplined process to bring those facts together, expose their relationships, and determine what deserves attention first.
A Structured Path Forward
- Requirements & intended outcome
- Project history & stakeholders
- Previous corrective actions
- Constraints & commitments
- Process, machine, part & program
- Tooling, toolholding & workholding
- Measurement & material
- Suppliers & organizational interfaces
- Facts vs. assumptions
- Symptoms vs. causes
- Contributing factors & risks
- Priorities & ownership
- Dependencies & resources
- Success criteria & validation methods
Coordinate resources and implement the required corrective actions — with Andy Watkins LLC, the customer, machine OEM, and other specialists as needed.
- Conforming, repeatable production
- Required rate & process stability
- Recommendations alone aren’t the finish line — a sustainable result is.
Complex Doesn’t Mean Unmanageable.
When a manufacturing problem involves equipment, process, people, suppliers, quality, historical decisions, and competing priorities, the relationships between causes can become more important than any single issue. Interrelationship analysis provides a disciplined way to expose those relationships and identify where attention should be focused.
Analysis That Doesn’t Stop at Analysis
A consultant can analyze. An applications engineer can program. A machinist can make chips. Complex manufacturing problems often require several of these perspectives simultaneously.
The Methodology, In Practice
Two real stories — one from senior engineering leadership, one from the production floor — showing how structured fact-finding surfaces what fault-finding misses.
Sometimes the Problem Isn’t Where Everyone Thinks It Is.
A manufacturing engineering organization had drifted from its charter. It was meant to be light and responsive to urgent, immediate production needs — but over time, attention shifted toward long-term, multi-year solutions. Internal customers grew frustrated. Executives started showing up to meetings. Nobody could quite say why.
A structured two-hour session — Affinity Diagram, Interrelationship Diagraph, Nominal Group Technique — made it visible. One senior engineer’s priorities looked almost opposite the rest of the group’s. He wasn’t being difficult — his role legitimately emphasized long-term technical work. His seniority and credibility were unintentionally pulling the whole organization away from urgent customer needs.
Nobody had to be wrong for the system to be broken. Individually reasonable decisions, made by capable people, had interacted to produce a collectively misaligned result.
Six Months of Conflict. Two Simple Corrective Actions.
Engineering had signed training records. Operators insisted the process wasn’t working. Both had facts. Neither had the whole picture. For six months, the standoff continued over two recurring problems: missing ERP transactions, and incomplete router paperwork.
Bringing operators into a structured Affinity Diagram session changed the room. One operator — who arrived expecting to wait out another meeting he didn’t believe in — became the biggest contributor once he had a real way to be heard.
Two root causes emerged. The pens issued to operators were too chunky to legibly fill the tiny required fields. And two router paper colors — red and green — didn’t contrast well enough for the barcode scanner, so it beeped as if the scan worked while the ERP transaction silently failed. Finer pens and different paper. The six-month conflict was over in about a day.
You don’t need to have the answer before contacting us. Start by telling us what should be happening, what is happening instead, and what has already been attempted.