Law 16 — Autonomy: ចាត់ចែងឯករាជ្យ និង Check-ins មានអត្ថន័យ

Law 16 — Autonomy: ចាត់ចែងឯករាជ្យ និង Check-ins មានអត្ថន័យ_ from Team Leadership with The 48 Laws of Power

Autonomy ≠ abandonment. Give clear lanes and real decision rights—then run meaningful, light-weight check-ins. Adaptability & Culture Autonomy Check-ins Master Post
Core Idea: អ្នកដឹកនាំកំណត់ Outcome និង Decision Rights ឲ្យច្បាស់ បន្ថែម Support និង Check-ins ដែលមានអត្ថន័យ (មិនមែន micromanage)។ វាធ្វើឱ្យមនុស្សដំណើរការលឿន ប៉ុន្តែរក្សាគុណភាព/សុវត្ថិភាព។

1) Autonomy Framework (4 Blocks)

1) Scope & Outcomes

  • សរសេរ Outcome ជាមួយ Exit criteria (តេស្ត/រូប/សញ្ញាសម្រេចចិត្ត)។
  • Link to code/spec/drawing; define dependencies & approval path។

2) Decision Rights & Boundaries

  • អ្វីដែល owner អាចសម្រេច (budget ≤ X, sequencing, vendor shortlist)។
  • Non-negotiables: Safety/Code; Change control for scope/$$ shifts។

3) Support & Resources

  • Tools/crew/access/SOP; inspection slots; PO lane; mentor។
  • Escalation lane (criteria + contact) ឲ្យច្បាស់។

4) Check-ins មានអត្ថន័យ

  • Agenda តូចៗ: Goal → Evidence → Risks/Blockers → Next step
  • Cadence: daily micro (board-first) · weekly 1-on-1 · milestone reviews។

2) Check-in Design (កុំ micromanage)

Evidence-First

  • រូប/តេស្ត/ប័ណ្ណស្នងការ នៅលើ card; កុំសុំរាយការណ៍វែងៗ។
  • Move to “Ready/Done” នៅពេល Exit criteria ពេញលេញ។

Time-Boxed

  • Daily ≤ 10–15′ (ties L4); weekly 1-on-1 30′ (ties L43/L5)។
  • Decision windows (ties L31/L35) បិទជជែកមិនចប់។

Owner-Led

  • Owner បើកការពិភាក្សា៖ progress %, blockers, ask for help។
  • Leader កាត់ផ្លូវ/unblock, មិនបញ្ជារលំអិតលើវិធីសាស្ត្រ។

3) Delegation Ladder (Grow Autonomy)

Steps

  • Tell → Show → Co-own → Own-with-review → Own-and-teach
  • Promote upward when evidence shows reliability (pass-first, on-time)។

Guardrails

  • WIP ≤ 3 active cards/person (ties L18/L30)។
  • Escalate on pre-set criteria: safety, code breach, schedule slip > X days។

4) Playbooks (អាចប្រើភ្លាម)

New Zone Owner

  • Ownership brief (L7) + mentor 1 សប្ដាហ៍ដំបូង
  • Daily micro check-ins; first milestone review at 1–2 weeks

Remote/Shift Team

  • Board-first async update + photos/tests
  • Weekly video 1-on-1; pre-book inspections centrally

Stuck Owner

  • Switch to 48–72h cadence; add decision brief A/B/C (L31)
  • Remove blockers or re-scope workload (ties L25)

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

✅ Do

  • Write outcomes, rights, guardrails, and support—before delegating
  • Run evidence-first, time-boxed check-ins; log actions (Owner·Due·Link)
  • Scale autonomy as reliability/evidence grows

❌ Don’t

  • Abandon people after delegating; “autonomy” ≠ “alone”
  • Micromanage methods when outcomes are on track
  • Let decisions float without windows or approvers

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

  • % owners with written decision rights/guardrails (target ≥ 90%)
  • Blocker resolution time ≤ 48–72h; # escalations by criterion
  • Pass-first rate on sections led by autonomous owners
  • Check-in completion rate & average duration (keep short)

7) One-Page Templates (Copy/Paste)

Autonomy Charter — Law 16
Owner: ____ · Scope/Zone: ____
Outcome & Exit Criteria: ____ (tests/photos/sign-off)
Decision Rights: budget ≤ __; sequencing; vendor shortlist; ____
Guardrails: Safety/Code non-negotiables; change control path ____
Support: tools/crew/access/SOP/inspection slots/PO lane;
Escalation: criteria ____ · contact ____ · SLA ____
Cadence: daily micro · weekly 1-on-1 · milestone review ___
Check-in Agenda — Law 16
Goal (%/milestone): ____ · Evidence links: ____
Risks/Blockers: ____ · Help needed: ____
Actions → Owner · Due · Links: ____ · Next check-in: __/__/____
Decision Window Card — (ties L31/L35)
Topic: ____ · Options A/B/C (Cost–Time–Risk–Code) · Approver: ____
Window closes: __/__/____ HH:MM · MoM link: ____

Related

Previous Post Next Post
📑