Start this week

Walk one high-variability process end to end during a single shift this week — bring a clipboard, a stopwatch, and your current written procedure (or a blank sheet if none exists). Time each major step, note every point where the operator makes a judgment call that isn't captured in the standard, and mark any step that runs in a different sequence than the written version describes. By Friday, you should have a one-page redline of that procedure showing what the work actually looks like versus what the document says. Bring that redline to a 60-minute session with the two or three operators who run that process most often, and let them confirm or correct your observations. That marked-up sheet becomes the baseline draft your team rewrites into a true standard — one process, one shift, before you touch anything else.

Start this week

Walk the floor with your most experienced maintenance technician this week and spend 90 minutes picking apart one high-frequency work order — ideally a PM or repair task your crew runs at least twice a week. Together, write down every actual step performed, in the order it's actually done, not the order the OEM manual or last supervisor thought it should be done. Capture any informal checks, tribal-knowledge shortcuts, or safety interlocks that aren't written anywhere. By Friday you'll have a single-page draft sequence — a rough standard work sheet — that you can take to the next shift's technician and ask: "Is this how you do it?" That gap conversation is where your standardization work begins.

Start this week

Convene a 90-minute working session this week with one person each from operations, quality, and maintenance — the three functions most likely to be pointing fingers at each other when a recurring problem doesn't get resolved. Before anyone walks in, write a single problem statement on the whiteboard: name one decision that stalled or bounced around in the last 30 days because no one function owned it. Spend the first half of the session confirming everyone recognizes the same gap, then spend the second half drafting a one-page charter — on paper is fine — that names the decision types this group will own, how often it meets (start with biweekly), who has a vote versus a voice, and what happens when the group can't reach agreement. Have a draft ready to review at next Monday's operations standup.

Start this week

Draft a one-page accountability matrix for your three or four most critical process steps or quality outcomes — on paper or a whiteboard, whichever you'll actually finish by Friday. For each row, write the process or outcome, the single named person (not a department, not a shift) who owns it, and what "closed" looks like for a corrective action on that item. Bring that draft to your next supervisor huddle — no longer than 30 minutes — and pressure-test two things: does every supervisor recognize their name on at least one row, and can they describe what they're supposed to do when their metric falls out of range? Gaps you find in that conversation are your real starting list, not the matrix itself.

Start this week

Schedule a 90-minute working session this week with your shift supervisors — one from each shift if you run multiple — and map out what actually happens today between the end of one shift and the start of the next: what information gets communicated, what gets written down, what gets skipped when it's busy, and where the first-line leader spends the first 20 minutes of their shift. Come out of that session with a single sheet of paper that shows the current sequence of events and highlights the two or three gaps where issues fall through — no standard check, no owner, no escalation path. That gap map is your design input for building a daily management routine that matches your actual floor, not a template from a conference.