Law 30 — Effortless: SOP/Checklist ដើម្បីបន្ថយកំហុស និងពេលវេលា_ from Team Leadership with The 48 Laws of Power
Core Idea: “Effortless” មិនមានន័យថា ងាយៗ ប៉ុណ្ណោះទេ ប៉ុន្តែមានន័យថា ត្រឹមត្រូវដោយលំនាំដើម។ បង្កើត SOP/Checklist ដើម្បីកាត់បន្ថយកំហុស កាត់ពេលវេលា និងធានា pass-first នៅលើការត្រួតពិនិត្យ—ជាក់លាក់ក្នុង Cluster 4 របស់ទំព័រអ្នកថា “Law 30 — Effortless: SOP/Checklist ដើម្បីបន្ថយកំហុស និងពេលវេលា”។ :contentReference[oaicite:1]{index=1}
1) Effortless Loop (5 សន្ទុះ)
1) Standardize
- SOP one-pager: Purpose → Tools → Steps → Exit Criteria.
- Attach code clause/drawing refs; show pass/fail examples (photos/tests).
2) Visualize
- Checklist on a board/tablet; images next to steps (ties to Law 6/18).
- Use naming & time-stamps so evidence is traceable (YYYYMMDD_zone…).
3) Execute
- Pre-task talk 3′: highlight top 3 error traps + PPE/tools check.
- In-process checks at critical points (hold points for photos/tests).
4) Verify
- Exit criteria = measurable: test value, photo with scale, sign-off path.
- Move card to “Ready/Done” only with evidence links (ties to Law 9/18).
5) Improve
- After defects: 24h mini-review → patch SOP step or add guardrail.
- Publish v# and date; keep one source of truth (dashboard).
2) Checklist Types & Guardrails
Pre-Task (Before Start)
- Tools/Materials ready? Drawings rev? Safety permits?
- Risk preview: 3 traps to avoid; mitigations listed.
In-Process (Hold Points)
- Measure/Photo at 25% · 50% · 100% stages.
- Witness sign if required; include test sheet no.
Post-Work (Exit Criteria)
- Spec/code thresholds met; cleanup & labeling done.
- Upload evidence; book inspection; move to “Ready”.
3) Playbooks (អាចប្រើភ្លាម)
Pass-First Inspection
- SOP with clause ref; mock-inspection video ≤ 30s.
- Checklist → evidence attached → slot booked.
Receiving & Storage
- Check PO/spec; photo upon arrival; damage log.
- Label/zone; FIFO; humidity/temperature guard.
Punchlist Closure
- Defect card: root cause, fix method, photo after.
- Close only with consultant/inspector sign-off.
4) Do / Don’t (សង្ខេប)
✅ Do
- Keep SOP ≤ 1 page with photos; link to code/drawing.
- Put checklists on the board; time-stamp updates.
- Require evidence for “Ready/Done”.
❌ Don’t
- Hide steps in long manuals; no one reads mid-task.
- Mark “Done” without exit criteria or proof.
- Maintain multiple conflicting versions of SOP.
5) Weekly Metrics (15 នាទី/សប្ដាហ៍)
- % tasks with active SOP/checklist (target ≥ 90%)
- First-pass yield (pass-first inspections) ↑
- Rework hours ↓; defect recurrence rate ↓
- Board freshness: % cards updated ≤ 3 days (ties to L18)
6) One-Page Templates (Copy/Paste)
SOP — Law 30
Purpose: ____ · Code/Clause: ____ · Drawing Ref: ____
Tools/Materials: ____
Steps (with photos): 1) ____ 2) ____ 3) ____
Exit Criteria (measurable): ____ (test/photo/sign-off)
Version: v__ (__/__/____) · Owner: ____ · Link: ____
Purpose: ____ · Code/Clause: ____ · Drawing Ref: ____
Tools/Materials: ____
Steps (with photos): 1) ____ 2) ____ 3) ____
Exit Criteria (measurable): ____ (test/photo/sign-off)
Version: v__ (__/__/____) · Owner: ____ · Link: ____
Checklist — Law 30
Task: ____ · Zone: ____ · Owner: ____ · Due: ____
Pre-Task: ☐ Tools ☐ Materials ☐ Drawing Rev ☐ Safety
In-Process Hold Points: ☐ 25% (photo/test) ☐ 50% ☐ 100%
Post-Work: ☐ Meets spec ☐ Evidence uploaded ☐ Booked inspection
Task: ____ · Zone: ____ · Owner: ____ · Due: ____
Pre-Task: ☐ Tools ☐ Materials ☐ Drawing Rev ☐ Safety
In-Process Hold Points: ☐ 25% (photo/test) ☐ 50% ☐ 100%
Post-Work: ☐ Meets spec ☐ Evidence uploaded ☐ Booked inspection
Evidence Card — Law 30
File name: YYYYMMDD_zone_task_detail_by.ext
Caption: Zone · Date/Time · What · Why it matters
Links: photo/test sheet/MoM · Approver: ____ (date)
File name: YYYYMMDD_zone_task_detail_by.ext
Caption: Zone · Date/Time · What · Why it matters
Links: photo/test sheet/MoM · Approver: ____ (date)
Related
Tags:
B.48Laws_Detail