What is Lateral Thinking and Do I Need It?

Two of the services we frequently use with our Clients are Idea Generation and Problem Solving. We approach both challenges with very different, process oriented methods but there is one thing that remains constant – Our ability to think laterally and come up with novel concepts by looking at situations in new and different ways. Many of our Clients are so deeply involved in an issue such as their daily business that they find it hard to change perspective and see things from an alternative angle. This is where we come in… we tend to see things that are ‘outside the box’.

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.

Make Better Decisions Today

What have you got to lose?

A training course designed to help you make better decisions takes approximately 2 days. Can you afford taking two days to learn the skills needed to make better decisions for the rest of your life?

We deliver training to 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 to make better decisions using a process rather than ‘gut feel’
b) They want their teams to make better decisions
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 objectives.

BoxOnline consultants have been providing the tools, training and guidance needed to help make better decisions for both groups and individuals since 1996.

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 staff, 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.

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 40+ 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 a 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 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 it. You would not believe how many engagement offers we received just last year to help support such pre-made decisions. In those cases, decision analysis is not a process that would help move our Client’s project forward; in those cases, we use a process called PPA to protect the plan.

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 getting results for our Clients and the DA process delivers consistently great results. It is truly a tool that you can use for the rest of your life. Go ahead, make better decisions today!

Business Case Basics 101

The most obvious reason for putting together a business case is to justify the resources and capital investment necessary to bring a change project to fruition. This may imply that a business case is simply a financial document but please don’t be mislead – business cases need to include financial justification but more importantly, they need to link all of the relevant facts in a cohesive story outlining the what, when, where, how and why for investing resources into a project. The purpose of a business case is to capture the reasoning for initiating a project or task. It is often presented in a well-structured, written document but may also come in the form of verbal argumentation. The logic of the business case is that when resources such as money or effort are consumed; they should support the business. Upgrading a given piece of kit (hardware, software etc) to improve system performance is a good example because the “business case” is that better performance would improve customer satisfaction.

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.

Its all about ROI or is it?

There are more than 60 years of combined healthcare experience between our senior staff consultants to date. We are fortunate to have on staff the former chairman of the board of Point Pleasant Hospital, a 20 year veteran of HP Medical and other leading healthcare organizations and a former director of General Electric Medical Services covering a broad range of healthcare process and management issues for our Clients. To be a bit more specific, they consult some of the largest and most reputable hospitals in Switzerland on a wide variety of topics to help their Clients establish, clarify and meet specific business driven objectives. These objectives are often financial related but more recently, the focus has been on softer targets such as patient comfort, duration of stay issues, architectural interior designs that make guests feel more comfortable and improvements in efficiency through implementation of technology.

A few of the hot consulting projects today relate to topics such as implementing DRG and RFID. The original objective of diagnosis related groupings (DRGs) was to develop a patient classification system that related types of patients treated to the resources they consumed. Since the introduction of DRGs in the early 1980’s, the healthcare industry has evolved and developed an increased demand for a patient classification system that can serve its original objective at a higher level of sophistication and precision. To meet those evolving needs, the objective of the DRG system had to expand in scope. Today, there are several different DRG systems that have been developed. They include:

• Medicare DRG
• Refined DRGs (RDRG)
• All Patient DRGs (APDRG)
• Severity DRGs (SDRG)
• All Patient Refined DRGs (APRDRG)
• International-Refined DRGs (IRDRG)
• German DRGs (G-DRG)

The overall purpose of such classification is to improve ROI while simplifying insurance related issues and thus, many hospitals have DRG on their agendas modeling and improving upon what has been learned in the 20+ years of US experience and applying it to European healthcare projects.

The other hot topic is RFID which stands for radio frequency identification. Among other things, this allows for easier inventory taking if each product in a given organization such as a hospital has a tiny bar code sized RFID tag on it or embedded into it. The objective is not only to reduce theft but also to track items such as medicine so that each patient gets only the medicine that has been prescribed for that specific individual. This helps to reduce the many deaths caused by human error when hospital staff mistakenly administer the wrong medicine to a patient during medicine distribution rounds.