Part 3 of our build-in-the-open series. The last two teammates came to find you: one when something broke, one before a meeting. This one waits to be asked, and answers with the reasoning nobody could remember.
"Why is the client's staging environment in their cloud and not ours?"
The question showed up in a Slack thread on a Tuesday, from someone who had joined after the decision was made. Reasonable thing to ask. It was an unusual setup, and I was the one who had built it that way. I knew there had been a good reason. I could not, staring at the message, produce it. The person who had been on the call with me when we decided had left the company months before.
So I did what you do. I went looking. A channel I half-remembered, a thread that turned out to be the wrong thread, a doc that stopped just short of the part I needed. Twenty minutes later I found it, buried in a message from the spring: a compliance requirement. The client's data had to stay inside their own subscription. Obvious once I saw it. Completely gone until I went and dug it up.
That is the post. Not the twenty minutes, which I will happily never spend again. The thing underneath it: the decision survived, but the reason for it did not. And a reason you cannot reconstruct is a decision you are doomed to relitigate, usually at the worst possible moment, usually with the one person who remembered already gone.
Where the "why" goes to die
There is a good line I ran into while writing this. When a team asks "why did we decide this?" and nobody can answer, it is not because the decision was bad. It is that the context that made it sensible has evaporated. It is not a documentation problem so much as a context-preservation problem.
That rings true to how it actually fails. The what of a decision tends to leave a trace. Staging is in their cloud, you can see that, it is a fact about the world. The why is softer. It lived in a conversation, in the half-hour of back-and-forth where someone raised compliance and someone else said fine, their tenant then, and everyone moved on. Nobody wrote "we decided their cloud because data residency" on a board anywhere. The reasoning was load-bearing and completely undocumented, and it walked out the door with a person.
