Product-org-os customer-health-scorecard

'Create customer health scorecard assessing account status across engagement, adoption, and satisfaction. Activate when: "customer health", "health score", "account health", customer status

install
source · Clone the upstream repo
git clone https://github.com/yohayetsion/product-org-os
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/yohayetsion/product-org-os "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/customer-health-scorecard" ~/.claude/skills/yohayetsion-product-org-os-customer-health-scorecard && rm -rf "$T"
manifest: skills/customer-health-scorecard/SKILL.md
source content

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

SignalModeConfidence
"update", "revise", "refresh" in inputUPDATE100%
File path provided (
@path/to/scorecard.md
)
UPDATE100%
"create", "new", "draft" in inputCREATE100%
"find", "search", "list scorecards"FIND100%
"the scorecard", "[Customer] health"UPDATE85%
Just customer name/segmentCREATE60%

Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete new health scorecard using template below.

UPDATE:

  1. Read existing scorecard (search if path not provided)
  2. Preserve structure, update metrics with new data
  3. Add new month to Historical Trend
  4. Recalculate health scores
  5. Show diff summary: "Updated scores. Previous: X/100 → Current: Y/100."

FIND:

  1. Search paths below for health scorecards
  2. Present results: customer, current score, last updated
  3. Ask: "Update one of these, or create new?"

Search Locations for Health Scorecards

  • customers/
  • health/
  • customer-success/
  • accounts/

Create a Customer Health Scorecard for the specified customer or segment.

Vision to Value Phase

Phase 5: Business & Customer Outcomes - This skill tracks customer health indicators.

Methodology

<!-- Source: Google HEART Framework — Kerry Rodden, Hilary Hutchinson, Xin Fu (2010) "Measuring the User Experience on a Large Scale: User-Centered Metrics for Web Applications" Published at CHI 2010. Developed at Google to provide user-centered metrics at scale. Framework: 5 dimensions (Happiness, Engagement, Adoption, Retention, Task Success), each decomposed via Goals → Signals → Metrics (GSM process). -->

This skill uses Google's HEART framework as the primary measurement structure, extended with B2B account health indicators. HEART provides five user-centered dimensions, each defined through the Goals → Signals → Metrics (GSM) process.

HEART Dimensions

<!-- Source: Google HEART — the 5 dimensions with GSM decomposition -->
DimensionWhat It MeasuresExample Signals
HappinessSubjective satisfaction, perceived ease of useNPS, CSAT, SUS scores, sentiment
EngagementDepth and frequency of interactionSession frequency, actions per session, DAU/MAU
AdoptionNew users/features gaining tractionNew signups, feature adoption rate, use case expansion
RetentionUsers/accounts returning over timeChurn rate, renewal rate, logo retention
Task SuccessEfficiency and effectiveness of core tasksTask completion rate, time-on-task, error rate

Goals → Signals → Metrics (GSM) Process

<!-- Source: Google HEART — GSM is the process for turning dimensions into measurable metrics. Goals = what you want to achieve; Signals = user behaviors indicating progress; Metrics = quantifiable measures of those signals. -->

Before scoring, define GSM for each dimension relevant to this customer/product:

DimensionGoalSignalMetric
Happiness[What satisfaction looks like][Observable user behavior][Quantified measure]
Engagement[What good engagement looks like][Observable user behavior][Quantified measure]
Adoption[What adoption success looks like][Observable user behavior][Quantified measure]
Retention[What retention success looks like][Observable user behavior][Quantified measure]
Task Success[What effective usage looks like][Observable user behavior][Quantified measure]

Output Structure

1. Overall Health Score

Score: X/100 [🟢 Healthy / 🟡 At Risk / 🔴 Critical]

<!-- Source: Composite scoring structure extends Google HEART with B2B relationship layer. HEART covers user-level health; Relationship covers account-level health. -->
ComponentWeightScoreWeighted Score
Happiness (HEART-H)X%X/100X
Engagement (HEART-E)X%X/100X
Adoption (HEART-A)X%X/100X
Retention (HEART-R)X%X/100X
Task Success (HEART-T)X%X/100X
Relationship (B2B)X%X/100X
Total100%X/100

2. Happiness Metrics (HEART-H)

<!-- Source: Google HEART "Happiness" dimension — subjective attitudes, satisfaction, perceived usability -->
MetricCurrentTargetTrendScore
NPS scoreXX↑/↓/→X/100
CSATX%X%↑/↓/→X/100
Perceived ease of useX/10X/10↑/↓/→X/100
Sentiment (support/feedback)Pos/Neu/NegPositive↑/↓/→X/100

