September 2017

Endpointing vs. Next-Stepping

I mentioned endpointing yesterday. I’m always using geepaw-isms & expecting people to know what I mean. Endpointing is over-focus on eventual destination. In s/w, it’s seeing development as a long trip to a known destination on a known map. John Winthrop, a few centuries back, used "the city on the hill" to describe an endpoint, in his case for the puritan colony. The metaphor, of a trip to a place, is as natural as any human expression. But it contains […]

Endpointing vs. Next-Stepping See Full Post

“Avoid Changing Code” Should Be Avoided

Of all the bad advice the geek trades inherit from over-simplified manufacturing & engineering, perhaps the worst: "avoid changing code". Take a minute, and think of all the things the trade does to avoid changing code. Virtually every element of "big design up front" policy is based in this view. Long stretches for analysis, longer ones for design. Planning cycles that extend years into the future. Years. I am not exaggerating for effect. Years. Contract-like specifications, database designs that start

“Avoid Changing Code” Should Be Avoided See Full Post

Using Strategy & Function-Specific To Attack Large Classes

In IT work — "it puts the database on its browser skin" — we often face sooner or later the problem of the gigantic object. Some systems, especially "global monolith reboots", just start there. Others just grow and grow and insensibly slide into it over time. The problem is that there are one or a few objects that are just plain central to the domain. To forestall ron and his marick quote, I’ll use the classic ‘order’ as my example

Using Strategy & Function-Specific To Attack Large Classes See Full Post

Idols of the Schema: Ignoring Data While Overvaluing Ideas

The ‘idols of the schema’ is a geepaw-ism, and deserves some background & explanation. When we value the simplicity & clarity of an idea over the complexity & muddiness of its referent, we’re caught in an idol of the schema. Sir Francis Bacon was an english noble, a famous lawyer, and author of the Novum Organum, one of the seminal texts of empirical method. He wrote among many other things, of the ‘idola mentis’: idols of the mind, and offered

Idols of the Schema: Ignoring Data While Overvaluing Ideas See Full Post

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

Scroll to Top