The purpose of a HelpDesk for a company like ours is to:

• Listen to our Client’s issues and respond in a timely manner with answers designed to resolve their issues.
• Delight our Clients and Users to such a degree that they recommend our products and services to others.
• Increase our own cycles of learning to improve our products and services faster than our competition is able to.

When you implement this in your business, the most likely end result is positive word of mouth marketing which brings in many more leads and that is something we really appreciate.

If you are going to implement a campaign using QR codes, be sure that the codes
- are displayed in locations that have reasonable cell phone reception
- are clear and easy to read using a variety of devices including low resolution cameras

Instead of linking directly to a youtube video, consider creating a mobile friendly site or web page with the video embedded and a backup option with text instructions and images in case the video refuses to load.

Be sure to track those clicks and put analytics on your landing page to gauge the effectiveness of the campaign and the browser / device breakdown of people pinging the QR code.

Remember to include a couple of simple social media sharing options and you have the makings of a great mobile & social media campaign without too much effort.

The mouse immediately ran into the barnyard to warn the other animals, “Hey guys, there’s a mousetrap in the farmhouse!”

The hen clucked “It’s not my problem!  I’m not a mouse.”

The pig responded.  “Sorry to hear the news, but all I can do is recommend that you don’t get caught in it.”

“It’s really no big deal, just ignore the thing.” said the cow.

The mouse returned to his little hole in the wall to wait for the farmer and his wife to go to sleep so that he could begin his daily quest for a bit of leftover cheese in the darkness.  The sudden snapping sound of the mousetrap disfiguring its prey caught everyone by surprise.

The first on the scene was the farmer’s wife. She was half asleep and failed to notice the venomous snake on the floor until it bit her. The snake apparently entered the house looking for a rodent dinner when it got caught in the trap.  The farmer rushed his wife to the hospital for treatment and then brought her back to the farm where the side-effects from the drugs and venom antidote created a high fever and excruciating pain.

On the premise that chicken soup would reduce the fever, the farmer sacrificed his chicken for the soup.  But the wife’s condition did not improve. Friends provided help around the clock so that the farmer could tend to his crops and animals.  In order to feed them the farmer butchered the pig.  Alas, the wife did not survive the week and hundreds more came to her funeral forcing the farmer to slaughter the cow to provide enough meat for the hungry and respectful crowd.

The mouse watched the events unfold with great sadness from his little hole in the wall. All his barnyard friends (the ones who ignored his warning) were now gone.

We all know stories like that:  we see a problem and try to warn our co-workers but they just don’t see the big picture until it’s too late.

When one area of your company is in trouble, chances are good that the entire company’s performance will feel the impact.  For example, if there are issues with production, sales will be impacted when Customers don’t receive their orders on time. Similarly, sales may be slow and it is only a question of when production will be reduced to reflect the decrease in demand.

Phone lines and websites that can’t keep up with demand can shut down an operation overnight and permanently damage the brand and your reputation even if sales are high and production is on schedule.  A natural disaster such as snowstorm, hail, hurricane or flood will derail the most efficient of businesses unless contingency plans are in place for remote operation.

It really does not matter if you are a one-person operation or a team player in a major corporation, you should always be prepared and ask yourself:  What could go wrong?

At BoxOnline, we call this process Protecting the Plan.

Protect Your Plan - Put our PPA Process to work today

A planned response to situations that have the potential for wiping out profit and ruining your business is what gives you that extra edge should disaster strike.

Setting up a contingency plan or taking preventative measures to minimize the most likely causes of potential problems are two processes that you can initiate immediately. We have well over a decade of Client experience Protecting The Plan and look forward to helping you and your team feel more at ease, knowing that you are prepared for the worst.

Remember the lesson many of us learned in school, the time to study for a test is before you take it.

Be prepared, or be prepared to fail.

Since hourly rates for coding, additional costs for rapid development and pricing of tools and other resources can fluctuate based on circumstances beyond our immediate control, we offer the following guidelines to help you create a consistent and justifiable budget that is also realistic.

