Chief Architect...huh?

So about a year back I took up a job where my title is 'Chief Architect'. The job is with a financial services company. So you ask - what does a Chief Architect do at a Financial Services company? Good question - I wondered about it too. My job profile as explained by my hiring manager was to provide architectural governance, help with technology roadmaps, mentor junior folks and provide expertise on key projects. So that doesn't sound too outrageous. However, after about a year in the job, I still wonder if the title of 'Chief' Architect is a bit misplaced. To me, the Chief Architect would be a suitable title for someone who was the mastermind behind the flagship product of a product company. A more suitable title could be that of 'Enterprise Architect'..I guess.
So after a few stints at small companies, I am now at this 'big' company with close to 50,000 employees overall. My division alone has close to 1000 employees within IT. Its startling how the politics plays out as such large companies. Everyone is more worried about protecting their turf, making sure that the respective 'asses' are covered and that the individual bosses are happy. There aren't many who are thinking about the overall good of the organization. And I don't for a second pretend that this is a problem with my workplace. Its the same story I hear about most large companies. So must be something to do with our human nature. However, I truly believe that I am here to make a difference...to be a team member and contribute towards creating value for the company.
The economy and especially the financial services industry is going through some tough times right now. Recently I attended a meeting where there were questions raised regarding the need for having a separate architecture representation. My translation - time to look for another job!
Architecture to me is truly about the strategic vision, a plan, a roadmap for aligning the IT systems with the business strategy. In times like these, most companies look at architecture as an overhead. Which is kinda sad. In fact, in such times is when companies should challenge the architecture team to find efficiencies, reuse leverage etc. Some companies decide to make strategic investments during lean times to position their organizations for taking the lead when the economy does turn around.
So regardless of what happens with me, its been a very interesting experience to work as a Chief Architect of a sizeable company. Have learned a lot in the process and hopefully contributed a lot to the job too. At some point, I will definitely share my experiences here for others.
Boy, each time I decide to keep the blog short, it never happens as the thoughts and ideas pour out. But I think its more important to chronicle the true feelings than to artificially truncate thoughts to keep things precise.
Adios for now!