Leading Technical Change is a small, live, remote seminar aimed squarely at a single topic: Real Change in the Real World. A new cohort is open now: March 11,12,14, & 15, 10am to noon Eastern (UTC-5). There are just six seats available, so we can drill down on the actual situations in which you’re seeking […]
Optimize for Our Humans Read More »
Today I want to answer a question that, honestly, almost no one ever asks. Why are we changing frames, instead of getting rid of them altogether? Talking about change in the geek trades is a joy for me, but I’m even more interested in seeing change out in the world. Please think outside the monitor.
Why Only Change Frames? Read More »
We started with the concept of the mental frame, a comparatively rigid & invisible construct which structures and guides nearly all our behaviors. Today, let’s take up the triad of powerful forces that we can use to change frames: community, narrative, and experience. https://www.geepawhill.org/2023/01/20/changing-the-frame/ As ever with me, though considering change in the geek trades
The Frame-Changing Triad Read More »
For nearly everyone who seeks to facilitate change, the first faltering step is usually in the crafting of a persuasive argument.
Changing The Frame Read More »
Here’s another technique card from my seminar, “Leading Technical Change”. We first get into midwifing change precisely because we want it to be smoother, easier, and faster. But sometimes, a coach needs not to rush a decision through, but to slow it down. It’s so exciting when our proposed change starts to catch fire, especially
Slowing Decisions Down Read More »
If we’re going to enable and support change, we’re going to fail, more often than we succeed, and we want to bake that idea in, early on, lest we fail both more often, and potentially more disastrously. Here’s some thoughts around this NOT DEPRESSING topic. 🙂 The weirdest thing about all this: it’s actually rather
What About Failure? Read More »
Can we be honest? If we’re going to be successful change midwives, honesty is very important. In this technique card from Leading Technical Change, I talk about some of the ins & outs of this complicated topic. The first point is urgent: Being honest means believing everything you say, not saying everything you believe. Honesty
I was gratified by the response to my first "detail" article. But I did note that many persons praised my article for its commitment to the long game. Framing the commitment, for a geek, to detail, as a long game, seems right, sounds right, cuz after all, we only ever care about quality in the
Detail: Not The Long Game Read More »
The people who hire me ask me to help their teams make changes. Most of the time, my first step is to see how I can slash those teams’ load. Here’s a technique card from my seminar, “Leading Technical Change” Raw text of a technique card: Wait, what? First thing I do To me, this
Detail: The thing that strikes me over and over again, in my own work style, in my Friday group’s analytics, in Ron’s long-running Kotlin and short-running Gilded Rose series, is how much attention high-skill geeks pay to some of the smallest details in the code. An example. I was doing Gilded Rose the other day,
Detail: Series Intro Read More »