The Basics
A budget is one of those pivotal tools that is used to make decisions in many areas of a company. When creating budgets please keep the GIGO rule in mind and input quality data as often as possible. For developers, budgets dictate the amount of time they can spend on specific areas of an application. For the project manager, it’s a baseline used to determine if the project is on track. For our Client, the budget correlates directly to the success of the effort. Regardless of circumstance, a number of basic philosophies can help your budgeting immensely by protecting it from subjective review. By understanding the basic concepts, and making sure that everyone involved understands them as well, you’ll be on the right track toward an accurate projection:

Identifying project costs 

When you’re identifying the costs of development, stay as close to reality as possible. Look at performance of the team members on past projects to get a feel for how long it will take them to program a given amount of code. Consult with your lead developer. Watch out for braggadocios estimates & consider multiplying your developer’s estimate by 3 to pad for your risk assessment stage. Remember to include costs for integration, meetings, security certificates, license fees, quality assurance, debugging, documentation, material costs, testing, deployment and planning time are all areas that need to be included in your estimate. Whether we will be billing our Client for these items or not, they are all valid and substantial expenses of a project. Including them will help you accurately measure the profitability of the solution down the road.

Be sure to itemize estimates for features that were not included in the specification. These are items that you suspect will be requested later on or those that would be beneficial to the final product. List these as options in your proposal and budget for them. Another good thing to up-sell is developer support time for about 60 days after launch. Often when a project is rolled out, support groups aren’t in place yet and thus many questions get deferred to the developers – plan for this eventuality.

Once you’ve got your costs outlined, it’s time to look at the probability of staying within those boundaries.

Risk
Risk assessment and assignment is very important to a successful budget. Without it, the crises that occur regularly and are an inherent part of any project, will affect your bottom line. Values in your estimate need to have this padding built in – it should not be considered a part of sales mark-up. Risk represents actual costs incurred over the course of development. Risk line items should include things like development team experience (or lack thereof), obscurity (supportability) of the technology used, planning time shortages, number of development teams, location of development teams, number of modular components, proximity and availability of the project driver, product dependencies such as databases or third-party software, server side technology, hosting configurations (cloud etc) and any unknowns.

Once you’ve determined your risk items, assign a scope and percentage to each. For example, if one part of your application is to be built in C and another in PHP, and your team consists mostly of C programmers, the PHP component may have a higher risk assignment under the ‘developer experience’ line item. The percent assigned should be applied only to the relevant portion of the project.

All projects have a certain amount of risk involved that can be attributed to human nature. People get sick, take vacation, disappear without notice etc. No one is an expert in everything. I always assign a percentage risk to this area – in addition to other considerations. Here is a sample of how we assess risk: An average 10-developer, 6-month project justifies a risk assessment of 7 percent of the total project costs. For longer projects and smaller teams, it will be higher; for shorter projects and larger teams, it will be lower. If your overall risk assessment is between 20 and 30 percent of the total project cost, you are within our operating norms.

Your actual total risk percentage will depend on your experience in evaluating the team and the pending effort. If, after calculating an estimate, your numbers are coming out too high, look at other projects delivered by your company. Did they actually fall within their budget? If not, your numbers may be justified. If so, you may be giving your team too little credit. Rectify project-to-project discrepancies before presenting your estimate to the project driver.

Regardless of how close you come to reality, a Client will be much happier if your project comes in below budget rather than over it; however, too high a risk value can create sticker shock, revealing inexperience and creating misgivings about your management abilities. By following the guidelines we’ve suggested and applying some common sense, you are more likely to deliver your upcoming projects on time, on budget and meeting your Client’s quality expectations. Remember that Time, Quality and Cost are interrelated. If you modify one of them, it will more than likely impact the others.

Since we want our own Customers to walk away feeling so good about their experience with us that they just can’t wait to tell others, we need to be sure that we empower the right people closest to our Customers, that they have an appropriate level of authority and that they have the right tools supporting the entire process.

If you deal with Customer service issues on a daily basis then you need a set of tools that help make your job easier. Customer service is a process that can be a pleasure for all involved if you know what to do next, have the appropriate tools working for you and are able to deliver satisfaction to your Customers effectively in both written and verbal form.

Now, don’t get me wrong, not everyone is cut out to be a Customer service rep – it takes a special person to do well with this kind of challenge. In our experience, those who excel in such a role are the type of individuals convinced that their Customer is King. For these lovely people, I’d like to extend a personal thank you as both a business owner and as one of your Customers – you folks are the reason that I recommend your products and services to my list without hesitation.

