When Software Architecture & Design Become The Problem

If a solution to a problem is so complex that it requires an architecture, a conceptual design of how a system will be implemented, to solve the problem, and if that document starts to take on the scope and size of War and Peace, it is very likely that the problem has now become the architectural design, rather than implementing a solution to the original problem as described. This happens as a result of the scope of the problem being tackled being too large. Rather than trying to come up with complex and  lengthy models of what the overall solution to the problem could be, instead, break the problem down into smaller, shippable problems, that can be described on one page, and then implement, deploy and validate those solutions. It is very likely that you will learn as you go and the end solution will be very different than what you had previously described in your initial architecture.