Back to My Sales Training
First dayLast day
Customer Onboarding · course index

Chapter 8

KPIs, Reporting & Customer Success Metrics

The seven KPIs that explain the function · time-to-value as the most predictive metric in onboarding · adoption as the leading indicator of retention · customer health scoring as the early-warning system · reporting that leadership actually reads · data-driven improvement as the engine of a learning function.

Chapter 8 progress

0 / 9 · 0%

0/6 modules · 0/3 homeworkSaving locally · sign in to sync

Category

The Metric Frame

2 modules
1

Module 1 · ~14 min

The Onboarding KPIs That Actually Matter

“Most Onboarding teams track twenty numbers and steer by none. The professionals who lead the function track the small set that explains the whole story · and ignore the rest as decoration.”

Every operational function eventually drowns in its own metrics. Onboarding is no different. The temptation to measure everything that moves produces dashboards no one reads, reports no one acts on, and a function that hides behind activity rather than steers by outcome. This module sets out the small set of KPIs that genuinely explain the health of an Onboarding operation · the numbers that, taken together, tell you whether the function is winning or quietly failing. Master these and the rest of the dashboard becomes supporting evidence rather than competing noise.

The Seven KPIs That Explain the Function

  1. 1Time to Value (TTV) — How many days from contract signature to the customer's first measurable win. The single most important number in onboarding.
  2. 2Onboarding Completion Rate — Percentage of customers who finish the full onboarding programme inside the agreed window. Reveals whether the process actually finishes.
  3. 3Adoption Rate — Percentage of contracted features, services, or modules a customer is actively using at the end of onboarding. The leading indicator of retention.
  4. 4Customer Activation Rate — Percentage of customers who reach the defined activation milestone (first invoice sent, first campaign launched, first report generated · whatever the proof-of-value moment is for your service).
  5. 5Onboarding Net Promoter Score (oNPS) — Customer sentiment captured at the end of onboarding, separately from the broader relationship NPS. Surfaces the experience while it is still fresh.
  6. 6Readiness Score at Handover — A composite score (0–100) that confirms whether the customer is genuinely ready to transition to Account Management. Stops broken handovers at the gate.
  7. 7First-90-Day Retention — Percentage of customers still active and engaged ninety days after handover. The most honest verdict on whether onboarding actually worked.

━━ The Test of a Useful KPI ━━

A useful KPI changes a decision.

If the number moves and nothing changes in how you operate, the KPI is decoration. If the number moves and you reallocate effort, redesign a step, or change a conversation · that is a KPI worth keeping on the dashboard.

Number of welcome calls scheduled. Number of training sessions delivered. Number of tickets closed. These feel like Onboarding KPIs · they are not. They are activity metrics · they tell you what the team DID, not what the customer EXPERIENCED. A team can hit every activity metric and still produce confused, half-adopted customers who churn within ninety days. The seven KPIs above start with the customer outcome and work backwards · which is the only direction worth measuring in.

“The function is steered by seven numbers · everything else on the dashboard is supporting evidence.”

◈ Pause & Reflect

Take a moment.

Of the seven KPIs above, how many can you give the current number for · without checking a system, without asking a colleague, from memory? If the answer is fewer than four, you are running the function on instinct rather than evidence.

Hold on to these

  • Seven KPIs explain the function · the rest is supporting evidence or decoration.
  • A useful KPI changes a decision · if the number moves and nothing changes, the KPI is theatre.
  • Activity metrics measure what the team did · outcome KPIs measure what the customer experienced. Only the second kind matters.

Reflection · write it down

List the current numerical value for each of the seven KPIs in your operation (estimate where exact data is missing). For any KPI you cannot answer, write the single source of truth you will build or find in the next thirty days.

Saves automatically · come back to it whenever.

What you walk away with

You now own the small set of KPIs that explain Onboarding health · seven numbers that, taken together, surface every problem and every opportunity worth acting on.

2

Module 2 · ~15 min

Time-to-Value · The Most Important Number in Onboarding

“Every customer is silently asking the same question from the day they sign the contract · 'Was this a smart decision?' Time-to-value is the speed at which you answer it.”

If you only ever measured one thing in Onboarding, this would be it. Time-to-value is the elapsed time between the moment money changes hands and the moment the customer experiences the first measurable, undeniable proof that the purchase was worth making. It is the most predictive single metric in customer success · short TTV is correlated with higher retention, faster expansion, stronger advocacy, and lower support load. Long TTV correlates with churn, regret, and the slow drift of disengagement. This module shows you how to define it, how to measure it, and how to compress it deliberately.

