L8. Onboarding

Outputs doc: outputs.md, L8 section. Fill it in as you work through the steps below. Raw onboarding-cohort data and new-customer conversations go in captures.md. L9 reads the L8 section before starting.

Jump to: Diagnostic · Step 1 · Step 2 · Step 3 · Step 4 · Step 5 · Step 6 · Step 7 · Summary · Assumption sweep

What this layer is: The experience the customer has right after they buy, designed to deliver the promise that won the deal. It is still marketing, because this is where the customer checks what they were told against what they got, and decides whether they made a good choice. It is not a product tour or a setup checklist. It is the deliberate path from “just signed” to “this is doing what they said,” reached fast enough that the customer never has time to regret it. The output is a first-thirty-days experience, across product, people, and communication, that carries the customer to the first real proof of the value from L2, plus a way to tell who is on track and who is quietly slipping toward churn.

Why it comes after L7 and before L9: L7 set a promise in the close: the value the economic buyer signed off on and the outcome the champion staked their credibility on. L8 is where that promise meets reality. It cannot be designed before L7, because onboarding has to deliver exactly what the deal sold; the promise is its specification. And it must come before L9, because referrals are a consequence of a customer who reached the promised outcome and felt good getting there. The first thirty days determine whether L9 ever exists: a customer who hits first value early and smoothly becomes an advocate, and one who stalls or feels oversold becomes, at best, a quiet non-renewal and, at worst, a detractor who warns others. Most of the work here is closing the gap between the expectation set upstream and the reality of using the product, fast, before buyer’s remorse sets in. If customers churn early or never refer, the cause is sometimes a weak onboarding here, but it is just as often a promise oversold in L7 or a product that cannot actually deliver the L2 value.

What finishing this layer produces: A written onboarding system in the L8 section of outputs.md: a clear definition of the promised outcome and the first-value moment, a map of the gap from purchase to that moment, a first-thirty-days experience built to close it across product, people, and communication, a set of success and early-warning signals, and the identified stall point with its fix. Backed by real customers run through it, not by an onboarding flow that was designed and never measured.

Diagnostic: is L8 actually done?

Before building anything, answer these questions in writing. Vague answers mean the layer is not finished.

1. Have you defined the first-value moment and when it should happen, or is “onboarded” just “they have a login”? A customer with an account is not a customer who has gotten value. If you cannot name the specific first win that proves the promise is being kept, and a target time to reach it, onboarding has no destination and no clock.

2. Does onboarding deliver the specific promise from L2 and the close, or does it just tour features? The customer remembers what they were sold. If onboarding walks them through every feature instead of the fastest path to the one outcome they bought, it buries the promise and lets doubt grow.

3. Do you know the gap between purchase and first value, the steps and the doubt points? Between signing and the first win is a set of things the customer has to do, learn, and believe. If you cannot name where they stall or where buyer’s remorse creeps in, you cannot design against it.

4. Is there a designed first-thirty-days experience across product, people, and communication, or do customers self-serve into silence? Going quiet after the sale is the most common onboarding failure. If there is no deliberate sequence of touches that reassures, guides, and proves value, the customer is alone with their doubt at the most fragile moment.

5. Can you tell when a customer is on track or at risk by a signal, with an intervention, or do you find out at renewal? If you only learn a customer stalled when they churn, you learned too late. There should be observable signals of activation and risk, and a defined save when a customer drifts.

If you answered all five clearly and in writing, L8 may already be done. Jump to the L8 section of outputs.md, fill in the fields, check the checklist, and move to L9. If not, work through the steps below.

Step 1. Pull the inputs from L7 (and above)

Duration: 30 minutes

L8 does not start from a blank page. It starts from the promise L7 set in the close, the outcome L2 sold, and the original problem L0 and L1 found. The fastest route to an onboarding that retains is to design backward from the promise, treating it as the exact thing the first thirty days must deliver.

What to do:

1. Open the L7, L2, L1, and L0 sections of outputs.md and copy the following into the “Inputs from L7 and above” field in the L8 section:

   • From L7: the promise made in the close, the value the customer bought and the outcome they expect, the objections and doubts that nearly lost the deal, and the buying group and who championed it. Onboarding delivers this promise, reassures these doubts, and protects this champion.
   • From L2: the final value proposition and the proof buyers said they would need. The first-value moment is the first real instance of this value; the proof is what the customer is waiting to see become true for them.
   • From L1: the original decision and blocker, and the buying context. The blocker that almost stopped them buying often returns as the doubt that stalls them in onboarding.
   • From L0: the problem and the workaround they came from. First value is felt against the old workaround; onboarding has to beat the thing they were doing before, quickly and visibly.

