Trouble? Change Hats

I’ve just finished reading “Why Wait for Trouble?” by Kenneth W. Freeman in Strategy and Business. Kenneth described a five stage condition model of a company.

  1. Bleeding
  2. Stability
  3. Gradual Improvement
  4. Rapid Improvement
  5. Arrogance

The danger Kenneth described was remaining in any of these stages too long. I agree, but you probably guessed that I disagree that there are five stages. I believe there are six stages and there are symptoms of remaining in them too long. Again I am referring to my Six Hats, Six Coats metaphor.

  1. Blue Hat: Synchronization Failure. You are not performing transactions at the optimal rate. Bleeding.
  2. Red Hat: Personalization Failure. You are not addressing employee/customer needs. Over Stability.
  3. Black Hat: Physicalization Failure. You are not minimizing cost. Overly Gradual Improvement.
  4. White Hat: Logicalization Failure. You are not maximizing value. Overly Rapid Improvement.
  5. Yellow Hat: Contextual Failure. You are not maintaining uniqueness. Arrogance.
  6. Green Hat: Conceptual Failure. You are not revising your vision. Dictating.

These are the symptoms of wearing any of the Six Hats too long. You can also wear any of the Six Coats too long, but that remains for another post.

SQL Authority

I have been following the blog of SQL Authority, Pinal Dave, since I came to discover WordPress.

Pinal’s focus on and dedication to his work comes through in his content. Although his specialty is SQLServer and I am a born and bred Oracle specialist, I often find Pinal has general concepts that benefit anyone who is working with SQL based databases.

Right now Pinal is writing posts on Data Warehousing Interview Questions. The scope and brevity of his definitions are perfect for anyone wanting to condense their thinking about the broad range of data warehousing terminology.

Visit and subscribe to SQL Authority. It will be worth your while.

relationary sql authority relationary sql authority relationary sql authority

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

STL: Structured Thinking Language (remix)

It’s been a short time coming, but I have hammered out another iteration of the vocabulary for the Structured Thinking Language (STL).

stl03.jpg

REVISE: Conceptualize. Expand Meaning. What are you enhancing or making right? Creativity.

RELATE: Contextualize. Focus on Uniqueness. What is your mantra? Relativity.

REPORT: Logicalize. Maximize Value. What are you normalizing to the limit? Optimicity.

RECORD: Physicalize. Minimize Cost. What is your business model? Pessimicity.

REFINE: Personalize. Humanize Interaction. How do you lower the barriers to adoption? Anthropicity.

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

MOTIVE: Why? Concepts affected.

LOCALE: Where? Contexts affected.

OBJECT: What? Logics affected.

METHOD: How? Physics affected.

PERSON: Who? Humans affected.

MOMENT: When? Synchrons affected.

From here on in there are only six verbs, irregardless of whether you are Inducting (Analyzing) or Deducting (Designing) or (something new) Producting (Developing) or Conducting (Operating). It is the order in which you are performing the verbs which is important.

lifecycle.jpg

I love this. I’m going to invent more words than Shakespeare.

stl structured thinking language remix stl structured thinking language remix stl structured thinking language remix