The importance of captaincy in cricket is greater than in almost any other sport. In football, for just one example, the captain has almost no influence whatsoever over team selection or strategy. This is not true in cricket. Not only are cricket captains involved in most strategic and tactical decision-making, this also comes with more responsibility for the other players in the team, their mindset and their morale. Measuring the value of a good captain is incredibly difficult

One aspect of captaincy that might be measurable is the decisions that they make on the field. Here, the decision-making is observable by an outsider. Obvious, even, in the case of bowling changes. They occur 20 times in an innings and at regular intervals

My current project is a ball-by-ball simulator for T20 matches. This post isn't about that. It is about one tiny component which took way too much time to build considering how little value it contributes to the endeavour of predicting T20 outcomes. I wanted my simulator to have the ability to simulate what bowling changes the captain would make during an innings. And so I built a model to pick the next bowler