2. Write one sentence: “We promised [outcome from L2/L7]; the customer will believe it when they first see [first-value moment], and the thing most likely to stop them getting there is [the risk, often the L1 blocker returning].” It frames onboarding as a race to first value against doubt.

3. If L7 oversold, promising more than the product delivers, that lands here as a gap onboarding cannot close. Note it in the L8 scope notes in outputs.md and log it in assumptions.md (Layer: L8, Status: Untested). If the promise and the product genuinely diverge, the fix is in L7 or in the product, not in a smoother welcome email.

Step 2. Define the promised outcome and first value

Duration: 30-45 minutes

Onboarding is a race with a finish line, and the finish line is the first time the customer sees the promised value become real for them. Define that moment first, before designing any of the experience, because everything in the first thirty days exists to reach it fast. There are two horizons to name: the full promised outcome (the value they bought, which may take longer to fully realise) and the first-value moment (the earliest credible proof that they are on the way to it). The first-value moment is the one that prevents churn, because it is what turns a hopeful new customer into a confident one.

What to do:

1. In the L8 section of outputs.md, under “Promised outcome and first value,” fill in the table below (it is also in outputs.md).

   Element	Definition	How the customer experiences it
   The promised outcome (the value from L2 and the close)
   The first-value moment (earliest credible proof)
   Target time to first value
   What “onboarded” means (the exit of the first 30 days)

2. Make the first-value moment specific and customer-felt, not internal. “They configured the integration” is an internal milestone; “they saw the first report that told them something they did not know” is first value. The test is whether the customer would describe it as the moment they thought “good, this works,” not whether a step in your setup was completed.

3. Set a target time to first value, and make it short. The longer the gap between paying and the first win, the more room for doubt, distraction, and the old workaround to reassert itself. The best onboarding compresses time to first value relentlessly; even a partial early win beats a complete win that arrives a month later.

4. Tie first value to beating the old workaround from L0. The customer is implicitly comparing the new thing to what they did before. First value lands hardest when it does something the workaround never could, visibly and early, because that is the moment switching feels justified.

5. The first-value moment and its target time are a hypothesis about what convinces a new customer until the data shows otherwise. Log them in assumptions.md (Layer: L8, Status: Untested). Step 6 measures whether customers who hit this moment actually retain.

Step 3. Map the gap from purchase to first value

Duration: 45 minutes

Between the signed deal and the first-value moment is a gap: everything the customer has to do, learn, set up, and believe to get there. Naming it is what turns onboarding from a generic welcome flow into a path engineered against the specific places customers stall. Part of the gap is practical (setup, data, configuration, learning), and part of it is emotional (buyer’s remorse, the doubt that nearly stopped the purchase, the fear the champion has of looking wrong). Both stall customers, and onboarding has to close both.

What to do:

1. In the L8 section of outputs.md, under “The gap to first value,” fill in the table below (it is also in outputs.md). For each thing that has to happen, note the current state, what it takes to clear it, and what could stall the customer there.

   Step to first value	What it requires of the customer	Where they could stall (practical or emotional)	What gets them through

2. Name the emotional risk points, not just the practical ones. The most dangerous moment in onboarding is often not a hard setup step but the quiet onset of buyer’s remorse: the customer wonders whether they made a mistake, especially the champion whose credibility is on the line. The doubt that nearly lost the deal in L7 usually returns here. Mark where it lands and what reassures it.

3. Minimise what the customer has to do to reach first value. Every required step, every form, every decision before the first win is a chance to stall. Strip the path to first value down to the essential, and defer everything that is not needed for that first win until after the customer is hooked. Effort before value is what kills early adoption.

4. Account for adoption across the buying group, not just the champion. In B2B the people who have to actually use the product daily are often not the champion who bought it, and if they do not adopt it, the champion’s promise fails and the founder’s fear is confirmed. If the value depends on a team using it, getting that team active is part of the gap, and often the hardest part.

5. Mark the single hardest, most decisive step toward first value. That step is where onboarding should concentrate its support, human help, and proactive attention. A flow that spreads evenly under-invests in the step that actually loses people.

