we’ve got this long (and still probably partial) list of reasons why people don’t try new things.
in recent weeks, i’ve gone pretty far afield around coaching. i picked out four or five threads separately and ran with each, separately. if it seemed a little incoherent to you, well, you know, join the club. analyzing individual threads isn’t necessarily the best way to analyze a fabric. i confess to feeling a little bewildered as i wrote it. i get you might feel that way reading it.
that list of reasons, tho, is the result of me struggling to understand how several different themes, the ones i constantly harp on, are in fact deeply interwoven. i’d like to mention each of the themes and mention in a line or two how it all connects.
i offered at one point “a list of gerunds”, describing (always partial) the list of activities that i use when i’m coaching day to day. they connect to the list of reasons in two ways.
third, and by far the most coherent of any of these, is the conversation around always-small-always-improve. the ASAI expression has two terms, and it connects on both of them to that list of reasons.
always small because it’s easier to try things that are small than to try things that are big. small often (not always) correlates well with easy, and easy-to-try is big plus in the try-selling business. always improve because s great many of those reasons have to do with proof, and some have to do with faith.
proof happens after the trial. if trying something new doesn’t actually improve things, why should we do it? faith happens before the trial. if prior tries have improved things, one’s sense of faith that trying new things is good goes up quite a bit.
my broad mistrust for branded methods isn’t associated with any given post, but is visible by the absence of advocacy for one or another, and a certain mean-spirited tone in my occasional pot-shots at method-warriors. the methods seem, far from easing opening the world up to trying new things, to contribute in a variety of ways to actually trigger some of those most common reasons from the reason list.
they are almost uniformly “cities on a hill”, large palaces made of words, located far away from here, and often sourced far above here, both factors that trigger some of those reasons. they rarely if ever provide a transition route. they are vested in having all and only their own parts present. they often fail altogether if any one element is still done “the old way”. they seem also to lend themselves to misunderstanding, another factor in some of those reasons not to try the new thing. and of course, they guarantee flavor-wars, gross generalizations, and reasoning around abstractions that are 5 and 10 hierarchichal levels beyond the concrete.
so there we are. that list of reasons underlies, overlies, intertwingles, with the whole fabric of coaching as i grasp it.
there are other threads to pursue, and i’ll probably get there. (already formulating a muse on “sociotechnicality” and why it’s such an important concept.) but to be honest, i want to do some more traditionally geek stuff for a while. i need geekery like i need music, to thrive.
thanks all for the various inputs, and for hanging in so long to read all these damned things. feel free to poke & prod, comment, question, critique.