Playbook
Launching a Product
A launch sequence built on one hard-won lesson: work out what customers would actually hire your product to do before your enthusiasm spends the budget. Job, proposition, beachhead, then a rhythm of cheap tests once you are live.
It took me years to work out what my consultancy clients were actually buying. I thought I sold tax advice. Mostly I sold the ability to sleep the night before a deadline without thinking about the envelope from the Revenue on the hall table. Once I understood that, everything about how we sold changed. That lesson sits underneath this whole sequence. A product launch fails most often because the team fell in love with the thing they built and never seriously asked what anyone would hire it to do. So start with Jobs to be Done, which forces that question. Then use the Value Proposition Canvas to state, in terms specific enough to be wrong, why one particular segment should care. Crossing the Chasm makes you choose the narrow beachhead where your first mainstream customers will come from, because 'everyone' is where launches go to die. Build-Measure-Learn keeps you honest once you are in the market, turning the launch from a single bet into a stream of small, cheap tests. The thread through all four is humility about your own guesses. Every framework here exists to get the customer's reality into the room before your enthusiasm spends the budget.
Customer & product
Jobs to be Done
For working out what a customer is really trying to get done when they buy from you, and what pushes them to switch or holds them back. Leave it alone when you need numbers across a whole market; this is a handful of good conversations, not a survey. Instead The Kano Model, surveyed properly, when you need numbers across a whole market.
Begin with the question that reshaped my own selling: what progress is the customer actually trying to make, and in what circumstance. Customers hire products, and what they hire them for is often several steps removed from what the product nominally does. Study the four forces around the switch too: the push of the current struggle, the pull of your solution, and the anxiety and habit that block the move. Most teams over-invest in pull because it is the force they can see. The blockers usually decide the sale.
Watch forThe trap is writing the job statement as a flattering description of your product; if your product's name appears in the job, start again.
Innovation & product
Value Proposition Canvas
For matching what one group of customers is trying to do, and what frustrates them, against what you offer and how it helps. Leave it alone when you are designing the whole business; this covers two of its nine blocks. Instead The Business Model Canvas, which covers the other seven blocks a whole business needs.
Now pin the guess down where it can be tested. Take one segment, map its jobs, pains and gains in ranked order, then map your offer against them: what relieves which pain, what creates which gain, and what you are deliberately ignoring. The discipline is in the ranking and the linking. A canvas where every feature answers a top-three pain is either a strong proposition or a team marking its own homework, and the customer interviews you run next will tell you which.
Watch forFit is judged from the customer profile towards the value map, never in the other direction, however elegant the map looks.
Marketing & customer
Crossing the Chasm
For getting a genuinely new product from the enthusiasts who will try anything to the mainstream buyers who want references, by winning one narrow segment first. Leave it alone when the product asks no change of behaviour from the buyer; there is no chasm to cross. Instead STP; if the product asks no change of the buyer, it is ordinary targeting, not a chasm.
Early enthusiasts will buy your product because it is new. The mainstream will buy it because people like them already have, and between those two groups sits the gap that kills more good products than bad engineering ever did. Moore's answer is deliberate narrowness: pick one beachhead segment, build the complete product that segment needs, win it convincingly, and let the references carry you to the next. Choosing a small pond feels timid when investors want a big market story. It is the fastest route to one.
Watch forA beachhead you could not plausibly lead within two years is too big; keep narrowing until domination is realistic.
Innovation & product
Build-Measure-Learn
For turning an idea into the smallest thing a customer can react to, measuring what they do, and learning whether to change course or carry on. Leave it alone when the requirement is already known; iterating towards a fixed specification is waste dressed as learning. Instead A plan and a delivery team; when the requirement is known, build it and test it against the specification.
Launch day is where your guesses meet the till, and the till wins every argument. Build-Measure-Learn gives the launch a rhythm: state the hypothesis before you build, agree the metrics before you ship, and hold an honest verdict afterwards, including the verdict nobody wants, which is pivot. Judge progress by hypotheses settled per month rather than features shipped. The two diverge more often than teams admit, and only one of them tells you whether the launch is working.
Watch forVanity metrics are the danger here; cumulative sign-up curves always rise, so insist on cohort evidence before calling anything validated.
In the end
By the end you should have a job statement grounded in real switching behaviour, a value proposition specific enough to fail a test, a beachhead you could credibly lead, and a launch that runs as a series of cheap experiments instead of one expensive opening night. None of it guarantees the product works. What it guarantees is that you find out quickly and at low cost, which in my experience is the difference between a setback and a write-off.