6. Where customers stall is an assumption until real customers move through. Log the gap, especially the hardest step and the emotional risk point, in assumptions.md (Layer: L8, Status: Untested).

Step 4. Design the first-thirty-days experience

Duration: 60-90 minutes

Now build the experience that carries the customer across the gap to first value and beyond it to “onboarded.” Each touch exists to move them through a step from Step 3 or to reinforce the promise, and the experience spans three registers: the product (what guides them in the tool), the people (human help where it matters), and the communication (the messages that reassure, orient, and prove). This is still marketing: what you say and how present you are in the first thirty days shapes the customer’s memory of whether the promise was kept as much as the product does. A good onboarding feels guided and reassuring; a bad one is either silence after the sale or an overwhelming feature dump.

What to do:

1. In the L8 section of outputs.md, under “Onboarding experience,” map the experience in the table below (it is also in outputs.md). Each row is one touch or step. Tie it to the gap step it closes or the doubt it reassures, and mark whether it is product, human, or communication.

   Touch or step	Gap step it closes / doubt it reassures	Register (product / human / comms)	Timing	What the customer gets from it

2. Open by affirming the decision, not by teaching. The first touch after purchase should reduce remorse and confirm the customer chose well, before any setup. A warm, specific welcome that restates the outcome they are about to get does more for retention than an immediate tutorial. The customer’s first post-purchase emotion is doubt; answer it.

3. Drive the whole experience toward the first-value moment, and cut anything that does not serve it. Resist the urge to show everything the product does; a feature tour delays the one win that matters and dilutes it. Guide the customer down the shortest path to first value, then expand once they have felt it.

4. Put human touch at the hardest step from Step 3, especially where adoption or the emotional risk concentrates. Automation scales the easy parts; a person matters most exactly where customers stall and where the champion needs reassurance. Decide deliberately which steps get a human and which are self-serve, rather than automating everything or scaling nothing.

5. Protect the champion explicitly. The person who bought this internally has their credibility riding on it. Give them early proof they can show their boss (the economic buyer), an early win to report, a way to look good for having chosen you. A champion made to look smart in the first month is the seed of a referral; one left exposed is the seed of a churn.

6. Build the anti-onboarding list. Some touches feel helpful and quietly hurt. Capture them in the table below (also in outputs.md).

   Tempting touch	Why it looks helpful	Why it hurts

   Common entries: the silence after the sale, the everything-at-once feature dump, the setup that demands a lot before any value, the generic automated welcome that ignores what they bought, and the first human contact being an upsell. Naming them keeps them out when resourcing the experience gets hard.

7. The experience is a set of bets about what gets customers to first value until it runs. Log the design, especially the time-to-first-value path and the champion-protection touches, in assumptions.md (Layer: L8, Status: Untested).

Example (continuing the L0 to L7 example):

The follow-up system just closed; the founder feared reps would ignore it. The first thirty days: (1) a welcome that restates the outcome (no more warm deals going dark) and sets the first-value target, reassuring the VP; (2) a fast guided setup that imports live deals and turns on one cadence, stripped of every optional config; (3) a human kickoff with the VP and the reps together, because rep adoption is the make-or-break step; (4) within two weeks, the first-value moment: the VP sees a dashboard showing reps actually running the cadence and the first warm deal advanced by a cadence task, which is exactly the proof the founder needed; (5) a one-screen summary the VP can forward to the founder, protecting the champion. Anti-onboarding: a full feature walkthrough of reporting nobody asked about yet, and going quiet after setup.

Step 5. Build the success and early-warning signals

Duration: 45 minutes

An experience moves customers; the signals tell you whether it is working for each one, in time to act. This step defines the observable markers that a customer is activating and on track, and the leading indicators that one is stalling toward churn, plus the intervention when they are. Without this, you discover a customer was in trouble only when they fail to renew, which is far too late to save them. The signals read behavior against the first-value moment from Step 2 and the gap from Step 3.

What to do:

1. In the L8 section of outputs.md, under “Success and early-warning signals,” fill in the table below (it is also in outputs.md). List the observable signals, whether each means on-track or at-risk, and what it should trigger.

   Signal (observable behavior)	On-track or at-risk?	What it indicates	Intervention it triggers

2. Separate activation signals from vanity ones. Logging in is attention, not value; reaching the first-value moment, the team adopting, the customer returning unprompted are activation. Weight the signals that actually predict retention, which are usually about reaching value and building a habit, not raw usage counts.

