9 posts tagged with "Product design"

Selling B2B software is half product, half change management. The product is what you ship; change management is what determines whether anyone uses it. Most B2B teams optimize the first, neglect the second, and lose deals they could have won.

Change management gets neglected because it's not on anyone's spec sheet. It's not a feature. It's not a metric on the demo. But it's the single biggest determinant of whether your product gets adopted in an organization that bought it, and most products are not designed for it.

AI copilots are framed as a productivity feature — "do work faster" — and shipped by feature teams. This framing is correct on the surface and misleading underneath.

Every AI copilot in a product is doing onboarding, whether the team thinks of it that way or not. It's teaching the user what the product can do, what good prompts look like, and where its limits are. The teams that recognize this ship better copilots. The teams that don't ship demos.

"Stickiness" is the most-used word in product retention talks and the least-defined. Pinned to a specific number, it's DAU/MAU — daily active users divided by monthly active users. As a piece of language, it's stretched to cover everything from "users come back" to "users like the product" to "the product has a moat."

The metric and the word have come apart. The metric is fine; the way it's interpreted has gotten loose.

Most companies treat self-serve support as a way to reduce ticket volume. The framing is correct in the way an accountant's framing is correct — it's measuring the right thing for the wrong reason.

A help center optimized for ticket deflection is one design. A help center optimized for the user actually getting their question answered is another. They look similar. They behave very differently.

Retention is the metric everyone talks about. Activation is the metric that decides whether retention even gets a chance to matter.

If a user signs up, opens your product, and doesn't get to the thing they came for inside the first minute, the rest of the funnel is academic. They don't churn — they evaporate. You won't see them in your retention dashboard because they were never there long enough to count.

Most product teams say they "know their users." Pressed for specifics, what they actually have is a vague sense of who's signed up — a sketch built from sales calls, the loudest voice in support, and the founder's gut. That sketch is not a mental model. It's a guess wearing the costume of a guess.

Real understanding is more boring than that, and harder to fake.

Time-to-value is the most-cited metric in onboarding decks and the least-measured one in actual products. Almost every team can name it. Almost none of them have a chart of it open in a tab right now.

That gap is not an oversight. Time-to-value is annoying to measure properly, and the easy ways to measure it are the wrong ways. This is a primer on the measurement, not the concept.

NPS is the most influential metric in B2B software and one of the easiest to lie with. The lie isn't usually deliberate — it's structural, baked into how the metric is computed and where it gets sampled. Most NPS dashboards are reading their own noise.

Every product team can draw their activation funnel. Sign-up → email confirm → first action → activation event. Four steps, neat and rectangular, the kind of diagram that fits in a slide.

The actual activation funnel — the one that describes what happens to real users — is shaped nothing like that. Most of the leverage in activation is in steps that don't appear on the diagram, because they don't appear in your tracking either.