Game.
The game a strategy plays in its market, by value chain: the way of going to market, the twin's template, the roles that play, the play families that read alpha there, what is counted, and the dynamics it assumes
Figure 1Gamespecified
- kind
- row
- scope
- platform
- key
- its name
- store
- postgres
- family
- strategy
Fields#
| field | type | required | note |
|---|---|---|---|
name | text | yes | |
way | WayOfGoingToMarket | yes | |
template | SystemsModelTemplate | yes | |
roles | RoleAroundADecision | yes | the roles that play |
play_families | [one of demand engineering | demand capture | channel and partnership | pricing | positioning and proof | offering design | market entry and beachhead | growth in a market | retention and existing customers | competitive | regulatory and payer | education and enablement | sales motion and operations | hedge and portfolio | ecosystem and platform] | yes | the families that read alpha in this game |
what_is_counted | text | yes | |
dynamics | text | yes | the loops, delays and limits the game assumes, in the living market’s words |
crowd | one of named players | a mean field | yes | whether the parties are named players or a crowd |
Routes that use it#
No route takes or returns Game directly. The record holds it, and the objects that point at it reach it.