While at Northeast Dreamin’ in Boston last week, the keynote speaker, Steve Baines, spoke about being a Salesforce architect.
One of his points was, “if you’re building trust and clarity – you’re an architect”.
The overall theme is, being an architect is more of a mindset than an official title. And here are things architects do:
- Define
- Envision
- Defend
- Counsel
- Align
- Evangelise
- Facilitate
- Inspire
- Guess
- Extract
If you perform all of the above, then you’re basically an architect, regardless whether you call yourself one or not.
While I generally agree with these ideas, I feel this dilutes the definition of an architect. This reminds me of the term “engineer” in the early 2000’s. Back then, everyone was an engineer, even a sanitation engineer 🙂
Sadly, Steve had to catch a plane before I was able to argue my points.
The takeaway
What do you think? Are these tasks sufficient to call yourself an architect?
Hit reply and let me know what you think!