> However, I make sure that after the call we write down some notes what decision we made, and why we decided the way we did. This makes sure that parties not p

> However, I make sure that after the call we write down some notes what decision we made, and why we decided the way we did. This makes sure that parties not present at the meeting (i.e. other developers, and our future selves) can pick up the context quickly and save us the pain of working through the decision process again. In the same way that you should comment your code with the "why" and not just the "what" you also should comment your non-code decisions with the "why" and not just the "what". Otherwise someone in the future will try to overhaul a process without knowing about some of the previous pitfalls that were discovered.