Skip to main content

Master the Meta


About 6 years ago I wrote a blog post titled Mastering Multiple Mountains where I spoke about the interesting dynamic of interaction that happens between people with different levels of understanding of any given concept.

The difficulties of engaging an exchange of knowledge between these different levels of understanding are what make the art of diplomacy and consensus building an art. The need to constantly gauge the state of knowledge of the others participating in the conversation is required and is made more efficient the more any given conversant has multiple mastery of different areas of potential conversational exploration.

A corollary to this skill that I've been considering is highlighted by the advantage to communication enabled by those who master multiple mountains of knowledge and that is being able to consider a meta analysis of a given discussion. Meta analysis is slightly different from simply gaining knowledge across different areas and being able to then illuminate relative ignorance between oneself and others in discussion as was the scope of the earlier article. Meta analysis also involves being able to shift perspective from ones own state of knowledge to that of the other and then to restrict the 'view' to consider the reasons why the other may be taking a line of argumentation. It is related but tangent to that earlier article.

In all types of engagement being able to master the meta is a powerful tool in exposing where one may be led to ruin by the very veracity of the data that they hold as basis for their expressed knowledge even if that data and knowledge has veracity behind it, failing to engage in this shifting of perspective via meta analysis could lead to ruin.

For example being oblivious to the social mores that may be in place when discussing subject matter in public in certain cultures could lead to perceptions of great offense which in some places could make one subject to violent response without even realizing it.

Science fiction has often used this potential schism in social norms as fodder for story lines from Star Trek on but it is a critical failing of making assumptions about the perspectives and expectations of others irrespective of the state of knowledge that may be had by different participants in a conversation. So in attempts to relay information it is important to both recognize the differential knowledge sets that we have compared to those we are communicating with and also be able to inhabit those knowledge sets in order to guide our approach to building consensus...sort of a rudder in the water to the angling of a wind born mast on the boat of our path through the sea of ignorance toward a common island of truth.

Comments

Moulton said…
The more analogies, metaphors, parables, and abstract models one can marshal, the richer is one's insight into an instance of a recurring thematic model.
December 2, 2014 at 9:03 AM
Post a Comment

Popular posts from this blog

the attributes of web 3.0...

As the US economy continues to suffer the doldrums of stagnant investment in many industries, belt tightening budgets in many of the largest cities and continuous rounds of lay offs at some of the oldest of corporations, it is little comfort to those suffering through economic problems that what is happening now, has happened before. True, the severity of the downturn might have been different but the common factors of people and businesses being forced to do more with less is the theme of the times. Like environmental shocks to an ecosystem, stresses to the economic system lead to people hunkering down to last the storm, but it is instructive to realize that during the storm, all that idle time in the shelter affords people the ability to solve previous or existing problems. Likewise, economic downturns enable enterprising individuals and corporations the ability to make bold decisions with regard to marketing , sales or product focus that can lead to incredible gains as the economic ...
1 comment
Read more

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way. The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created. Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write. Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is d...
7 comments
Read more

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform cert...
2 comments
Read more