We’ve been helping people make better decisions on a variety of levels since 1999. As you can imagine, decisions need to be made in board rooms and offices as well as over the kitchen table.  We provide the tools and processes so that you can master the art of decision making in any situation whether it be in a board room or a dining room, your business environment or during a meeting with neighbors. You can count on our process to deliver results for you every single time.

A typical training course that guides you to making the best possible decision takes approximately 2 days to learn including time spent on applying the secret process to your unique situation and one on one coaching time to answer questions, eliminate barriers and speed the process up. We all know that learning something new requires an investment in time and energy and usually it takes a while before we master a skill to the level where it becomes second nature to us. Our objective is to follow up with our Clients and help make the process become one of your favorite and most trusted tools in your mental toolbox. After coaching, most of our Clients require no more than 30 minutes to apply our DA process to an important decision.

Are you willing to invest just two days to learn the core skills needed to make better decisions for the rest of your life?

Hey, I’m sure that you’ve already invested more than that for other courses which may or may not have given you returns year after year but this is different. This is a life-skill that, as long as you use it, will deliver results for you and those you care about.

At BoxOnline and through the b6group of consultants, we deliver top level training to both companies and individuals that want a methodical process for making and supporting decisions. Along these lines, our corporate Clients typically want three things.
a) They want their board members, executives, employees and team members to make better decisions using a proven process rather than a ‘gut feeling’
b) An increase in confidence that their subordinates will make similar decisions to those that their team leader would have made thus improving both delegation and trust within teams.
c) They want to present clear reasoning, proof that risks were evaluated and that the best possible alternative was chosen for each decision made based on the company’s (or supervisor’s) objectives.

BoxOnline has been providing the tools, training and guidance needed to help make better decisions for both groups and individuals since 1996. This process was developed in the 1950s for NASA and has been honed to perfection over the years. Wouldn’t it be great if such a decision making process were a required part of a high school or University curriculum?

In the case study below, the focus was on selecting the best possible alternative for an information technology purchase decision. This decision involved selecting a vendor, the appropriate software, hardware, infrastructure, staff support and an implementation partner. It was something of a complex decision to tackle and thus worthy of review here since so many of our Clients need to make exactly this sort of decision at least once every 5 years.

The decision analysis or ‘DA’ process can be used on simple decisions as well. You can adapt the DA process to meet EVERY decision making situation you are likely to encounter in both your personal and professional environments.

Knowing when to apply the DA process is important as well.

The method we teach is a tool you can apply when you need to make a selection from a set of alternatives to meet your specific objectives for a given project.
Personal examples include selecting a new place to live, rent or buy decisions, buying a car or even selecting a gift.
Work examples include leading the Board of Directors toward a mutually acceptable decision based on facts rather than emotions, selecting a distribution partner, hiring decisions, choosing the best possible option for growth, selecting marketing events given time and budget constraints. There are literally millions of ways to use this powerful tool and we challenge you to put it to task today.

The plain fact is that the pressure is on to make decisions rapidly in today’s market, including choosing which software and services suppliers to partner with to deliver on strategic objectives. Responsible managers want to deliver on objectives in a timely way, yet protect themselves from career jeopardy. Can they achieve both?

One approach to making the best possible decision is to use a highly logical process. The DA (Decision Analysis) methodology used and taught for 50+ years by top business process consultants world-wide is something that we have adopted and applied for many of our Clients. Yes, it’s a time proven process that even NASA uses and it involves many well-orchestrated and synchronized steps. The BoxOnline DA process is designed to avoid some of the classic pitfalls typical of the way many people make decisions today.

Here are the key steps when evaluating alternatives for an important decision:

• Clearly state the decision to be made.
• Set the strategic and operational objectives.
• Classify objectives based on Client’s musts and wants.
• Weight the “wants.”
• Generate alternatives.
• Screen alternatives through the “musts.”
• Compare alternatives against the “wants.”
• Identify adverse consequences.
• Make the best, most balanced choice.

IT decision making requires additional steps:

• Decide on technology standards into which the decision fits.
• Recognize the major pitfalls typical in each step of the IT purchase process.
• Use the “relationship manager” between IT and business organizations.
• Evaluate vendors against objectives.

Setting Strategic Objectives

The decision analysis method begins with the decision statement, which provides the focus for everything that follows and sets the choice’s parameters. The criteria to be developed will follow, detailing the decision requirements. Alternatives will be evaluated according to those requirements. The decision statement always indicates a choice and its intended result, and it often implies a prior decision has been made, such as to select a services vendor for a certain operation. The decision statement sets all activities in motion, so be sure to word it carefully.

Conducting a full decision analysis for every single decision you make is not very time efficient. Sometimes, just agreeing on a decision statement and objectives will give you and your team the clarity needed to make a sound decision.

Decisions must meet objectives. Once the decision statement is drafted, objectives are established. Alternatives are discussed and identified possibly only after objectives are established. The opposite of decision analysis would be a process in which the course of action is identified first; then a case is built to support the intended action. In such situations, decision analysis would not be the tool of choice, we use a process called PPA to protect the plan. If this is something that interest you, please don’t hesitate to ask us for more information.

