Hey Folks! It’s a new site. If you see bad links or odd behavior, please contact me right away. Thanks! – GeePaw
 Home  Home  hom  Meet with GeePaw  Meet with GeePaw  mee  Work with GeePaw  Work with GeePaw  wor  Who's GeePaw  Who's GeePaw  who  Blog  Blog  blo  Contact  Contact  con

The Team And Three Flows

 15. August 2017

when i think about teams, i think about them with a strange mixture of metaphors.

first i see a thing that is in some respects like one of our classic pictures of an atom. there’s some particles in the middle, and some others that seem somewhat clearly “outside” like the electrons in their clouds. but that metaphor slips a little. in atoms, the electrons & protons & neutrons are separate and separated. in teams, it’s more like a swarm.

so slip that to a flock, instead, or a school of fish. the center is moving, and fish are moving in and out of the center, changing places. the center is a kind of strange attractor, moving through space with its attendant swarm around it, all moving to stay near or far. moving through space? well. no. not space, because space is fairly empty. the space teams move in is fairly full.

having watched a lot of teams, i’ve watched a lot of flows those teams swim in and through. now, i can’t tell you i know everything required for software development excellence. in fact, i’d go so far as to say no one can.

but i do know three things required. i see them as flows or currents in the soup through which the team moves. they are nutrient flows. if any one of them is missing, the team dies. if any are attenuated, the team suffers. and every team i’ve seen that was developing software excellently used those three flows at nearly optimal efficiency.

the first flow i call “valued results”. valued results is the chief steering mechanism of the flock. if the strange attractor at its center is moving, it’s moving to the flow of valued results. trivially, valued results are how the team knows it’s winning, how it knows it’s going the “right” direction.

a minor but not remotely ignorable point. it’s not valuable results. it’s valued. that is, this is a true flow, into and around the team, it’s the exchange of output for valuation, not a distant end-result. excellent teams consistently find ways to keep these exchanges going, and there are myriad approaches.

the second flow or current through which the team swims, on which it feeds, is called “geek joy”. i use that word geek a lot. what i mean by it is someone who is highly technical and highly creative. i don’t distinguish by title or role. so when i say geek joy, i’m talking about the flow that provides the team’s drive. in the geek trades, we have an incalculable advantage over most others. simply put: geeks love this shit.

i know, and i know you know, many geeks who do it all day long, then come home and do it all evening long on their own projects. your designers, your programmers, your analysts, and others i’m not even thinking of right now, all of these are such geeks.

one never has to motivate geeks. one only has to avoid de-motivating them.

the flow of geek joy in excellent teams is what keeps them constantly leaping ahead, loping across the plains, to mix all metaphors further. i’ve never seen an excellent software development team that wasn’t suffused with geek joy, the sheer wild exuberance of doing THAT THING.

the third flow is the flow called “courageous curiosity”. this flow provides the team with a feeling for where it is at right now. it is the asking and answering of questions. it includes, especially, scary questions, which have hard answers. remember that the strange attractor at the center is itself always in motion. nothing sits still.

courageous curiosity is our only way to know where that attractor is going, what flows it’s consuming, & where individuals stand, relative.

so those are three flows i know are required for excellence in software development. valued results, geek joy, and courageous curiosity.

i’ve seen a lot of teams. i never saw an excellent one that wasn’t drinking deeply from all three flows. i’ve never seen a failing team that wasn’t failing to take advantage of one, two, or all of them.

as i said at the outset, i’m not sure those three flows are “sufficient”. but i am sure they are “necessary”. if your team is failing, or you think it might be, look to the three nutrient flows that keep it healthy.

is one weak? is one altogether absent? start there.