We named microsimulations. The community made it a movement.

We named microsimulations. Not the practice — risk teams had been running short scenario drills for years — but the tech. Within about eighteen months analysts were using it, competitors were using it, and buyers were walking into calls asking for it by name.

That is the outcome every category program wants. It is also where most of the writing on category design stops, which is unhelpful, because what happens next is the part that doesn't have a script.

Adoption is not ownership.

The first thing that happens is flattering. Analysts pick up the word, which is what you wanted. The second thing is less flattering: every vendor with a scenario feature relabels it the thing. The word travels faster than any product change, and it arrives at buyers attached to things that are not what you built.

There is no defending this. You cannot trademark your way out of it, and trying makes you look small. Category names are public goods the moment they work — which is the deal you accepted when you named the thing in the first place.

The word drifts toward the mechanism.

This is the costly part, and it is easy to miss because nothing looks broken.

“Microsimulation” names a mechanism. That precision is exactly why it caught on, and it is also its limit. A mechanism competes on features, and a market that has settled on your mechanism will start comparing you on scenario count, library size, and integration list. Meanwhile the buying conversation moves somewhere else entirely.

And slowly then all at once, the shift happened. Boards and regulators stopped asking whether teams practiced and started asking for evidence they could withstand disruption. The CISOs, CSOs and CROs doing the buying needed to prove capability, continuously. Microsimulations are how you get there. They are not what the board asked for — and the outcome is where the budget sits.

A mechanism name wins the evaluation. An outcome name wins the budget line.

When to start the second journey.

Competitors adopting your term is not the signal. Neither is dilution, or a crowded G2 grid, or the vague sense that the word has gone stale. Those are noise, and reacting to them produces a rebrand, not a movement.

The signal is the buyer's mandate changing. When the question your buyer is being asked upstairs is no longer the question your category answers, the category has aged out of the conversation regardless of how well the name is doing.

• Your win themes are drifting toward features while your losses cite priorities you do not address.
• Buyers use your term correctly and still route budget elsewhere.
• The people above your buyer — board, regulator, auditor — have started using vocabulary that is nowhere in your messaging.
• You are being compared against products that solve a smaller problem than the one you solve.

Two of those four, consistently, across a quarter of pipeline. That is a category problem, not a messaging problem.

What the second journey actually looks like.

For iluminr it meant naming Capability Intelligence and anchoring it to what the buyer had to prove to regulators and leadership, then rebuilding the message house and the website around the practitioner's decision process rather than the product's feature set. Analysts got briefed on the new term early, before it appeared in a single piece of our own marketing — which is the only sequence that works.

Microsimulations did not go anywhere. They became the mechanism inside the category — the how, sitting under a what that the board already cared about. That relationship is the whole move: you are not replacing the word that worked, you are giving it somewhere to sit.

If you are on the buying side.

When four vendors use the same category term, ask each one what outcome the term produces and watch which ones can answer without walking you through the UI. The company that named the category can usually tell you what it is for. The companies that adopted the word are often describing a feature.

And when a vendor introduces a term you have not heard, that is worth two minutes rather than an eye-roll. Arguably, sometimes it is padding. But sometimes it is the only person in the market who has noticed your mandate changed.