Imagine a moment of triumph being overshadowed by a single ill-chosen word that sparks global outrage— that's the drama unfolding in cricket right now. But here's where it gets controversial: can a coach's slip-up really steal the spotlight from a team's historic victory, or does it reveal deeper issues in how we handle language and history in sports? Let's dive in and unpack this story, step by step, to understand why it's not just about cricket, but about respect, context, and the delicate balance of international relations.
Eleven days after Shukri Conrad shifted attention away from his team's stellar performances by using a term loaded with racial undertones during a media briefing, he offered some insights but held back on a full apology. Speaking at a press gathering in Visakhapatnam on Saturday, Conrad shared his thoughts in a candid way. 'My goal was never to hurt anyone or come across as arrogant,' he explained. 'Looking back, I might have picked a more neutral expression, as it allowed people to interpret it in ways I didn't foresee. The meaning I was aiming for was simply that India would face a long, grueling time chasing our score, making it incredibly challenging for them. I have to watch my words carefully now, because anything I say could be twisted too!'
This all traces back to November 25, during the fourth evening of the Test match in Guwahati. Journalists inquired about South Africa's decision to bat for an impressive five hours and four minutes before closing their innings with a commanding lead of 549 runs—161 more than any team has ever successfully overhauled in an Indian Test match. Conrad's original response? 'Our aim was to force the Indian players to endure extended periods standing out on the field,' he said. 'We wanted them to truly grovel, borrowing a phrase. Essentially, we planned to dominate them so thoroughly that they'd have to scramble just to survive on the final day and a bit into the evening.'
Out of those 48 words, 47 were unremarkable. But that one word—'grovel'—ignited a firestorm. It carries heavy associations with slavery, colonization, and racism, reminiscent of Tony Greig's infamous use in May 1976. Greig, England's captain at the time, employed it to describe his team's brutal treatment of the West Indies, fueling such fury that the West Indies team turned the tables and won the series 3-0. And this is the part most people miss: how a word's historical baggage can linger and redefine its meaning in sports culture.
'It's truly regrettable,' Conrad reflected on Saturday. 'Perhaps it added some extra spice to the upcoming ODI series, and with India clinching that, the T20 matches are set to be even more intense. The downside is that despite the uproar, I stand by 'grovel' as a legitimate English term. Unfortunately, it invited too many conflicting interpretations.'
The very next day, South Africa secured a resounding victory by 408 runs—marking India's most lopsided home defeat—and claimed the Test series 2-0, their first such win in India in over 25 years. 'What happened was that it dimmed the shine of an extraordinary triumph for our Test squad,' Conrad noted on Saturday. 'Humility is fundamental to all our teams. It's a shame the buzz centered on the coach instead of the players. Ideally, the spotlight should stay on the athletes, and I hope this matter is now behind us.'
Well, maybe yes, maybe no. Conrad is right that 'grovel' is indeed a valid English word, but it implies relentless domination and a kind of ruthless behavior from those enforcing it—think of it as almost psychopathic bullying. Does he really want his team linked to that image? For starters, the term's cricket context is forever stained by the racist undertones in Greig's statement. Greig, a white South African who thrived under apartheid, might not have pursued a cricket career if he weren't of that background, unlike Basil D'Oliveira, a talented player of color who was forced to leave South Africa to chase his dreams elsewhere. D'Oliveira had no choice; Greig did. Why borrow a phrase from such a dark, troubling chapter when there are countless better alternatives out there?
Ultimately, Conrad—and no one else—is to blame for the 'noise' he resented. That's the true misfortune here. He inadvertently robbed his team of their well-deserved glory. And to make matters trickier, captain Temba Bavuma faced questions about Conrad's wording at two separate press events. It's fundamentally unjust for players to defend a coach's misstep, but how can journalists ignore it when the issue hangs unresolved?
Potentially even more problematic is the risk of straining relations with Cricket South Africa (CSA). The Board of Control for Cricket in India (BCCI), known for their sensitivity to perceived slights, might not take kindly to Conrad's comments—or deem his Saturday explanations insufficient to mend the breach, or worse, see them as aggravating the situation. Remember, India holds the purse strings of global cricket, and CSA felt that sting back in November 2013 when the BCCI scaled back India's tour to South Africa from 12 to just 7 matches, costing CSA over USD20 million. No official reason was given, but insiders pointed to retaliation against CSA hiring Haroon Lorgat as chief executive. Lorgat had longstanding tensions with the BCCI, dating back to the 2011 World Cup, where he vetoed Eden Gardens as a venue for India's clash with England. The BCCI had even cautioned CSA against appointing him, warning it could harm board relations.
That said, Conrad deserves immense credit for his coaching achievements. He's transformed a team that once consistently fell short into one that regularly exceeds expectations. He's instilled in his players the belief that they can conquer any challenge, and he's won over cricket fans with his infectious optimism and quick wit. It's hard not to root for him. He surely wouldn't want to jeopardize all that by being lumped in with Lorgat in the BCCI's eyes. South African cricket, still recovering from years of financial hardship due to poor management and governance, simply can't afford another blow like that.
Conrad has encouraged his squad to play with their authentic selves—a bold balancing act. Its payoff was clear in India, where South Africa outshone their hosts in the first four matches, winning three. However, in the decisive third ODI on Saturday, they faltered badly. Quinton de Kock's composed and powerful 89-ball 106 and Bavuma's 48 formed a solid partnership of 113 for the second wicket, but the innings unraveled as the final seven wickets fell for just 100 runs, with the last five collapsing for 35.
Kuldeep Yadav was a standout, claiming 4/41 by dismissing Dewald Brevis and Marco Jansen in quick succession during the 39th over, halting South Africa's momentum. Prasidh Krishna bounced back from a rough start—conceding 27 in his first two overs—to end with 4/66. De Kock's innings was a masterclass, earning him his eighth ODI century against India, but South Africa's total of 270 seemed underwhelming compared to the 300-plus scores in the series' first two matches, especially with dew posing challenges for bowlers under the lights. As expected, India triumphed with nine wickets intact and 10.1 overs to spare, securing the series.
Yashasvi Jaiswal had only one half-century from his six other innings during South Africa's tour, but he shone brightly on Saturday, smashing an unbeaten 116 off 121 balls—his maiden ODI hundred, completing a trifecta of centuries across all formats. Jaiswal and Rohit Sharma raced to 155 off 155 balls before Keshav Maharaj trapped Sharma at deep square leg for 75 in the 26th. Virat Kohli then strode in, unleashing an unbeaten 65 off 45, and with Jaiswal, they added 116 off 84 to wrap it up.
'We'd hoped for a more thrilling contest today,' Bavuma admitted to the hosts. 'Our batting didn't deliver enough runs. With the dew factor, conditions often favor batsmen under lights, and we should have been more strategic—we handed over wickets too freely.' Yet, not everything was negative for the South Africans: 'We've grown significantly. Facing India's elite spinners is tough, but for much of the series, we kept them on the back foot. If I had to rate our performance out of 10, we'd hit six or seven.'
Conrad made a key move on Saturday. At the very least, South African cricket hopes the BCCI sees it that way. But what do you think—should a single word carry so much weight in sports, or is it time to let go of historical baggage? Does Conrad's refusal to apologize fully redeem the situation, or does it just add fuel to the fire? Share your thoughts in the comments; I'd love to hear if you agree, disagree, or see another angle entirely!