━━ Time-to-Value Defined Precisely ━━

Time-to-Value = the number of calendar days from contract signature to the customer's first measurable outcome.

Not the first welcome call. Not the first login. Not the first training session. The first OUTCOME · the moment the customer produces something or achieves something that justifies the spend.

Defining the First-Value Moment for Your Service

  1. 1For an accountancy practice — First-Value = the first complete monthly management account delivered with confidence.
  2. 2For a marketing agency — First-Value = the first campaign launched and producing measurable leads.
  3. 3For a SaaS platform — First-Value = the first business workflow fully running in the new system, replacing the old one.
  4. 4For a recruitment firm — First-Value = the first qualified candidate shortlist accepted by the customer.
  5. 5For a managed IT service — First-Value = the first month with zero unplanned downtime and a clean cybersecurity report.
  6. 6The principle is the same in every case · find the smallest, soonest, undeniable proof that the purchase was worth it. That moment is what you are measuring the time to.

✦ Pro Insight · Why Short TTV Compounds Across the Whole Relationship

When the customer experiences value quickly, three things happen in parallel.

First, the buyer's internal narrative shifts from 'I hope this works' to 'This is working.' That narrative shift is the foundation of every expansion conversation that comes later.

Second, internal stakeholders inside the customer's business stop questioning the purchase · which means the buyer's reputation inside their own organisation is safe, and the relationship enters the trust phase faster.

Third, the customer becomes referenceable · they can be quoted, named, and pointed to as proof for the next prospect. Short TTV creates marketing assets, not just happy customers.

⚠ Common Mistake · The Most Common TTV Failure

Teams celebrate TTV milestones the team controls (system live, training delivered, configuration complete) instead of milestones the customer experiences (first outcome produced, first measurable benefit, first 'this is working' moment).

The team can be hitting every internal milestone on schedule while the customer is still sitting at zero value · because the milestones that matter to the customer were never on the project plan in the first place.

Five Ways to Compress Time-to-Value Deliberately

  1. 1Front-load the first-value moment — Re-sequence the implementation so the first outcome the customer experiences happens in the first two to three weeks, not month three.
  2. 2Strip the launch scope — Cut the original go-live to the smallest possible useful version. Add the rest in phases AFTER first value is proven.
  3. 3Eliminate customer-dependency bottlenecks — Identify every step that waits on the customer to do something. Reduce, automate, or co-deliver as many as possible.
  4. 4Provide a quick-win template library — Pre-built configurations, sample data, or proven playbooks let the customer experience a working version on day one, then customise behind it.
  5. 5Measure and publish TTV weekly — What gets measured improves · what gets published improves faster.

“Short time-to-value does not just satisfy customers · it compounds across the entire relationship. Long time-to-value does not just frustrate customers · it slowly poisons every conversation that follows.”

Hold on to these

  • Time-to-value is the single most predictive metric in onboarding · short TTV correlates with retention, expansion, and advocacy.
  • First-value is a customer outcome, not a team milestone · define it from the customer's perspective or the metric is meaningless.
  • TTV can be compressed deliberately · front-loading, scope stripping, and quick-win templates are the most reliable levers.

Reflection · write it down

Define the first-value moment for your service in one specific, measurable sentence. Then write the current average TTV (in calendar days), the target TTV you want to achieve in the next ninety days, and the single biggest lever you will pull to close the gap.

Saves automatically · come back to it whenever.

What you walk away with

You now hold a precise definition of time-to-value for your service · the current number, the target number, and the named lever you will pull to close the gap.

Category

Reading the Signals

2 modules
3

Module 3 · ~13 min

Adoption Metrics · The Leading Indicators of Retention

“Retention is a trailing indicator · you find out twelve months later. Adoption is the leading indicator · you find out in week six. Track the right one and you stop being surprised.”

Retention is what every executive cares about. Adoption is what every executive should be watching long before retention becomes a metric worth reporting on. By the time retention drops, the customer is already gone in spirit · the only question left is how long until they exit on paper. This module shows you how to read adoption signals early, what to measure, and how to act on the patterns before they become attrition.

