Since I created the Six Hats, Six Coats metaphor I have made several modifications to the language used. It has lead me to come up with what I call the Structured Thinking Language (STL). I am working on the syntax and will discuss this in later posts. The one term I want to draw attention to in this post is in the left column, the new verb “INTUIT”.

I have chosen the verb “INTUIT” first, because of Edward de Bono’s inspiring six thinking hats, second because I do not like the verb “develop”. To intuit is in part to provide the materials and know how to build the system based on the result of the REDUCE statement. The other part is consideration of the origins, physical and cultural development, biological characteristics, social customs and beliefs of the users to create affordances. The use of the term “affordance” is much broader than and includes Donald A. Norman’s usage in The Design of Everyday Things. In STL an “affordance” is synonymous to the Zachman Framework’s “focus”. A complete system is composed of motivational, spatial, formal, functional, personal and temporal affordances which are complete intuitively designed subsystems including the appropriate intuitive cues. I want to use a word that implies not only developing, but developing with the REDUCE result and the intuition of persons who interact with the system as primary considerations.

STL: Structured Thinking Language


Over the course of analyzing the Six Hats, Six Coats metaphor it has occurred to me that a structured language can be created for thinking about a system. Each of the Six Hats are actually verbs and each of the Six Coats are nouns. Together they create a minimal structured language framework for guiding the design of a system.

CREATE: Conceptualize. Expand Meaning. What are you making right?

DEFINE: Contextualize. Focus on Uniqueness. What is your mantra?

REFINE: Logicalize. Maximize Value. What is your effect?

REDUCE: Physicalize. Minimize Cost. What is your business model?

INTUIT: Humanize. Familiarize Interaction. How do you lower the barriers to adoption?

ENGAGE: Synchronize. Increase Availability. How do you make yourself convenient?

MOTIVE: Why? Goals affected.

LOCALE: Where? Locations affected.

OBJECT: What? Data affected. Note that I agree with C. J. Date that objects in Object Oriented Programming are data, not properties.

METHOD: How? Functions affected.

PERSON: Who? Populations affected.

MOMENT: When? Times affected.