Who are we to recommend something in the Customer support space? Well, over the past 10 years BoxOnline’s b6group consultants have implemented more than 60 Customer service solutions for our Clients and from that experience across a broad install base, I’d like to share some tips on improving your Customer service processes so that you too can focus on delivering world-class Customer service instead of fighting with technology that was not designed to treat Customers as King or to make your life any easier.

Let’s try to tackle these items one at a time with the objective of satisfying more Customers, following up with each issue in a professional, organized and sequential manner and also allowing these Customers to walk away feeling so good about their experience with you and your company that they just can’t wait to tell others about the great experience.

To deliver world-class Customer service you are going to need three things.
1. A ticketing system
2. An issue tracker
3. A platform for Customer service

While most software used to be installed directly on your computer or server, today there is a web application service model rapidly gaining acceptance. Three superb examples of such systems are Zendesk, JIRA and Get Satisfaction. I list these Apps specifically because they are not only three of the best Customer service web-based applications we have implemented in the past but also because they are now well integrated to provide a best of breed complete CS solution. Ticketing system Zendesk, issue tracker JIRA, and Customer service platform Get Satisfaction can now communicate seamlessly with each other.

Though much of this functionality was created independently by each of the three vendors, the result is a smooth connection between a public support tool, an enterprise issue tracker and a customizable help desk. Together, the trio delivers a powerful set of tools for responding to Customers in either a public or private forum.

The basic process outline is that CS issues and bug reports get submitted into the system by your Customer service reps (or your own Customers) then a ticketing system handles each request, humans prioritize and delegate the tasks and decisions if needed and then resolutions are shared and resolved via Customer dialog.

Get Satisfaction provides a friendly front door for Customers to enter into a dialog with your team plus optional access to positive communities where they can interact with others.

Ticketing systems are an enormously helpful way for a company to prioritize support issues, but for Customers it can be frustrating to report a problem and then be given a really long string of numbers and letters as proof that they submitted a problem to your team. But what happens then? If companies do the follow-up steps of ticketing poorly, they end up making Customers feel like they’ve been swindled. The exact opposite is what we refer to as Customer Zen and a company called Zendesk has tackled this issue superbly with an elegant and simple solution. They offer a great ticketing and tracking system.

To take this example one step further, let’s say that your business has a technical side to it and you have a software development team who need to identify and kill bugs regularly as they improve your software. Well, Zendesk has a plugin for JIRA (one of the best bug and issue trackers ever invented). This plugin allows anyone to draw tickets into the tracker, while any updates within JIRA are automatically mirrored in your Zendesk. This means that a developer can continue to use JIRA to resolve the bug while your support staff can use Zendesk to keep your Customer informed and both platforms are updated simultaneously and seamlessly.

Tying It All Together
The final piece of the puzzle is the Zendesk and Get Satisfaction integration. This is direct fusing of the two apps. Today you can send and edit Zendesk support tickets without ever leaving your Get Satisfaction interface.

So what this all means is that Get Satisfaction has evolved into a superb Customer Service tool that makes your Customers feel special while giving them the support that they need to resolve each and every one of their issues with your company, your products, your services and your staff. So if you are in need of a powerful viral marketing weapon – try giving great Customer service and then power it with both Get Satisfaction and Zendesk.

Vertical thinking, also known as logical thinking, takes an idea and carries it forward. Lateral thinking, on the other hand, provokes fresh ideas and essentially changes the frame of reference in almost any situation. Vertical thinking tries to overcome problems by dealing with them head-on, lateral thinking attempts to bypass obstacles using a variety of different approaches.

In essence, Lateral thinking is a tool that helps us change our way of thinking about something often by modifying our perceptions.

With logical thinking you start out with certain given components and boundaries wrapped in a process. This is similar to the situation in chesswhere you start out with specific pieces and are expected to play by the rules. The issue is that in most real life situations, we can not use the chess model or logical thinking to solve problems because you don’t know what the pieces are, what they represent or how many pieces actually exist… knowing the rules is almost irrelevant to solving a problem or generating new ideas.

