Images thanks to DALL-E
5 minute read. Don’t feel like reading it? You can listen here:
A builder’s guide to “Yellow Teaming” any product
The current political environment has made me think a lot about how to create better products to meet the needs of the digital world. I strongly favor open source and decentralized protocols, as they are what make the internet work so well and continue to do so.
However, the majority of all our digital experiences are by builders who create on top of these protocols, and it is these builders who must ensure that we are creating for better human outcomes. So, how can we do this?
The architect, Christopher Alexander, developed a field of work focused on understanding what makes something feel living (a product that produces a whole and coherent human-centric outcome) or static (that which creates fragmented human outcomes).
I often contemplate this concept.
It’s interesting to think about how the systems and products we create, even with the best intentions, can lead to these fragmented outcomes. More and more of the products we build in the digital and physical world contribute to fragmentation, rather than fostering a whole and cohesive lived experience.
If you are unfamiliar with Christopher’s work, I recommend starting with his book “A Pattern Language” and then reading “The Nature of Order”.
The main objective of Christopher’s work, as he would explain, was to incorporate this thinking (which is actually methodical, structured, and mathematical, despite sounding esoteric) into the building process. Based on this idea, I thought it might be practical to consider it in line with a concept I heard Daniel Schmachtenberger speak about, called “Yellow Teaming”.
Yellow Teaming is a critical process that complements Red and Blue Teaming approaches. In product building, Blue Teaming usually focuses on how to ensure the success of a project or initiative. Red Teaming analyzes how a project could fail and identifies potential vulnerabilities.
In contrast, Daniel proposes that “Yellow Teaming” examines the potential negative consequences or externalities should the project succeed, especially if it’s really successful.
At its core, these three processes involve asking critical questions about your product to enhance its potential success outcomes. What sets Yellow Teaming apart is that it assumes the product will achieve absolute success and then asks; “What happens next? What impact will this success have?”
Performing Yellow Teaming without a basic moral framework is somewhat pointless. Therefore, I propose Christopher Alexander’s concept of a cohesive and human-centric outcome versus fragmented human outcomes as a base moral framework.
If my product is a huge success, does this foster a more cohesive lived experience or does it foster fragmentation?
To test this thinking, I propose five questions below that any product team, regardless of whether they are building with atoms or bits, can use to Yellow Team their project.
- How might this product fundamentally reshape human behavior, relationships, and societal structures over the next few decades? What cascading effects could this have on cultural norms, economic systems, and the environment?
- How might the widespread adoption of this product influence seemingly unrelated industries, power dynamics, and resource distribution, and what might be the long-term impacts on the resilience of communities and ecosystems?
- What potential unintended uses or consequences could arise from this product, and how might they affect human well-being, decision-making processes, and the ability of future generations to meet their needs and pursue fulfilling lives?
- How does this product interact with and depend on existing resources and systems, locally and global, and what responsibility do you, as a product builder, have to guide its development and use for the benefit of humanity and the planet?
- Considering the cumulative impact of this product’s success, how might it shape human cognition, values, and our relationship with technology and nature over time, and what are the implications for the future adaptability and sustainability of our species and the world we inhabit?
Obviously, you can come up with your own questions.
Even just asking.. what happens if this works? is a good start!
The point of this process is not to create a morally perfect product or never release something that can cause externalities. That’s impossible, since we don’t know what, we don’t know. It also isn’t about imposing a moral tax on builders.
The point is to allocate time as part of your building process to genuinely consider the human and ecological impact. We can build truly remarkable things while also caring about the betterment of the human experience.