The Four Adoption Metrics That Predict Retention

  1. 1Breadth of Adoption — How many of the contracted features, services, or modules is the customer actively using. A customer using two of seven services is a churn risk hiding in plain sight.
  2. 2Depth of Adoption — How deeply is each adopted feature being used. Are they running the full workflow or just the surface?
  3. 3Frequency of Adoption — How often is the customer engaging with the service. Daily, weekly, monthly · and how does that compare to the cohort norm?
  4. 4Stakeholder Adoption — How many users inside the customer's organisation are actively engaged. Single-point-of-contact customers churn dramatically faster than multi-stakeholder customers.

━━ The Adoption Pattern That Predicts Churn ━━

Breadth dropping. Depth narrowing. Frequency declining. Stakeholder count shrinking.

Any one of those alone might be noise. All four moving together over a four-week window is the single most reliable churn signal you will ever see · and it shows up months before the customer ever utters the word 'cancel.'

Satisfaction surveys ask the customer how they feel. Adoption data shows you what they actually do. A customer can report 8/10 satisfaction on a survey and quietly stop using the product the following month. A customer cannot fake their usage data. Behaviour is the truer signal · always. This is why mature Onboarding operations watch the adoption dashboard like air-traffic controllers watch radar · because the radar tells you something the conversation does not.

✦ Pro Insight · Setting Adoption Benchmarks by Customer Cohort

Adoption norms vary by customer type · a five-person practice will not adopt at the same pace or breadth as a fifty-person firm.

The professional move is to define adoption benchmarks BY COHORT · what does healthy adoption look like at week four, week eight, week twelve, for a small customer, a mid-sized customer, an enterprise customer. Customers below the benchmark for their cohort are flagged for intervention; customers above are flagged for advocacy.

Without cohort benchmarks, you cannot tell a slow-adopter from a customer who is operating exactly where their size and shape should put them.

⚠ Common Mistake · The Adoption Vanity-Metric Trap

Reporting 'logins this month' as an adoption metric is the customer-success equivalent of measuring website traffic without measuring conversions.

A customer can log in fifty times a month and never use the feature that delivers their first value · because they keep checking the dashboard and never running the workflow. Logins are presence; adoption is use. Measure the use, not the presence.

“Behaviour is the truer signal. Adoption data tells you what the customer will do six months from now, before the customer themselves knows it.”

Hold on to these

  • Adoption is the leading indicator of retention · retention is what you find out twelve months too late.
  • Four dimensions matter · breadth, depth, frequency, and stakeholder count. All four moving down together is the churn pattern.
  • Cohort benchmarks beat global averages · a small customer and an enterprise customer cannot be held to the same adoption curve.

Reflection · write it down

Pick three customers currently in your portfolio · one you believe is in great shape, one you believe is at risk, and one you have not thought about recently. For each, score adoption (1–5) across the four dimensions (breadth, depth, frequency, stakeholder count). The 'not thought about' customer is your interesting case · note where their scores surprised you.

Saves automatically · come back to it whenever.

What you walk away with

You can now read adoption signals as leading indicators of retention · breadth, depth, frequency, stakeholders · and act on the patterns before they become attrition.

4

Module 4 · ~16 min

Customer Health Scoring · The Early-Warning System

“A customer in trouble almost never announces it. They go quiet, slow, ambiguous · then one day they tell you they are leaving. Health scoring is the discipline that catches the quiet phase, while there is still time to act.”

Customer health scoring is the operational answer to one question · 'Which of my customers are quietly drifting?' Done well, it surfaces customers at risk weeks or months before the obvious signals (escalations, missed renewals, formal complaints) arrive. This module shows you how to design a customer health score that is honest, simple, and actionable · the kind that becomes a daily operating tool rather than a quarterly reporting exercise.

Sample Customer Health Scoring Formula

  1. 1A practical 100-point composite score, weighted across five dimensions:
  2. 2Adoption Score (30 points) — Breadth + depth + frequency of usage versus cohort benchmark.
  3. 3Engagement Score (20 points) — Recency of meaningful contact, response rates to outreach, attendance at scheduled reviews.
  4. 4Sentiment Score (15 points) — Most recent NPS or satisfaction signal, weighted by recency.
  5. 5Outcome Score (20 points) — Has the customer achieved their stated success outcomes (first-value, ROI targets, named milestones).
  6. 6Relationship Score (15 points) — Stakeholder count, executive sponsorship presence, multi-thread relationship strength.
  7. 7Scores are colour-coded · Green (80–100), Amber (60–79), Red (below 60). Reds are reviewed weekly. Ambers are reviewed fortnightly. Greens are reviewed monthly to confirm they are still green.