Throughout our lives we are handed several different rulebooks (cultural, social, business oriented etc). When we get these rulebooks we just assume that the components that the rulebooks refer to, simply exist and we tend to accept that certain boundaries and limitations are present because they were mentioned in the rulebook. Lateral thinking throws out the rules and assumptions as well as the boundaries and limitations so that we are free of our social, cultural, geographic and demographic bonds.

Lateral thinking focuses on changing some element to enable a new and fresh perspective of a given situation. Lateral thinking deals primarily with perception. By using lateral thinking techniques we can organize the external world into the pieces that we can then process. Perhaps more importantly, by observing lateral thinking in others we can generate new ideas and better understand how they perceive the world around them.

The brain is a self-organizing information system that forms asymmetric patterns. In such systems there is a mathematical need for moving across patterns. The tools and processes of lateral thinking are designed to achieve such lateral movement to accomplish a given result.

A famous person once said that you can’t dig a hole in a different place by digging the same hole deeper. Think about that for a moment… If you were driving in a car on the highway but your intended destination is behind you, driving faster while keeping the car on the same heading will not get you to your intended destination.

If you were to continue thinking about a problem or a solution in a given way, this may not be as useful as changing tact and trying something completely different. Additional effort in the same direction will not necessarily help you get the results you were after but applying some proven tools designed to turn the car around, may offer you options that you never knew existed. It’s a format of thinking ‘out of the box’ and our Clients believe that we are very good at it. It may be because we do it frequently.

If you have a challenging problem or need some new ideas, please, fill out our form and allow us to get in touch with you today.

To start with, think about the following:
1. Journal your thoughts
Dedicate 4 pages for every member of your staff. Throughout the year note specific points on achievements, failures, Client feedback, project involvement and results, behavior within the team etc. I love to use a mind map for this sort of thing. So, if Autumn is the season for performance reviews, all you will need to do is whip out your mind map and create a summary for the discussion.

2. SWOT Analysis
This has always been a favorite tool for me. It is really nothing new but it sure is efficient. I typically use page 2 of the employee’s section in my journal to jot down the person’s strengths and weaknesses as they unfold during the year. Then I add to that the opportunities both inside and outside the firm in addition to the threats that I perceive relevant to this team member. I do the same SWOT for the firm as it applies to this employee such as the threat of losing this person to the competition or the opportunity to promote this person to run a new project should we land the big deal next quarter. It is very helpful in keeping my thoughts clear when decision time is upon us managers.

3. Review the Mantra and if you don’t have one… the mission statement will do. This element of the review relates performance to our company’s goals and with our company culture. One thing that I do is compare an employee’s performance with our mantra… Have they helped us to live up to our goals? How can they improve or do the goals need some adjusting? This is what I reserve page 3 of the journal for.

4. Management principles
I am asked once in a while to review a company’s management principles and rate management’s performance against these principles. This is such a ridiculous task since most managers have not memorized the principles and are expected to follow them. The real joke is that the principles are usually very honorable and inspiring but rarely if ever adhered to in the real workplace. These docs are handed to me with pride, but few managers are able to provide concrete examples of how they live up to such ideals in their daily business. How sad is that? My 2 cents… drop the ideals and get a grip on reality. Either write something that your people will use as helpful guidelines or simply stick to the mantra. End of story.

5. Client feedback
Each employee should have a folder or binder containing feedback from Clients. It serves as a reminder of good performance, gratitude and it inspires your people to keep over-delivering. I too keep a list on page 4 in my journal of every instance (that I am aware of) where Clients have provided me with feedback on my employee’s performance and whether it was positive, negative or neutral in each case. I can highly recommend this as it is usually a very real reminder of things that went right during the past year.

Since I have suffered through several ridiculous performance reviews in the past using standardized forms and the happy face vs sad face methodology which inevitably lead to more smiley faces than you can shake a stick at, I decided to ban such nonsense and get on with pissing people off when they need to hear the truth and delighting others when they over deliver and make my Clients happy – I don’t wait until the annual review, I offer my feedback on a job well done immediately.. OK, I am the first to admit… I offer my 2 cents when something goes wrong as well. After all, my goal is to over deliver and thus delight my Clients so that I can live by our mantra and help you to succeed.

