Picturing the complexity

First let's have a proper language for efficient communication

Then let's prevent fallacies based on simplistic determinist solutions

Also let's sometimes? consider? as teams that innovative approaches may prevent useless overw


Let's apply it to yourself

Looking at you complex system, organisation or product, you may have partial views and viewpoints on it, with as consequence some bias on the way you perceive it.

But also let's consider that, when organisations or product according to an organization, you are part of those organizations, with specific and contextualized roles, and that the people you are collaborating with may have different roles, constraints and objectives. They can also have a different background in terms of knowedge, experiences or abilities.

So neither enterprises nor products are elephants!

Here you need to adopt an holistic view and consider the various viewpoints, backgrounds and abilities of the other stakeholders.

  • It is where enteprise architectural descriptions are very helpfull.
  • It is where you will have to consider mapping of several languages and various viewpoints to be consider, which are attached to stakeholders, purposes and concerns.

In a digital age and computer aider world, it's not only about communication between people in organizations, but also the applications supporting them and the technologies realizing the applications.

  • ?Machines are stupid, formal languages are needed!
  • Those languages can be textual, they can also be visual?

Next

Here is a collection of visual representations of what is to be adressed next.

Holarchy


















要查看或添加评论,请登录

社区洞察

其他会员也浏览了