━━ Why Five Dimensions, Not Twenty ━━

Five dimensions are enough to tell the whole story and few enough that humans can hold them in their heads at once.

A twenty-dimension health score is technically more accurate and operationally useless · no team will ever read it consistently. The goal is not perfection. The goal is a number that genuinely changes the next conversation.

✦ Pro Insight · The Subjective Override · When the Number Lies

Every health score will occasionally produce a green customer who is actually in trouble or a red customer who is actually fine. This is not a flaw in the system · it is a feature, as long as you respect the override.

The professional discipline is to allow the customer-facing operator to override the score with a documented reason. 'System says green, I have spoken to them three times this week and they are unhappy · I am moving them to amber.' That override IS the early-warning system at its most valuable.

The number gets you in the room. The judgement decides what happens next.

Translating Health Score Into Action

  1. 1Red (below 60) — Same-week intervention. Senior involvement. Named recovery plan. Frequency of contact temporarily doubles.
  2. 2Amber (60–79) — Fortnightly review. Documented improvement actions. Targeted outreach to lift the lowest-scoring dimension.
  3. 3Green (80–100) — Monthly review to confirm sustained health. Eligible for advocacy programme, case study request, referral conversation.
  4. 4The action follows the colour automatically · which means the score is operational, not theoretical.

⚠ Common Mistake · The Health Score That Never Changes Anything

Many operations build a customer health score, report on it monthly, watch it move up and down · and never actually change what they do with any customer based on the colour.

This is the health-score equivalent of a smoke alarm with the batteries removed. The signal exists. The response does not. Build the score AND the playbook the score triggers · otherwise you have built a measurement tool that protects no one.

“A customer health score is not a measurement exercise · it is a smoke alarm with a fire response attached to it.”

Hold on to these

  • Health scoring catches the quiet phase · the weeks or months before a customer's trouble becomes visible in obvious signals.
  • Five dimensions are enough · adoption, engagement, sentiment, outcomes, relationship. More dimensions buy precision and lose usability.
  • The score gets you in the room · the judgement decides what happens next. Always allow the documented override.

Reflection · write it down

Build a one-page customer health scoring template for your operation. Define the five dimensions, the weight on each, the data source for each, the thresholds for red/amber/green, and the response playbook for each colour.

Saves automatically · come back to it whenever.

What you walk away with

You now own the architecture of a customer health score · five dimensions, weighted thresholds, response playbooks for each colour. An early-warning system, not a measurement exercise.

Category

Reporting to Leadership

2 modules
5

Module 5 · ~15 min

Reporting Dashboards · What Leadership Needs to See

“Leadership does not need more data · they need fewer numbers, better chosen, presented in a form they can act on inside ninety seconds. The dashboard that fails to do that does not get read · regardless of how clever it is underneath.”

Reporting is where most Onboarding operations lose the executive audience. Dashboards that pour out fifty metrics drown the reader. Reports that explain everything explain nothing. The leadership team needs a small set of signals that answer three questions · 'Is the function healthy?' 'Where is the risk?' 'What is changing?' This module gives you templates for the three reporting artefacts every mature Onboarding operation produces · the weekly operating report, the monthly executive summary, and the always-on dashboard.

Sample Weekly Onboarding Operating Report

  1. 1A one-page report, delivered every Monday morning, structured in five sections:
  2. 2Section 1 · The Headline — One sentence on the state of the function this week. 'We are tracking ahead on TTV and behind on adoption.'
  3. 3Section 2 · The Numbers — Current value of the seven core KPIs, with delta versus last week, delta versus target.
  4. 4Section 3 · The Risks — Named customers in red status, with the recovery action and the owner.
  5. 5Section 4 · The Wins — Named customers who hit a first-value milestone, completed onboarding, or converted to advocacy this week.
  6. 6Section 5 · The Asks — Two or three specific things the team needs from other functions (Sales, Product, Account Management) to operate smoothly this week.
  7. 7The report is one page. Always one page. Constraint is what forces clarity.

Sample Monthly Executive Summary

  1. 1A two-page document, delivered to leadership monthly, structured around outcome rather than activity:
  2. 2Page 1 · The Headline Story — Three to four sentences on what the function delivered this month, what changed, and what leadership needs to know.
  3. 3Page 2 · The Evidence — TTV trend (rolling 90-day average). Onboarding completion rate. First-90-day retention. Onboarding NPS. Top three risks. Top three wins. One recommendation that requires leadership decision or sponsorship.
  4. 4Delivered with the dashboard link for anyone who wants to dig deeper. The summary should be readable in under ninety seconds and decision-ready in under five minutes.