3. Define the at-risk signals as leading, not lagging. A customer who has not reached first value by the target time, whose team has not adopted, who went quiet after setup, is at risk before they are anywhere near churning. The whole point is to catch the drift early, while a save is still cheap. Name the specific early signals for your case and the intervention each triggers.

4. Assign the save. For each at-risk trigger, decide who reaches out and how. An early-warning signal with no owner is just a sad report. The intervention is usually human and specific: not “send a re-engagement email” but “the success owner calls the champion and helps them get the team active.”

5. Define “onboarded,” the exit. A customer is onboarded when they have reached first value, are on the path to the full promised outcome, and have the habit that predicts they will stay. That is the moment they leave the intensive first-thirty-days experience and become a candidate for L9. Name it observably.

6. The predictive power of each signal is an assumption until the cohort data confirms it. Log the signals, especially the at-risk triggers, in assumptions.md (Layer: L8, Status: Untested).

Step 6. Run real customers and find the stall

Duration: at least one onboarding cycle, often 30-60 days | Target: enough customers through onboarding to see where they stall and who churns

An onboarding system is a hypothesis until real customers live through it. Step 6 runs new customers through the experience, measures how many reach first value and how fast, watches who stalls and who churns early, and asks new customers about the gap between what they were promised and what they got. As in every layer, when a customer stalls you have to judge whether the fault is L8 (a slow path to value, a missing reassurance, silence at the wrong moment) or upstream: a promise oversold in L7, a value proposition the product cannot actually deliver from L2, or a customer who was never really the segment from L1.

There are two halves to L8 validation: the cohort data (time to first value, activation rate, early churn, where customers stall) and conversations with new customers about whether the promise was kept and where they nearly gave up. The data finds the stall; the conversations explain it, and they are also the first read on whether the value actually landed, which L9 depends on entirely.

6a. Run a cohort and measure activation

Duration: the bulk of the time, bounded by the onboarding cycle

Put real new customers through the experience and instrument it. Because retention plays out over weeks, give it enough time that early churn and habit formation are visible, not just first-week logins.

What to measure:

• Time to first value: how long customers actually take to reach the Step 2 moment, against the target. The gap between target and reality is the core onboarding metric.
• Activation rate: the share of customers who reach first value at all. The ones who never do are the ones who churn.
• Where customers stall: the step from Step 3 where most get stuck or go quiet. This is the onboarding bottleneck, and where you work first.
• Early churn and its reasons: who left in the first stretch, and why. A cancellation reason of “never got it working” is an L8 signal; “it did not do what I was told” is an upstream one.

Find the stall and name it specifically: not “onboarding underperforms” but “customers set up but their team never adopts, so they never reach first value,” which points at a specific step and fix.

6b. Ask new customers what was promised versus delivered

Duration: light, a handful of short conversations

The cohort data shows where customers stall; conversations show why, and whether the promise held. Talk to a few who activated and, more valuably, a few who stalled or churned early. Recruit from the same customers.

What to ask those who activated:

• When did you first feel this was worth it? What was that moment?
• Was there a point in the first weeks you doubted the decision? What got you past it?

What to ask those who stalled or churned:

• Where did you get stuck, or when did you stop?
• Was what you got what you expected when you bought? Where did it differ? (this surfaces L7 and L2 gaps)
• What would have had to happen in the first weeks for this to stick?

You are listening for whether the stall is a fixable L8 problem (too slow to value, a hard step, silence, no human help where it was needed) or an upstream signal (the promise was bigger than the product, they were the wrong customer, the value never really existed for them). That judgement decides whether you fix the experience or go back a layer.

6c. Capture immediately after the cohort and conversations

Do this while the detail is fresh. Add entries to the L8 section of captures.md using this structure:

Cohort [number] | Segment fit + close date range:
Size:

Time to first value (vs target):

Activation rate (share reaching first value):

Stall step (where customers get stuck):

Early churn (who left, and the reason given):

---

Customer conversation [number] | Activated / stalled / churned:
Customer (role, segment fit):
When it became worth it, or where they stopped (verbatim):
Promise versus delivered (verbatim):
What would have made it stick (verbatim):
Is the stall an L8 fix or an upstream signal?:

Surprises (anything you did not expect):
Any L8 assumptions this confirmed or challenged:

The time-to-first-value data and the verbatim “promise versus delivered” are the most valuable output. The first locates the stall; the second tells you whether to fix onboarding or go back a layer, and previews whether this customer could ever become an L9 advocate. Capture both exactly.

