Often as architects we have the tendency to over complicate solutions as the first solution often either sounds far too simple or it looks wrong. A typical example is the Clustering, the tendency to erroneously consider the inevitable “streaks” or “clusters” arising in small samples from random distributions to be non-random. Using this illusion you can easily manipulate any multiple choice test by just putting all correct answers as ‘e’ or as the fifth answer. People that would usually score perfect will not accept the result as it just looks wrong. The same is true if a random PIN number turns at 1234, instead we prefer 9317.
The same applies to architecture where we often ignore simple solutions, such as when we are asking a customer on customer service. Usually a simple yes and no gives a much better real score as if you ask detailed questions as the detailed questions make people think how they should respond instead of getting an easy quick, and natural response. I have also often seen a similar behaviour in software, enterprise and solution architecture where solutions were rejected as they seemed too simple. Five years ago I actually had a co worker in a project who said that my architecture could have been done by his 14 year old daughter. The funny think was that I was pleased as I thought it to be a compliment of reducing complex requirements into a simple solution, while he meant as an insult.