Sample Always-On Onboarding Dashboard

  1. 1A live dashboard, accessible to the function and leadership, organised in four panels:
  2. 2Panel 1 · Pipeline — Number of customers in each onboarding stage, time in stage, days since signature, scheduled go-live.
  3. 3Panel 2 · Health — Customer health score distribution (count of green/amber/red), with red customers named and owned.
  4. 4Panel 3 · Performance — Rolling KPI charts (TTV, completion, adoption, NPS, readiness, retention) versus target line.
  5. 5Panel 4 · Quality — Recent customer feedback verbatims, recent escalations, recent advocacy moments.
  6. 6The dashboard tells the story without anyone narrating it · which is the test of a well-built operating dashboard.

━━ The Ninety-Second Test ━━

Hand your dashboard or report to someone outside the Customer Success function. Give them ninety seconds.

At the end of ninety seconds, can they answer · Is the function healthy? Where is the risk? What is changing?

If yes, the dashboard works. If no, you have built a measurement tool, not a leadership tool. Strip back until the test passes.

✦ Pro Insight · How to Make a Report That Leadership Actually Reads

Three rules separate read-every-week reports from delete-without-opening ones.

First, the headline is a sentence, not a number. 'TTV improved 11 percent this month' is forgettable; 'We are now activating customers a full week faster than ninety days ago, which means earlier advocacy and stronger expansion conversations' is memorable.

Second, the asks section is specific. 'Better Sales handovers' is noise; 'Sales to include the customer's top three success criteria in every contract package · request for sign-off by month end' is action.

Third, the report ends with what changes next week, not what happened last week. Forward-leaning reports get read; backward-only reports get archived.

“The dashboard that fails the ninety-second test does not get read. Strip back until it passes.”

◈ Pause & Reflect

Pull up the most recent report you sent to leadership.

Apply the ninety-second test honestly. Can a reader outside your function answer all three questions in ninety seconds? If not, you have just identified your highest-leverage reporting improvement.

Hold on to these

  • Leadership needs fewer numbers, better chosen, presented in a form they can act on inside ninety seconds.
  • Three artefacts cover the reporting need · weekly operating report, monthly executive summary, always-on dashboard.
  • The headline is a sentence, the asks are specific, the report leans forward · these three rules separate read-every-week from delete-without-opening.

Reflection · write it down

Draft a one-page weekly onboarding operating report for your function · this week. Use the five-section structure. Be brutally specific · real names, real numbers, real asks. Then run the ninety-second test on it by handing it to a colleague outside the function.

Saves automatically · come back to it whenever.

What you walk away with

You now hold three reporting artefacts · the weekly operating report, the monthly executive summary, and the always-on dashboard. All three pass the ninety-second test or they do not ship.

6

Module 6 · ~14 min

Data-Driven Improvement · Turning the Numbers into Decisions

“Measurement is the easy part. Acting on what the measurement tells you · changing process, retraining people, killing favourite practices that the data has just disproved · is the hard part. The teams who do the hard part are the ones who keep getting better.”

A dashboard is not improvement. A KPI is not improvement. A health score is not improvement. Improvement happens in the gap between seeing the number and changing what you do because of it · and most teams never close that gap. This module shows you how to convert measurement into action · the discipline of running structured improvement cycles, the courage to retire what the data tells you is not working, and the operating cadence that turns analytics from a reporting exercise into the engine of a learning function.

The Four-Step Improvement Cycle

  1. 1Step 1 · Observe — Pick one specific metric that is below target or below where you believe it should be. Just one.
  2. 2Step 2 · Diagnose — Ask why. Then ask why again. Then ask why a third time. The root cause is rarely the first answer · it is usually the fourth or fifth.
  3. 3Step 3 · Intervene — Design one change, ship it inside the next two weeks, and measure the effect on the metric.
  4. 4Step 4 · Decide — Keep the change if the metric moves. Reverse the change if the metric does not. Either way, write down what you learned and move to the next cycle.
  5. 5Four steps. Two weeks. One metric. The constraint is what creates the learning.

✦ Pro Insight · Why the Cycle Beats the Project Plan

Most Onboarding teams attempt improvement through quarterly projects · 'Q2 we will redesign the welcome experience.' The project lasts ten weeks, ships in week eleven, and nobody is sure afterwards whether it worked because too many things changed at once.

