Someone asks, “What do you do for a living?”
You respond, “I’m an architect.”
They reply, “Really, what buildings have you built?”
You reply, “I’m in IT. We build systems.”
They respond, either “Oh, my brother in law fixes computers too!” or “Oh, my friend is a computer programmer.”
I have had many of these types of conversations. Of course, I look at them as a learning situation, a chance to teach someone the finer points of IT and to introduce some of those concepts. But, in the end, they mostly still don’t get it.
They really need to have a dozen years of war wounds, they need to get their hands involved and develop a thick gnarly skin, grizzled by years of scratching and scrapping to get things done. This level of understanding is best learned by participation.
To know the intricacies of this field, one must be driven to understand how things work and why things break. Why can’t we segment our customers this way or that way? We have the data! Why are we not able to align hard project costs, labor, revenue and customer attributes to get a 360 degree view of our business – our competitors do? It’s not until you are faced with these big challenges that you pick up your weapons and go to battle.
Well, I could go one with these stories, but my real point is that even dealing with IT managers that have 10 or 20+ years of experience, they often times still don’t get it. In this blog, I’ll introduce the role of the architect, or better said, to lay the foundation for some other blogs by outlining the architecture role.
Here is an outline of architecture. Please feel free to remind me if I am missing any, as I am writing this on the bus on my way to work.
Architects
• Solutions Architect (Business Solutions Architect)
• Data Architect (Integration Architect, Data Warehouse Architect)
• Information Architect (Reporting Architect, Metadata Architect)
• Infrastructure Architect (Technology Architect, Systems Architect)
• Applications Architect (Software Architect)
• Strategic Architect (Enterprise Data Architect, Chief Architect, Business Architect)
Next post “What is an architecture?”
Near future posts will contain the role, value or services provided by each architect. Stay tuned and hopefully we can have some great discussions!
Happy Building!
~ Scott Felten
Filed under: Architecture | Tagged: Value, Scott Felten, Architect, Applications, Applications Architect, Business Solutions Architect, Cincinnati, Computer, Consulting, Data, Data Architect, Data Warehousing, Information Architect, Information Technology, Infrastructure Architect, Software
