scenario-map

The other skills in this library each describe one mechanic. None of them answers whether your business needs that mechanic, what to build first when you cannot build everything this quarter, or what to do with a mechanic that runs correctly and nobody needs any more.

The failure this skill exists to prevent shows up nowhere in a per-mechanic report. Every flow in the set can pass its own review and post a normal conversion while the set as a whole chases one person with two occasions for the same argument, and while rows that have not fired once since launch sit on it unread. A report on a mechanic looks inside the mechanic. The questions here are about the set: what belongs in it, what order it gets built in, and what leaves.

One thing this skill is not: a list of scenarios. An industry set (thirty-six scenarios for online schools, twelve for a marketplace) is a useful list of occasions and a useless configuration, because the constants that make a mechanic work come out of your own purchase cycle rather than somebody's article. What follows is how a roster is built from such a list, not a longer version of the list.

When to use this