User Experience Mapping

The finished task model

The task model map

Some authors suggest adding connections (usually arrows) between different tasks. While it's okay to do that for linear task models, such as the checkout for an e-commerce site, in my opinion they just add visual clutter. For complex scenarios, such as our game, the tasks are rarely in a linear order, and always necessary. For example, download, install, and launch must come in that order, but the player will not always level up or unlock a new thing after each game. It's also likely that the user will start customizing the pilot, then go to a microtransaction, buy new camouflage, then go back to ...