Design: Business Design Induction/Deduction


This is my latest incarnation of the Business Design Process.  Induction (Brainstorming–generation of ideas) is Counter-Clockwise.  Deduction (Refinement–elimination of ideas) is Clockwise.

Below is the Intelligence Architecture:


Here is the Media Architecture:


This is the Data Architecture for this model.  Note that all values are accepted even if they are wrong:


Below is the Network Architecture of this model.  Note that the values are unique (nodes) and they are sequential (edges):


Here is the Text Architecture:


Here is the Numeric Architecture:


Here is the Octonion Architecture:




I am slowly creating another blog I call “WordWine”.  This blog will contain the text of speeches by great historical figures.  I feel this is important because we are too reliant on single sentence quotations instead of the complete thoughts of the men and woman who led in this world.  I invite you to visit the WordWine blog and partake of the words of greatness.

Link: WordWine Blog

Posted in Uncategorized. Tags: , , , , , . 2 Comments »

Six Unities Analysis: SuiteTwo

I have recently been exposed to a new Intel intranet appliance product called SuiteTwo. SuiteTwo is an integration of MoveableType, SocialText, NewsGator, SimpleFeed, VisiblePath and SpikeSource for the enterprise to take advantage of Blogs, Wikis, Social Networking, RSS feeds, RSS aggregation and Open Source internally. Apparently, eager clients are offering plenty of ideas to even further enhance SuiteTwo and its integrated products, but let’s take a moment to analyze what an ideal tool would ultimately do from the ground up from the perspective of the Six Unities.

Note: the Six Unities are resource groups and resources are both internal and external to the enterprise.

Location – Contact Resources

Locations for each of the entities for each of the unities would be available. I would be able to track the location of staff and inventory according to internal and external coordinates be it geographic, facility, postal, telecom, internet or any other. These are all the enterprise’s touch points. Where are we receiving and transmitting to/from the enterprise? REPOSE. Where the resource contacts.

Trigger – Event Resources

Activations for each of the entities for each of the unities would be available. Ultimately, all events are reactive–dependent on internal or external entities. REFLEX. When the resource contacts.

Data – Product Resources

Inventories of all entities for each of the unities. I would know the quality and quantity of any fixed, virtual and liquid assets of the company according to internal and/or external metrics internally and externally. Data is a repository of all enterprise resources allowing check in and check out. RECORD. What the resource contacts.

Information – Service Resources

Functions performed by all the entities for each of the unities. Whether digital, mechanical or manual all the processes would be documented in human readable form. The work and play done and being done within the enterprise and externally. REPORT. How the resource contacts.

Knowledge – Human Resources

Social Network for all entities for all unities. In every case someone is responsible for every entity internally and externally. Who are we, who do we report to, who do we share with internally and externally? RELATE. Who the resource contacts.

Wisdom – Policy Resources

Meaning and mantra for every entity for every unity. It is important to know the motive of everyone and everything both internally and externally that involves the system in order to know whether they will abide by the greater goal of the enterprise. Why are we united according to internal and external rules? REVISE. Why the resource contacts.

Take a look at the products SuiteTwo integrates and ask yourself if they answer the needs of the six unities. In my opinion SocialText’s Wiki is bearing the brunt of the requirements, but does it stand up? I don’t think it does, because it does not correctly incorporate location, event and inventory.






Goodbye Breakfast Flock

Richard Bach’s story Jonathan Livingston Seagull is a very insightful work about innovators and innovation.  I’m not going to give a lengthy review of it except that I recommend reading it.  Leave the breakfast flock and learn how to truly fly.

Systema: The Six Hats, Six Coats Hypercube

Later in this post we will discuss this man:


The following table represents my interepretation of the Zachman Framework:


I have taken this framework and applied the following de Bono metaphor:


I also incorporated my own metaphor to differentiate the axes:


These two modifications produced the following table:


This is where I had an “aha” moment. I asked myself what the entities would be:


I also recognized that in each column these entities were related hierarchically allowing the creation of a six dimensional hypercube. In creating the hypercube it was possible to look at a variety of “slices”. For example:


The table above combines Motive with Person. We can see that Motive is verbal while Person is a noun.

Next we will combine Function and Data to create another slice:


Again, Function is a verb and Data is a noun.

Let’s look at one final slice:


Here we see that nodes and time have many possible states.

