• Explore More Strategy Topics

  Agile Agility Alignment Architecture Benchmark Business Cost Decision-Making Definition EA Enterprise Architecture Enterprise Archuitecture Execution Framework Good Enough Governance GTD Heuristic IEEE 1457 IT IT Governance ITIL Management Measurement Methodology Performance Planning Planninig Principle Principles Process Project Reference Architecture Research Security Simple Small Wins SOA Social Architecture Software Architecture Solution Standards Strategy Technology Thinking TOGAF Trends Zachman

• Blogroll

  • Enterprise Architecture: From Incite comes Insight…
  • Pragmatic Enterprise Architecture
  • Serge Thorn’s IT Blog
  • Smart (Enough) Systems
  • Technology Architecture & Projects
  • The Practice of Leadership
  • Todd Biske: Outside the Box
  • User-Centric Enterprise Architecture

Photo by marj k

"You should treat decisions as an enterprise asset. You should make even the most high-volume, operational decisions as though they are enterprise decisions." - Smart (Enough) Systems

Enterprise architecture is really all about effective decision making….! At its core enterprise architecture is a tool that informs and guides decision-making…

• Planning decisions
• Investment decisions
• Solution decisions

Enterprise architecture is a tool that consists of frameworks, principles, standards, processes, reference models - anything that can help us make better decisions! What’s unique about an enterprise architecture, is that it’s built upon the a core belief that an holistic or enterprise perspective is produces better decisions than taking a silo view of the problem. A high-level holistic perspective the enables decision-making from an overall systems perspective.

Creating architecture, although required, produces no value. Value only comes from applying architecture to influence projects. This is best supported by a decision making approach as:

• Decisions move us from the “as-is” to the “to-be”, one step at a time.
• A focus on decisions makes enterprise architecture practical and action-oriented …rather than theoretical.
• Focuses enterprise architecture on helping to foster decision-making, rather than on the frameworks and the processes. Focusing on ends, rather than means.
• Ensures that enterprise architecture addresses stakeholder decision-making needs, as they make decisions at different levels of abstraction

Technorati Tags: Decisions, Architecture, Enterprise Architecture, System, Management, Practical

The book "The Art of Systems Architecting" discusses the importance of heuristics as an architectural tool. The authors define a heuristic as follows:

"Heuristics are guides along the way - channel markings, direction signs, alerts, warnings, and anchorages - tools in the larger sense"

The word heuristic has it’s origin in the Greek word ‘heuriskein‘ which means "to find a way" or "to guide" in the sense of guiding a boat through treacherous waters. I liked this definition of a heuristic from Steve Pavlina:

"An heuristic is a rule for exploring a search space that can help you get close to an optimal solution when you cannot explore the entire search space."

Dave Snowden, discussing heuristics, provides the following insight:

"Heuristics are common sense sayings that make us think about things."

Heuristics are especially useful in decision-making, in providing guidance, and in solving ill-structured problems. There are primarily two types of heuristics:

• Descriptive heuristics: these describe a situation or context but do not provide any guidance on how to resolve it.
• Prescriptive heuristics: these provide guidance about what to do about a specific situation.

Carefully selected heuristics are great tools that architects can use to guide their journey into the unknown, they a great way to consciously apply the wisdom, insights, the lessons learned and gleaned from personal experiences and from the experiences of others. Heuristics are most useful when they are used as a set. Some example  heuristics are:

• The beginning is the most important part of the work - Plato, 4th Century B.C.
• Build and maintain options al long as possible in the design and implementation of complex systems. You will need them.
• In order to understand anything you must not try to understand everything.
• Politics, not technology, sets the limits of what technology is allowed to achieve.

Deliberately and consciously selecting a set of heuristics at the start of a project is a great way to reuse the wisdom gained from past experiences. A team discussion on the most appropriate heuristics that should be "top of mind" and used as a set of guides, shared by the team, to guide their journey. Heuristics are especially important given the increasing level of complexity and uncertainty in architecting large systems.

In book "The Art of Systems Architecting" the authors provide the following rules to consider when applying heuristics:

• If it works, then it’s useful.
• Knowing when and how to use a heuristic is as important as knowing the what and why.
• Heuristics work best when applied early to reduce the solution space.
• Strive for balance - too much of a good thing or complete elimination of a bad thing may make things worse not better.
• Practice, practice, practice.
• Heuristics aren’t reality either.

To conclude:

“Heuristics are an essential complement to analytics, particularly in situations where analysis alone cannot provide either insights, or guidelines.”

How much have you learned as an architect? Have you codified some of your lessons learned into succinct expressions or heuristics to guide future architecture efforts?

Technorati Tags: Heuristics, Principles, Architecture, Rules, Guidance

• Search for:

• Welcome

  Welcome to Architecture and Change. You can subscribe to my blog using RSS or you can subscribe by e-mail

• Contact

  
  
  

• Busy Reading...

• Interesting Blog Stats

• Show of Support