[2/2] Soviet Space Mythologies: Public Images, Private Memories, and the Making of a Cultural Identity (The Mythology of Soviet Space) (Category Space)

Continue. story I would like to talk about the insights that came to my mind as I read it, given my design experience and current focus on agency development and moving development engineers into a different role than before. (Astronaut pilots became more astronauts-engineers).

1Automation is not only architecture, but also governance. Once you decide when the system works on its own and when manual intervention is needed, you allocate not only functions, but also power, responsibility and blame. Glory Gerovich is one of the central axes of the book.

2️ If the public narrative diverges from operational reality, the organization loses its ability to learn. (It just doesn't close the feedback loop.). Soviet space history, in the official version, cleaned up the failures and complexity. This is good for the showcase, but bad for the real cycle of improvements. A very modern thought for any company where PR and reality diverge too much.

3Those who build the system and those who present it to the public almost always have different incentives.. Engineers in the Soviet program had more influence on design but were invisible; cosmonauts were public heroes, but often with a stripped-down ability to influence decisions. This is an almost classic example of hidden platform teams and public business product teams.

4Counter-narratives are not noise, but telemetry. When the author says that the task of the historian is not only to debunk the basic myth, but to disassemble the foundations of the myth, it is very similar to a good incident review. In general, you can not trust the only official version, you need to compare logs, interviews, documents, interests of groups and what the system prefers to keep silent.

5Memory is the basis of culture and the basis for making further decisions. What the organization celebrates, silences and repeats becomes its architectural myth in a few years. And architectural myth then influences hiring, role status, and what decisions seem "natural."

All in all, this is a great book about how a complex technological system turns into a mix of architecture, power, propaganda, and collective memory. For channel readers, it can show that system design, role allocation, crash management, and official narrative never exist separately. I would say even more that this is an example of what happens when observability is replaced by myth.

#Science #SystemDesign #Architecture #Processes #History #PopScience #Engineering #Culture #Leadership