Operations management produces outputs that directly affect production performance, product quality, cost, and safety: root cause investigations that identify what went wrong and prevent recurrence, improvement projects that increase throughput or reduce defects, capacity assessments that inform capital decisions, and compliance determinations that establish how the operation meets regulatory requirements. Each of these outputs requires research — data analysis, process observation, literature review, or regulatory research — and each benefits from a structured research-to-output workflow that makes the reasoning transparent and the record retrievable.
The research-to-output workflow for operations managers links data and observation to decisions through structured analysis that produces documented, retrievable records.
Stage 1: Root Cause Investigation
Root cause investigation is the most frequent research-to-output cycle for operations managers. A quality escape, an equipment failure, or a safety incident triggers an investigation that must move quickly but rigorously — fast enough to restore operations, rigorous enough to prevent recurrence.
The root cause investigation structure:
ROOT CAUSE INVESTIGATION REPORT
Problem statement: [Specific, factual description — what happened, where, when, how much]
Note: "the machine broke" is not a problem statement; "Machine #7 (injection molder)
experienced an unplanned downtime event at 14:23 on [date] due to a bearing failure
in the Z-axis servo motor, resulting in 4.5 hours of downtime and 2,200 units behind
on the daily production plan" is.
CONTAINMENT (completed before investigation begins):
Containment actions taken: [What was done to prevent further impact while investigation proceeds]
Containment effectiveness confirmed: [How we know containment is working]
PROBLEM UNDERSTANDING (the "what"):
What is affected: [Product / equipment / process / area]
When did it start: [Timeline of the problem]
Is / is not analysis: [What has the problem vs. what doesn't — narrows the search space]
IS: [What shows the problem]
IS NOT: [Similar situations that don't show the problem — this is the diagnostic signal]
Data collected: [Performance data, defect data, observations, measurements]
ROOT CAUSE ANALYSIS:
Method used: [ ] 5-Why [ ] Fishbone / Ishikawa [ ] Fault Tree [ ] FMEA review
[If 5-Why:]
Why 1: [Directly observed immediate cause]
Why 2: [Why did Why 1 occur?]
Why 3: [Why did Why 2 occur?]
Why 4: [Why did Why 3 occur?]
Why 5: [The systemic root cause — the management system, process design, or standard that allowed this to happen]
Root cause category: [ ] Machine [ ] Method [ ] Material [ ] Measurement [ ] Man [ ] Environment
Root cause statement: [Clear, specific statement of the root cause]
Knowledge base check: [ ] Prior events with this failure mode reviewed — [Findings from KB]
CORRECTIVE ACTION PLAN:
Corrective action for root cause: [What specifically will be done to address the root cause]
Responsible party: [Who is implementing]
Completion date: [When]
Corrective action for any contributing causes: [If additional causes identified]
Verification plan: [How will we confirm the corrective action was effective?]
Metric: [What we'll measure]
Target: [What the corrective action should achieve]
Verification date: [When we'll check]
EFFECTIVENESS CONFIRMATION:
Date of follow-up: [When effectiveness was assessed]
Result: [ ] Effective (failure mode not recurred) — Evidence: [Data]
[ ] Partially effective — What's still open:
[ ] Not effective — What happened instead:
LESSONS LEARNED:
What this investigation taught us: [Non-obvious learnings from this investigation]
KB updates: [ ] Process KB updated [ ] Equipment KB updated [ ] Quality KB updated
The is/is-not analysis discipline: the most valuable diagnostic tool in root cause investigation is identifying what has the problem vs. what doesn't. If the defect appears in the morning shift but not the afternoon shift, that difference is a diagnostic signal. If it appears on machine A but not machine B, that's a signal. If it started on a specific date, what changed on or just before that date? The is/is-not analysis narrows the investigation space dramatically.
The five-why discipline: the fifth why should reach a systemic cause — a management system failure, a process design gap, or a standard that allowed this to happen — not just a technical cause. If the fifth why is "the bearing wore out," that's not a systemic cause; that's a technical observation that doesn't prevent recurrence. The systemic cause is why the bearing wearing out wasn't caught before failure.
Stage 2: Improvement Project Development
Improvement projects — whether lean events (Kaizen, 5S, SMED), Six Sigma DMAIC projects, or simpler process improvement efforts — follow a research-to-output cycle that moves from problem definition to solution design to implementation and control.
The improvement project structure:
IMPROVEMENT PROJECT CHARTER
Project name: [Brief description]
Project type: [ ] Kaizen event [ ] 5S implementation [ ] SMED [ ] DMAIC [ ] Other
Start date: [Date]
Target completion: [Date]
PROBLEM DEFINITION:
Current state metric: [The specific, measurable performance problem being addressed]
Current performance: [Measured value]
Target performance: [Target value]
Gap: [Current minus target]
Business impact: [What achieving the target is worth — cost, throughput, quality, capacity]
KB CHECK (completed before project design):
[ ] Prior improvement projects in this area reviewed — Findings: [What was tried, what worked, what didn't]
[ ] Process knowledge for this area reviewed — Relevant design rationale identified: [Yes/No + what]
[ ] Quality history for this area reviewed — Any related failure modes: [Yes/No + what]
CURRENT STATE ANALYSIS:
Process observation: [What was observed through direct process study]
Data analysis: [What the performance data shows — trends, patterns, variation]
Root cause hypothesis: [What the current state analysis suggests is driving the performance gap]
SOLUTION DESIGN:
Solutions considered: [What options were evaluated]
Solution selected: [What was chosen]
Basis for selection: [Why this solution vs. alternatives]
IMPLEMENTATION:
Implementation steps: [Specific actions + responsible party + dates]
Resources required: [People, equipment, expense]
RESULTS:
Post-implementation metric: [Measured value after implementation]
Improvement achieved: [Improvement vs. baseline]
% of target achieved: [How close to target]
Sustainability plan: [How the improvement will be maintained — SOP update, visual management, monitoring]
CONTROL AND SUSTAINABILITY:
SOP updated: [ ] Yes — [Document number + revision + effective date] [ ] Not applicable
Training completed: [ ] Yes — [Who received training + date]
Visual management updated: [ ] Yes [ ] Not applicable
Monitoring: [What KPI will be tracked to detect regression, at what frequency]
LESSONS LEARNED:
What worked well: [Approaches or techniques that were effective]
What would we do differently: [What to change for next time]
What was surprising: [Unexpected findings or outcomes]
KB updates: [ ] Process KB [ ] Improvement history KB [ ] Other
Stage 3: Capacity and Capital Decision Analysis
Capital investment decisions (new equipment, facility expansion, automation), capacity strategy decisions (adding shifts, outsourcing, line balancing), and significant operational changes require structured analysis that documents the research basis for the decision.
The capital/capacity analysis structure:
CAPACITY / CAPITAL DECISION ANALYSIS
Decision: [What is being decided — what equipment, investment, or operational change]
Decision deadline: [When the decision must be made]
CURRENT STATE:
Current capacity: [Demonstrated capacity in relevant metric]
Current utilization: [% of capacity used]
Current OEE: [Baseline OEE for relevant equipment]
Capacity constraints: [What limits current capacity]
DEMAND ANALYSIS:
Current demand: [What we're currently producing]
Projected demand: [Demand forecast + basis for forecast + time horizon]
Demand growth requiring additional capacity: [When we'll need more]
OPTIONS ANALYZED:
Option 1: [e.g., "Add a second shift"]
Capacity impact: [How much capacity this adds]
Cost: [Investment or operating cost]
Lead time to implement: [How long to have running]
Risks: [What could go wrong]
Option 2: [e.g., "Add equipment"]
Capacity impact:
Cost: [Equipment cost + installation + tooling + training]
Lead time: [Delivery + installation + qualification]
Risks:
Option 3: [...]
TOTAL COST / ROI ANALYSIS:
Investment required: [If capital — total investment]
Operating cost change: [Annual operating cost change vs. current]
Revenue or throughput enabled: [Value created by the additional capacity]
Payback period: [Investment / annual benefit]
Key assumptions: [What this analysis assumes — demand growth rate, uptime, efficiency]
Sensitivity: [How does the analysis change if key assumptions are wrong by 20%?]
RECOMMENDATION:
Recommended option: [Which + why]
Next steps if approved: [What happens immediately after decision]
Decision: [Approved / Denied / Deferred — date + decision maker]
Rationale: [Documented basis for the decision]
Stage 4: Regulatory Compliance Research
When a new regulatory requirement, an OSHA inspection, or a quality certification audit requires compliance research, the output is a documented compliance determination.
Worked example: OSHA Machine Guarding Assessment
A new piece of equipment has been installed and the operations manager needs to ensure machine guarding compliance before putting operators on the machine.
Research conducted:
- OSHA 29 CFR 1910.212 (Machine Guarding General Requirements) reviewed — primary standard for all machines
- OSHA 29 CFR 1910.217 (Mechanical Power Presses) reviewed — specific to the equipment type
- OSHA Letter of Interpretation (dated [date]) on point-of-operation guarding requirements — captured with archive.org backup
- Equipment OEM documentation reviewed for any specific guarding requirements or recommendations
- Prior compliance assessment for similar equipment in our facility reviewed for applicable standards
Output produced:
- Machine guarding assessment report: specific OSHA requirements applicable to this equipment, current guarding status, any gaps identified, corrective actions required before operator use
- Documented in quality/compliance system with source citations and dates
- Training requirement identified and documented
Monthly or quarterly performance reviews, annual operations strategy development, and periodic operational assessments require structured research and analysis that links performance data to strategic decisions.
The operational performance review structure:
OPERATIONS PERFORMANCE REVIEW
Period: [Month/Quarter + Year]
PERFORMANCE vs. TARGET:
OEE: Actual [X%] vs. Target [Y%] vs. Prior period [Z%]
First-pass yield: Actual vs. Target vs. Prior period
On-time delivery: Actual vs. Target vs. Prior period
Safety (TRIR): Actual vs. Target vs. Prior period
Cost per unit: Actual vs. Target vs. Prior period
TOP PERFORMANCE GAPS:
[Gap 1]: [Magnitude + trend + root causes identified or hypothesized]
[Gap 2]: [...]
IMPROVEMENT INITIATIVES STATUS:
[Project 1]: [Status + results to date + at-risk items]
[Project 2]: [...]
STRATEGIC ISSUES:
Capacity: [Current capacity headroom vs. demand forecast]
Equipment: [Any aging or reliability concerns that need medium-term capital planning]
Workforce: [Skill gaps or training needs]
Regulatory: [Any compliance gaps or upcoming regulatory changes requiring preparation]
DECISIONS NEEDED:
[Decision 1]: [What needs to be decided + by when + who decides + options]
[Decision 2]: [...]
NEXT PERIOD PRIORITIES:
[Priority 1]: [What + why + metric + owner]
[Priority 2]: [...]
Key Takeaways
-
The research-to-output workflow for operations covers five major cycles. Root cause investigation (is/is-not analysis + 5-why to systemic cause + effectiveness verification); improvement project development (KB check first + current state analysis + solution design + control plan); capacity and capital analysis (options + total cost + sensitivity analysis); regulatory compliance research (primary regulation + interpretation guidance + archived documentation); operational performance review (performance vs. target + gap analysis + decisions needed).
-
The problem statement precision is the foundation of root cause investigation quality. Vague problem statements produce unfocused investigations. A specific, factual problem statement — what happened, where, when, by how much — focuses the investigation from the first step.
-
The KB check before any improvement project prevents re-solving solved problems. Checking what was tried before, what the process design rationale is, and what the quality history shows for this area is the practice that allows improvement projects to build on prior work rather than starting from scratch.
-
The fifth why must reach a systemic cause. A root cause investigation that concludes with a technical finding ("the bearing wore out") hasn't reached the root cause. The systemic cause is what in the management system, process design, or standard allowed the bearing to wear out without detection and correction.
-
Regulatory compliance research generates archived documentation. The specific regulation cited, the interpretation guidance reviewed, and the archive.org snapshots of both are the compliance record that demonstrates what the requirement was when the determination was made.
Conclusion
The research-to-output workflow for operations managers connects data and observation to decisions through structured analysis: root cause investigations that use is/is-not analysis and five-why methodology to reach systemic causes; improvement projects that check prior work before starting and build control plans that prevent regression; capacity and capital analyses that evaluate multiple options against total cost; regulatory compliance research that generates archived documentation; and operational performance reviews that link performance gaps to strategic decisions. The documentation of the research behind each decision creates the organizational learning record that makes future investigations faster, future improvement projects more effective, and future compliance audits less panicked.
Related reading: AI Knowledge Management in 2025.