Jury duty and differentials — when to back the crowd

Sometimes the popular pick is the right pick. Here is when to trust the selection percentage.

This guide covers the framework, the application, and the limit cases. The framework is the structure you apply before every fixture. The application is how you adjust the framework to the specific match. The limit cases are the fixtures where the framework does not hold and you need to override it.

The first step is to read the venue. Boundary size, average score, dew forecast, and surface behaviour. If the venue rewards pace, weight your seam picks. If it turns, weight your spinners. The venue is the most reliable predictor of XI in any given fixture.

The second step is to lock the role. Pick the players whose role is the clearest — batting slot, overs allocated, powerplay or death window. Captaincy goes to the highest-floor role, not the most famous name. The role is the function of the venue, the captain's pattern, and the opposition.

The third step is to read the match-up. Specific bowler-batter match-ups matter at the margin. A powerplay aggressor against a wicket-taking new-ball bowler is a downgrade candidate if both are available. Two picks that share a role and bat in the same window — one of them is unlikely to score fully.

The fourth step is the captain order. Decide before the toss. Safer captain = anchor with confirmed role. Higher-variance captain = all-rounder with defined powerplay or death window. The captain order should not change after the toss unless the team sheet has a confirmed surprise.

The fifth step is the post-match review. After the fixture, compare the actual role each player was given against the preview. A new role is a new signal — update your model, do not argue with the result.

The limit cases are when the framework does not hold. A venue with a major weather disruption, a captain who has been rotated mid-season, an opposition with a confirmed surprise selection — these are the cases where you override the framework. The override should be explicit, not implicit.