3. Engagement Metrics (HEART-E)

<!-- Source: Google HEART "Engagement" dimension — depth and frequency of user interaction -->
MetricCurrentTargetTrendScore
DAU/MAUX%X%↑/↓/→X/100
Session frequencyX/weekX/week↑/↓/→X/100
Session durationX minX min↑/↓/→X/100
Actions per sessionXX↑/↓/→X/100
Feature usage breadthX%X%↑/↓/→X/100

4. Adoption Metrics (HEART-A)

<!-- Source: Google HEART "Adoption" dimension — new users and new use cases gaining traction -->
MetricCurrentTargetTrendScore
Activated usersX%X%↑/↓/→X/100
Use cases liveX/XX/X↑/↓/→X/100
Feature adoption rateX%X%↑/↓/→X/100
Integration depthXX↑/↓/→X/100
Admin engagementXX↑/↓/→X/100

5. Retention Metrics (HEART-R)

<!-- Source: Google HEART "Retention" dimension — rate at which users/accounts return over time -->
MetricCurrentTargetTrendScore
Logo retentionX%X%↑/↓/→X/100
Net revenue retentionX%X%↑/↓/→X/100
User churn rateX%X%↑/↓/→X/100
Renewal rateX%X%↑/↓/→X/100

6. Task Success Metrics (HEART-T)

<!-- Source: Google HEART "Task Success" dimension — efficiency and effectiveness of key user tasks. Measures whether users can accomplish what they came to do. -->
MetricCurrentTargetTrendScore
Core task completion rateX%X%↑/↓/→X/100
Time-on-task (key workflows)X minX min↑/↓/→X/100
Error rateX%X%↑/↓/→X/100
Support tickets per taskXX↑/↓/→X/100

7. Relationship Metrics (B2B Extension)

MetricCurrentTrendScore
Executive sponsor engagedYes/No-X/100
Champion identifiedYes/No-X/100
QBR participationX%↑/↓/→X/100
Escalation frequencyX/quarter↑/↓/→X/100

8. Expansion Signals

SignalStatusImplication
Approaching usage limits🟢/🟡/🔴[Opportunity/Risk]
New use case interest🟢/🟡/🔴[Opportunity/Risk]
Team growth🟢/🟡/🔴[Opportunity/Risk]
Contract renewal approaching🟢/🟡/🔴[Opportunity/Risk]

9. Churn Risk Indicators

IndicatorStatusImpactAction
Usage decline (HEART-E drop)🟢/🟡/🔴High/Med/Low[Action]
Champion departure🟢/🟡/🔴High/Med/Low[Action]
Task success degradation (HEART-T drop)🟢/🟡/🔴High/Med/Low[Action]
Happiness decline (HEART-H drop)🟢/🟡/🔴High/Med/Low[Action]
Competitive evaluation🟢/🟡/🔴High/Med/Low[Action]

10. Action Recommendations

Immediate (This Week):

ActionHEART DimensionOwnerDue Date
[Action][H/E/A/R/T][Owner][Date]

This Month:

ActionHEART DimensionOwnerDue Date
[Action][H/E/A/R/T][Owner][Date]

11. Historical Trend

MonthHealth ScoreHEART Breakdown (H/E/A/R/T)Key Events
[Month -3]X/100X/X/X/X/X[Events]
[Month -2]X/100X/X/X/X/X[Events]
[Month -1]X/100X/X/X/X/X[Events]
CurrentX/100X/X/X/X/X[Events]

Instructions

  1. Start with GSM — define Goals, Signals, Metrics for each HEART dimension before scoring
<!-- Source: Google HEART GSM process — don't jump to metrics without defining what success looks like -->
  1. Ask about specific customer if not specified
  2. Reference any customer data provided via @file syntax
  3. Not all HEART dimensions apply equally — weight by product type:
<!-- Source: Google HEART guidance — "not every dimension is equally important for every product" -->
  • B2C high-frequency: Weight Engagement + Retention highest
  • B2B enterprise: Weight Task Success + Happiness + Relationship highest
  • Growth-stage: Weight Adoption + Engagement highest
  1. Include both leading indicators (Engagement, Task Success) and lagging indicators (Retention, Happiness)
  2. Provide specific, actionable recommendations tied to HEART dimensions
  3. Save as markdown file
  4. Offer to create presentation version using /present