6d. Synthesise and fix the stall

Do this once a cohort has been through. Go through your captures in captures.md and update the Onboarding synthesis fields in the L8 section of outputs.md, covering:

Time to first value, real versus target. How long did customers actually take, and where did the path drag? Compress the step that adds the most delay. The corrected time to first value is the real one.

The stall and its likely cause. Name the step most customers stall at and what the conversations say is behind it. Be specific about L8 versus upstream: a slow or unsupported step is an L8 fix; a promise the product cannot keep is not. This judgement is the most important output of the layer.

Promise versus reality. Did customers feel they got what they were sold? A gap here is an L7 or L2 problem made visible in onboarding. Feed it back upstream and tighten the promise; do not paper over it with onboarding cheer.

Champion protection. Did the champion get the early proof they needed to look good internally, or were they left exposed? A champion who stalled is a referral lost and a renewal at risk. If the champion-protection touches did not land, that is high-leverage to fix.

Is the constraint upstream. If customers stall at a point no onboarding change improves, and conversations point to an oversold promise or customers who were never the segment, the constraint is above L8. Say so and go back.

The fix and the re-test. State the one change you are making to the stall step and what you expect it to do, then run the next cohort through it. One change at a time.

After synthesis, mark the relevant rows in assumptions.md as Validated or Invalidated, and note what the evidence showed. If the constraint is upstream, fix it there. A customer who onboards but was sold the wrong thing churns later anyway.

6e. If you genuinely cannot run a cohort yet

If you have too few new customers to measure in the time available, reduce the unknowns and mark the gap.

• Onboard the customers you do have by hand, and watch closely. A handful of hand-held onboardings teaches more about where customers stall than a polished flow run by nobody.
• Walk the experience past a customer or a segment-fit person. Ask where they would lose confidence, where they would stall, and when they would feel it was worth it.
• Pressure-test against the promise. For each step, ask whether it moves the customer toward the exact outcome L7 promised, or just shows a feature. Cut the ones that do not.

Document each in the L8 section of captures.md, noting it is secondary. Log the absence of a measured cohort as an assumption in assumptions.md. An onboarding never run with real customers is a draft; L9 should know its advocates were made by an untested process.

Step 7. Write the final onboarding system

Duration: 30-45 minutes

You now have a first-value definition, a gap map, a designed experience, success signals, and a diagnosed stall. Lock the system.

A complete L8 output has six parts. Write a line or two for each:

1. The promised outcome and first value: the value the customer bought, the earliest credible proof of it, and the target time to reach it.
2. The gap and what closes it: the steps to first value, the practical and emotional stall points, and what gets customers through.
3. The first-thirty-days experience: the touches across product, people, and communication, opening with affirmation, driving to first value, with human help at the hardest step and explicit champion protection.
4. The success and early-warning signals: the activation markers, the leading at-risk signals, the assigned interventions, and the definition of “onboarded.”
5. The stall and the fix: the step customers stall at, its likely cause (L8 or upstream), and the change you made.
6. The upstream finding, if any: whether the cohort revealed a promise or a product gap from L7 or L2 that onboarding cannot solve, so it is visible.

Keep it as structured fields. Format does not matter. Speed to a real, felt first value does: this is the layer where “we send a welcome email” is not good enough.

What to do:

1. Write the final system directly into the matching fields in the L8 section of outputs.md.
2. Read it once as a new customer with first-week doubt and a champion whose boss is asking if this was a good call. Does the experience get you to a real win fast, and make you glad you chose it?
3. Run the diagnostic from the top of this page one more time. If all five questions now have clear written answers, L8 is done.

What you’ve built

After completing the steps above, the L8 section of outputs.md should contain:

This is not a deliverable for anyone else. It is a constraint on L9.

Assumption sweep

Before moving on, scan the L8 section of outputs.md for any field you filled in from reasoning rather than evidence. Common ones at L8:

• The first-value moment (did customers who hit it actually retain, or did you assume it is the moment that matters?)
• The target time to first value (did customers reach it that fast, or is it aspirational?)
• Where customers stall (did the cohort show it, or did you guess the friction?)
• The at-risk signals (do they predict churn, or are they just the behavior easy to track?)
• That the promise matches the product (did customers feel they got what they bought, or was L7 oversold?)

