a little more on coaching theory today…
folks ask me a lot of questions whose fundamental focus could be expressed as “how do you get them to do what you want them to do?”
so. here goes. i hereby reveal my entire competitive advantage as a professional coach, by telling you my special secret for how i get them to do what i want them to do.
i don’t. i don’t get them to do what i want them to do. i get them to do what they want to do themselves.
that sounds weird, maybe a little zen-like, i spoze. “what is the sound of the one hand getting them to do what it wants them to do?“ but i don’t really mean anything very mystical by it. it connects back to the always-small-always-improve thing we’ve talked about before.
a common way to express these problems is to talk about horses and water, “you can lead a horse to water but you can’t make him drink.“ (tickled memory: the algonquin round table wits use to play “use this word in a sentence” as one of their punning games. i think it was dorothy parker who used “horticulture” in a sentence this way. “You can lead a horticulture, but you can’t make her think.”)
here’s the thing about horses and water. horses like water. they drink it all the time. they drink it because they’re thirsty, and because it tastes or smells good, because it cools them, and it heals them, and prolly other reasons i don’t even know. when a horse doesn’t drink water, what does that mean? well, it could mean a bunch of things, some pretty scary, but i could collapse those into one vague hand-wave: it isn’t drinking this water just now because it does not want this water just now.
well, if i only get horses to drink when they want to, how do i even do my job at all? i mean, the whole point of getting hired to be a coach is to get horses to drink the software development modern synthesis water.
i do my job by hanging around and/or pitching in, with really good water right in my hands in just the right portions with just the right flavor. when the people i’m with are thirsty, i give them water.
and the more i manage to pull this off, the more they come to expect me to be the kinda person who gives out good water. some of them come very quickly not only to enjoy my water but to want to know where i keep getting it from, so they can get it when i’m not standing around.
as water-bearer’s, software development coaches do have certain advantages.
advice: develop a catalog of “better-than-this” changes. the job is not to install the one best way to make software. (there is no one best way, but that’s for another day.) the job is to make things better. and even a little better is better.
advice: focus in the beginning on small owwies that they agree are owwies. it’s both doing your job, making things better, and it’s generating “capital” you can use later for larger owwies or owwies they don’t yet know they have.
advice: collaborate with them. “coach” is not a synonym for “boss” or “teacher” or even “expert”. work on your collaboration skills more than any other thing.
advice: be kind to the victims and kind to yourself. forgive both parties as often as you can. neither you nor they can always be open, strong, decent, right, or fast. in the AA rooms, we say, “time takes time”. patience is one of your most important resources.
advice: look out especially for the times when they want to do something you also want them to do, and be ready with a small concrete step that will pay them back quickly.
anyway, that’s what i got. how do i get them to do what i want them to do? i don’t. i get them to do what they want to do.