Objectives related to technology strategy are important for selecting software and services providers. You need to know if the company is trying to build a platform for the future or keep existing systems cobbled together. Some strategic decisions will include certain vendors and technologies, and thereby eliminate others. In essence, the guts of the technology platform should be well understood, covering strategic areas such as security, data, development frameworks, communications standards, infrastructure and available people skills. This view enables the IT manager to attain a strategic perspective.

Some common mistakes in this phase include overemphasizing cost objectives and defining requirements without Customers in mind. There is a whole class of criteria for front office people or users of the system, that will have different weights for different Customer needs. Costs must be estimated, and viewed according to whether the project is strategic (an investment is justified) or tactical in which case low cost is an important criteria in the decision process.

Many times a manager is not exposed to the real project requirements and thus, looks at the estimated price tag and says, “We can’t do that – it’s too expensive.” You might find that you are unnaturally constrained by a budgetary concern that has nothing to do with the problem you are trying to solve.

Getting back on track again:
Decision analysis divides objectives into two categories: musts and wants. Musts are the minimum requirements, not necessarily the most important. When alternatives are later evaluated against objectives, any alternative that can’t fulfill a must objective is immediately dropped.

Objectives must be measurable to screen against alternatives. In IT decisions, measurable objectives may include response time, mean time between failures, service levels and access speed.

Must objectives need to be reasonable. For example, requiring .Net programmers to have five years of experience might be unrealistic, if the .Net framework was launched less than 5 years ago. To require e-business service firms to have such experience would knock out many options. To rate vendors, IT managers need to establish their minimum requirements. This is an absolute priority.

Once must objectives are clearly defined, all other objectives are called “wants”. Wants are used to provide a picture of how alternatives compare.

A common IT pitfall is to base objectives on ‘new’ or ‘compatible technology’ when actually, the Customer’s needs may be satisfied by older technology. IT guys should not purchase products simply because they are new. Newness has to be weighted against factors such as potentially longer testing cycles.

The second largest stumbling block to decision making success is when a group responsible for making the decision begins their process with what from our perspective is a comparison of the alternatives; Thus System A may be compared to System B, or Product X to Product Y, or Hardware C to Hardware D. This comparison of one to another so early on in the decision making process launches the team into a challenge / defense mode and is clearly not a productive way to reach the best possible decision outcome.

Creating a written record of the reasons why a specific decision was made is an additional benefit of the decision analysis process. In the real world, when people are making decisions, some things are more important than others. If you can get that on the table, it really helps move things forward. This also demonstrates to people both in the decision making quorum as well as those outside (perhaps sitting on the management team or board of directors) that logic, fairness and process were used to reach a mutually agreeable conclusion that also took into account potential risks and probability of occurrence among other factors.

Try using decision analysis to determine which projects to work on. Your objectives should include the anticipated results of the project, as well as resource and other restrictions you face.

When a group is choosing between a current and proposed course of action, both are considered alternatives. Both are evaluated against the objectives as if both had been proposed. In the absence of any alternative, the group can usually build an alternative from available components.

Never get tangled up in the alternatives before you define the objectives. IT people are typically analytical, so they go for a system involving weights and scores, but that is not an end in itself. The decision meeting is about making the decision not influencing your favorite alternative with a high score. In fact, the KT method has some brilliant built-in checks and balances to ensure that the best possible group decision gets made. Use the objectives to help the team keep an open mind while working toward a viable solution and be sure to keep score.

The final step in decision analysis is to consider adverse consequences for all feasible alternatives. Once a decision has been made and implemented, any negative effects can grow into real problems. The effect of the decision always outlives the process that led to it. Before making a final decision, the group must explore and evaluate adverse consequences. When the group identifies a risk, it can plan to avoid the risk or reduce its likely effect. A risk may not be fatal, provided someone recognizes it in time to do something about it. Omitting this step is an invitation for disaster.

It can all be overwhelming: strategic objectives, alternatives, weighting, scores and implementation plans. Many IT organizations now have defined the role of “relationship manager” to bridge the gap between the IT and the operational business worlds. The decision process outlined in this article helps you figure out how to start. Since we all know that IT people come from different planets and speak different languages than their business counterparts, the clearly defined process helps them understand exactly what needs to get done on the road to making a good decision. After a few minutes of bewilderment, most people physically relax as they learn this 40 year old time proven methodology for making the best possible decisions. There is an order and a logic that helps the IT people become more like internal consultants. They are not just throwing stuff over the cubicle wall, but rather listening to their Customers and applying their knowledge to come up with viable solutions.

Here is one more tip regarding your MUST criteria. When you evaluate your MUSTs consider if you would accept something slightly more or less than described in the objective? If the answer is yes, then the objective is a want, not a must.

If you’d like some help getting started with your own decision analysis just drop us a line – we love helping our Clients achieve results and the DA process delivers consistently great results. It is truly a tool that you can use for the rest of your life. So, go ahead, make better decisions today!