THE FIRST THIRTY DAYS

Most of this guide takes a month and no new software. The order matters: count first, then look at every touch, then listen, then fix one thing. Skipping to the fix is how brands end up with a new flow for a stage they never measured.

1. Week 1 · CountRun the audit in chapter 1. Write your stages as events and pick a first-use signal (chapter 3). Pull the cohort table for the last three closed cohorts and find the stall (chapter 4). Set a target for each stage and pull time in stage (chapter 5).
2. Week 2 · Every touchExport the message log for ten new customers from every system and lay it out by day. Put the three collision rules in place (chapter 6). Start tagging tickets by stage. Blueprint the stall with operations, support and retention in one room (chapter 7).
3. Week 3 · Listen and assignHold ten interviews with customers from the stall and five with customers who passed it (chapter 8). Label every part of the map measured, heard or inferred. Replace the emotion curve with measured points (chapter 9). Fill in the stage table with one name per stage and book the monthly review (chapter 10).
4. Week 4 · Rank and ship onePut every proposed fix for the stall into the ranker, with confidence on the fixed scale (chapter 11). Size the holdout and ship the top fix. Build the scorecard (chapter 13) and hold the first monthly review on day thirty.

Count the journey, see every touch, hear the customers who stalled, then fix one stretch and prove it.

At day thirty you should have a cohort table, the stall named with a number, a timeline with no collision days, a blueprint, fifteen interviews, an owner for every stage and one fix running against a holdout. The map won’t be finished. It’s meant to be reviewed next month, with new numbers.

Do this

• Put the four weeks on the calendar today, with one owner for each week’s list, and book the first monthly map review for day thirty.