Big Sky Thinking

Better Decisions Faster


SOA: The Cure for Accidental Architecture

The term Accidental Architecture was coined in a paper published by the University of Kent that discusses the evolution of IT architectures over time and the complex issues surrounding legacy systems. The term has come to represent how narrowly focused technology investments result in an enterprise IT infrastructure that is both complex and challenging to manage. In most organizations, functional units drive IT investments in areas such as procurement, operations, and service delivery. Oftentimes, these IT systems are built to meet ‘local’ requirements and are not thought of as an enterprise-class solution that will interact with other systems and platforms. The net result of these siloed IT investments is an “Accidental Architecture”.

This is not to say that each individual solution is not well-architected, nor that if fails to meet the defined business need, but rather that at an enterprise level the architecture becomes ‘accidental’ as it is dictated by the provincial IT and business decisions that created it. In essence, IT decisions are made without evaluating their full impact on the enterprise and without an eye to the bigger picture, thus creating information gaps in the
value chain. This is a missed opportunity to improve information quality, drive new efficiencies, and enable collaboration to provide additional value to the customer or end user. The end game here is to eliminate the information gaps to improve decision-making about operations, investments, and the execution of the organization’s mission.

So how do we avoid the pitfalls of an accidental architecture? We take a move out of
Steven Covey’s playbook and ‘begin with the end in mind’. If our goal is to eliminate islands of information and barriers to collaboration, then we require a solution that promotes interoperability. The way to achieve this goal is to adopt enterprise standards that specify how different applications will interact and that also bridges the gaps between different platforms. We recommend adopting the IT principles commonly known as Services Oriented Architecture (SOA). SOA is an architectural style that is based on a set of evolving standards (some of which are mature, e.g. SOAP) that provide a framework for the development of Web services.

SOA provides the tools to manage Web services and specifies the means for service integration and interoperability. This allows developers to create the applications they need to solve business problems without having to worry about application integration issues down the road. This effectively separates the infrastructure from the application, which provides flexibility, reduces development costs, increases re-use, and allows the organization to deploy solutions that work across the enterprise.


As organizations move toward a Services Oriented Architecture, they often take an incremental approach and work to meet a discreet need before implementing web services on a large scale across the entire enterprise. A case study of ING Bank’s first SOA implementation is discussed in “The SOA Magazine” and gives a good overview of the process and lessons learned.

Using Visuals to Make Decisions: Excel 2007

We've previously posted about the importance of using visuals to make decisions. I ran across an excellent post by Jon Peltier at PTS blog that provides a very useful overview of the new charting functions in excel. For those of us who use excel frequently to manage and present data in support of decision-making, a solid understanding of the new 2007 features are a must-have. Thanks, Jon.

Labels: , ,

Decision-Making Traps Part 6: The Estimating and Forecasting Trap

In our previous post in this series, we introduced “The Hidden Traps in Decision Making” by John S. Hammond, Ralph L. Keeney, and Howard Raiffa, in which they describe six traps in organizational decision-making that can adversely affect performance. This week’s post covers the final trap, the “The Estimating and Forecasting Trap”. Even though most of us are not very good at making estimates, we tend to be overconfident about our accuracy – which can lead to bad decisions. There are three different traps that can have a particularly distorting effect in uncertain situations because they cloud our ability to assess probabilities.

  1. The Overconfidence Trap – Tend to be overconfident about our accuracy

  2. The Prudence Trap – Over-cautiousness or prudence

  3. The Recallability Trap – Base predictions of future events on the memory of past events.

Big Sky sees this trap in our clients especially when executives have strong domain or market experience. In addition, because very experienced people have excellent instincts, they can overlook trends that change the implicit assumptions in their mental decision-making process. For example, Clayton Christensen’s work on Innovation shows how the excellent customer-focused instincts of executives can actually crush the development of new, market-changing products. You can read more about Christensen’s “Innovator’s Dilemma” here.

