Asb Carol Keystones

Keystones: Who Needs an Extreme Version of What You're Best At

Passionate purchase decisions don't come from sort-of liking a few features. They come from an overwhelming pull toward one of your strengths — something specific about the customer's circumstances that makes them think "I've got to make this work for us." That pull is a keystone, and mapping your keystones is how a strengths chart becomes a target market. This skill walks the strengths one at a time, generates keystone candidates with the user, and holds each to the gate that separates keystones from wishful thinking: a real market segment must typify it.

The mental model

What a keystone is

A keystone is the critical characteristic that drives a customer's desire for the product — the thing that grabs their attention even in a noisy world, even while other trade-offs are in flux. It is not the strength itself; it is the customer circumstance that makes the strength critical. "Fast website" is a strength. "Has a website where even 0.1 seconds faster directly results in more revenue" is a keystone — and it immediately names its market: e-commerce stores, where studies put conversion of fast sites at multiples of slow ones, and where the giants have measured revenue loss per tenth of a second of load time. Same pattern across a real keystone chart: "scalable" becomes has traffic spikes at unpredictable times (news sites whose story can break any moment); "secure" becomes just got hacked and is still terrified or has a legal mandate for vendor certifications (the regulated industries); "inexpensive to build on" becomes big plans, limited budget (every small business, every "do more with less" marketing department).

The generative question

For each strength, ask: what characteristics, behaviors, or circumstances REQUIRE an extreme version of this strength? Imagine the customer for whom this strength is absolutely critical to their strategy — or so delightful it pulls them in through pure joy. Require is the operative word: a circumstance that merely prefers the strength generates a trade-off shopper — a buyer who weighs your strength against a competitor's and picks whoever wins the spreadsheet — not a keystone that drives a sale by itself. (Trade-off shoppers are a fine, large audience; the method's point is that targeting the keystone customer is what wins them too.)

The gate: no segment, no keystone

After naming a keystone candidate, describe real-world examples of companies or people who embody it. If you cannot name a significant market segment that typifies the keystone, it isn't a keystone — the strength is probably table stakes: true, useful, not compelling enough to drive a purchase alone. That's fine — that's why it's called brainstorming — but the candidate is cut, on the record, not recorded hopefully. The segments named should be described by circumstance and behavior ("e-commerce stores where speed measurably moves revenue"), not raw demographics; the sharper the description, the more useful every downstream step becomes.

Keystones concentrate in the head, not everywhere

You won't find keystones by asking what your best customers have in common — most of that is common to all your customers, including the worst. A trait that describes everyone predicts nothing about buying, paying, or staying. The right keystones concentrate in the best customers and show up weakly, or not at all, in the bad ones. If the strengths chart carries a best-vs-worst differential, mine it: the differences are where keystones live.

The one-keystone verdict

If the walk ends with one keystone — or none — that is not a failed exercise; it is the most valuable strategic lesson available: the product isn't compelling yet. Say it plainly, because learning it now is a multiplier — fixing it increases sales, and it was hidden. The twofold response, from the source: (a) increase marketing spend in the markets where keystones DO exist (with zero keystones, this half is empty and the verdict says so), and (b) use market and customer research to determine what to build next that would address a real keystone. Don't pad the chart to avoid the verdict — and don't pick what to build yourself: a feature chosen from inside the strengths chart is an invented keystone, exactly the wishful thinking the gate kills. With one survivor, phrase it precisely: compelling to that one segment only.

Why this is worth doing at all

The customers keystones find are the head of the profit distribution — in the canonical case, roughly 5% of customers producing 40% of profit, which justifies spending many times more to acquire each one. The keystone chart is the map to exactly those customers.

Vocabulary

• Keystone (K1, K2, …) — a customer characteristic, behavior, or circumstance that requires an extreme version of a strength; cites its [S-number].
• Example segments — the real-world companies or people who typify the keystone; the gate every keystone must pass.
• Table stakes — a true, useful strength that compels no one by itself; recorded as a cut, not a keystone.
• Requires vs. prefers — the bar: a keystone circumstance makes the strength critical, not merely nice.

The refiner's posture

Be clear, not clever

Write to be understood, not admired. The work here wrestles with hard concepts, and clever metaphors, wordplay, or cute turns of phrase make them harder to grasp, not easier. Say plainly what you mean. If a sentence reads more clearly without a flourish, cut the flourish. State the actual point rather than gesturing wittily at it.

Restate references; never cite a bare token

When you mention a numbered or lettered item to the user — K4, W2, O17, H3, and the like — add a few plain words on what it actually is ("K4 — the owner whose career rides on the site"). A bare token is unreadable to a human who saw it defined hours or days ago: the tag is for traceability, the gloss is for comprehension. Keep the tag for accuracy; always add the gloss.

Generate freely; gate ruthlessly

Keystone-finding is brainstorming — propose candidates yourself, liberally, alongside the user's: the imaginative leap from "strength" to "whose circumstance requires this" is exactly where an outside perspective helps. But every candidate, yours or theirs, faces the same two tests before recording: does the circumstance require the extreme version (not merely benefit from it), and can a significant real segment be named that typifies it? Run both visibly. A predefined way to press harder: if a devil's-advocate interrogation skill is installed in the environment (for example Rude Q&A / asb-rude-qa, from the same author as this method), invoke it against the draft keystone chart with this brief: attack these keystones — find every one whose segment is vague, tiny, or invented; every one where the circumstance merely prefers the strength rather than requiring it; every segment described so broadly it describes everyone. Don't accept wishful or hand-wavy defenses. If no such skill is available, run that interrogation yourself, visibly — the per-candidate tests inline, the batch attack at the closing sweep.

Press segment descriptions into specifics

"Small businesses" is not a segment description; "e-commerce stores processing enough revenue that a measurable conversion lift pays for premium hosting" is. When the user names a vague segment, ask for the example companies — actual names, or a description sharp enough that a salesperson could qualify against it. Generic words (many, serious, growing, quality-focused) get pressed into numbers, behaviors, and circumstances. A keystone whose segment can't be made specific after pressing fails the gate.

The user owns the market knowledge

Whether a named segment is significant, whether those customers really exist, whether the circumstance actually occurs — the user