Most manufacturers think their operations run on workflows. They do not. They run on habits. The difference matters — because habits break when the experienced person is absent, and workflows do not. --- What Makes Something a Workflow A real workflow has four properties. It has a defined trigger — a specific event that starts it. It has a defined owner — a specific function or person responsible for each step. It has a defined escalation path — what happens if the owner does not respond in time. And it has a system record — a documented trail of what happened and who decided it. Most manufacturing processes have none of these. They have a general understanding of what should happen. They rely on specific people to make it happen. When those people are absent, the process breaks. That is not a workflow. That is an institutional habit. --- How to Tell the Difference The fastest test is simple. Ask what happens when the experienced shift supervisor is on leave. If the answer involves things falling through gaps, informal escalations taking longer, and incoming supervisors discovering problems mid-shift — you have habits, not workflows. Property Habit Workflow Trigger Someone notices or is told System detects and initiates automatically Owner Whoever is available Defined role, regardless of who is present Escalation Chase informally if no response Automatic escalation after defined time window Record WhatsApp message or verbal Structured system record with timestamp and decision Reliability Depends on who is on shift Consistent regardless of who is on shift --- Why Habits Are Expensive Habits feel efficient. The experienced team member handles exceptions fast, knows who to call, and resolves issues without formal process. It looks like it works. The cost appears in three places. First, when the experienced person is absent — performance degrades in ways that feel like bad luck but are absent-dependency. Second, when volume grows — informal coordination that managed 50 exceptions a day cannot manage 150 without adding people. Third, when something goes wrong and there is no audit trail. These are not edge cases. They are the predictable cost of running on habits. --- The Five Processes Most Worth Converting First Not every process needs to be a workflow. Start with the five that cause the most damage when informal. Quality hold notification. When a quality hold is placed, the production planner, materials coordinator, and customer service team all need to know immediately. Routing this through a structured workflow rather than phone calls cuts hold-induced cascade by 60–80%. Discount approval. When a sales rep quotes below the pricing floor, the approval should route automatically — with cost breakdown, customer margin history, and competitive context attached. Not a WhatsApp message. Shift handover. Every open issue from the outgoing shift should transfer as a structured record. Not a verbal briefing that depends on memory. Customer priority change. When a customer requests expedited delivery, the production planning team should see the current schedule and the impact before confirming. Not a verbal relay. Supplier delivery alert. When a supplier confirms a slip, the affected work orders should surface to the planner immediately — with response options visible. --- What Changes When Habits Become Workflows The operational improvement from converting these five habits to structured workflows is measurable within 30 days. Exception resolution time falls — information reaches the right person immediately. Audit trails appear — every decision is recorded in the system. Absent-dependency disappears — the workflow runs consistently regardless of who is on shift. The team does not change. The process does not change. What changes is that the system now enforces the process rather than relying on the team to remember it.