So, when a Client tells us that they have a problem, we get all excited because we are trained and experienced problem solvers. The thing is, most people claim to have a problem when what they really mean is that they have an issue or a situation instead. So, what exactly is a problem?

A problem can be defined as a situation where you have all 3 of the following circumstances simultaneously:
1) You have a deviation from norm.
2) You do not know the cause of the deviation.
3) You must know the cause of the deviation in order to continue

Let’s clarify the above a bit better. When there is a deviation from norm, something unexpected occurred and when you do not know why this something occurred, it is likely that you do not know the most probable cause for the deviation.

If your project is not able to continue after the unexpected thing occurred then you need to repair the damage. The best way to repair something is to know what broke. Thus, if you do not know the cause for an unexpected deviation and you cannot move forward, you have a problem. Most people (especially those with lots of experience) attack each problem with guesses as to the most probable cause (MPC). There are two issues with guessing:
a) it is hit or miss
b) you can’t pass your lucky guess on to others so that they could solve their problems in a similar manner

The good news is that problem solving is not rocket science. The method that we use was designed and layer out by Kepner Tregoe back in the 1950s to provide NASA with a powerful tool for solving real problems in space. This problem solving tool is one of the reasons that Apollo 13 was able to make it back to earth despite multiple systems failures. The process works.

We can apply our problem solving process to your problem and help you get to the bottom of it without guessing. If you have a problem and would like to see this process in action, one of our consultants would be delighted to help you so please feel free to contact us and let us know when you’d like to schedule a problem solving session.

If one or two of the three circumstances described above do not apply to your situation – YOU DO NOT HAVE AN ACTUAL PROBLEM. You have something else!

Analogy: You look at a board in the floor and spot a metal nail sticking out. You don’t want someone to trip over the nail or to cut their foot so you go get a tool to put the nail back where it belongs. Do you select a hammer or a screwdriver?

That’s right, as soon as we have labeled a given situation “a problem”, we can reach for the appropriate tool to help identify what the most probable cause is or was. Then the cause can be dealt with and your project can move forward again. Any questions?

Our consultants have been using this tool successfully for more than a decade. That’s the thing about good process, it never gets old.

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!

Essential elements of a business case include:

• Reasons why the project is necessary.
• How the project or results generated by the project will solve given issues or capitalize on specific opportunities facing the organization.
• Focus: Exactly what ‘problem’ or ‘issue’ does the project address or solve?
• What is/are the recommended solution(s)?
• What are the benefits to the business?
• What will happen to the business if the project is not undertaken?
• Timing: When will the solutions be deployed?
• Resources such as money, people, and time needed to deliver the solution and realize the benefits?

The Business Case Process should ensure that:

• The required issues and concerns have been thoroughly considered and documented
• Both the value and risks inherent in the proposed project are clear
• The project is sponsored by, and has the commitment of an executive with the capability and authority to deliver the benefits
• The delivery of the outcomes and benefits can be tracked and measured.

Your Business Case should contain some or all of the following information types (depending on the size, timing, scale and availability of information):

• Reference; project name/reference, origins/background/current state
• Context; business objectives/opportunities, business strategic alignment (priority)
• Value Proposition; desired business outcome(s), outcome roadmap, business benefits (by outcome), quantified benefits value, costs/ROI financial scenarios, risks/costs of not proceeding, project risks (to project, benefits and business)
• Focus; problem/solution scope, assumptions/constraints, options identified/evaluated, size, scale and complexity assessment
• Deliverables; outcomes, deliverables and benefits planned, organizational areas impacted (internally and externally), key stakeholders, dependencies
• Workload; approach, phase/stage definitions (project (change) activities, technical delivery activities, workload estimate/breakdown, project plan and schedule, critical path)
• Required resources; project leadership team, project governance team, team resources, funding
• Commitments (required); project controls, reporting processes, deliverables schedule, financial budget/schedule

While one of your primary goals may be to get funding, your chances of success will be greater if you keep the following goals in mind as well:

• Make it interesting; remember someone will need to read it.
• Keep it clear and concise.
• Minimize jargon and conjecture.
• Provide the reader with a clear vision of the end state.
• Communicate all facts as part of the overall story – if you’ve done your homework, here is the chance to prove it.
• Demonstrate the value the project brings to the organization, Customer(s) and financial bottom line of the company.

