I am aware that it is common practice for a guy with a title architect be the "smoke and mirrors" guy during the sales phase. I am referring to so called architects who have the role of leading a group of programmer during the building of software. Unfortunately many times their understanding of software does not go beyond the Visio and Powerpoints but it is falsely assumed they can still lead due to pointy-hair-boss soft skills. What ends up happening is crapware due to a lack of understanding of fundamental software design and process.

Unfortunately he's also the guy that tells the customer "yes we'll do it in Blub!".