I would argue there is another important benefit than the takeaway suggested in the second sentence of [1], that is the attention to architecture choices that allow for simple or complex (costly) refactoring later can engender more forward-looking awareness in the team's culture.

[1] "One approach I use when mentoring developers in this situation is to ask them to imagine the refactoring they would have to do later to introduce the capability when it's needed. Often that thought experiment is enough to convince them that it won't be significantly more expensive to add it later."