Who needs an architect?

Since I was a little kid I always wanted to change things to work in a more efficient/easier/convenient way, as simple as organizing my toys as per usage, this idea evolved all the way to my professional career.

Currently I manage projects of commercial systems and what I've found are many learnings:

• Similarities between a project manager and a software architecture
• Get $#!T done, a PM has to ensure communication and that workflows happen, as well as an architecture according to the lecture, has to have some high convincing skills, as his recommendations have to be listened and applied
•  Experience and responsibility
• As said previously, recommendations and tips... there's nothing like experience of getting involved in projects in order to have your voice have a valid and substantial background
• Importance and scalability
• A PM as well as a SA must have under their scope how easily their project/software will be taught, learned, scaled, this is their responsibility as they must know they will have some day to do a handover of their knowledge

Therefore, both are very alike talking of their soft skills... but what happens when you combine both things in a project? Maybe I'm not a software architect or a fully developed project manager, but my increasing expertise in systems and company's business is making me an integral asset and opening every day more and more my scope.