It is very important to be able to understand what is not a requirement, because this makes it possible to greatly simplify and reduce the cost of the solution.
A few examples.
RAID on K8s notes: usually a K8s system should be built in such a way that it is easy to survive the shutdown of any of the nodes, so RAID is not needed. In theory, it will not even reduce the time for server maintenance: in theory, the time for replacing the disk is the same, and installing the node on a new server should be automated. Perhaps RAID will give the server some time to work while the person is busy or there is no spare disk, but this is also the case, in theory both points should not be critical.
When developing software, the examples are much more serious, you can save months of development, but describing the context is quite long and hardly interesting.