The four-step cycle solves this. Ship one named change in two weeks. Measure one named metric. Know unambiguously whether it worked. Stack twelve cycles a year and the function compounds; ship two projects a year and you mostly cannot tell what improved and what did not.

Sample Executive Summary Report · After an Improvement Cycle

  1. 1A one-page report delivered after each two-week cycle, structured in five lines:
  2. 2Line 1 · The Hypothesis — 'We believed that moving the kick-off meeting from week 2 to week 1 would compress TTV by 5–7 days.'
  3. 3Line 2 · The Intervention — 'For the last 14 days, every new customer was scheduled into a week-1 kick-off.'
  4. 4Line 3 · The Result — 'Average TTV dropped from 38 days to 31 days across the test cohort.'
  5. 5Line 4 · The Decision — 'We are making the week-1 kick-off the new standard from next Monday.'
  6. 6Line 5 · The Next Cycle — 'Next we are testing whether splitting the kick-off into two 45-minute sessions improves stakeholder coverage.'
  7. 7Five lines. One page. Compounded twelve to twenty times a year, this is what a learning function looks like.

⚠ Common Mistake · The Single Biggest Improvement Failure

The team identifies a process step that the data has disproved · the welcome pack that nobody reads, the training session that nobody attends, the report that nobody opens · and keeps doing it anyway, because 'it is part of our process.'

Process loyalty is the enemy of improvement. The whole point of running cycles is to find out what does not work and stop doing it. If the data says a step is dead, kill the step. Keeping it on the schedule is more expensive than the embarrassment of admitting it never worked in the first place.

Two questions, asked at the end of every quarter. First · 'What did we change about how we operate this quarter, specifically, because of something the data showed us?' Second · 'What process step did we stop doing this quarter because the data proved it was not worth the cost?' Teams that can name three things for each question are learning teams. Teams that can name nothing are stagnant teams running on instinct, regardless of how full their dashboard is.

“Process loyalty is the enemy of improvement. The whole point of measurement is to find out what is not working · and have the courage to stop doing it.”

◈ Pause & Reflect

Reflect honestly on the last six months in your function.

Name three specific things you changed about how you operate, because the data told you to. Then name three things you stopped doing, because the data showed they were not worth the cost.

If you cannot name three of each, you have just identified the operating discipline you most need to install in the next ninety days.

Hold on to these

  • Measurement without action is reporting · improvement happens in the gap between seeing the number and changing what you do because of it.
  • The four-step cycle (observe, diagnose, intervene, decide) compounds faster than quarterly projects · twelve to twenty cycles a year is the learning function rhythm.
  • Process loyalty is the enemy of improvement · if the data disproves a step, kill the step and write down what you learned.

Reflection · write it down

Pick one KPI that is currently below target in your operation. Run a complete four-step improvement cycle in writing · the observation, the diagnosis (with at least three 'why' questions), the intervention you will ship in the next 14 days, and the metric you will use to decide whether to keep the change or reverse it.

Saves automatically · come back to it whenever.

What you walk away with

You can now convert measurement into action · running structured two-week improvement cycles, retiring practices the data has disproved, and stacking learnings into compounding improvement across the year.

Chapter 8 · Homework

Lock it in · before you move on.

Build Your Onboarding KPI Dashboard

Build a one-page dashboard for the seven core onboarding KPIs · time-to-value, completion rate, adoption rate, activation rate, onboarding NPS, readiness at handover, first-90-day retention. For each KPI, define the precise calculation, the data source, the current value, the target, and the owner. The deliverable is something you could hand to leadership next week.

Build your seven-KPI onboarding dashboard · definitions, current values, targets, and owners.

Design Your Customer Health Score

Design a customer health score for your operation. Define the five weighted dimensions, the thresholds for red/amber/green, the data sources behind each dimension, and the response playbook that triggers automatically for each colour. The deliverable is a system, not a measurement · meaning the action is built into the design from the start.

Design your five-dimension customer health score with thresholds and response playbooks.

Run a Two-Week Improvement Cycle

Pick one onboarding KPI that is currently below target. Run a complete four-step improvement cycle over the next two weeks · observe, diagnose with at least three 'why' questions, intervene with one named change, and decide whether to keep or reverse the change based on the metric. At the end of the two weeks, write the five-line executive summary of what you learned.

Run a complete two-week improvement cycle and produce the five-line executive summary.

Back to My Sales Training
First dayLast day