PMCU Culture Transformation, Executive Recommendation

1 The problem, and the shift

The data points to one structural root, not a values gap: an opaque, who-you-know advancement system that has quietly taught good people to keep their heads down. PMCU is not short on knowing what fair looks like. Staff named these exact fixes in the 2025 surveys and nothing moved, so what we are facing is a doing gap held by fear, not a knowledge gap. Two real strengths are what the fix rides on: pride in the Chula mission (5.32/7, only 6% rate it low, the one asset that survives every administration) and the job security people still trust. The clearest single signal: clarity on pay and promotion sits at 2.73, the worst item in the whole survey, and it sits next to ten-year staff who have stopped expecting advancement to follow their work.

2.73

comp/promote clarity (67% rate low), worst item

3.08

"who-you-know > ability"

4.00

cross-BU coordination friction

5.32

pride in the Chula mission, the anchor

FROM (now, data)	TO (staff's own Q19)
Advancement runs on who-you-know, behind secret criteria	Merit is visible and fair; people advance on real results
Play-it-safe is rational, success unrewarded, a brave call punished alone	พางานเดินสุด, own the work and drive it to done (Q19 #1)
Silos dump work on the front line ("ถังขยะ")	จับมือข้ามหน่วย, solve constraints together (Q19 #2)
Secrecy + a leaky channel kill candor (trust-leak 2.88)	Safe voice; decide on ข้อเท็จจริง not เส้นสาย
Every 4 years the strategy churns; "long effort = wasted"	Continuity that survives the rotation, anchored to the mission

The style-shift, named preciselyThis is Authority → Order, not a leap to "Results." We purge the patronage-Authority element (opacity, "The One") and strengthen the rule-based Order PMCU already values, with a measured injection of Learning. We are not asking a stability-anchored, audit-bound workforce to become Silicon-Valley risk-takers.

2 The recommendation

The single reframe it rests on: "Results" is not an instruction to employees. It is a leader-owned promise that the organization will measure and reward results fairly and openly. You cannot ask staff to value real results while the organization visibly rewards connections.

Five moves, not twenty-five, and the first one only on a green light PMCU can genuinely run about four to five things at once, no more. So the recommendation is five critical moves, done fully, with everything else held in a visible backlog the leadership group pulls from only when a slot frees up. The five: (1) open the criteria (the keystone), (2) remove the brakes and bank one felt win, (3) พางานเดินสุด, the Owner's Handoff, (4) make speaking up safe and build leaders' capacity to let go, (5) lock it so it survives the 4-year rotation. The other twenty are the backlog, not the plan, and presenting them as a 25-item menu would just invite the org to cherry-pick the easy ones.

The one condition on the keystone. Opening the criteria takes discretion away from the two people who hold it today, รองอธิการ อาจารย์แป๊ป and ผอ. พี่ชอว์. So the readiness we read first is theirs, not only the ~30 line leaders', through a short structured conversation before 13 ก.ค. (a "force-field" read: what genuinely pulls them toward the reform, what holds them back, and one restraint we remove first). If they are genuinely behind it, the keystone leads. If they are not, we lead instead with making voice safe and handing real decisions down to the front line, and the merit reform becomes the second move, once people can safely say out loud "that promotion did not follow the rules." Publishing fair rules into a room that is still afraid just produces a fair-looking document that quietly protects the old game. That was the council's sharpest warning, and the check is cheap insurance.

Read this off the map, not on top of itNothing below is invented. Each value is a behavior-shift on the system map (§6) (the "to" that replaces a behavior node). Each leader play is one of the intervention nodes, chosen because it cuts a specific mechanism. The sequence follows the vicious loops (you break the loop that feeds everything else first). The grey "◆ Map" line under each item is its exact trace.

Employee behaviors, the critical few (≈289 staff)

Three, not four. Each ships with a scripted Monday move, not a slogan.

1 · พางานเดินสุด Own it and drive it to done

Scripted move, The Owner's Handoff: when you pass any item on, attach one line, "งานนี้ทำถึง [X], ที่เหลือคือ [Y], คนรับช่วงคือ [ชื่อ], เสร็จ [วันที่], ติดอะไรกลับมาหาได้." No anonymous file at the last gate.

FixesBuck-passing + play-safe. Q19 #1 by far (283); cross-BU 4.00. Why nowA scripted move needs no new system, gives the 290 something to do in Wave 1, not just watch. MeasureCross-BU handoff-defect rate ↓; % handoffs carrying the owner-tag. OwnerBU managers (modeled) + all staff; carried by the informal leaders (Play 4).

◆ Map: the "to" that replaces behaviors Play it safe + Silo / dumping. Those are driven by Brave = punished and Solo KPIs, so the value only sticks once Plays 1-2 cut those mechanisms.

2 · จับมือข้ามหน่วย แก้ที่ข้อจำกัด Solve constraints together, across units

Cloned from พี่สิทธิชัย (พัสดุ): when a unit is blamed for delay, the opening move is "งานช้าตรงไหน, มาดู TOR/ระเบียบด้วยกัน หาเส้นทางที่ทำได้" not "ไปอ่านระเบียบเอง." Compliance-craft, not compliance-cage.

FixesSilo + the compliance-shield process. Q19 #2 (207); cross-BU 4.00. Why nowDecouple from the appraisal build, informal-leader exemplars carry it now in high-readiness Front BUs. MeasureCross-BU joint problem-solves logged; silo-perception ↓. OwnerBU + support heads; bright-spot AILs as exemplars.

◆ Map: the "to" for behavior Silo / dumping (fed by Solo KPIs + Hub-and-spoke). Already proven by assets Working teams, Compliance craft, Workarounds; installed by interventions Shared KPIs, Cross-BU labs, Cross-BU council.

3 · ตัดสินด้วยข้อเท็จจริง Decide on evidence; value real results, not connection

FixesPatronage at the behavioral level. Q19 (174 + 166); who-you-know 3.08. Why nowCredible only if Play 1 is real, the employee behavior and the leader-system are two halves of one fix. Measure% decisions with documented evidence; who-you-know item ↑; promotion-traceability. OwnerAll staff (behavior) + HR/exec (the system that makes it true).

◆ Map: attacks the keystone mechanism Patronage at the behavioral level. But behavior alone fails while the system rewards connection, so it is only credible once intervention Merit + PMS redesign (Play 1) makes it true. The value and the leader-system are two halves of one fix.

Integrity + service/results are woven into the handbook Do's, not headline values, matching the exec instinct and the data (neither is a top gap; pride already high).

The leader's playbook (≈30 leaders), this is where the real change lives

These five plays are the heart of the change. Each is a ⭐ move the roadmap (§3) sequences and the map (§6) explains. They are collapsed here to keep the page scannable; open the playbook for the full case behind each one.

Open the five leader plays, the case for each (what · why · measure · map trace)

Play 1 · เปิดเกณฑ์ วัดที่ผลงาน, Open the criteria, measure on merit KEYSTONE▸

What: Publish grade/comp/promotion criteria + raise logic; replace patronage appraisal with fact-based, cross-BU-calibrated ratings. Ride the live system, PMCU HR is already redesigning the PMS, so this is integration not greenfield: Lead+D supplies the behavior-to-PMS mapping, HR owns the build.

Why: Opacity shields patronage; publish the criteria and patronage loses its cover automatically, no person is accused, the secrecy just stops protecting it. Confirmed by four blind analysts and the exec's own best quick-win score (10).

Why now (split by depth): Wave 1 = public commitment + disclose as-is bands. Wave 2 = the calibrated redesign (the half that kills patronage). Run each deep step as a test-the-fear experiment, publish one unit's bands first and watch whether the feared catastrophe arrives.

Two pieces it cannot ship without: (1) a real appeal channel, owned by someone other than the decision-maker, live before the first criteria-based promotion. Published criteria with no way to contest an off-rubric call can actually raise the sense of unfairness, because staff can now see the gap and still have no recourse. (2) A published-vs-observed tripwire: the coalition tracks whether the rationale on paper matches who actually got promoted, and flags the drift early.

Measure: comp/promote-clarity 2.73 → ≥3.5 by month 12 (a staged target the org's own rate of change can support; the +4.5 in 18 months that v1 implied is faster than PMCU has ever moved any item); % of promotions with a published, criteria-referenced rationale (target 100% from month 6); appeals received and resolved (tracked, never suppressed).

Durability lock (primary embedding, not a paper charter): bind the sitting exec to a public criteria-referenced rationale for every promotion, and stage one honored "uncomfortable call." One enacted incident embeds more than a year of charter language.

◆ Map: this play IS intervention node Merit + PMS redesign (+ Career ladder). One move, three fix-edges: it cuts the entire keystone bundle Secrecy = power → Secret criteria → Patronage. It goes FIRST because every other amber node depends on it being real.

Play 2 · กระจายอำนาจให้จบที่หน้างาน, Cede decision authority to where the work is▸

Fixes: Authority-hoarding + "accountability without authority." 700+ standard leases escalate to the top of house; cross-BU 4.00.

Stakeholder play: the signatures sit with รองอธิการ อาจารย์แป๊ป (day-to-day "The One" = ผอ. พี่ชอว์). Pre-frame privately with พี่ชอว์; lead with the revenue/competitiveness case; never deliver as "you are the bottleneck"; offer a voluntary, face-saving pilot. Design tiered-with-audit.

The structural half of จับมือข้ามหน่วย: the cross-unit behavior cannot be coached into existence while every unit is still measured alone. Name one real shared goal that no single BU can hit by itself (a tenant-facing service target that spans Front and Back units), and stand up a small cross-unit pilot team with a shared scorecard. That shared goal is what makes "solve it together" rational instead of a slogan. When you push a decision down, move four things together so it does not snap back: the authority, the data, the skill (trained first), and the recognition for using it well.

Measure: % decisions resolved at the right level without escalation (≥70% of the pilot class); approval cycle-time ↓; zero audit findings traceable to a piloted decision (the non-negotiable threshold); cross-BU 4.00 → ≤3.0.

◆ Map: interventions Decision-rights + Reengineer approvals, aimed at the red authority spine Authority hoarding → Hollow middle mgmt → No authority → Manager burnout → Talent drain. Cut the head of the spine and the whole cascade slackens.

Play 3 · ฟังให้จริง เปิดพื้นที่ปลอดภัย, Make voice safe (split by depth)▸

Wave 1: teach the three leader voice-safety micro-behaviors, fix the leak, stand up the duty-of-care net, and pre-commit a rupture protocol. Wave 3: a real standing channel for staff to raise issues upward (a skip-level review or an ombudsperson, specified once the Wave-2 safety baseline tells us which fits).

The 3 micro-behaviors: (1) frame the work as a learning problem; (2) model your own fallibility out loud, "I have rated on relationship before, here is what I am changing"; (3) ask genuine questions and wait, especially toward the quietest. Vehicle: a regular structured one-on-one between each manager and their direct reports.

The rupture protocol (the piece that actually builds safety): in a culture shaped by ten years of public scolding, the first time someone speaks up and gets punished re-teaches silence to the whole organization in one incident. So the exec pre-commits, in writing, what counts as punishing a disclosure, a named non-rotating HR person who receives it, and a 48-hour public-repair move ("this is exactly the kind of call we said we would protect"). One repaired rupture builds more safety than ten workshops.

Gate the one-on-one rollout on observed safety, not attendance. Re-pulse each leader's own team on a short safety check every 8 weeks; a leader opens one-on-ones only once their team's score crosses a floor. An untransformed leader (whose team still scores low) sent into one-on-ones simply confirms that speaking up is unsafe.

Why: safety is a precondition for the keystone. A published rubric only kills patronage if someone can safely say "that promotion did not follow the rubric." Protect the smart, well-reasoned call that did not work out, not the careless rule-break.

◆ Map: interventions PMI / 1:1s + Process facilitation + Conflict + care, cutting mechanism Deference + scolding. This breaks the single tightest vicious loop on the map: Silence ↻ Secrecy = power, silence is what keeps the secrecy safe. Break it early or the keystone never holds.

Play 4 · รักษาความต่อเนื่อง, Continuity: a coalition + a non-rotating lock▸

(1) A real guiding coalition (~15–20): the new exec, credible BU heads, the non-rotating HR layer, and the Authentic Informal Leaders (พี่ดาว, พี่หนึ่ง, นิพัทธ์, พี่สิทธิชัย). The AILs are named only with their consent: in a patronage network, being publicly tied to the reform carries real exposure, so this is an invitation, not an assignment. Charter the group in Wave 1 (its mandate, who decides what, and an explicit succession trigger: if แป๊ป or ชอว์ rotates before month 18, a named non-rotating custodian runs the incoming exec's briefing within 30 days). An uncharterted group in a เกรงใจ culture defaults to "The One" the moment the exec walks in.
(2) The lock is the audit binding, and it starts in Wave 1. Quietly open the conversation with internal audit and แป๊ป in month 1 to bind the new criteria to the สตง. regime. This structural anchor, not the sitting exec's goodwill, is the primary refreeze. The one enacted promotion is the accelerant that proves it, not a second pillar.
(3) Name the consequence. After the first calibrated cycle, the coalition reviews promotions for an off-rubric pattern. A leader with repeated off-rubric calls after coaching is moved out of a gating role, not dismissed (civil-service-feasible). Without this, the published criteria are just a new document sitting on top of the old game. This is the single most-skipped culture-change practice and the most predictive of failure.
(4) Onboarding as the carrier: each incoming exec is briefed on what their predecessor attended to, funded, and rewarded, and on the incident that will test them. Anchor to Chula-mission pride, never to this administration.

One check before the keystone is handed to a driver: publishing merit criteria disrupts a deeply entrenched norm, and that kind of change sticks only when its champion is someone trusted close to the fence-sitters, not a well-connected broker. If แป๊ป (rotating, holds the signatures, gains nothing personally) does not fit, the answer is not to lean on him harder, it is to pair him with a co-chair whose standing does fit, most likely a non-rotating AIL.

◆ Map: interventions Guiding coalition + Durability lock + Knowledge mgmt, aimed at the locked context 4-yr rotation and mechanism Strategy whiplash. These are the only fix-edges that reach the rotation node, without them, the next administration eats every other play.

Play 5 · เตรียมใจผู้นำให้ "ปล่อย" ได้จริง, Build leaders' capacity to let go▸

A structured "letting go" process for the ~30 leaders, run in small same-rank groups (the trust to be honest cannot hold in a room of 30, and never with a leader's own reports present). Start with disconfirmation: before any coaching, each leader sees their own unit's data, the people who left and the ones who turned down promotion under them. Leaders today carry almost no felt pressure to change, so this is the missing first step. Why: when 23 leaders volunteered safe commitments and not the deep pains, that is not readiness, it is the immune system protecting itself. Asking for a public transparency commitment in Wave 1 while this work waits until Wave 2 is backwards: a leader whose private fear ("open criteria means I lose face and control") is never surfaced will perform transparency in public and protect the back-channels in private. So the patronage-holding leaders do this work before the public commitment, not alongside it. Name the developmental demand to the exec plainly: we are not only changing rules, we are asking ~30 people to grow into them. Budget for that, or the rules revert.

◆ Map: intervention Leader coaching (letting go). On the map, asset Leaders ready carries a caveat, the readiness clusters on safe levers, which is the immunity showing itself. This play is what converts that soft asset into the real capacity Plays 1-2 demand.

How the behaviors reach 289 people, and outlast us, the TOR toolkit

The deliverable, and why it is more than a document The TOR asks for a Toolkit that turns the Core Values into practice: a Culture Handbook, a Town Hall Deck for the launch, a Manager Communication Guideline, and Key Messages for the exec to introduce the new values. We build all of it by 30 มิ.ย. But a toolkit is only worth the paper unless what it says is what the system actually does, so on the roadmap it is not a one-off handover. It is a fifth workstream, "communicate and embed the behaviors" (§3, the rose bars): build the toolkit → launch it riding a real Wave-1 win → cascade it manager-by-manager → wire the 3 behaviors into recognition, onboarding, 1-on-1s and appraisal → reinforce and measure that staff actually see the behaviors, not just recite them.

This is what answers the two outcomes the TOR is really buying: usable tools that build the culture for the long term (a handbook + guidelines a manager can pick up and run, not a slide that dies after the town hall), and a clear path for developing people sustainably (the behaviors become how recognition, growth and appraisal work, so the change keeps running after Lead+D walks out). The launch is deliberately held until the system is visibly starting to move, because values announced into an unchanged system are exactly the "แค่กระดาษ" staff have learned to expect.

3 Roadmap, three waves

This is the plan, and the heart of the whole recommendation. Everything else supports it. The roadmap holds the 5 critical moves (the ⭐ bars) plus the backlog, on one timeline, paced to what PMCU can realistically absorb, with the gates and the order that make it work. The "why" behind each move lives on the diagnosis map (§6). Click any bar for its full plan: what, when, why, how, who, the politics to manage, and the risks. If you read one section in depth, read this one.

Can PMCU build the pay and structural systems in one month? Honest answer: no, and here is exactly what one month does buyPMCU is audit-bound (สตง. plus the Procurement Act), civil-service-paced, and its reward and HR systems have been frozen 8 to 10 years. So Month 1 buys decisions, disclosures, and one pilot, not built systems.

Genuinely doable in the first month (these are signatures, statements, communications, protection, and one workshop, not system builds): form the coalition · the exec transparency commitment · suspend the headcount-forfeiture rule · close the HR leak · disclose the as-is pay bands (publishing what already exists) · stand up care for the 5 distress cases · run the leader voice clinic for the ~30 · baseline the pulse · fund one ritual staff asked for.

NOT a one-month job (multi-quarter builds, paced across Waves 2-3): the calibrated PMS, career ladder + pay-band, delegation-of-authority, BPR of approvals, the service desk, training delivery, onboarding. Forcing these fast under personal audit liability is how you get a grievance or an audit finding. And the org has a day job: it can hold ~4-5 active workstreams at once, no more. That is a hard limit, not a wish. The leadership group runs a simple board, holds the limit, keeps the rest of the moves in a waiting list, and starts the next one only when something finishes (most-urgent-first). A new move starts when one ends, never because it suddenly feels urgent. So Wave 1 is mostly leadership and governance work that adds little frontline load, and staff-facing change ramps up in Wave 2.

The sequence IS the intervention, six orderings that are non-negotiable

Contract the sponsors before the exec room. The keystone strips power from แป๊ป + ชอว์. Co-diagnose + contract with them privately BEFORE 13 ก.ค. so they co-own it, or their hesitation detonates live. (The single most-named council fix.)
Coalition before everything else. Someone must own this across the 4-year rotation, or it dies at the next handover.
Close the leak + coach leaders on voice BEFORE opening 1-on-1s. Sending scolding-prone, untrained leaders into 1-on-1s confirms to staff that speaking up is unsafe. The voice clinic gates the PMI rollout.
Coach leaders to let go BEFORE handing them more authority. Hand power to leaders who cannot release it and it snaps back harder, with a grievance attached.
Build the skill before pushing decisions down. You cannot decentralize a skill that was never built, and under personal audit liability an under-skilled delegate is dangerous.
Disclose early, redesign in the middle, lock late. The public commitment is Month 1; the fair appraisal is built in the middle; the audit-anchored lock comes only after one real promotion has proven it works.

Three hard gates, the plan stops if any of these is not met

Sponsor-readiness gate (before committing the keystone). Read the readiness of the two people the reform takes discretion from, อาจารย์แป๊ป and พี่ชอว์, not only the ~30 line leaders. If they are not genuinely behind it, do not open the criteria yet. Lead with making voice safe and handing decisions down, and the merit reform becomes the second move. Publishing fair rules into a fearful room just produces a fair-looking cover for the old game.
Legal gate (before publishing pay/promotion rules). An outside Thai HR-legal and civil-service review must clear the published bands and criteria first. Changing pay and promotion in a สตง.-audited Chula entity carries real legal exposure, and this is the one area our own knowledge base does not cover.
Proof-point gate (before declaring any win). One real, criteria-based promotion, including one honored hard call where the rules did not favour the connected candidate, must happen inside the funded window (Wave 2, month 3 to 6), before any "you asked, we did" win is celebrated. It is a milestone that blocks the launch-and-celebrate work from turning green. Otherwise the cheap early wins read as success, the engagement ends, and the keystone (the only deep move) never gets built. One real promotion teaches more than a year of posters.

Wave 1 · 0–90d
Remove brakes, open the keystone, bank a felt win

Wave 2 · 3–9 mo
Build merit, cede authority, build the human side

Wave 3 · 9–18 mo
Open the loop, de-silo, lock past the rotation

Pay & careers Systems & structure People & relationships Direction & continuity Communicate & embed ⭐ keystone

Click a bar for the full step-by-step. Every intervention bar is a node in §6 and a row in the backlog, the map, the matrix, and this timeline are one object. Two kinds of bar sit on top of that mechanism layer rather than being mechanism nodes themselves: the gold Wave-0 "Sponsor co-diagnosis + contracting" bar (the OD entry/contracting precondition that earns the right to run everything else), and the rose "communicate & embed" workstream (the TOR toolkit that carries the 3 behaviour-shifts already on the map out to all 289 staff and wires them into the people systems so they last). Bars are paced to PMCU's real capacity, not best-case, and held to the coalition's ~4-5 active-work limit. Re-check the 3–5 process measures every 4–6 weeks; the mo6 recycle gate decides whether Wave 2 is funded. Key dates: TOR + Culture Handbook 30 มิ.ย.; exec presentation 13 ก.ค.

5 The backlog, the full Option Pool

The five leader plays in §2 are the recommendation. This is everything else we could do: every other move, each one tracing to a mechanism on the map (§6). The leadership group holds ~4-5 active at once and pulls the next item only when one finishes, so the exec is approving five plus a disciplined way to choose what comes next.

This is the backlog, not the planThe recommendation is the 5 critical moves above (the ⭐). This full menu is the Option Pool: every other move we could make, each one tracing to a mechanism on the map. The leadership group keeps a hard limit of ~4-5 things active at once and pulls the next item off this list only when one finishes (most-urgent-first). So the exec is not buying 25 projects. They are approving 5, and a disciplined way to choose what comes next. The human-side moves are the largest group, because the structural fixes only survive if the human side is built alongside them, which is the half a rules-only plan always forgets.

Move	Cuts / enables (map node)	Wave	Owner
Pay & careers, make merit real (7)
⭐ Merit + PMS redesign	SECRECY · SECRET-CRIT · PATRONAGE	1–2	HR + Exec
Career ladder + pay-band	SECRET-CRIT · PAY-CAP · REFUSE-PROMO	2	HR
Training system (restart)	NO-TRAIN · NO-AUTH	2	HR + LA
Onboarding / socialization	NO-TRAIN · ENDURE	2	HR
HR-pipeline fix	HR-GATE · BURNOUT	1	HR + Exec
Recognition + re-fund rituals	NO-RITUAL · PATRONAGE	1	BU heads
Knowledge mgmt / Continuity Book	WHIPLASH · ROTATE	2	HR + coalition
Systems & structure, fix the plumbing (5)
Decision-rights (RACI + audit)	HOARD-AUTH · NO-AUTH	2	Exec + COO
Cross-BU shared KPIs	SOLO-KPI	2	Exec + BU heads
De-silo service desk	SILO · HUB-SPOKE	3	Exec + Unisearch
Reengineer approvals (BPR)	SLOW · HOARD-AUTH	2	COO
Role / JD clarity + SLA	DUMP · SOLO-KPI	1	BU heads
People & relationships, make the structural moves survivable (9, the largest)
Process facilitation + meeting norms	DEFER · SILENCE	1	Lead+D
PMI / recurring 1:1s	DEFER · SILENCE	1	BU heads
Conflict + care / EAP	BURNOUT · WAIT-OUT (5 distress cases)	1	HR + Lead+D
Pulse feedback loop (4–6 wks)	SECRECY (models transparency)	1	Lead+D + HR
Leader coaching (letting go)	HOARD-AUTH · DEFER (the immunity)	2	Lead+D
Team building (spread star teams)	STAR-TEAMS · SILO	2	Lead+D + BU
Cross-BU problem-solving labs	SILO	2	Lead+D
Cross-BU council (parallel structure)	SILO	2	Exec
Future-Search (staff-owned vision)	WHIPLASH	2	Lead+D + Exec
Direction & continuity, lock it past the rotation (4)
⭐ Guiding coalition + vision continuity	WHIPLASH · ROTATE	1	Exec
Identity alignment (w/ Unisearch)	IDENTITY · PLAY-SAFE	2	Exec + Unisearch
⭐ Durability lock (charter + audit refreeze)	ROTATE (protects Merit-PMS)	3	Exec + HR
Self-design capability	WHIPLASH · ROTATE	3	Lead+D + Exec
Communicate & embed the behaviors (5, the TOR toolkit), turns the 3 values into something usable + lasting
⭐ Core Values Toolkit (TOR deliverable)	the 3 behaviors → made usable (Handbook · Town Hall Deck · Manager Guideline · Exec Key Messages)	0–1	Lead+D
Launch the Core Values (Town Hall)	SECRECY (models openness)	1–3	Exec + Lead+D
Manager-led cascade to teams	the 3 behaviors → into daily work	2–6	BU heads
Embed behaviors in people systems	reinforced by recognition · onboarding · 1:1 · appraisal	4–15	HR + BU heads
Reinforce + measure adoption	SECRECY (closes the loop, proves it lasts)	3–18	Lead+D + coalition

The full move portfolio (the four OD families plus the communicate-and-embed workstream). ⭐ = a critical move the exec actually approves now; the rest is the Option Pool, pulled by the leadership group as slots free.

Added by the generative + red-team pass , moves the first plan missed, found by sweeping the full library

These are not new theory. They are interventions already in our knowledge base that the first draft (built on one OD taxonomy) skipped. They join the Option Pool; two of them harden the critical few directly.

Added move	What it fixes / why it was missing	Where it goes
Anti-gaming check on the new criteria	Designs the reward rules against the SPECIFIC patronage failure (same rule for everyone, no connected-person exception) so the new rubric can't be quietly gamed. The strongest comp tool we own, unused in v1.	folds into the keystone
Outside HR-legal review (Thai civil-service)	Publishing pay bands + changing promotion rules in a สตง.-audited Chula entity carries real legal exposure. The one gap with NO coverage in our library. A partner, not a DIY move.	GATE before publishing
Cross-unit work debrief (after-action review)	A short, disciplined "what worked, what didn't" after shared work. ~20% performance lift, free, and it makes จับมือข้ามหน่วย a self-correcting habit instead of a slogan.	Option Pool, Wave 1 pilot
Onboard the next rotated-in exec into the reform	The 4-year rotation is the plan's biggest leak; v1 left it a thin line. A real 90-day handoff protocol protects the keystone across the one rotation it must survive.	strengthens move 5
Confidence-building micro-workshop (for the worn-out base)	A short, evidence-based session that rebuilds hope + resilience in a surveyed-out workforce + the 5 distress cases. Cheap, pairs with the duty-of-care net.	Option Pool, Wave 1
Non-cash rewards + a real change-communication plan	Recognition the audit can't block (the welfare-gap wound), and a proper "who-says-what-when" comms cascade, both absent from v1.	Option Pool, Wave 1

Appendix B · Stress-test

7 How we stress-tested it , 25 voices + our own case against

Open the stress-test (the 25-voice council and the red-team case against the plan)

25 of 25 lenses judged the diagnosis + keystone SOUND. Not one faulted the analysis; every concern lands in the activation layer and piles onto the six themes below. Verbatim outputs (full PROTECT / ISSUES / SEQUENCING / MISSED per voice) are recovered to pmcu-rebuild-council-notes-2026-06-28.md.

Then we did it again, with more of our libraryFor v4 the plan went through a second, larger pass: 25 atom-grounded lenses (every relevant scholar plus the domains the first council under-sampled, organizational justice, total rewards, anti-fraud incentive design, behavioural economics, motivational interviewing, network-fit) and 5 fresh red-team reviewers, with a completeness-critic checking nothing was missed. That pass is what produced the sponsor-readiness re-gating, the appeal channel, the rupture protocol, the team-level safety gate, the earlier proof-point promotion, the network-fit co-chair, and the de-jargoning. Findings recovered to pmcu-council-findings-2026-06-28.md.

Who was in the room15 scholar agents (Cummings-Worley, Anderson, Schein, Kotter, Lewin, Kegan-Lahey, Edmondson, Katzenbach, Groysberg, Latham, Watkins, Heath, Bauer, Dewar-Keller, pmcu-advisor) + group-dynamics (Yalom) + MI + the 7-book culture-change canon we digested this week (Alvesson-Sveningsson, Burke, Cameron-Quinn, SAN Seven Deadly Sins, Bashforth, Schein-2016) + 3 ingested OB/agile lenses the named-agent council had been missing (Organizational Justice / Greenberg, Agile-Kanban-Flow / Rigby-Leopold, OD-consulting-process). Honest library gap: Teal / Laloux was never ingested, so it could not be consulted.

1 · The SPONSOR is the load-bearing risk 8 voices · highest severity▸

The single most-repeated finding. Schein: "never tests whether แป๊ป/ชอว์ are themselves patronage-holders." Burke: "the sponsor who must surrender the most never examines himself before launch." Anderson: it is "doing change TO them." OD-consulting: "no contracting step that names, to their faces, that the keystone costs THEM power." Echoed by Dewar-Keller, pmcu-advisor, Watkins, Bauer. FIX: a private joint-diagnosis + contracting with แป๊ป/ชอว์ before 13 ก.ค., naming that the keystone strips their power, and reframing 13 ก.ค. from a presentation into a co-owned diagnosis so they present the keystone, not us. Now the first Gantt bar (Sponsor co-diagnosis + contracting, Wave 0).

2 · Transparency without a consequence is a dashboard 3 voices▸

SAN: "specify the stick, what happens to a leader who promotes off-criteria." Fairness research (Greenberg): a fair process needs a way to challenge a decision; publishing criteria without one can actually raise the sense of unfairness, because people can now see the gap. Kegan-Lahey: "measure the gap between published-rationale and observed promotion as a live tripwire." FIX: the Merit move now carries an appeal/review channel, one honored consequence event in Wave 1 (not a footnote), and a published-vs-observed gap tripwire.

3 · The measurement is thin where it must be hard 3 voices▸

Latham: "no rater agreement / rater-training, the single methodological hole that can sink the keystone." Cameron-Quinn: "no baseline culture-profile survey, so you cannot prove the culture moved." Cummings-Worley: "no mo6 recycle gate, no institutionalization scorecard." FIX: rater-calibration training + a rater-agreement check on the appraisal; an culture-profile survey now-vs-preferred baseline run with the leaders (re-run at 12mo); a mo6 recycle gate that re-enters diagnosis if comp/promote-clarity hasn't moved off 2.73.

4 · You're touching the reward system without bolting down the anchor 3 voices▸

Lewin: "no refreeze on the ASSET, job-security is the restraining-force anchor; touch the reward system and the long-tenured base reads 'they are taking away what we have.'" Katzenbach + Heath: "pride-builder energy is thin; bright spots are named but not cloned hard enough." FIX: an explicit job-security guarantee stated up front in Wave 1, a Pride-Builder ritual (AILs publicly telling the family-pocket wins as identity, not deficit-fixing), and a Wave-1 positive-deviance sprint that transplants the stars' specific behaviors.

5 · Capacity is asserted as prose, not built as a system Agile-Kanban + Cummings-Worley▸

Agile-Kanban (Rigby / Leopold): "'~4-5 active' is a sentence, not a real limit. Make the coalition a traffic-control board that holds the limit, starts a new move only when one finishes, picks the most-urgent next, tracks how long each move takes, and shows the exec a visible board so they can SEE overload before it bites." Cummings-Worley: "let Wave 2 start on a readiness check, not a calendar date." FIX: the ~4-5 limit is now a real board the coalition owns, waves start on readiness, and the rest of the moves sit on a waiting list pulled most-urgent-first.

6 · Readiness + team-level safety must precede the public promise 4 voices▸

Alvesson-Sveningsson: "a public promise the leaders cannot yet keep manufactures hypocrisy, the 'แค่กระดาษ' verdict by month 3." Edmondson: "safety is team-level, not org-level; you will get safe pockets and unsafe ones, add a rupture protocol." MI: "the leaders may be pre-contemplation, not ambivalent, don't mandate; evoke." Kotter: "anchoring before the wins exist." FIX: the leader voice-clinic + surfacing the leaders' real fears now gate the public transparency commitment and the 1-on-1s; let-go coaching gates delegation; the single success metric in the risk register is the plain question will staff call this "แค่กระดาษ"?, ranked above any dashboard number.

7B · The case AGAINST this plan , we argued ourselves wrong, on purpose

The 25 voices above all judged the plan sound, which is a warning sign on its own (agreement can be groupthink). So we ran the opposite exercise: three reviewers whose only job was to argue the keystone is wrong, the plan fails, and we should do far less. They converged, and they reshaped the recommendation. This is why the plan leads with five moves and a conditional keystone, not a 25-move menu.

Challenge 1 · "Open the criteria first" may be the wrong move reshaped the plan▸

In a deep-patronage, face-sensitive culture whose sponsors benefit from the patronage, publishing fair rules before there is any trust to absorb them can drive patronage underground (now hidden AND deniable) or trigger an elite backlash that kills the engagement. The audit floor we treat as a lock can just as easily become a cover: a documented rationale makes patronage deniable, not absent. How the plan answers: the keystone is now conditional, gated on a leader-readiness read. If readiness is low, we lead with safety + delegation and the merit reform becomes the second move.

Challenge 2 · The plan dies of "premature victory" reshaped the plan▸

Wave 1 is full of cheap, visible wins (a refunded ritual, removed brakes, a public commitment). The exec reads them as proof it worked, the engagement ends as the deep work begins, and the keystone (the only deep move, all in Waves 2-3) never gets built. Theatre, then reversion. Front-loading felt wins, as written, is the bait for this, not a guard against it. How the plan answers: the proof-point gate, one real, criteria-based promotion must happen inside the funded window before any win is celebrated. The win condition is "PMCU ran one fair promotion without us in the room, " not "PMCU adopted the values."

Challenge 3 · 25 moves against a 4-5 limit is fantasy reshaped the plan▸

A 25-move menu against a real capacity of ~4-5 at once will be cherry-picked into incoherence, and to a scope-wary, audit-bound exec it reads as a consultant maximizing scope. The critical few wins more buy-in, not less: a smaller ask, defensible move by move. How the plan answers: the recommendation is now 5 critical moves; the other twenty are a visible backlog (Option Pool) the leadership group pulls from as slots free. The exec approves five and a disciplined way to choose what comes next.

What the red-team did NOT shakeThe diagnosis. All three accepted that patronage-behind-opacity is the root. The fight was about sequencing and scope, not the analysis. So the map (§6) and the keystone-as-target stand; what changed is that we now check readiness before committing it, prove it with one real promotion, and present it as five moves, not twenty-five.

The meta-lesson (for the next engagement)Our scholar-agent council UNDER-SAMPLES our own knowledge base, and a critique-only council never tests whether the core idea is wrong or what is missing. Organizational justice (the exact theory for a fairness keystone) and the team-debrief (a 20% free win) were both in the library the whole time, unused. The fix is a method: sweep the full library, then run a generative pass + a red-team pass, not just critics. (Captured to system memory + Tong's build queue.)

Stream	Hard signal	Confidence
Value survey (raw re-analysis, n=212/131)	Worst: comp/promote-clarity 2.73 (67% low), trust-leak 2.88, who-you-know 3.08, stay-for-security 3.17, strategy-churn 3.29, social-bonding 3.52, promotion-not-merit 3.73, cross-BU 4.00. Strength: Chula-pride 5.32.	data-certain
Q19 desired behaviors (forced-rank)	Accountability-to-completion 283 (runaway #1), constraint-solving 207, service/results 190, evidence-based 174, value-results 166, integrity 161.	data-certain
Phase-1 engagement, both 2025 waves	Comp/eval/career-growth stayed lowest; relational dims rose (psych-safety +0.27, learning +0.47); leader-vision the only decliner (−0.13).	data-certain
Phase-1 qualitative (both waves)	All 8 worst 2026 items have a named 2025 ancestor; HR leak named verbatim; staff already prescribed the fixes.	data-certain
Manager interviews (28)	Problem is structural not attitudinal; the alarm, competent staff refusing promotion + change-agents burning out.	strong (tier-2)
Focus group (729 quotes)	8 polarities; opacity flagged highest-leverage; family-pockets prove silo isn't fate; 5 distress cases.	strong (raw)
Blind leverage check (4 analysts)	Converged with no keystone named: root = opacity-as-power; move = publish transparent criteria + fact-based appraisal.	strong (convergent)
Exec decision-board scores	Fair-evaluation best quick-win (10); Growth highest lasting (9.2); Trust&Voice + Service hardest; Pride narrative-only.	exec-provided

PMCU Culture Transformation, Executive Recommendation

★ The recommendation, in one screen

เปิดเกณฑ์ความก้าวหน้า

ปลดเบรก + ชัยชนะแรก

พางานเดินสุด

ทำให้พูดได้ปลอดภัย

ล็อกให้อยู่ข้ามการหมุนเวียน

1 The problem, and the shift

2 The recommendation

Employee behaviors, the critical few (≈289 staff)

1 · พางานเดินสุด Own it and drive it to done

2 · จับมือข้ามหน่วย แก้ที่ข้อจำกัด Solve constraints together, across units

3 · ตัดสินด้วยข้อเท็จจริง Decide on evidence; value real results, not connection

The leader's playbook (≈30 leaders), this is where the real change lives

How the behaviors reach 289 people, and outlast us, the TOR toolkit

3 Roadmap, three waves

4 The decision the exec must make (13 ก.ค.)

Confirm + decide

Sponsorship asks

5 The backlog, the full Option Pool

Added by the generative + red-team pass , moves the first plan missed, found by sweeping the full library

6 The system map (internal, never shown raw to the client)

7 How we stress-tested it , 25 voices + our own case against

7B · The case AGAINST this plan , we argued ourselves wrong, on purpose

8 Evidence base

9 Unisearch alignment

10 Provenance, what was read, and how

Read directly / re-analysed

Tier-2 digest / honest gaps