WORLD CUP T20 FINALS – A REAL-TIME FAN VIEW
At Fantain, we run a real time game called Playcall©. In this game, cricket fans take decisions that captain’s make in real-time. The questions are asked before the actual decisions are taken in the field of play and answers locked in. In effect, the fans act like captains. Fans know and understand a lot about the sports they love, and how the fans feel about the action is very interesting to understand.
So here is what the fans felt during the finals between Sri Lanka and India. And remember, none of this is retrospective. The fans have decided the following at the same time the captains were deciding…
|Ajinkya Rahane failed with the bat. Should Dhoni have played Shikhar Dhawan instead of Rahane. 19% of fans selected Shikhar Dhawan while 81% opted for Rahane.|
What about Yuvaraj? Should he have played the match in the first place. Yes, said 64% of fans. 36% said that either Shikhar Dhawan or Stuart Binny should have replaced Yuvaraj in the playing XI.
What about India’s second seamer? 39% of fans selected Shami and 61% selected Mohit Sharma in the team. Surprisingly, not one fan selected Varun Aaron.
|Hindsight is 20-20. Many of us felt Dhoni made a mistake by asking Yuvaraj to bat at No.4. But guess what, an overwhelming 70% of fans also selected Yuvaraj to bat at that position. 24% decided that Suresh Raina should have batted then and 6% felt that M S Dhoni should have batted at No.4.|
DHONI’S DECISION-MAKING DURING THE MATCH
There were a few pivotal points in the game where the direction could have changed because of Dhoni’s decisions. Let us analyse some of them:
- Dhoni asked Suresh Raina to bowl before Ravindra Jadeja Was this a mistake? This was a close one. 53% of fans made the same decision that Dhoni made while 47% of fans decided that Jadeja should have bowled first.
- Both Ashwin (1-0-4-1) & Amit Mishra (1-0-1-0) bowled excellent first overs. But Dhoni did not give both of them another over in the same spell. Was this a mistake? What would you have done if you were the captain? Well, 64% of fans would have kept Ashwin and Amit on for a longer spell. Only 36% of fans took the same decision that Dhoni took.
FINAL ANALYSIS OF CAPTAINCY OF BOTH DHONI AND MALINGA
At the end of the match, we asked the fans how they rated the captaincy of the Dhoni and Malinga
86% of fans thought that Malinga’s captaincy was either brilliant or good. Only 46% of fans thought Dhoni’s captaincy was either brilliant or good. Clearly, the fans thought Malinga was the better captain on the day. But, this question is asked in hindsight. It is easy to criticize captains when they lose a match. Important thing is to see if we would have taken a different decision if we were the captain. We measure this through what we call ‘Fan Alignment Score’.
How aligned were the captain’s to the fans.In other words, how much did the fans concur with the decisions made by the captain. We calculate this score using a proprietary algorithm and here are the numbers
Dhoni made decisions more aligned with India fans during the game, a tad more than what Malinga made. This underlines the difficulty and snap-decision making process captains go through. In our experience, any alignment score above 50% is very good, indicating good alignment with fans and therefore, presumably, the best ‘crowd-sourced’ decision.
WHY ARE WE DOING THIS?
There are a lot of polling bots out there that ask random questions during a game, show the results and move on. We look at this differently. We identify and segment fans, get real time inputs, and using deep data analysis and game heuristics, provide insightful views of the game from a fan’s perspective. This is ultimately a great gaming platform for the fans to engage them, in real-time, in the field of action, a great tool for captains and players to analyse what their fans perceive of them, and a great medium for franchises, brands and other stakeholders to reach out to different segments of the sporting audience.
For more information, please get in touch with us at firstname.lastname@example.org.