Consider a principle as a basic generalization that is accepted as true and that can be used as a basis for reasoning or conduct.
I believe there are basic generalizations accepted by all leading CTOs and therefore these CTO principles can be studied and learned. I have my own list that I’ve applied at several organizations and will expand on them in future posts. But my real point here is to underscore that by study of the principles of CTOs we can look for deeper insights into our profession.
For my enterprise, the principles I’ve always used are:
- Our systems and architectures will always be mission focused
- Our enterprise must be flexible and adaptable
- Our technical team will constantly upgrade their skills and knowledge
- Our technology plan will be broadly communicated/understood
- We unify enterprise architecture, governance and engineering efforts
- We embrace the ideal of a single enterprise-wide SOA
- We embrace and embody the concept of “mission assurance”
- We will divest ourselves of efforts which do not support the mission
- We err to the simple over complex
- Disciplined collaboration is critical to our success
I’ll expand on each of those over time.
About BobGourley