Law 11 — Dependency (វិជ្ជាជីវៈ): បង្កើត core expertise ក្នុងក្រុម

✎ Edit

↓ Quick Down

Law 11 — Dependency (វិជ្ជាជីវៈ): បង្កើត Core Expertise ក្នុងក្រុម_ from Team Leadership with The 48 Laws of Power

Build professional dependency—real expertise, clean SOPs, and inspection-ready evidence. Avoid political dependency. Trust & People Core Expertise Skills Matrix Master Post
Core Idea: “Dependency (វិជ្ជាជីវៈ)” មានន័យថា អ្នក និងក្រុមមានជំនាញ ដែលគ្មានជំនួសងាយៗ តាមស្តង់ដារ—មិនមែនដោយនយោបាយចំណាប់ខ្មាំង។ បង្កើត core expertise ដែលធានា pass-first inspections, កាត់ rework, និង សម្រេចចិត្តលឿន តាមភស្តុតាង។ (Cluster 3 របស់ទំព័រអ្នករាយ “Law 11 — Dependency (វិជ្ជាជីវៈ): បង្កើត core expertise ក្នុងក្រុម”)

1) Pillars of Core Expertise

A. Capability Map

  • បង្កើត Skills Matrix (Trades × Skills, 0–3 scale): BIM/Shop-drawings, Code clauses, Inspection methods, Procurement/Vendor, Scheduling/CPM, Safety/QC tests។
  • សម្គាល់ bus factor (single-point-of-failure) និងបង្កើត coverage ≥ 2 per skill។

B. SOP & Evidence Library

  • SOP/checklist បង្ហាញ how to pass (tools, steps, exit criteria) + photo/test templates។
  • Code clause index → drawing refs → inspection forms → sample “pass-first” packets។

C. Guilds & Mentors

  • គ្រឹះ “guild” (e.g., Waterproofing, MEP testing, Concrete QC) ជួប 30 នាទី/សប្ដាហ៍។
  • Mentor/Apprentice ជាមួយ mini-projects (demo before/after; test results)។

D. Certification & Rotation

  • 90-day plan: learn → practice → demo → certify (badge on board)។
  • Rotation across zones/trades ដើម្បីបង្កើត T-shaped skills។

2) Playbook — From Skill to Influence

Inspection-Ready in 2 Weeks

  • Week 1: SOP rehearsal + mock inspection (photo/test capture)
  • Week 2: Real section → pass-first → publish packet as template

Vendor Evaluation Cell

  • Compare lead-time/quality track record; build quick-reference sheets
  • Recommend A/B/C vendor options (ties to Law 31)

Failure Review → SOP Update

  • When defect occurs: 24h review → root cause → SOP patch
  • Share 5-min guild brief; update evidence examples

3) Do / Don’t (សង្ខេប)

✅ Do

  • Make expertise visible: skills matrix, badges, pass-first reels
  • Centralize SOP + evidence; keep one source of truth
  • Cross-train to reduce bus factor; document decisions

❌ Don’t

  • Rely on “hero knowledge” or politics for influence
  • Hide code clauses/specs—cite them in checklists
  • Keep failures private—convert into SOP improvements

4) Weekly Metrics (15 នាទី/សប្ដាហ៍)

  • Coverage ≥ 2 people per critical skill (bus factor)
  • % inspections pass-first (target ↑), # SOP updates after failures
  • # certified badges earned, # guild demos completed

5) One-Page Templates (Copy/Paste)

Skills Matrix — Law 11
Trade/Role × Skill(0–3): ____ · Gaps (Top 3): ____
Coverage Plan: training/rotation/mentor pairs · Next Check: __/__/____
Guild Charter — Law 11
Focus: ____ (e.g., Waterproofing QC) · Cadence: weekly 30m
Outputs: SOP v__ , evidence pack, vendor sheet · Demo date: __/__/____
SOP Template — Law 11
Purpose: ____ · Tools: ____ · Steps: 1) ____ 2) ____ 3) ____
Exit Criteria: tests/photos/sign-off · Code Clause Ref: ____
Evidence Slots (attach): Before/After | Test sheet | Inspector sign
90-Day Certification Plan — Law 11
Skill: ____ · Mentor: ____ · Milestones (30/60/90d): ____ / ____ / ____
Assessment: demo + pass-first packet · Badge publish date: __/__/____

Related

Tags:
Previous Post Next Post
📑