After preparing your business case you and your team will likely experience some positive side effects including:

• CLARITY: Organization of thoughts, activities and knowledge
• REALITY CHECK: An objective review of the ideas and facts related to the project
• STRENGTH: The ability to identify holes, inconsistencies or weaknesses in the effort
• ELEVATOR PITCH: An improved ability to communicate the purpose of the project
• ROI: Financial justification for the effort

Below we offer an outline that includes many of the above recommendations. Remember that your business case should describe to the reader the problem or opportunity that exists. Then, the business case should describe how the problem will be solved or the opportunity exploited. The outline presented below shows you how to effectively tell the entire story of your project and concludes by demonstrating the expected ROI and financial impact you expect to achieve.

Executive summary:
Pretend that you have two minutes to tell someone about the project and justify your requests for resources and funding.

Each paragraph in the executive summary should succinctly convey vital information about the project, and communicate the story to the reader. The information in each section of the executive summary is typically extracted from the detailed sections of the business case. We recommend creating the executive summary after you have completed the rest of the sections.

Current state assessment and problem statement:
The situational assessment or current state assessment refers to the details regarding the problem or opportunities facing the organization. It is a statement about what is happening in the organization today. Most projects are started by the original project stakeholder or champion because something is wrong, or a major opportunity is being missed. Every project usually has one or two key themes related to issues or opportunities. In one paragraph or less, clearly state the specific business problem.

Project Overview:
The project description section introduces your reader to the details of the project. This section should give your stakeholders confidence that your team will professionally, efficiently and aggressively seek the best processes, systems, and organizational elements to enable your company to overcome the issues presented above. There are two main components of the project overview section:

• description and scope
• objectives

Use a maximum of nine bullet points to state what the proposed solution is expected to accomplish. Some examples may include purchasing hardware and software or selecting a new vendor.

Solution Overview:
Summarize the solution that your team recommends to address the issues and opportunities presented in the current state assessment. Be sure to cover the following topics:

• Current Process and ‘fit’ into the big picture
• Requirements
• Alternatives
• Compare Alternatives
• Additional Considerations
• Action Plan

Current process: Identify the organizational processes that the proposed solution will likely affect, including the departments within your organization, relationships with Clients, external partners, and the competition.

Requirements: List the resources needed to complete the project, such as staff, hardware, software, print materials, time, budget, and so forth.

Alternatives. Outline at least three other options to implementing the proposed solution. Be sure to include basic requirements and an estimation of project risks for each, ramp-up time, training costs, and potential project delays.

Compare alternatives. Compare and contrast each of the alternatives with the proposed solution and the other alternatives. State similarities and differences, benefits and detriments, and costs associated with each option. Basically, answer the question: “What is the cost to get to the future state, and is it worth it?”

Additional considerations. List critical success factors other than ROI metrics; for example, affects on partnership agreements with specific vendors or the potential need for help desk or Customer support.

Action plan. Now that management understands the solution and the financial return that will be realized from implementing the solution, they will want confirmation that the solution can actually be implemented. Propose specific action steps. State your short-term (first three months) and long-term (three months to conclusion) action plans, including major milestones. This section will reassure management that your team has carefully and professionally considered all major issues of the implementation. A number of major elements are important to successful implementation. Your implementation section should address each area.

• Implementation components
• Implementation timeline
• Major milestones
• Major dependencies

Critical assumptions and risk assessment:
Most business improvement projects will make assumptions in order to develop the solution. It is vital that the business case documents these assumptions. You should test your assumptions with project stakeholders and operational managers prior to placing them in the business case. The statement of assumptions should be followed by an impartial discussion of the strengths, weaknesses, opportunities and threats (SWOT) that are associated with the recommended solution. It is also important that the business case discuss the risks associated with both implementing and not implementing a solution, the seriousness of the apparent risk should it occur and the probability of the risk occurring.

Conclusions and recommendations:
This section closes out the business case. It should reiterate the key themes that caused the project to be undertaken. It should restate the solution in at a high-level. It should identify the return on investment and the overall benefits of the solution. It should restate the risks of doing nothing and re-convey a sense of urgency. Finally this section should state the conclusions the reader should draw from the business case, and your recommendations for next steps.