Week of 2022-07-25
Where I explore this weird transformation of “becoming a setting” that most popular products and services undergo, and talk a bit about stewarding platforms. Specifically, it’s the traps that a builder might get snagged by while trying to become a gardener.
Builder and gardener mindsets
My dear friend Alex Komoroske did a podcast episode recently on all of my favorite topics. I highly recommend watching it and studying the excellent deck that the majority of the discussion rotated around. I also wanted to riff on the builder and gardener archetypes that were featured in the title of the article.
Briefly, the distinction emphasizes the difference in mindsets with which we approach unsolvable problems. As builders, we view them as ultimately solvable, and so our actions usually yield building something that solves the problem. Unfortunately, as the problem is unsolvable, the thing that we end up building is solving a problem that is different from the one in front of us. In rare cases we are lucky: the difference is small enough and we get to reap some benefits from the solutions. More often, we now have a solution that still needs to find a problem that fits it.
In my experience, the latter outcome is pervasive around ecosystem work, aka “platforms”. Since ecosystems adapt to our actions, changing them to behave in accordance with our intentions is indeed an unsolvable problem. So when a team charges forth with the idea of building a platform from scratch, my response is usually a skeptical eye roll or a wince: I detect the “builder” mindset and all that falls out of it.
The mindset Alex suggests as an alternative is that of a gardener. Just like builders, gardeners have blueprints. They have an idea of some state that they want the garden to eventually reach. The key difference is that they accept that they are working with a living matter. Living matter has a mind of its own and is likely to surprise us. The blueprints will need to be redrawn and mental models adjusted frequently. In many cases, gardeners never reach what they’ve drawn in the initial sketch. They know it and hold them lightly, and it’s the only feasible approach. Holding firmly to the original blueprints is a path to eventual madness.
For technologists, the shift from “building” to “growing” is a bit hard to perform. There are two common traps that I am familiar with. The first one is what I call “garden-builders”. Here, even after armed with the gardening metaphors and ideas, we still imagine how we’ll grow perfectly cylindrical carrots and spherical potatoes. We may talk the talk, but underneath, the builder mindset is still present. Projects run this way will have words like “ecosystems” and “platforms” and maybe even “emergent” and “complexity” plastered all over them, but the manifested outcomes reveal the story of rigid construction.
The second trap is “garden-workers”. This one plagues teams that swung way too hard into the idea of working with the living matter and abandoned the intention behind it. Garden-working is still an engineer’s escape. Assuming that gardening is just about waking up very early, weeding, watering, and tilling the dirt is comfortingly similar to the common activity of continuous refactoring that many teams in mature stages undertake. The blueprints are mostly forgotten in the soothing practices of daily work. Projects run this way will ship incoherent bags of features that even they themselves can’t cogently describe. If you hear a presenter say “we can’t wait to find out what you’ll build with these APIs” to the audience of developers, chances are the team shipping this API is stuck in the “garden-worker” trap.
If I am being brutally honest, I don’t actually know if it is possible to achieve the full zen of the gardener mindset. Based on what I’ve seen, a platform team is usually either completely unaware of this mindset or is caught undulating between the two traps. Last release: “OMG, we shipped was a bunch of random stuff, let’s organize this better!” … next release: “Crap! We shipped things that nobody needs again, let’s get back to gardening, folks!” And that might be okay. Here’s my hope. By making these traps legible, I can help you, my reader, to learn how to work with them and countervail their effects.
🔗 https://glazkov.com/2022/07/28/builder-and-gardener-mindsets/
Becoming a setting
I’ve been geeking out about this fascinating phenomenon when parts of one customer-vendor loop become a setting for others. By virtue of connecting the dots to find a functioning setting, we necessarily make this setting more accessible and legible to others. As one outcome, others can now copy our setting and create its clone. The discipline of business strategy covers this situation well, so I want to direct your attention to its alternative. When others can observe our setting, they may – and more than likely will – reuse its conveniences for their own purposes.
Take the ice cream shop example (boy, did I wear it out or what). When my shop becomes a destination for teens to hang out, it’s no longer about the ice cream. For them, it is a setting for satisfying their need to connect and belong. Teens take all of my hard work of establishing a setting and, just like that, make it their own. This might be good for me at first – more ice cream being sold! – but quickly, it turns into a nuisance. The teens loiter at my store after buying just a couple of cones and their youthful exuberance turns other patrons away.
In my experience, this “becoming a setting” is so common that it ought to be a law or something: as the Customers stock of my customer-vendor loop grows, the probability of this loop becoming a setting for others approachers 100%.
If we accept this “law”, our hypotheses for how our customers will behave must include scenarios of them setting up camp within our customer-vendor loop and appropriating parts of it in unpredictable ways. The more I embrace such scenarios and prepare for them, the more likely I will engage with them in a mutually beneficial relationship.
For a less made-up example, let’s look at Midjourney. If asked to define their product, my first response might be, “well, the AI-generated art, of course!” But that is only part of the story. As I mentioned before, their embrace of community-based creation, and the way they made the process of creation tweakable and shareable (thanks for pointing that out, Ade!) all hint at something different.
Midjourney might look like a simple AI-generated art service, but as it grew, it became a setting for artists – a place where they can co-create, remix, riff off each other, and have that sense of belonging. The prompt and variation mechanism design seems to be begging: “please take this prompt and mess some more with it!” Even if intuitively and completely by chance, Midjourney’s decision to lean into Discord had a big role in ensuring that the explosive power of creativity continued to play to their strengths – unlike the annoying high-schoolers in my ice cream example.
Similarly, Midjourney’s eagerness to hallucinate compared to similar products becomes a feature: if I am an artist looking for inspiration, I don’t want the tool to give me exactly what I am asking for. I want it to surprise me, to stir my imagination. From the perspective of technical excellence, it might be tempting for Midjourney engineers to look around and worry about “more accurate and lifelike” representation, but that is not what technical excellence means for the audience that gathered around them anymore. It turns out, “weird and unexpected” is more valuable when it is part of a creative setting.
This is the most delightful and terrifying part of becoming a setting: it is impossible to know how it works out. Even if we have our eyes open to the possibility, we must be prepared to be surprised by what happens next. In human systems, exaptation is not a rare occurrence. It’s a continuous process. And most certainly, we must not start with an idea that we somehow can control it.
One of the greatest follies of high modernism – from architects to dictators – is the belief that becoming a setting can be constructed through a mechanical waterfall process. According to this belief, if we know enough things and think hard enough, we can draw the blueprints, plan, organize, and manage resources, and given enough time, bring forth the ideal setting of our design, be that a building, or a country. It is the belief that becoming a setting is solvable problem, that people will just come and dwell in the thing we create in just the way we planned for them. And when people refuse to and the conclusion of the waterfall process is revealed to be just a first step of an ongoing dance of exaptation, a high modernist is left with the choices of having a painful, but transformative learning experience or blaming the pesky people for screwing up their plans. You can guess which one happens more often.
A thing that might be helpful is recognizing that there’s a bit of a high modernist in all of us, and knowing how it shows up in our thinking. For instance, the irritation over “pesky users screwing up our plans” is a really good marker. Not expecting exaptation is a sure sign that we’ve fallen back into the waterfall model of becoming a setting.