One of the lessons in life is that shit happens, and this is why you have to design for failure as Tom Graves talks about.

To be able to make the right choices for IT-platforms, we need to know future business volumes.

If you want to write a piece of software, you need to make a design effort before writing the code. But if you have a complex situation, you need to do a bit of architecture work before the detailed design and we always start with why.