How process improvement, ERP, quality control, and TQM affect performance and implementation risk.
Process improvement questions ask whether the way work moves through the entity supports the performance objective. The issue may appear as slow cycle time, duplicated data entry, weak ERP use, rework, customer complaints, quality failures, or poor handoffs between departments. A strong answer identifies the process cause, not just the cost symptom.
Process improvement belongs in Management Accounting and Performance when workflow, ERP use, quality control, handoffs, bottlenecks, or process ownership explain a performance issue more directly than a calculation alone.
| Coverage area | Performance Management question |
|---|---|
| Process cause | Is the weakness workflow design, cost information, reporting, risk control, staffing, supplier performance, or policy? |
| ERP impact | Does integration, automation, reporting, access, training, or control design solve the actual problem? |
| Quality approach | Do prevention, detection, feedback, continuous improvement, or TQM principles fit the evidence? |
| Implementation risk | What cost, disruption, data-quality, control, or adoption risk could the improvement create? |
| Recommendation | What workflow change, owner, measure, implementation step, and monitoring method should management use? |
Process improvement should match the problem.
| Case facts | Likely process issue | Possible improvement |
|---|---|---|
| Long wait times and work queues | Bottleneck or capacity imbalance | Redesign flow, rebalance staffing, remove non-value-added steps, or revise scheduling. |
| Multiple spreadsheets and reconciliations | Fragmented data process | ERP workflow integration, master-data cleanup, approval routing, and exception reporting. |
| High defect or return rates | Quality process weakness | Root-cause analysis, prevention controls, supplier quality review, and TQM-style feedback loop. |
| Repeated manual entry errors | Automation or control gap | System validation, barcode or form controls, training, and exception review. |
| Delayed management reports | Closing or reporting workflow weakness | Standardized close calendar, data ownership, dashboard automation, and review checkpoints. |
| Cost reduction harmed service | Poor improvement criteria | Add service, quality, and customer measures to the process redesign. |
Do not recommend a broad methodology when a narrow process fix is enough. Conversely, do not recommend a small training session when the facts show a structural workflow or system problem.
ERP can improve performance when the problem is fragmented information, duplicate entry, weak integration, or delayed reporting. It is not automatically the answer to every process problem.
| ERP benefit | What to evaluate |
|---|---|
| Integrated data | Whether master data, chart of accounts, product codes, and customer records are reliable. |
| Standardized workflow | Whether approvals, roles, and exception handling are properly designed. |
| Better reporting | Whether dashboards measure decisions, not merely available system fields. |
| Automation | Whether automation reduces error without removing needed review controls. |
| Scalability | Whether the system can handle volume, locations, products, and reporting needs. |
| Control improvement | Whether access rights, segregation of duties, and audit trails are configured. |
| User adoption | Whether training, process ownership, and change support are realistic. |
In a case response, separate the business process from the software. If the process is poorly designed, automating it may make the wrong process faster.
Quality improvement is relevant when defects, complaints, warranty claims, rework, service failures, safety issues, or inconsistent output appear in the case. Total quality management is broader than inspection; it emphasizes prevention, process ownership, employee involvement, customer focus, and continuous improvement.
| Quality cost category | Example | Response implication |
|---|---|---|
| Prevention cost | Training, supplier qualification, design review. | Often supports long-term cost reduction by avoiding defects. |
| Appraisal cost | Inspection, testing, quality audit. | Useful but can become reactive if prevention is weak. |
| Internal failure cost | Scrap, rework, downtime before delivery. | Indicates process waste and root-cause investigation need. |
| External failure cost | Returns, warranty, lost customers, complaints. | Often most damaging because it affects reputation and revenue. |
The recommendation should not say only “improve quality.” State the process point where quality fails and the measure that will show whether the improvement works.
Process symptoms can mislead. Use case facts to trace the cause.
| Symptom | Root-cause questions |
|---|---|
| Overtime increases | Is demand higher, staffing low, scheduling weak, rework high, or equipment unavailable? |
| Cycle time rises | Which step creates the queue, approval delay, missing information, or rework loop? |
| Defect rate increases | Did inputs, supplier quality, training, machine maintenance, or design change? |
| Reports are late | Which data source, approval, reconciliation, or system extract is the bottleneck? |
| Customer complaints rise | Are expectations unclear, service capacity insufficient, quality poor, or communication weak? |
| ERP project disappoints | Were requirements unclear, users untrained, controls misconfigured, or data not cleaned? |
Use this sequence: process objective, symptom, root cause, recommended change, implementation risk, owner, timeline, control, and success measure. If there are several possible causes, rank them by case evidence and state what additional data would confirm the diagnosis.
Good measures include cycle time, first-pass yield, error rate, rework hours, backlog age, wait time, system exception rate, customer complaint rate, and cost of poor quality.
| Pitfall | Correction |
|---|---|
| Recommending ERP as a generic cure. | Explain the specific process, data, reporting, or control problem ERP would solve. |
| Treating quality as an inspection-only issue. | Address prevention, root cause, feedback, and continuous improvement. |
| Confusing symptoms with causes. | Trace the workflow to the step creating delay, error, rework, or waste. |
| Ignoring user adoption. | Include training, process ownership, and change-management steps. |
| Recommending a metric that creates new behaviour problems. | Pair speed, cost, quality, service, and control measures. |