Techniques to overcome:
  1. Start by considering the extremes, the low and high ends of the possible range of values

  2. Challenge estimates of your subordinates and advisers (overconfidence trap)

  3. Always state your estimates honestly and explain to anyone if or not the estimates have been adjusted (prudence trap)

  4. Carefully examine all your assumptions to ensure they’re not unduly influenced by your memory (recallability trap)

Closing thoughts on Decision-Making:

When it comes to business decisions, there’s rarely such a thing as a no-brainer. Our brains are always at work, sometimes, unfortunately, in ways that hinder rather than help us. At every stage of the decision-making process, misperceptions, biases, and other tricks of the mind can influence the choices we make.

The best protection against all psychological traps – in isolation or in combination – is awareness. Forewarned is forearmed. Even if you can’t eradicate the distortions ingrained into the way your mind works, you can build tests and disciplines into your decision-making process that can uncover errors in thinking before they become errors in judgment.

Labels:

Decision-Making Traps Part 5: The Framing Trap

In our previous post in this series, we introduced “The Hidden Traps in Decision Making” by John S. Hammond, Ralph L. Keeney, and Howard Raiffa, in which they describe six traps in organizational decision-making that can adversely affect performance. This week’s post covers the fifth trap, the “The Framing Trap” which states that the way a problem is framed can profoundly influence the choices one makes. Research proves that people are risk averse when a problem is posed in terms of gains, but risk seeking when a problem is posed in terms of avoiding losses.

Big Sky sees this trap in our clients especially when executives consciously or unconsciously frame the problem such that their proposed solution seems to be the best answer. Also, executives might focus on highlighting their pain areas which might not be a pain area for somebody else.

Techniques to overcome:

  1. Don’t automatically accept the initial frame, try posing problems in a neutral redundant way that combines the gains and losses or embraces different reference points
  2. Think hard throughout your decision-making process about the framing of the problem, and when others recommend decisions, examine the way they framed the problem.
Our next post in this series will discuss the “Estimating and Forecasting Trap” outlined in the article.

Labels:

Decision-Making Traps Part 4: The Confirming-Evidence Trap

In our previous post in this series, we introduced “The Hidden Traps in Decision Making” by John S. Hammond, Ralph L. Keeney, and Howard Raiffa, in which they describe six traps in organizational decision-making that can adversely affect performance. This week’s post covers the fourth trap, the “The Confirming-Evidence Trap” that leads us to seek out information that supports our existing instinct or point of view while avoiding information that contradicts it. This not only affects where we go to look for evidence, but also how we interpret the information that we receive.

Big Sky sees this trap in our clients especially when executives are biased based on their past experience and knowledge, or if they are pushing for their pet projects. For example, when we help client prioritize investments, we find that some executives are very surprised with how an objective process is at odds with their “gut.” For a great read on this phenomenon, check out Moneyball by Michael Lewis. Clients who are in “The Status-Quo” and “The Sunk-Cost” traps also succumb to “The Confirming-Evidence” trap.

Techniques to overcome:

  1. Confirm that you are examining all the evidence with equal rigor
  2. Find someone you respect to play the devil’s advocate
  3. Be honest with yourself about your motives (are you gathering information to confirm what you already think?)
  4. While seeking advice of others, don’t ask leading questions that invite confirming evidence

Our next post in this series will discuss the “The Framing Trap” outlined in the article and will be posted next week.

Labels:

Decision-Making Traps Part 3: The Sunk-Cost Trap

In our previous posts in this series, we introduced “The Hidden Traps in Decision Making” by John S. Hammond, Ralph L. Keeney, and Howard Raiffa, in which they describe six traps in organizational decision-making that can adversely affect performance. This week’s post covers the third trap, the “Sunk-Cost Trap”, that talks about our deep-seated biases to make choices in a way that justifies past choices, even when the past choices no longer seem valid. These past decisions often involve considering sunk costs in assessing the viability of a project – old investments of time or money that are no longer recoverable. One might also call this “throwing good money after bad.”

