The fact is that the architectural mindset is a very distinct and recognizable mentality and most certainly not the byproduct of a "process".
I suggest one first try their hand at defining what is "architecture" and if one has trouble with that, suggestion is to not venture to the subsequent topic of "what is an architect and how does one recognize this rare [1] animal?"
[1]: it is definitively a talent and a rare one at that.
I've long had the notion that taste is secretly the most important quality of a good developer or worker in computing technology more generally, and we only pretend other things matter so much because taste is hard to measure in an interview, difficult to quantify, and no-one knows how to teach it reliably.
Taste works well when you are in a position to receive a large amount of work that can be organised in a hierarchy according to the work's quality. We will need a lot of that in a few years.
Working up from first principles, staying on time to produce a large quantity of stuff and discovering new facts are valuable methods too. You can't get to useful work from tasting without an ocean of work to receive.
I suggest one first try their hand at defining what is "architecture" and if one has trouble with that, suggestion is to not venture to the subsequent topic of "what is an architect and how does one recognize this rare [1] animal?"
[1]: it is definitively a talent and a rare one at that.