If we are a product or application architect, this may mean we still write code. But the architect does not have to write just any code to show that he or she is still getting exposure to the technology and staying current with the moving frontier of "hard problems" that must be solved to make this system fly.

 An architect inspires, mentors, and encourages colleagues to apply intelligently customized industry’s best practices. Educating the recipients and participants of system architecture is essential to successfully selling the chosen architectural path. Specifically the stakeholders must be able to understand, evaluate, and reason about software architecture. If an architect is the only one who can read and understand documented system architecture, then he has failed to integrate his best practices into the organizational culture. 

 In order to be effective, an architect must be familiar with the business domain at hand so that solutions crafted are practical and less academic. At the same time an architect must stay in touch with the rapid evolution of the field as the discipline grows towards becoming a true engineering discipline. New methodologies, practices, and vendor tools are re-defining, again and again, the responsibilities and duties of an architect. Proactive participation and involvement in the software architecture community in is a duty of every architect.

Overall, a TRUE ARCHITECT who always visualizes the complete blue print of systems and draft into presentable documents for non-technical viewers.