Tom The Architect

Technology and other Interesting Stuff

Tag: principles

My 10 Standard Operating Principles

Teams operate best when they have perfect clarity and focus. This can be challenging to almost impossible at times, but one thing I have learned is we all need a common set of operating principles to fall back on when clarity and focus are in short supply. These basic principles  are intended to help an individual or team to keep moving. The list provides basic tools to help create clarity or to allow for action to be taken without fear of a mistake.  I have found that 7 out of 10 principles generally work for any team and only need minor adjustment or 2 or 3 additional principles.  I am also constantly looking for ways to refine the principles to make them more clear and actionable without being specific instructions.  So here they are in no particular order:

  1. 2 in the box.  Escalate until you have someone with shared responsibility or accountability. Batons get passed not dropped.
  2. Lead with a straw man. No one likes to be put on the spot, give them something to work with or to save face with if they are not prepared.
  3. A problem has a cause and a solution bring both.
  4. Decisions are made better with data.
  5. People understand what they know.  Give examples using what they know.
  6. Outcomes first, then focus on the means and the credit.
  7. Your communicating enough when you feel like you are bothering people.
  8. UNODIR (Unless Otherwise Directed) Take measured action, adjust and communicate.
  9. Draw a picture.  A picture is worth 10 meetings (at least), even one hand drawn in pencil and scanned.
  10. Here Be Dragons.  There are many risks, challenges and issues mark them for others.

These 10 aren’t perfect but they can only get better.

My Interface Design Principles

I did some work on putting together a new interface design for an application. So, I thought I would provide my guiding principles.

  1. “Information becomes the interface”, Edward Tufte in Visual Explanations p.142.
  2. “OODA Loop” (Observation, Orientation, Decision, Action) By Col John Boyd, USAF (Ret).
  3. Information displays should strive to be no wider than 16 choices and 2 levels deep.
  4. Base change on real observed behavior. The qualitative can not eliminate the quantitative
  5. To some degree the interface has to be stupid simple. The antithesis to this principle is demonstrated by some large ERP software vendors.
  6. Do as much work beyond view of the customer as possible.
  7. Icons are Iconic or they are not valuable.
  8. Visual oriented communication occurs a faster rate and results in increased short term retention
  9. Make help always available and obvious
  10. Continuity Continuity Continuity
  11. Empathy