Lately I’ve been emailing with several coxswains who have been using their time indoors to work on their calls and eliminate some of the repetitiveness that comes with not knowing what to say. A question I got back in December (that encapsulates the general vibe of the other questions I’ve been asked) said “how do you suggest rephrasing things and not just spouting meaningless calls?”. Below is my response.
“As far as styles of calls, it’s different for every coxswain and varies between the crews they’re coxing. So, knowing your crew is step one. What do they respond best to? Are they the type of crew that needs a lot of positive reinforcement and motivation or are they the type that wants very blunt, straightforward, no bullshit-type of calls?
Step two is understanding technique and the style of rowing your coach is trying to teach. The more you understand the nuances of the rowing stroke, how the bodies connect to the blades, etc. the easier it will be for you to communicate what you’re seeing and feeling to what actually needs to happen. The winter is a good time to talk about all this with your coach and ask questions if you have them.
Step three is taking a copious amount of notes. If you’re ever in the launch you should be able to come off the water with at least a page or two of notes based on the things you hear your coach saying. Obviously it’s a little harder to do this on the water because you’re not going to remember everything but that’s why you use your recorder – most of the time you can pick up your coach’s voice on there so listen to what he’s saying to your crew and write down stuff from that that can be used as calls. I ride in the launch with our head coach nearly every day and I tend to write in shorthand the stuff he’s saying to each guy so I can pass it on to our coxswains for them to make calls with.
For example, (I’m just flipping open to a random page in my notebook), during a practice back in September he was talking to two of the guys about burying their blades too deep through the drive and how part of the reason why they were doing that was because they were opening their backs too early instead of hanging their weight off the handle. I actually remember us sitting in the basin as he explained this for about five minutes but of that five minute long technical explanation, what I wrote down was “don’t confuse hanging body w/ opening backs too early → why Charlie and Sam are going too deep w/ the blades”.
After practice I talked about that with our coxswains and they’ve been able to take that and turn it into a handful of different calls, all relating back to the same concept of suspension. Because this specific issue was originally aimed at those two guys in particular, they’ll occasionally incorporate them into their calls too – i.e. “let’s hang the bodies off the handles and suspend our weight through the drive – Charlie and Sam, stay horizontal here through the water”.
What I’m getting at is the majority of what you’ve gotta do to avoid becoming repetitive with your calls has to happen off the water. Creating a backlog of sorts of the things your coach says to the rowers is a great place to start though because from there you can incorporate that stuff into your calls and spin your own calls off of whatever technical thing he’s coaching the rowers on based on what you’re seeing.”
To that last point, I do this in Google Docs. Every couple of weeks I’ll take all the semi-legible notes I scribble on the launch and dump them into a Google Doc that houses, at this point, three years worth of technical and motivational calls and phrases. Trust me though, your notebook and recorder will be two of your biggest assets here so take advantage of them. You can check out the two posts linked below if you’re not sure how to keep a notebook or what the best type of recorder is to get.
Most of what I said in that email has been said in a variety of posts over the years but now that it’s all in one place, I hope this will help you hone in on the steps you need to take if being less repetitive with your calls is something you’re working on too.