Transparency means saying why, not just what

This has happened a few times lately:

1. An MR updates the handbook.
2. It says what it does, but not why.
3. People find it, worry, and start asking a lot of questions.

On the surface, this is transparent: the change was made through an MR, in public. But the reasoning for the change was not public, and so we have step 3.

In general, whether it's a process change or a code change, we should have more explanation about why than about what in an MR. This can remove a lot of follow-up questions, and make the questions that do come out of it more focused. That's more efficient. Additionally:

1. It builds empathy with the decision, and reduces anxiety from feeling disconnected from the decision.
2. The why is more important for the long term. Processes change more frequently than values, and the why is more closely related to values than the what.