Venkatesh was promoted to No. 4 to counter Gujarat\u2019s left-arm spinner Sai Kishore and leg-spinner Rashid Khan. However, the left-hander failed to justify the move, scoring a scratchy 14 off 19 balls without hitting a boundary.<\/p>\r\n\r\n
\u201cI do agree that Venkatesh didn\u2019t play the role he should have. But was he told to just survive? Was the message from the dugout to simply knock it around when Rashid was bowling?\u201d Pujara said on ESPNcricinfo\u2019s Time Out<\/p>\r\n\r\n
For Pujara, it wasn\u2019t just about individual decision-making but a larger question of tactical clarity. \u201cTimeouts exist for a reason. When you realise things aren\u2019t working, the support staff must intervene and give a clear directive. That seems to have been missing.\u201d<\/p>\r\n\r\n
Pujara also turned the spotlight on KKR\u2019s bowling, which he believes allowed GT to post 198 on a surface that wasn\u2019t as flat as the score suggested. \u201cThe pitch had enough turn. If you\u2019re conceding over 60 runs in the last five overs on such a surface, then your execution is lacking. They should\u2019ve restricted them to around 180,\" he said.<\/p>\r\n\r\n
KKR were 68 for 2 after 10 overs, needing 131 more at 13 runs per over. The lack of urgency and misreading of the pitch cost them dearly\u2014much like their previous match against Punjab Kings, where they couldn\u2019t chase 112.<\/p>\r\n\r\n
\"It\u2019s not just about batting collapse; it\u2019s about failing to understand what\u2019s needed at the moment. They were behind in all departments\u2014strategy, clarity, and execution,\" Pujara said.<\/p>\r\n\r\n
KKR were 68 for 2 after 10 overs, needing 131 more at 13 runs per over. The lack of urgency and misreading of the pitch cost them dearly\u2014much like their previous match against Punjab Kings, where they couldn\u2019t chase 112.<\/p>\r\n\r\n
Also Read: <\/b> LIVE Cricket Score<\/a><\/p>\r\n\r\n