The tech industry needs to shift from focusing on individual knowledge stock to fostering knowledge flow to make better decisions amidst change. This involves understanding the differences between data, information, knowledge, understanding, and wisdom, and recognizing the importance of developing knowledge systems as a core architectural practice.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
Architecture, in the systems age, is not (just) Kubernetes. It is is designing relationships between parts (people and tech parts) then adapting those relationship patterns as circumstances change.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
Architecture, in the systems age, is not (just) Kubernetes. It is is designing relationships between parts (people and tech parts) then adapting those relationship patterns as circumstances change.