The fact that it is wrong (or rather, incomplete)
It should be "make it work with a clear path to scaling, then make it scale" - that's true with respect to both software engineering and business plans.
It's the same with "premature optimization is [the|a root of [all]] evil" - Premature optimization is a waste of time and often paints you into a corner. However, if you don't think about the bottlenecks and how to optimize them in advance, you more often than not find later, when profiling, that there are not enough hotspots, and the performance is "lost" all over the place.
And I remember an earlier project that had to be completely rewritten in the early '90s because at the time, Oracle couldn't yet scale even throwing money at it (and DB2 reportedly could - but the required Mainframe was not an option).
Simple is often best, yes. But not oblivious-to-the-future simple.
And, honestly, sometimes you've done variants of the same problem enough that you know where some of the bottlenecks are inevitably going to be - so why not design them out right at the start?
This. What happened to "make it work then make it scale" ?