Muses

Purpose As Motivator: The P in RAMPS

This entry is part [part not set] of 15 in the series RAMPS

Purpose is the P in RAMPS. Purpose as motivator is about the sense an individual has that she’s contributing to a greater mission shared by many. Both attributes matter: mission must be of a higher order than any individual’s whim, & it must be felt to be shared by the whole team. Purpose is really always purposes. Seen "from above", it resembles a sloppily drawn cross-section of a stem, a larger (sloppy) boundary, decomposed into smaller (sloppy) circles, some nearly […]

Purpose As Motivator: The P in RAMPS See Full Post

Rhythm as Urgency: The R in RAMPS

This entry is part 3 of 15 in the series 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

Rhythm as Urgency: The R in RAMPS See Full Post

Safety as Motivator: The S in RAMPS

This entry is part 2 of 15 in the series RAMPS

Let’s do Safety, the S in the recent RAMPS as motivational force series. Safety is hard to get at in one summary sentence, but i’ll try. Safety is the sense we have that we belong: that we’re trusted, valued-in-spite-of, inside a team that welcomes our strange unruly selves. At its simplest, this sense manifests as the belief i’m allowed, even encouraged. Allowed to be different. Allowed to be mistaken. Allowed. You can see how hard that is to summarize! It

Safety as Motivator: The S in RAMPS See Full Post

Autonomy: How Freedom Correlates To Urgency

This entry is part [part not set] of 15 in the series RAMPS

Let’s talk about the A from RAMPS today: Autonomy. Autonomy is "simple not easy," just like the rest of the motivating forces. Autonomy is the sense of an individual that she is free to work the best way she knows how to achieve the tasks in front of her. We call self-driving cars "autonomous". We do that to contrast them with cars that are controlled by humans: machines. If I say an individual doesn’t feel he has autonomy, I’m saying

Autonomy: How Freedom Correlates To Urgency See Full Post

Mastery As Motivator: The M of RAMPS

This entry is part 14 of 15 in the series RAMPS

Let’s talk a little about mastery today, in the sense of the RAMPS conversation from yesterday. What is mastery-as-motivator, and what can we do about increasing its motivational force? As I said before, the motivational force called mastery is about how humans value their own growth. All of us carry around an idea, implicit or explicit, of how as individuals we could be "better". Mastery as motivator is the sense we have that we’re stepping towards that "better" as we

Mastery As Motivator: The M of RAMPS See Full Post

A Sense Of Urgency: RAMPS As A Motivation Model

This entry is part 1 of 15 in the series RAMPS

A very common question: managers turn to me and say, "My team lacks a sense of urgency, how can I give them one?" After I get over the snarky replies — I come from a long line of "the managed" — I do have what I think is an answer: "Study the idea of RAMPS, find the missing or depleted elements, move to restore them. And friend, don’t expect you can do it using words." RAMPS is my acronym for

A Sense Of Urgency: RAMPS As A Motivation Model See Full Post

When I Need to Not Pair

So, a friend asked me to say more about "not pairing". As so often, it triggered me to muse. Sometimes I need to not pair. Now, don’t get me wrong, I love pairing. I love it for three reasons. It makes me a better geek. That is, I learn from pairing. Pairing makes two geeks more productive than if they solo’d. That is a pair writes mo’ better code than two solos. PAIRING IS AWESOMELY MORE FUN. But there are

When I Need to Not Pair See Full Post

Done With “Technical Debt”

I am done with "technical debt" as a useful concept. As so often happens, an appealing idea happened, one with useful connections to the concrete, and we took it and ran with it. Unfortunately, that idea has more appeal than it does decision-making value. Folks justify the most ridiculous nonsense and put it under the heading of "technical debt". In particular, they write shitty code, I mean terrible code. They do this in the name of productivity. The claim is

Done With “Technical Debt” See Full Post

Optimize Collaboration, Not Meetings

There’s a lot of internet out there about meetings. Sturgeon’s law applies here. There’s some good advice, tho, too. Where I come from’s different. What I see, as with so many other topics, is how hard we try to fix problems our assumptions created. There are a lot different ends to which folks want to apply meetings as means. Three common ends are the "orders meeting", the "report meeting", and the "decision meeting". In an orders meeting, we’re there so

Optimize Collaboration, Not Meetings See Full Post

On Pedagogy In The Geek Trades

I find 4 major failings in both how & what we teach in geekery. We mostly don’t. That is, actual teaching of actual geekery-for-a-living is almost non-existent. We suffer in attitude & content & structure from the trivially flawed “information transfer” view of what teaching & learning is. We purport to more knowledge than we actually have, teaching crude guesses as if they were writ, and aphorisms as if they were Euclid. We withdraw the field, abrogating our responsibility and

On Pedagogy In The Geek Trades See Full Post

Scroll to Top