· Diana Montalion · Events  · 1 min read

Architecture is Designing Knowledge Flow -- Explore DDD

Event Date: Apr 16, 2025

In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.

In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.

In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidates stock of knowledge. 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. The ability to craft and share knowledge in ways that enable the best possible decisions, under the circumstances, in the midst of change. In this talk, we’ll explore:

  • The difference between information, knowledge, understanding and wisdom. In that group … what is data?
  • How “management” differs from systems leadership
  • The emerging practice of developing knowledge systems as a core architectural practice.

As Larry Prusak says, “Companies that don’t adapt to understanding knowledge as a force of production … will slowly die, and will never know what killed them.” The same is true for technology teams … we are knowledge workers designing knowledge flows. How does this change our approaches?

Join in!

Source: https://exploreddd.com/

Posted in: Wednesday Schedule(keynote)

Share:
Back to Blog

Related Posts

View All Posts »
Mindshifts: Thriving in the Systems Age -- OOP

Mindshifts: Thriving in the Systems Age -- OOP

Event Date: Feb 3, 2025 - Feb 7, 2025

In my lifetime, we have experienced the equivalent of 20,000 years of change. Nonlinear change. In many respects, we are the architects of change, yet we seem to do the same things again and again, expecting different results.

Architecture isn't Kubernetes -- JaxNY

Architecture isn't Kubernetes -- JaxNY

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.

Architecture isn't Kubernetes -- wJaxDE

Architecture isn't Kubernetes -- wJaxDE

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.