Rhythm & Urgency: The R in RAMPS

Rhythm is the R in RAMPS. let’s take a look.

rhythm is about tension & release. it is the sense one has of readying, girding, coiling, then taking that stored energy & sending it out.

we’ll get to music in a second, tho maybe in a way that will surprise you. but let’s start with some non-musical kinds of tension & release. a spring is stretched, creating tension, then let go of, creating release. your movement is your muscle cells in rhythm: they get fat and short, storing potential energy, then thin & long as they let go of it. a bow and arrow works identically: you pull the string to store energy, let go of the string and the store goes out to the world.

some nearby words: expansion & compression, coil and strike, build & peak, the list is long.

now we come to music. a first reaction to the word ‘rhythm’ in music is to associate it primarily with what musicians call ‘meter’. meter is just the thump thump thump of the beat, whether explicit or implicit in the performed song.

but to think that’s the only example of what we’re talking about is to grossly limit your understanding of rhythm as motivator & music both. music is arguably music because of the sheer variety & multiplicity of the tension-release cycles that go on inside it.

when you hear a verse and a chorus and a verse and a chorus, notice that the verse is usually different & the chorus is same-ish. the verse builds tension — anticipation that the chorus is coming — and the chorus resolves that tension. rhythm.

if you listen closely to great performers work your well-known songs, you’ll notice how often they *leave* the melody. they rise above or below, they trill around, they add fillips: they are creating the tension in you that they’re coming back. rhythm.

and of course, there’s actual rhythm. sophisticated drum lines walk away from or elaborate on meter, reaching climactic moments on return. i could easily go on all day about musical forms of this. i will spare you, in one of my occasional bouts of beneficence.

what rhythms, cycles of tension & release, do the individuals on your teams feel, and how do they relate to urgency?

there are myriad rhythms in geekery. as in music, there’s usually major & minor beats, phrases and measures. these come quickest to mind:

the daily standups, if you’re doing that. the weekly retros and, if you’re doing it, planning sessions. all of these form a beat.

but there are many more. refactoring, green to green code-changes, provides wonderful tension+relief in tiny little doses. all of the steps of TDD are like this. we briefly perturb the system, sending it into imbalance, then we hit the closing keystroke: TA-DAH! the cycles i use to push code, easy in my case, harder in many VBCA shops, are themselves little rhythms.

obviously, every software release is a release in this sense, too. OR SHOULD BE. hmmm. there’s a clue.

one kind of tension & release is taking a deep breath, holding it, and then exhaling. let me ask you a question:

how long can you hold your breath? and when you hold your breath a long time, does that first gasping out instantly restore you to normalcy? another clue.

on the one hand, the longer you build tension before release, the more powerful the force. cool. but incomplete. because on the other hand, the longer you hold it, the harder it gets, and the slower your recovery — the greater your need for respite. (in the nervous system, this is called the refractory period. the time required between one tensioning before the next can happen.)

we started w/the concern about a lack of a sense of urgency. do you see that a sense of urgency is exactly what the tension-building makes? it’s our anticipation of the resolution, the release, that provides us with the primary motivation for coiling in the first place.

i almost always want to ask an urgency-lacking manager: how long since the last tonic? how long have we spent in refractory? recall that most of the time the manager’s asking me this are already in deep shit. it’s not the sort of question one asks, otherwise.

the odds are good that a) it’s been forever since the tonic, and b) the refractory time is at zero because of it.

the first thing you need to do when you see your team lacks urgency is to look very hard at what you are now and have been asking of them.

to get to urgency, you have to have a normalcy from which to depart. a team lacking the one nearly always lacks the other. so the biggest thing you can do to create urgency is to refuse to demand it until the team has recovered its normalcy.

that’s a big one, and i know it’s hard. it consists of telling people — usually above you — that the answer is no. no. you can’t have it 10/1. no. you can’t add that in, too. no. you can’t ask for a stretch goal from a team that isn’t meeting normal ones. yikes. but if you want a team that can pull off a dramatic rise to the occasion now and again, you have to do this.

what about at a lower level? are there things we can do there? yes, of course.

a substantial building of tension can be thought of as many smaller cycles. the smaller cycle raises tension, then releases *some* of it. i might encourage the team for this very reason to adopt the many so-called “continuous” aspects of the agile technical set.

microtests take minutes to write and pass. when they go green, they release a little tension, but not all of it: the story isn’t done yet. refactoring green to green is a kind of globally neutral process. it builds & releases. it’s very soothing for most people, and though it produces no new feature in the instant, it actually makes the production of new features easier. a good normalcy to have!

every actual release to the field is certainly a release of tension also. could we release to the field far more often? every commit to head — your geeks know what this means even if you don’t — is similar in effect.

you can think of it this way: experiencing tension & release & maximizing their effect is a skill. skills need practice. *all* of the step-wise work your team does gives them that practice. some of it, because it’s only partial, also builds towards the climax.

one more piece of advice before i pause for release.

looking away from the problem is a form of release AND a form of tensioning at the very same time. when i hit a local climax: back to green let’s say, and i take a walk around the block, or add a move to the team game, or whatever, i am releasing local tension. but only *local*. my mind is usually still chugging away on the next larger tension i’m in.

it’s important not to confuse urgency with busy-ness. the amount of time i spend staring at a screen is decidedly not a valid measure. neither is the number of hours i’m in the building. neither is the frequency with which i scowl and look very serious. (in my admittedly special case, just the opposite, actually.)

help your team develop its own rhythms. help them create refractory periods: stretches of normalcy. help them ramp tension by stepping, and intermix partial-release stepping like pushing code with neutral stepping like refactoring. if you’re asking me about urgency, you’re dug into a deep hole. it will take you time — and rhythm — to dig out of it.

just as you need to give your team normalcy, refraction, ramping, you need to do the same for yourself. investigate rhythm by looking around you and noticing all the cycles in the daily life of your individuals. watch how they respond as individuals to each kind of cycle. strengthen the reactions you like. share them with other teammates.

rhythm is to some extent the most *technical* of the forces we’ve talked about in rhythm. this will require some thought and delicacy. urgency is fundamentally about tension and release, and any investment you make in rhythm will pay off mightily in team energy. have at it!

Leave a Reply

Your email address will not be published. Required fields are marked *