As software practitioners we must move beyond a willful ignorance of the potential for failure in our architectures to a humble acceptance of our responsibility to not only monitor, but also mitigate that potential. To do this, we must understand the inherent risk of the systems we build. Only then can we decide how to become resilient, become vigilant, and adapt. This talk address the first step towards owning our potential for failure - which is identifying it. It does so by describing a way to model complex systems and then how to facilitate just in time discussions around architectural changes that could introduce new modes of failure. In order to demonstrate these practices, examples from various systems ranging from embedded consumer electronics to large stream processing pipelines will be used.