Big Sky sees this trap in our clients especially when…switching costs are high or if there are budget constraints. When huge investments have already been made, the team that made that decision tries to justify that decision. In many of Big Sky’s government clients’ large complex IT projects continue to command major investment well after it’s clear to all that the projects have failed. Rather than redirecting investment to better options, some organizations will continue to try to salvage huge IT investment by bolting on functionality or placing band-aids on system issues.

Techniques to overcome:

  1. Always be mindful of long-term objectives and examine how they would be served by the status quo, if at all
  2. While considering other options, evaluate the status-quo alternative if it was just another option, rather than the front-runner
  3. Avoid exaggerating switching costs
  4. And finally, always evaluate alternatives in terms of future as well as present context
Our next post in this series will discuss the “The Confirming-Evidence Trap” outlined in the article and will be posted next week.

Labels:

Decision-Making Traps Part 2: The Status Quo Trap

In our previous post in this series, we introduced “The Hidden Traps in Decision Making” by John S. Hammond, Ralph L. Keeney, and Howard Raiffa, in which they describe six traps in organizational decision-making that can adversely affect performance. This week’s post covers the second trap, the “Status Quo Trap,” that we also observe in our clients on a regular basis. In organizations that display the Status Quo trap, decision makers display a strong bias toward alternatives that perpetuate the status quo. Breaking the status quo means taking action, and when we take action, we take responsibility, thus opening ourselves to criticism and to regret.

Big Sky sees this trap in our clients especially when…organizational cultures do not encourage change. When employees are not rewarded to take risks but are penalized for unfavorable outcomes, they choose to stay with the tested-and-tried way of doing business. For example, we have observed in some R&D clients a tendency to reward large projects that transition to operational use, but stigma is applied to failed attempts at innovation. This encourages R&D planners to over-weight project with a high probability of success and projects that are already fully funded, rather than creating a portfolio that includes some high-risk projects.

Techniques to overcome: A few ideas for avoiding the status quo trap include:

  1. Remind yourself of your objectives and examine how they would be served by the status quo
  2. Identify other options – don’t assume that there aren’t any
  3. Ask yourself if you would choose the status-quo alternative if it was not the status quo
  4. Avoid exaggerating switching costs
  5. Evaluate alternatives in terms of future as well as present context

Our next post in this series will discuss the “Sunk-Cost Trap” outlined in the article and will be posted next week.

Labels:

Decision-Making Traps Part 1: The Anchoring Trap

John S. Hammond, Ralph L. Keeney, and Howard Raiffa wrote an article in Harvard Business Review The Hidden Traps in Decision Making” which discusses different traps of the mind and different ways in which we can overcome these traps. All of us are susceptible to making bad decisions and judgments unless we can learn to recognize and avoid them. Even though the article was written nearly a decade ago in 1998, it is still highly relevant and important in the context of decision making. Hence, despite its age, we decided to devote a series of posts highlighting each of these six “traps,” and the techniques that these authors recommend to overcome them. This first post discusses “The Anchoring Trap” and will be followed by one post for each of the five remaining traps identified by the authors.

#1: The Anchoring Trap: When considering a decision, the mind gives disproportionate weight to the first information it receives. Initial impressions, estimates, or data anchor subsequent thoughts and judgments. This pernicious mental phenomenon is known as anchoring.

  • Big Sky Sees this trap in our clients when. . . time is of the essence. When organizations are under particular pressure to make a decision fast, the anchoring trap becomes particularly acute as there is little patience to wait for alternative information.
  • Techniques to overcome: View a problem from different perspectives (use a different starting point to avoid the anchor), be open minded, be careful to avoid anchoring your advisor (tell them as little as possible and ask for their opinion), and be particularly wary of anchors in negotiations.

Our next post in this series will discuss the “Status Quo Trap” outlined in the article and will be posted next week.

Labels: