“Why is the banana crooked?” That’s a good question that comes up again and again. We want to avoid such ambiguities, recurring questions and assumptions in software projects at all costs. When we make a decision, we want it to be easy to understand later on. But how do we do that? How can we record decisions and what do we need to bear in mind?