Skip to content

Instantly share code, notes, and snippets.

@esz135888
Created May 23, 2026 23:43
Show Gist options
  • Select an option

  • Save esz135888/0543237a06f9fe0d4bf1f3d8c7e80924 to your computer and use it in GitHub Desktop.

Select an option

Save esz135888/0543237a06f9fe0d4bf1f3d8c7e80924 to your computer and use it in GitHub Desktop.
PLS people response follow-up adoption scoring pack - job 0b893bd2

Adoption Rubric

Scoring

Customer clarity: 1 to 5.

1 means the statement is internal jargon. 5 means a customer can immediately understand the value.

Evidence strength: 1 to 5.

1 means no proof. 5 means proof includes customer case, number, artifact, or directly observed outcome.

Actionability: 1 to 5.

1 means no behavior change. 5 means the person names exactly what they will say or do in the next customer touchpoint.

Status

Accepted:

  • customer clarity >= 4
  • evidence strength >= 3
  • actionability >= 4

Needs coaching:

  • any score below threshold
  • reply contains only abstract claims

No response:

  • no structured reply by due time

Review Owner

Louis or assigned adoption owner reviews scores and decides whether the reply enters the customer-proof library.

profile_id status advantage customer_proof next_behavior confidence blocker clarity_score evidence_score actionability_score next_owner next_due
2a3628b7-d28f-4161-9ca8-ce15c4ead131 pending adoption_owner 2026-05-24
45a2dfa3-9174-4f64-b333-33dfd9eafc87 pending adoption_owner 2026-05-24
b89e1674-24fe-4189-808d-0825914ee35a pending adoption_owner 2026-05-24

Artifact URL Or PR

Primary artifact: https://gist.github.com/esz135888/0543237a06f9fe0d4bf1f3d8c7e80924

PR/deployment: not claimed. This job is communication/adoption workflow and no repository or deployment target was provided.

Upload-files note: PLS context returned deliverable: null, so no deliverable_id was available for the fixed upload-files helper. This pack uses a shared-cloud Gist.

Verification:

  • Gist published publicly.
  • HTTP and GitHub CLI verification completed before PLS completion writeback.

Production Readiness: Data Model, API, Sync, Permissions, Audit

Data Model

people_adoption_prompt

  • id
  • org_id
  • topic_key
  • source_signal
  • prompt_text
  • due_at
  • owner_profile_id
  • created_at

people_adoption_reply

  • id
  • prompt_id
  • profile_id
  • advantage
  • customer_proof
  • next_behavior
  • confidence
  • blocker
  • raw_reply
  • status
  • replied_at

people_adoption_score

  • id
  • reply_id
  • clarity_score
  • evidence_score
  • actionability_score
  • reviewer_profile_id
  • review_notes
  • reviewed_at

customer_proof_library_item

  • id
  • reply_id
  • approved_statement
  • proof_type
  • usable_in_sales
  • created_at

API / Sync

POST /api/pls/people-adoption/prompts

Creates prompt and recipient tasks.

POST /api/pls/people-adoption/replies

Stores structured reply and triggers scoring.

POST /api/pls/people-adoption/:reply_id/score

Stores reviewer score and status.

GET /api/pls/people-adoption/customer-proof-library

Returns accepted proof-backed statements for customer use.

Permissions

Raw replies are visible to respondent, adoption owner, and org leadership reviewers.

Customer-proof library items can be reused only after review.

Sensitive blocker notes should not be shown in customer-facing views.

Audit

Audit events: prompt sent, reply received, score submitted, coaching requested, no-response escalated, proof library item approved.

Decision Record

Decision

Create a follow-up adoption scoring pack instead of repeating the previous one-time message pack.

Problem

The people-sync signal repeats, but PLS context still lacks deliverable, project details, action items, or actual replies. Repeating the same prompt would not improve production maturity.

Options

  1. Recreate the original LINE prompt.
  2. Stop because context lacks replies.
  3. Produce a follow-up scoring and escalation pack.
  4. Build a full adoption system.

Recommendation

Choose option 3.

Reasoning

The next useful step is to capture reply quality and assign follow-up. This keeps the solution lightweight while preparing for SOP/watchdog upgrade if repeated.

Adoption Status

Recommended for immediate use.

Feedback Needed If Not Adopted

Provide actual replies, profile display names, LINE delivery result, and desired customer-proof review owner.

E2E Verification

Verification This Round

Artifact verification: shared-cloud Gist will be verified before complete.

Operational verification: LINE delivery and human replies are not claimed because PLS context did not include send result or reply data.

E2E Tests

Test 1: Prompt sent to three profiles. Expected: three pending tracker rows.

Test 2: Accepted reply. Input: structured reply with customer proof and next behavior. Expected: status accepted and library candidate created.

Test 3: Vague reply. Input: internal slogan without proof. Expected: status needs_coaching and Message B sent.

Test 4: No reply. Input: no structured reply by due time. Expected: status no_response and Message C escalation.

Test 5: External-use guard. Input: unreviewed statement. Expected: not available in customer-proof library.

