When coaching cricket to kids, the explanation of an activity is one of the most tricky parts.
Explaining rules is essential but it’s also downtime from the action. Most kids get distracted easily, which then takes up more time.
My current solution leads to some messy initial outcomes but getting to the action more quickly:
Spend as little time as possible explaining, just sticking to the absolute basics, then start the game quickly.
It is surprising how fast people learn when they have to; like learning French by living in France. That said, there is plenty of chaos. People shouting rules at each other, standing looking confused, making up their own rules as they go and so on.
For example, a net game like “21s” can be explained quickly like this:
The aim to be the first to 21 points between batsman and bowlers.
Bowlers get 10 points for a wicket, 1 point for a play and miss and 3 points for a ball hit above head height.
Batsmen get a point for a cross bat shot contact, 3 points for a straight bat shot contact and 5 points for surviving 10 balls.
Then you start. Use a whiteboard or tokens to keep score if needs be.
In my experience, glitches iron out fast and naturally within the basic framework of the game. Anything that doesn’t work needs a reset from the coach, but this is rare.
Once the game is running you can build up extra rules. Deal with wides, give batsmen an aerial option, encourage riskier play from the batsman or give bowlers more points for wickets. Design the game to meet your needs.
But the key point is to crack on and be comfortable with it not being perfect. After all, cricket matches never happen perfectly so why should practice?