Each unconfirmed field is an assumption. Log it in assumptions.md now if you have not already. The first-value moment and the promise-versus-product match are usually the highest-impact assumptions in the layer; if untested, mark them leap-of-faith and run a cohort before trusting the system.

What this layer hands off to L9

Before moving on, confirm the L8 section of outputs.md is complete. L9 opens by reading it. Specifically, L9 needs:

• The customers who reached the promised outcome and felt good getting there, because those are the only honest source of referrals. L9 is a consequence of L8; the advocates it works with are the customers L8 successfully activated, not a list of everyone who bought.
• The first-value moment and when it lands, because the best time to ask for a referral is at or just after a customer feels a real win. L8 tells L9 when that moment is.
• The champions who were made to look good, because a champion whose bet paid off and whose boss noticed is the most likely and most credible referrer. L8’s champion-protection work is L9’s raw material.
• The signals of a genuinely happy, activated customer, so L9 targets advocacy at customers who will say something true, not at customers who will be embarrassed to be asked.
• The early detractors and why they soured, because L9 also has to know who not to ask and what to fix before advocacy is even possible.

The quality of your L8 onboarding sets the ceiling on whether L9 can exist at all. Referrals cannot be manufactured from customers who never reached value; they are the natural overflow of customers who did. If referrals never come, check whether customers are actually reaching the promised outcome in onboarding, and whether a referral problem that looks like an L9 failure is really an L8 one, or an oversold promise from L7, or a value that was never there in L2. You do not build referrals. You onboard well, deliver the promise, and then earn them.

Common failure modes

Silence after the sale. The customer signs and hears nothing, left alone with buyer’s remorse at the most fragile moment. The absence of an experience is the most common onboarding failure. Open with affirmation and stay present through the first thirty days.

Onboarding is a feature tour, not a path to value. The customer is walked through everything the product does instead of guided to the one outcome they bought, so the win that matters is buried and delayed. Drive everything toward the first-value moment; expand later.

There is no defined first value, so there is no clock. “Onboarded” means “has an account,” and nobody knows whether a customer is on track. Define the specific first win and a target time, and measure against it.

Too much effort before any value. The customer faces heavy setup, configuration, and learning before the first win, and stalls. Strip the path to first value to the essential and defer the rest until they are hooked.

The team never adopts, so the champion’s promise fails. The buyer signed but the daily users never came on board, confirming exactly the fear that nearly lost the deal. Treat adoption across the buying group as part of the gap, and put human help where it concentrates.

The champion is left exposed. The person who bought this internally gets no early proof to show their boss, so their credibility erodes and the renewal and any referral die with it. Give the champion an early win they can report upward.

You find out about churn at renewal. With no leading signals, a stalling customer is invisible until they leave, when it is too late and too expensive to save them. Build early-warning signals with assigned interventions.

You polished onboarding while the fault was upstream. Customers churn, so you rebuild the welcome flow while the real problem is a promise L7 oversold or a value L2 never truly had. When customers stall at a point no onboarding change fixes, check the layer above before redesigning the flow again.

“We have an onboarding email sequence.” Said with an automated flow nobody has measured against time to value or churn. If you cannot point to a first-value moment, the activation rate, and a defined save for at-risk customers, it is a sequence, not a system.

Sources

• Never Lose a Customer Again by Joey Coleman. The core source for L8. On the emotional journey after purchase, the predictable onset of buyer’s remorse, and the first hundred days as the window that decides retention and advocacy. Behind the affirmation-first design in Step 4 and the emotional risk points in Step 3.
• Onboarding Matters by Donna Weber. On customer onboarding as a deliberate, designed system, the orchestration of welcome, ramp, and first value, and compressing time to first value. Behind the experience design in Step 4 and the first-value definition in Step 2.
• Customer Success by Nick Mehta, Dan Steinman, and Lincoln Murphy. On time to value, activation, leading indicators of churn, and intervening before renewal. The foundation for the success and early-warning signals in Step 5 and the cohort metrics in Step 6.
• The Effortless Experience by Matthew Dixon, Nick Toman, and Rick DeLisi. On reducing customer effort as the driver of loyalty, and why friction, not delight deficits, is what loses customers. Behind the effort-minimisation in Step 3 and Step 4.
• Hooked by Nir Eyal. On the trigger, action, reward, and investment loop behind activation and habit formation, and why an early, felt reward is what makes a product stick. Background for the first-value moment in Step 2 and the habit definition of “onboarded” in Step 5.