But, why am I doing this exhaustive analysis of the possible combinations in the Six Hats, Six Coats hypercube?

Let’s go back in time for a moment and look at this table:


When Dmitri Mendeleev created this table to describe periodic behaviour of the elements, many of the elements had not been discovered. However, the table projected what the properties of those elements would be making the search much easier.

The Six Hats, Six Coats hypercube is also a form of periodic table. Its entire collection of possible cells are called the framework space. Many of the cells in the hypercube do not yet exist, however their properties can be predicted. This makes their search and discovery of system components systematic instead of random or organic.

Related Posts:

Systema: Seven Hats, Seven Links

Systema: CI-DIKW Hierarchy Definitions

I have been wanting to clearly define each of the terms Data, Information, Knowledge and Wisdom for some time. I have thought about Artificial Intelligence, Knowledge Bases, Knowledge Management, Data Management and other disciplines and have decided on the following simple definitions:

  1. Wisdom is the ability to model entities in a system. This is extrapolative.
  2. Knowledge is the ability to model relationships in a system. This is interpolative.
  3. Information is the ability to model attributes in a system. This is intrapolative.
  4. Data is the ability to model constraints in a system. This is extrapolitive.
  5. Intuition is the ability to model definitions in a system. This is interpolitive.
  6. Communication is the ability to model manipulations to and from a system. This is intrapolitive.

I have been forced to come up with the root “polite” to describe a single input value as opposed to “polar” which is a collection of input values. But what I want to point out is there is no automated tool capable of creating new models of communication, intuition, data, information, knowledge or wisdom, as simply defined as this is, that can be regarded as “intelligent.”
The above six perspectives affect the following focuses or modeling languages:

  1. Motivation Modeling
  2. Network Modeling
  3. Data Modeling
  4. Process Modeling
  5. Person Modeling
  6. Time Modeling

The perspectives CIDIKW and focuses MNDPPT make a thirty-six cell framework I call the Six Hats, Six Coats Framework. What I am pointing out here is that no system is simply one dimensional. Human systems are six dimensional at least. There is also a meta-layer, the model, and a data-layer, the database, for each dimension. The modeling systems and databases for all the dimensions are still very primitive and incompatible. Slowly, we are getting there, but there is more than enough work out there for anyone who wants to come up with a consistent modeling language. And if you do, you will have the foundation for a true AI.

Systema: Exteroception and Interoception


I was reading an article in Scientific American MIND this evening which discussed the research of Hugo Critchley on emotional intelligence and interoception. Interoception which is narrowly defined as the perception of stimuli inside the body. Interoception activates the brain’s right insular cortex and has lead Critchley to a broader definition of interoception. The reason being that not only perception of internal stimuli, but of emotion results in intense activity in the insular cortex. It has also been found that another center in the brain associated with ideas, motives and values often shows activity in conjunction with insular cortical activity. The right insular cortex appears to be the location where mind and body meet. Neurologically, you perceive hunger in the same way you perceive anger. You have a physical location for intuition, that “gut feeling”.

So, why do I bring this up? The main reason is I am thinking about Maslow’s hierarchy and the DIKW hierarchy. I have been struggling to substantiate a hexad as opposed to a tetrad for the number of layers of input and output and I think this provides another cornerstone for my argument. Interoception, the perception of stimuli inside the body, and exteroception, the perception of stimuli outside the body, fill the gap beneath data and divide Maslow’s physiological needs. I am proposing the following hexad:

  1. Green Hat: Wisdom. Self-Actualization. Conceptualization.
  2. Yellow Hat: Knowledge. Esteem. Contextualization.
  3. White Hat: Information. Belonging. Logicalization.
  4. Black Hat: Data. Safety. Physicalization.
  5. Red Hat: Intuition. Physiological. Humanization. Interoception.
  6. Blue Hat: Communication. Existential. Detection and Effection. Exteroception.

In my future discussions I am not going to talk about the movement of data or information or knowledge or stimuli. I am simply going to refer to input and output. Input ascends the hierarchy and output descends the hierarchy. From which level it originates is also irrelevant if it is ascending it is always input, if it is descending it is always output. The transformations are discrete. They are not increases or decreases in detail, but changes in perspective.

If you are following this lengthy thread you may notice my terms changing a bit each time. It is an iterative refinement of my understanding that is leading to these changes. Hopefully, I get closer to a final version with each change.