Unravelling the mystery behind a most prolific pair

Flag Indian cricket
1. Make me Understand / 2. Make me Engaged

Unravelling the mystery behind a most prolific pair

The Indian test team under Virat Kohli has hit a fabulous purple patch and may end up becoming the best in Indian cricket history. While the contributions of Ashwin, Kohli and Jadeja to this success are well acknowledged, one contribution is not so well known: the batting partnership of Murali Vijay and Cheteshwar Pujara.

Here’s some data to back that up from ESPN CricInfo (the best place on the internet for cricket data, analysis and opinion). This chart ranks Indian batting pairs in descending order of average partnership per dismissal (minimum partnership runs 2000):

Among Indian pairs with 2000 or more runs together, Vijay and Pujara average the best.

That table there has some serious batting talent. Not bad to be topping it.

But this is still data (albeit analysed a bit). Is there a story behind this data? What makes this pair so successful? Conversely, is there something that actually impedes their success, despite which they have achieved these numbers?

Enter the master

Let me handover the stage to Sidharth Monga – probably among the top three cricket writers in India (and it is a competitive field). I’m a big fan of Sid’s ability to “find the story” and narrate it in a compelling manner.

Read this recent article where he goes beyond the numbers and explores the fascinating underlying story.

He starts off – as he often does – by describing a small incident that would have probably gone unnoticed by 99.9% of the viewers:

“In the 26th over of the day’s play, Cheteshwar Pujara played a lovely straight drive. It should have gone for a four between the stumps at the non-striker’s end and his batting partner M Vijay. Except that Vijay almost had his back to the action and didn’t make the slightest of efforts to get his bat out of the way. The ball knocked the bat out of Vijay’s hand, and created a misunderstanding as Pujara wanted a single off the ricochet, but Vijay was still processing what had just happened.” (all emphasis mine)

He then adds another incident from a recent test:

“It was quite reminiscent of India’s first Test with modern DRS. Pujara was given out lbw to a legbreak that was hitting leg and middle and thus ought to have pitched outside leg. Except that when you are batting and given out, you look at cues from your partner so as to not look selfish with reviews. In this case, Vijay again had his back to the action by the time Pujara looked up.”

And another one:

“They are both slow runners who can often be caught ball-watching. In Hyderabad on Thursday Vijay took a few steps for a single, Pujara charged off, looking at the ball and not his partner. Then both made off for the same crease. Vijay, who now knew he was to be beaten to the crease at the striker’s end, tried to complete the run. They were lucky this didn’t result in a run-out.”

Sid then goes on to reveal the other side of the coin: powerful stats that inarguably make a case for stellar achievements since they started playing together:

“Among Indian pairs with 2000 or more runs together, this partnership averages the best. They are also India’s most prolific pair since the start of this decade.”

So here’s the difference in the storytelling. Instead of just starting with the data, Sid chose to narrate three vivid, concrete incidents, and then followed it up with the performance data. By juxtaposing them, he highlights a striking point: these two players – the guys with the best partnership average in a list that includes Tendulkar-Dravid and Gauti-Sehwag – don’t seem to be the best communicators on the field. In fact, they seem to have serious issues communicating with each other. How can that be?

He then tackles the apparent contradiction head-on, in this stunningly insightful paragraph:

“More than anything else, the sight of Vijay and Pujara batting well together in a partnership is the sign that the India Test team is doing well. The irritants – Vijay switching off at the non-striker’s end and both ball-watching when running – are offshoots of what are integral parts of their game. They are old-fashioned Test batsmen. They build their innings through a lot of leaves and a lot of defensive shots when it is the most difficult time to bat. They need to switch off between balls otherwise they will exhaust themselves in no time.” (emphasis mine)

That’s the brilliant insight – batsmen at this level need so much concentration on every ball, that they need to switch off between balls – which explains the apparent lack of communication (especially when at the non-strikers end). And what explains the hunger for runs? Another aspect which distinguishes Vijay and Pujara from the other batsmen on the list. Monga again:

“They (Vijay and Pujara) get to play international cricket in only one format (i.e. Tests) and they are under extra pressure when they play Tests, especially given the amount of batting talent in India. They were both dropped for flashier batsmen during the West Indies tour.”

And so that’s the story of India’s most successful pair by batting average: focus on one format and when at the crease, concentrate for long periods by periodically switching off (even if it means the odd missed DRS or lost boundary opportunity).

What can we learn from this?

  1. Notice the small things: Noticing the first incident (of the ball hitting Vijay’s bat) is the sign of an expert – one who can quickly discern something of greater import from a seemingly ordinary fact or event. Such ‘story-spotting’ ability comes with experience in a particular field. Keep your eyes and ears open for these.
  2. Know your historical data: It helps to have a comprehensive view of your field. Sid (and many of the other CricInfo writers) are excellent at referencing relevant incidents and stats from matches in the faraway past. You can apply it in  your work too – how does this quarter’s workers’ strike compare with the one that happened four years ago? HUL showed excellent awareness of their past in this instance.
  3. Use context and perspective: Sid used many statements that differentiated Vijay and Pujara and gave better perspective to this pair’s performance:
    • Vijay and Pujara need to be different from other batsmen, since they face bowlers at their freshest best
    • They play only one format (tests) as against the others in the list
  4. ‘Reveal’ the answer after creating an element mystery/surprise: Before talking about the batting achievements, Sid starts almost on a negative note – highlighting the communication issues between the pair. He then reveals the performance stats: the pair has the best average among stalwarts. He then mentions the contradiction (“If you didn’t know better, you would think they are a dysfunctional pair”). What explains the apparent contradiction? It’s a mystery isn’t it?! The reader is intrigued, and is keen to know what the answer is going to be. The answer comes as a fulfilling insight that explains the mystery so well. Imagine if Sid had directly put his main thesis (the mental concentration one) front and centre in the article. Readers would’ve been like: where did that come from? Even when you are presenting business data, you can use elements of mystery and surprise (without making it gimmicky) by building it into a clear narrative as shown in this case, to enhance the impact of your findings.

Will Vijay and Pujara become the most successful batting pair in Indian cricket in terms of runs (surpassing the Tendulkar-Dravid colossus?). Only time will tell, but one thing is for sure: you’ll be seeing much more of Sid Monga on this blog!

******

Featured image credit: By hughiethethird [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons. Cricket stats table link.

Get Storytelling tips in your Inbox

Subscribe to the 'Story Rules on Saturday' newsletter

Get a free e-book that decodes the hidden storytelling structure used by leaders like Jeff Bezos, Bill Gates and Warren Buffett.
Your infomation will never be shared with any third party