C ជាមួយ Cost–Time–Risk–Code)_ from Team Leadership with The 48 Laws of Power

Frame the decision so stakeholders choose among clear, comparable options—each with Cost · Time · Risk · Code. Communication & Influence Decision Design (A/B/C) Evidence & Timing Master Post

Core Idea: ជំនួសឱ្យឲ្យប្រជុំពិភាក្សាទៅមិនចប់—អ្នកដឹកនាំគួរតែ រចនាជម្រើស ឲ្យច្បាស់ A/B/C ជាមួយ Cost–Time–Risk–Code និង ស្នើជម្រើសដែលបានផ្ដល់អនុសាសន៍។ វាជាចំណុចស្នូលនៃ Cluster “Communication & Influence” និងត្រូវបានបញ្ជាក់នៅក្នុង Decision Template (A/B/C) របស់ទំព័រអ្នក។

1) Option Architecture (រចនាប័ទ្មជម្រើស)

Columns That Matter

Cost: capex/opex, change-order, lifecycle (if relevant)
Time: lead time, install duration, schedule impact/float
Risk: safety, quality/defect, supply, rework, approvals
Code: standards/clause, inspection readiness, sign-off path

Design Rules

3 options max (A/B/C) + one recommended pick
1-page limit; images/tests on top; numbers consistent
Decision window stated clearly (e.g., 48h)
Include Go/Kill criteria to prevent backtracking

2) Example Option Patterns

Material/Method

A: Keep baseline — low change cost, slower, low risk
B: Prefab part — moderate cost, −1wk schedule, needs early PO
C: Alternate supplier — cheaper, but higher QC/lead-time risk

Sequence/Schedule

A: Single shift — safe, but slips handover by 3 days
B: Split shift — +OT cost, recovers 2 days
C: Parallel trades — fastest, risk: clash/inspection slots

Commercial

A: Standard PO — normal cash cycle
B: Early payment discount — cost ↓ 2–3%, cash need ↑ this week
C: Volume lock — price ↓, but commitment risk if scope changes

3) Playbook សម្រាប់ស្ថានការណ៍

Case A — Change Order

One-pager with A/B/C + photos/tests
Show cost deltas, delay avoided, code clause
Ask for approval window; MoM same day

Case B — Inspection Strategy

Slot map vs. readiness; risk of fail/rework
Include sign-off path & responsible inspector
Pick option with best pass-first probability

Case C — Procurement Expedite

Compare vendors on lead time/quality track record
State payment terms & logistics risk
Recommend B and place PO within window

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

✅ Do

Limit to 3 options; make them meaningfully different
Lead with visuals; numbers in a neat table
Declare decision window and approver up front
Log Go/Kill criteria; lock a 7–10 day execution window

❌ Don’t

Present open-ended “what do you want?” threads
Mix contradictory numbers across files
Hide code clauses; omit inspection plan
Invite re-litigating after decision—route changes formally

5) Weekly Cadence

Decision Calendar: list topics, A/B/C ready, decision windows
Conversion Metric: % meetings with 1-page A/B/C (target ≥ 90%)
Post-Decision Audit: re-check numbers vs. outcome after 1–2 weeks

6) One-Page Templates (Copy/Paste)

Decision Brief — A/B/C (Law 31)
Topic: ____ · Ask: choose A/B/C by __/__/____ HH:MM

Option	Cost	Time	Risk	Code	Benefit (For You)
A — ____	____	____	____	____	____
B — ____	____	____	____	____	____
C — ____	____	____	____	____	____

Recommendation: ____ · Go/Kill Criteria: ____
Evidence links (photos/tests/quotes/schedule): ____
Owners after decision: ____ · Due: ____ · MoM link: ____

✎ Edit Post ↑ Top Up

Law 31 — Control the Options: ផ្តល់ជម្រើស A/B/C ជាមួយ Cost–Time–Risk–Code