<!doctype html>
<html lang="zh-Hant">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>People Adoption Follow-Up</title>
<style>
body { margin: 0; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; background: #f6f8fb; color: #20242d; }
main { max-width: 920px; margin: 0 auto; padding: 28px 18px; }
section { background: #fff; border: 1px solid #d7dce5; border-radius: 8px; padding: 22px; }
h1 { margin: 0 0 8px; font-size: 24px; line-height: 1.25; }
h2 { margin: 22px 0 8px; font-size: 16px; }
p, li { font-size: 15px; line-height: 1.55; }
.badge { display: inline-block; color: #0f766e; border: 1px solid #9ccbc4; border-radius: 999px; padding: 4px 10px; font-size: 13px; font-weight: 650; }
.reply { background: #eef8f6; border-left: 4px solid #0f766e; border-radius: 4px; padding: 12px 14px; }
code { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 13px; }
</style>
</head>
<body>
<main>
<section>
<span class="badge">Follow-up adoption scoring</span>
<h1>把公司優勢變成可評分、可對客戶使用的證據</h1>
<p>這輪不是重問一次,而是把回覆轉成 adoption evidence:accepted、needs_coaching、no_response。</p>
<h2>請回覆</h2>
<div class="reply"><code>優勢=...;客戶證據=...;下次對接會改=...;信心1-5=...;卡點=...</code></div>
<h2>通過標準</h2>
<ul>
<li>客戶聽得懂。</li>
<li>有案例、數字、交付物、結果或客戶原話。</li>
<li>下一次對接行為清楚。</li>
</ul>
</section>
</main>
</body>
</html>

Follow-Up LINE Pack

Message A: Follow-Up Prompt

昨天的題目不是要大家表態,而是要把公司優勢變成客戶感受得到的證據。

請今天 18:00 前用這個格式回覆:

優勢=...;客戶證據=...;下次對接會改=...;信心1-5=...;卡點=...

判斷標準很簡單:客戶聽完後,能不能知道我們強在哪裡、憑什麼相信、下一步會看到什麼不同。

Message B: Coaching Reply

這版還不夠客戶化。請補一個「客戶看得見」的證據,最好是案例、數字、交付物、速度、風險降低、成本下降或客戶原話。

補完後我會把它放進 customer-proof library;沒有證據的句子先不對外使用。

Message C: Escalation Reply

這題今天 18:00 後若沒有回,我會先標成 no_response,並請 adoption owner 指定一個你最近碰過的客戶情境,直接把優勢句重寫出來。

這不是催訊息,是避免公司有優勢但客戶沒有感覺。

Adoption Status Rules

Accepted: has advantage, customer-visible proof, and next behavior.

Needs coaching: has advantage but proof is vague or internal-only.

No response: no structured reply by due time.

{
"job_id": "0b893bd2-dda3-4c06-8ef0-1b262bb623d0",
"topic_key": "people-response-and-sync",
"ai_native_project_id": "02b5a090-b490-425c-8f19-e2e6cc3aa51b",
"learning": [
"Repeated people-sync signals should not produce duplicate prompts; they should upgrade into scoring, escalation, and adoption memory.",
"The key missing context is actual replies and profile display names.",
"A useful D7 artifact is a customer-proof library, not another summary."
],
"next_round": [
"Fetch or collect actual LINE replies.",
"Score each reply with clarity, evidence, and actionability.",
"If no response repeats, upgrade to watchdog or SOP."
]
}

Market Context And Maturity

External Context

Prosci ADKAR emphasizes that individual change requires awareness, desire, knowledge, ability, and reinforcement. This pack focuses on ability and reinforcement: people must write a usable customer-facing statement and be scored.

McKinsey transformation writing emphasizes sustained behavior and capability change, not only awareness. That supports using a reply tracker and coaching queue.

PLS Maturity Rating

Current maturity: Level 2.5 of 5.

Reason: the signal has a clear leadership concern and a usable first prompt pattern, but reply evidence is not yet captured.

Target D30 maturity: Level 4 of 5.

Reason: PLS should have a customer-proof library, adoption status, and escalation cadence for repeated people-sync gaps.

Sources

People Sync

Targets

  • 2a3628b7-d28f-4161-9ca8-ce15c4ead131
  • 45a2dfa3-9174-4f64-b333-33dfd9eafc87
  • b89e1674-24fe-4189-808d-0825914ee35a
  • Louis or adoption owner as reviewer.

LINE Short Message

這輪不是再問一次「公司優勢是什麼」,而是要把每個人的回覆變成可評分、可對客戶使用、可追下一步的 adoption evidence。

請今天 18:00 前回:

優勢=...;客戶證據=...;下次對接會改=...;信心1-5=...;卡點=...

如果沒有客戶證據,會標 needs_coaching;如果未回,會標 no_response 並交給 adoption owner 指派下一步。

Expected Signal

At least two structured replies and one accepted customer-proof statement.

Production Acceptance

Owner

Louis or assigned adoption owner.

Due

2026-05-24 18:00 Asia/Taipei.

Acceptance Criteria

  • Follow-up LINE prompt is sent to all three related profiles.
  • Reply tracker is created.
  • Each received reply is scored with the adoption rubric.
  • At least one accepted reply becomes a customer-proof library item.
  • No-response and needs-coaching statuses create owner/due follow-up.
  • Decision record is updated with whether to keep as communication, upgrade to SOP, or create watchdog.

Stop Conditions

  • Replies contain only slogans.
  • No owner is assigned for coaching or no-response.
  • Customer-proof statements are used externally before review.
  • Adoption score is not captured.

People Response Follow-Up Adoption Pack

Job: 0b893bd2-dda3-4c06-8ef0-1b262bb623d0 AI native project: 02b5a090-b490-425c-8f19-e2e6cc3aa51b Topic: people-response-and-sync Iteration: follow-up scoring and escalation

Situation

The signal remains the chairman reflection: the team has fallen behind in self-recognition, and customers therefore cannot feel the company's advantages. A prior D1 adoption prompt is not enough unless replies become scoreable and follow-up actions are assigned.

This pack turns the one-time LINE prompt into a measurable response and adoption loop.

D1 / D7 / D14 / D30 Path

D1: Send follow-up message to the three related profiles. Require reply in the structured format and mark each person accepted, needs_coaching, or no_response.

D7: Create a customer-proof library from accepted replies and a coaching queue for weak replies.

D14: Run one rehearsal where each respondent uses the revised advantage sentence in a customer scenario. Score clarity and proof strength.

D30: Upgrade repeated people-sync signals into an adoption scorecard or watchdog when the same response failure repeats three times.

Purpose-To-Purpose E2E

Original purpose: make company advantages visible to customers.

Output: follow-up message pack, scoring rubric, adoption tracker, escalation SOP, and data model.

Human adoption: each person either provides customer-facing proof or is assigned coaching/escalation.

Business improvement: customer conversations become clearer, leadership rework decreases, and weak capability/proof gaps become visible.

Measurable loop: reflection -> prompt -> structured reply -> score -> accepted/coaching/no-response -> customer-proof library -> next customer conversation -> feedback.

Value And Money Path

Revenue: stronger proof-backed advantage language improves proposal and renewal confidence.

Cost saving: reduces repeated leadership alignment and vague internal discussion.

Risk reduction: stops unproven internal claims from becoming customer-facing promises.

Conversion: moves team language from abstract advantage to evidence customers can understand.

Human leverage: gives each person a repeatable way to decide what to say, why it is true, and what behavior changes.

Owner / Due / Acceptance

Owner: Louis or assigned adoption owner.

Respondents:

  • 2a3628b7-d28f-4161-9ca8-ce15c4ead131
  • 45a2dfa3-9174-4f64-b333-33dfd9eafc87
  • b89e1674-24fe-4189-808d-0825914ee35a

Due: 2026-05-24 18:00 Asia/Taipei.

Acceptance:

  • Two of three respondents reply.
  • Each accepted reply includes advantage, proof, next behavior, confidence score, and blocker.
  • Every reply is scored.
  • Missing or vague replies have an assigned next owner and due date.

Signal Annotations

Source

Source: company_signal_mastery Topic key: people-response-and-sync Recent signal count: 16 Related people: 3 Related projects: 3 Latest evidence: chairman reflection that team self-recognition lags and customers cannot feel company advantages.

Project Annotation

AI-native project 02b5a090-b490-425c-8f19-e2e6cc3aa51b should remain a people adoption project until reply evidence shows whether the gap is messaging, proof, behavior, or actual capability.

Person Annotation

The three related profiles are respondents and should be scored by adoption status.

Decision Annotation

Decision: continue communication path for this round, but introduce scoring and escalation to prepare SOP/watchdog upgrade.

Risk Annotation

  • Repeated prompt without scoring creates noise.
  • People agree but do not change customer behavior.
  • Customer-facing statements may be unproven.
  • Missing replies hide capability or ownership gaps.

Source Project Handling

Do not merge the three source projects yet. Use reply scores to decide whether projects should merge, split, or upgrade.

Skill Usage

Applied model: purpose_e2e_toolbox_v2

Application

30-day path: D1 structured replies, D7 proof library, D14 rehearsal, D30 adoption cadence.

Purpose-to-purpose: chairman reflection becomes customer-proof language and measurable behavior change.

Value path: better customer conversations, less leadership rework, lower overclaim risk.

Human capability: respondents learn to turn internal advantage into proof-backed customer language.

Solution stack: follow-up prompt, rubric, tracker, data model, API, acceptance, E2E tests, people sync, and decision record.

Solution Selection

Selected Type

communication / follow-up LINE message draft with adoption scoring.

Options Considered

  1. Repeat the first prompt.
  2. Build a full system immediately.
  3. Create follow-up communication plus scoring and escalation.
  4. Convert directly into watchdog.

Recommendation

Choose option 3.

Reason

The issue is still a one-off people sync, but this is a repeat iteration. The right upgrade is scoring and escalation, not another loose message.

Upgrade Rule

If the same three-person adoption gap repeats three times, upgrade to SOP plus watchdog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment