• Fueling conversations and igniting meaningful experiences for cricket fans around the world
  • Fueling conversations, igniting experiences
12 months ago

The great man, Warren Saunders, gave me many great ideas in regard to captaincy, but the 2 mentioned below are ones that I never forgot and have passed these ideas onto other captains along the way.

1. At the start of a season, set your team a target for the number of wins that you need to have to achieve your goal of making the semi-finals or possibly the top 3-4 positions on the ladder. For the sake of argue, let's say 10 wins out of 15 games. In this way when you have a loss, it's not the end of the world, you simply need to refocus on the winning mentality to get back on the road that you have set out. I think this attitude helps sides not slide into self-doubt and lack of confidence. This also creates the mentality of always going for a win rather than having a fear of losing.

2. At the start of a season address all your players together. Explain your expectations for the season but particularly point out that you don't want to hear any whinging or complaints 2nd hand through someone's teammate, or parent or whoever. If you have a grievance, bring it directly to the captain as he is the only one who can fix it. If a complaint arrives 2nd hand it will be viewed very badly.

Partner Sponsors

Responses

Great tips. I would also add a third one, which is a continuation of the 1st point. In addition to expected wins, it is also key to set goals and roles for individuals and let everyone know that.

If your goals is to score a total of 400 runs and a 50+ every 3 innings, the player can mentally prepare themselves during the season. Knowing others goals, will help teammates to encourage and provide the right support where required, again helping the team morale

Your Answer

If you wish to include a video or audio response, you can do this by including links to Youtube, Vimeo or SoundCloud (https://www.youtube.com/watch?v=xxxxxxxxxx OR https://vimeo.com/xxxxxxxxx)

<% error.message %>