Prashant Khanna has expanded his JioStar remit to cover Rights & Innovation for Sports and the Cricinfo Business. He set out the move in a LinkedIn post, tying the change to nearly nine years across Star, Disney Star and JioStar.
Khanna’s wider JioStar remit
Khanna said he is taking on a broader mandate spanning sports rights, partnerships, innovation and digital businesses. He wrote that the new role will let him build on work across production, technology and innovation from a wider business perspective and support the next phase of growth for JioStar Sports.
That gives one executive responsibility across the commercial side of sports rights and a digital property in Cricinfo, a combination that pulls business and product thinking into the same seat. For JioStar, the shift points to a tighter link between how sports inventory is handled and how related digital businesses are managed.
Star and Disney Star background
Khanna said his path into the role ran through Star, Disney Star and JioStar, and that he joined the Star network in 2017. He also said he spent more than seven years at The Walt Disney Company before joining the Star network.
He said closer collaboration between broadcasters, rights holders and technology partners is creating new opportunities across the ecosystem. He also said he looks forward to working with teams, partners, leagues and governing bodies to strengthen partnerships, unlock new opportunities and create long-term value.
ICC and BCCI responsibilities
His current remit sits alongside other cricket-facing responsibilities. Khanna serves as Production Contract Manager for the International Cricket Council for the 2024–27 cycle and is a member of the IPL World Feed Production Committee under the Board of Control for Cricket in India.
He has also worked with News Corporation, NDTV, Turner Broadcasting, Reliance MediaWorks, Hinduja Group, Encompass Digital Media and QSport Media. The role expansion leaves JioStar with a clearer executive lane for sports rights and Cricinfo, but the post does not spell out what specific operating change triggered it now.
