problem solving approach business analysis

How to Define a Problem and Generate Solutions

Tools versus experience.

A common concern for business analysts is a lack of experience, especially in the application of tools, i.e. frameworks and modelling techniques and the software that supports them. There are so many things to know and learn, and it can be very overwhelming. It seems that there are so many techniques to apply these days and it is confusing to know where to start.

However, there is a tendency by the business analyst to over rely on having a swag of tools and techniques to provide confidence. It is like if you are good at the tools then you are a good business analyst, but this is not true. Tools are only as good as the problem that is being solved. Of course, tools and techniques are important, but they are not the place to start.

The real value in business analysis is understanding the problem. You gain true experience in engaging with stakeholders, understanding their issues and aligning with their needs.

When the problem is properly understood, then the real difference can be made. You are able to narrow down and choose the right tool and use it to analyse and communicate the problem and articulate a possible solution. This way there is less overwhelm, and you can produce better results.

Problem solving

The business analysis process can be viewed as an exercise in solving a series of problems to produce beneficial outcomes for an organisation. Those problems may be related to:

• issues occurring in the business (see ‘Example business problems’ below)
• project methodology and personal skills
• people and organisation (see ‘Common problems encountered by business analysts’ below).

Being a confident problem solver is fundamentally important for your success as a business analyst. Having a good process to use when approaching a problem helps you solve problems quickly and effectively. Without a process, your solutions may be ineffective, or you will get stuck which can produce painful consequences.

Here is a basic approach to solving a problem in four steps:

• Define the problem.
• Generate ideas to solve the problem.
• Evaluate and select alternatives.
• Implement solutions.

There are other more complex approaches such as Simplex, Appreciative Inquiry and Soft Systems Methodology.

You will find on closer examination that you may already use a combination any of the above-mentioned techniques. Problem solving is something we do in every aspect of our daily lives and therefore it occurs largely as an unconscious activity, i.e. something we do so often we don’t have to think about it.

Possibly without knowing it, your unconscious mind is constantly used as an engine for problem solving. But you can use your unconscious mind to solve problems in a deliberate fashion. This is the process of listening and a readiness to record ideas as they percolate into your conscious mind. To do this requires the ability to relax and allow ideas and solutions to flow into your mind. One common technique is to saturate yourself in understanding the problem, ask yourself the question as to how to solve the problem, and then take a break or ‘sleep on it’.

You would have heard of this before, however conscious utilisation of this form of problem solving will greatly benefit your business analysis work. It can produce some very creative ideas that are very satisfying to include in the evaluation and selection of alternatives. The important thing is not to try too hard. Go with the flow. Incubate.

Defining the problem

Problem solving does not have to be an elaborate and difficult process.

Firstly, you need to understand what the problem is. Half the battle is won when you can identify the true source of the problem, as ideas to solve the problem may then be readily available.

It is not enough to only treat the symptoms of the problem, as this will not solve the underlying issue and symptoms will keep occurring. Just treating the symptoms will eventually come at significant cost for an organisation.

Business analysis problem solving techniques such as mind mapping and root cause analysis can help you work through the layers of a problem to uncover what’s really going on. They can be used in a group setting or as a personal tool for uncovering possible causes that can be later examined in a group setting.

When working with stakeholder groups you can simply use one or a combination of the above-mentioned tools and a brainstorming approach to uncover the root causes of a problem. In this case, you would start with the perceived ideas about what the problem is and use a problem identification technique to arrive at a true problem statement .

Problem identification can also be combined with other elicitation activities, e.g.

• Business process mapping workshops . In this case, the business analyst is defining and documenting the current state of how the organisation operates. In these workshops, the business analyst captures the activities performed by various functions in the organisation, pre-defined roles, information used and created (e.g. reports), systems used, location and temporal information, and other inputs and outputs. Often through the process mapping issues are raised by stakeholders and a quick ‘Five Whys’ analysis can uncover root causes that can be later examined in a separate session.
• Business process analysis and blue skies workshops . In these workshops, the focus is on uncovering ideas that will affect change on a business process or system that supports a business process. Without the exclusion of other approaches, there are two good ways of doing this.

The first approach occurs when you are examining the ‘as-is’ business process in a step-by-step fashion for improvements (business process analysis). A short and powerful questioning technique is described here , but through the analysis of processes you may encounter issues that required clarification. Again, the ‘Five Whys’ method is a good approach as it is more conversational than other problem identification techniques and therefore it does not break from the flow of the process analysis workshop.

The other approach is to disregard close examination of ‘as-is’ business process maps (blue skies workshops ) . This option depends on what you plan to achieve in your business analysis process, but it is very useful in situations where the stakeholders are more senior in the organisation or have no patience or desire to pay close scrutiny to business processes. Here you would develop a questioning technique that points at a process or function in the business but allows a free style generation of issues and ideas to overcome the issues. In this situation Lean Six Sigma principles can be used as the basis for questioning (using the acronym: DOWNTIME) to give the session structure, identify process improvements without looking at a map, and allow a free thinking and brainstorming approach to ideas generation. Again, the ‘Five Whys’ method is a good way to test the identification of a problem without breaking the flow of the workshop.

Generating ideas to solve the problem.

One way to generate ideas to solve problems has been described above, i.e. through blue skies workshops. Other methods mostly involve creative techniques such as brainstorming. There are different ways to structure brainstorming sessions, but it is important to note that:

• Good stakeholder analysis will inform who you include in which session so that you can optimise for best ideas generation and different points of view.
• You must have a planned approach which includes pre-planned questions and an agenda.
• You must set the scene so that participants know what their role is and what they will be doing in the session (no surprises).
• You facilitate rather than dictate the solutions.

It is important to note that participants know their own business and usually have an idea of what could be a good solution to a problem. If they don’t, then instead of telling the answer it is better to ask questions to trigger ideas. If they are supported in arriving at the answers, then they are more likely to invest ownership in the outcome of the project. Good questioning and conversation flow will support participants in producing good ideas. Participants should be challenged and pushed beyond the obvious solutions – this is where the real thinking starts – to get the best possible results from the brainstorming session.

Evaluating and selecting alternatives

The evaluation and selection of options to resolve a problem is part of these BABOK Knowledge Areas:

• Requirements Analysis and Design
• Solution Evaluation.

The work performed by the business analyst may culminate in the following deliverables:

• Business requirements specification ( see example template ). This deliverable encapsulates the analysis of elicited, validated and prioritised requirements.
• Business case ( see example template ). This deliverable summarises solution options and recommendations.

It is important to note that the templates provided above are more suited to Waterfall methodology or a ‘big requirements upfront’ approach to requirements documentation. At the very least they can be adapted or provided as a guideline for the type of information required in analysing requirements and making a recommendation. More about standard business analysis deliverables can be found here .

Implementing solutions

The implementation of solutions depends on the pathway described in the options analysis and recommendation (business case). This depends on the type of problem you are solving.

Properly identifying the business problem helps ensure you understand the project’s end game . You may be faced with documenting business processes to enhance business efficiencies, developing or purchasing a software system to support a changing business environment, or developing some kind of architecture to support an organisation’s strategic process.

Therefore, the implementation of the solution is defined by problem being solved and can take a number of pathways. The pathway to take is therefore another problem to be solved and another challenge for the business analyst and the project team (we must not forget that project management has a big role to play).

After all, business analysis is a series of problem-solving activities that delivered the best outcomes for an organisation.

Example problems

Common business problems solved by business analysts.

There are many business problems that you will solve over the course of your career and many will have a similar pattern. The list below describes some common examples of problems, their possible causes and some skills and techniques that would be utilised by the business analyst to deliver satisfactory outcomes for the organisation.

Common problems encountered by business analysts

Aside from the problems that business analysts solve as part of their work, there are other problems that they encounter in their work that are due mainly to people and organisational issues. The table below shows a list of common problems face by business analysts, possible mitigation activities to reduce or resolve the occurrence of the problem, and possible skills and techniques used as part of the mitigation strategy.

If possible, describe a business problem that you have identified and solved in the past. If you cannot describe a work-related business problem, then choose another problem that has occurred in your life, e.g. anything associated with club/social events, moving to a new house, changing career, travel or other. What was initial perceived problem (problem description)? What were the root causes of the problem? What approach did you take to identify and solve the problem (approach taken)? What tools and techniques did you use? What was the final outcome?

In consideration of the problem you described above, how could you have improved on the problem identification and resolution process? Is there anything you could have done better? What problem identification techniques could you incorporate in future work?

This exercise not only helps you reflect on problem solving in general but can be used in job interviews and conversations around problem solving.

If you are keen, add another row to the table above and repeat the exercise. The more you can spell out how you have solved problems and where you can improve, the more articulate you will be in describing this very important skill.

MBA059: Problem Solving for Business Analysts

by Dave Saboe | Feb 16, 2016 | Podcast , Start | 0 comments

In this episode, Matt Fishbeck shares a six step problem solving framework that can help you to address the right problem and come up with the best solution for your organization and customers.

After listening to this episode, you'll understand:.

• Why the skill of problem is so critical
• How to apply a 6 step problem solving framework
• How to apply problem solving techniques
• Defining the problem statement
• Defining scope
• Elicit information & resolving ambiguity
• Identifying associations and relationships
• Root cause analysis
• Solution proposal

The Problem Solving Process Start by creating the problem statement.  The problem statement is a well-defined statement or question to frame the context. After you have a clear and unambiguous problem statement, define the scope of the effort.  The scope definition is probably the most important stage since it basically whether or not the problem can be solved satisfactorily.  Scope is defined to apply constraints to the domain of consideration. When we have scope we know what to consider and what not to consider.  Therefore, all possible solutions are directly dependant on the information within the scope. Once the scope is defined, you can move on to eliciting information & resolving ambiguity.  Perform a stakeholder analysis and elicit information from all known stakeholders/sources as a basis for investigation.  You can use workshops, focus groups, interviews, document analysis, and other approaches to elicit information. When we elicit information, we try to remove ambiguity as ambiguity represents the unknown, liability, and risk.  To reduce ambiguity, we need to consider the taxonomy of ambiguity to provide a frame of reference to how we will resolve it.  Ambiguity may be:

• Missing information
• Incorrect information
• Duplicate information
• Conflicting information
• Incomplete information

The above provide a basis to ask questions concerning all information that is within scope, to challenge this information to be reliable and suitable for use.  Context diagrams and domain diagram can help resolve ambiguity. Next, we identify associations and relationships to organize the information so we can derive meaning from it.  Information needs to be structured, aligned, and associated that provides an additional level of meaning. This is the basis for traceability. The linking of concepts. It’s not just solely used for requirements. Once we thoroughly understand the information, we can move on to performing a root cause analysis.  A root cause analysis helps you to understand the underlying cause of the problem so you can address it instead of addressing a symptom of a greater issue. There are many techniques for root cause analysis including 5 Whys and Fishbone diagrams. Now that we understand the real root cause, we can propose solutions that will address that root cause.  When identifying proposed solutions, consider the scope, constraints, and relative cost and value of each option.   Problem solving is not some illusive black art; it’s an analytical process that can be broken down, quantified, and analyzed to identify the root cause to give rise to a viable solution. Listen to the full episode to hear all of Matt’s examples and tips for problem solving.

Your Homework

• Begin applying Matt’s six-stage problem solving approach.  Often, the most difficult part of problem solving is knowing where to start.
• Start learning the root cause analysis techniques in the Guide to the Business Analysis Body of Knowledge (BABOK).  The techniques will give you more tools to help in your problem solving efforts.

Links mentioned in this episode:

• Matt’s Problem Solving article on ModernAnalyst.com

Matt Fishbeck

Senior Business Analyst and Writer

Thank you for listening to the program

Trackbacks/pingbacks.

• Think Like a Freak to be a Trusted Advisor - […] BAs solve the right problem with the right solution among multiple possible options.  We’re able to see work that…

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Exclusive Discount from cPrime Learning

Buy One, Get One Free

• Top Courses
• Online Degrees
• Find your New Career
• Join for Free

Fundamentals of Business Problem Solving

This course is part of Business Problem Solving Specialization

Taught in English

Instructor: Alton Henley

Financial aid available

Recommended experience

Intermediate level

To be successful in this course, learners will need a basic knowledge of the business process and of Microsoft Excel.

What you'll learn

Develop an understanding of the business process, including how to identify opportunities and risks.

Utilize Microsoft Excel to create and manipulate spreadsheets.

Interpret and analyze spreadsheet modeling outputs.

Skills you'll gain

• Spreadsheet
• Microsoft Excel
• Business Analysis
• Business Process
• Business Strategy

Details to know

Add to your LinkedIn profile

10 quizzes, 7 assignments

See how employees at top companies are mastering in-demand skills

Build your subject-matter expertise

• Learn new concepts from industry experts
• Gain a foundational understanding of a subject or tool
• Develop job-relevant skills with hands-on projects
• Earn a shareable career certificate

Earn a career certificate

Add this credential to your LinkedIn profile, resume, or CV

Share it on social media and in your performance review

There are 4 modules in this course

This course introduces how to classify data and create models used to solve business models. Learners will use Solver to create expressions to find optimal paths for business problems.

Introduction to Business Problem Solving

This module introduces the key components of a business model. It also provides an overview of how to use Solver in Microsoft Excel.

What's included

9 videos 1 reading 3 quizzes 1 discussion prompt

9 videos • Total 36 minutes

• Introduction to the Specialization: Business Problem Solving • 2 minutes • Preview module
• Introduction to Fundamentals of Business Problem Solving • 1 minute
• Introduction to the Instructor • 1 minute
• Introduction to Modeling • 7 minutes
• Modeling 101 • 3 minutes
• Vital Spreadsheet Techniques for Modeling • 8 minutes
• Introduction to Solver • 4 minutes
• Installing Solver • 1 minute
• Using Solver • 5 minutes

1 reading • Total 15 minutes

• Welcome to Business Problem Solving • 15 minutes

3 quizzes • Total 90 minutes

• Graded Quiz Lesson 1.3 • 30 minutes
• Practice Quiz Lesson 1.1 • 30 minutes
• Practice Quiz Lesson 1.2 • 30 minutes

1 discussion prompt • Total 30 minutes

• Meet and Greet • 30 minutes

Creating a Basic Business Model

This module describes how to create a spreadsheet model for a business problem and use data points to analyze the trends.

5 videos 3 readings 3 quizzes 3 assignments

5 videos • Total 23 minutes

• Analyzing a Business Problem • 4 minutes • Preview module
• Walkthrough: Analyzing Ike's Guitar Shop • 2 minutes
• Walkthrough: Analyzing Property Development • 1 minute
• Analyzing a Business Problem II • 9 minutes
• Walkthrough: Analyzing Geneva's Hair Emporium • 6 minutes

3 readings • Total 30 minutes

• Business Case: Ike Guitar Shop • 10 minutes
• Business Case: Property Development • 10 minutes
• Business Case: Geneva's Hair Emporium • 10 minutes
• Graded Quiz Lesson 2.2 • 30 minutes
• Practice Quiz Lesson 2.1 • 30 minutes
• Practice Quiz Lesson 2.2 • 30 minutes

3 assignments • Total 180 minutes

• Ike Guitar Shop • 60 minutes
• Property Development • 60 minutes
• Geneva's Hair Emporium • 60 minutes

Building Different Model Types

This module focuses on how to build and solve business problems related to profit and product mix models.

7 videos 4 readings 3 quizzes 4 assignments

7 videos • Total 39 minutes

• Understanding Profit Model • 3 minutes • Preview module
• Additional Modeling Tools • 2 minutes
• Walkthrough: Brian's Barbershop • 6 minutes
• Dante's Canes Walkthrough • 10 minutes
• Understanding the Product Mix Model • 6 minutes
• Walkthrough: Forrest Pizzeria • 5 minutes
• Walkthrough: Geneva's Mom's Hair Emporium • 4 minutes

4 readings • Total 40 minutes

• Business Case: Brian’s Barbershop • 10 minutes
• Business Case: Dante's Canes • 10 minutes
• Business Case: Forrest Pizzeria • 10 minutes
• Business Case: Geneva's Mom's Hair Emporium • 10 minutes
• Graded Quiz Lesson 3.2 • 30 minutes
• Practice Quiz Lesson 3.1 • 30 minutes
• Practice Quiz Lesson 3.2 • 30 minutes

4 assignments • Total 240 minutes

• Brian's Barbershop • 60 minutes
• Dante's Canes • 60 minutes
• Forrest Pizzeria • 60 minutes
• Geneva's Mom's Hair Emporium • 60 minutes

Model Optimization

This module explains how to use Solver in Microsoft Excel to optimize business models.

6 videos 1 reading 1 quiz

6 videos • Total 19 minutes

• Using Solver to Optimizer a Model • 2 minutes • Preview module
• Optimizing Brian's Barbershop • 3 minutes
• Optimizing Dante's Canes • 3 minutes
• Using Solver for Product Mix Models • 3 minutes
• Optimizing Forrest Pizzeria • 2 minutes
• Optimizing Geneva's Mom's Hair Emporium • 2 minutes

1 reading • Total 60 minutes

• Business Model Case: Charmaine and Shieng's Cupcakes • 60 minutes

1 quiz • Total 30 minutes

• Graded Quiz Lesson 4.3 • 30 minutes

Founded in 1867, Howard University is a private, research university that is comprised of 14 schools and colleges. Students pursue more than 140 programs of study leading to undergraduate, graduate and professional degrees. The University operates with a commitment to Excellence in Truth and Service and has produced one Schwarzman Scholar, three Marshall Scholars, four Rhodes Scholars, 12 Truman Scholars, 25 Pickering Fellows and more than 165 Fulbright recipients. Howard also produces more on-campus African American Ph.D. recipients than any other university in the United States. For more information on Howard University, visit www.howard.edu.

Recommended if you're interested in Business Strategy

Howard University

Business Problem Solving

Specialization

Business Modeling Tools

Solving Business Problems with Spreadsheet Modeling

Coursera Project Network

Query data in Django

Guided Project

Why people choose Coursera for their career

New to Business Strategy? Start here.

Open new doors with Coursera Plus

Unlimited access to 7,000+ world-class courses, hands-on projects, and job-ready certificate programs - all included in your subscription

Advance your career with an online degree

Earn a degree from world-class universities - 100% online

Join over 3,400 global companies that choose Coursera for Business

Upskill your employees to excel in the digital economy

Frequently asked questions

When will i have access to the lectures and assignments.

Access to lectures and assignments depends on your type of enrollment. If you take a course in audit mode, you will be able to see most course materials for free. To access graded assignments and to earn a Certificate, you will need to purchase the Certificate experience, during or after your audit. If you don't see the audit option:

The course may not offer an audit option. You can try a Free Trial instead, or apply for Financial Aid.

The course may offer 'Full Course, No Certificate' instead. This option lets you see all course materials, submit required assessments, and get a final grade. This also means that you will not be able to purchase a Certificate experience.

What will I get if I subscribe to this Specialization?

When you enroll in the course, you get access to all of the courses in the Specialization, and you earn a certificate when you complete the work. Your electronic Certificate will be added to your Accomplishments page - from there, you can print your Certificate or add it to your LinkedIn profile. If you only want to read and view the course content, you can audit the course for free.

What is the refund policy?

If you subscribed, you get a 7-day free trial during which you can cancel at no penalty. After that, we don’t give refunds, but you can cancel your subscription at any time. See our full refund policy Opens in a new tab .

Is financial aid available?

Yes. In select learning programs, you can apply for financial aid or a scholarship if you can’t afford the enrollment fee. If fin aid or scholarship is available for your learning program selection, you’ll find a link to apply on the description page.

More questions

The Community

Modern analyst blog, community blog.

• Member Profiles

Networking Opportunities

Community spotlight, business analysis glossary, articles listing, business analyst humor, self assessment.

• Training Courses
• Organizations
• Resume Writing Tips
• Interview Questions

Let Us Help Your Business

Advertise with us, rss feeds & syndication, privacy policy.

Problem Solving for Business Analysts

This article explores the discipline of problem solving. Some might consider problem solving an art, while others might define it as science. The reality is a little in between since part of problem solving involves creativity, which by definition cannot be rationalized as science since we are basically unaware or not conscious of it occurring. Creative formulation of new concepts and ideas is a process lies deep within the sub consciousness and we are only aware of the output of the creative process; a new idea is a good example. We don’t understand how the idea was created, but we know we thought of it.

This article does consider the creative process and instead deems it out of scope. Instead a process for problem solving is proposed that defines a number of phases that can be rationally quantified, executed and basically tested and verified.

Introduction

What does it mean to solve a problem? It relies upon two things occurring in the following order; an issue, or undesirable state that remains to cause angst, disadvantage, some negative consequence, or a limited capability and as a result some drive to overcome this situation through the formulation of some kind of a solution to resolve, nullify, or improve the current state of affairs.

How do we solve problems? Some people would say, by thinking. Thinking about what? The problem, right? Not necessarily. Thinking about the problem may help the situation and provide a starting point, but if thinking about the problem alone is not immediately returning positive inspiration and results then you are probably selling yourself short, being too narrow minded in breath and/or depth or focused on the symptoms rather than the cause. If the solution is not obvious, then there is obviously something missing from the equation.

For languages sake of descriptions, the term ‘problem’ is sometimes used interchangeably with the word ‘issue’. We don’t say ‘issue solving’, only ‘problem solving’. Issue is used since it is a more positive expression of the situation. One might say that there are no problems, only issues.

Practical Context

Undertaking business analysis, business architecture, or enterprise architecture involve the use of a broad spectrum of knowledge and best practice in frameworks and techniques to solve business problems. Apart from information relative to the professional practices, there are other domains such as the specific context in the organisation; the drivers & motivations, constraints, legacies, culture, etc. and issue or problem.

Finding a solution to a problem involves some kind of change within the organisation to be realized and formulated that could include a new product or service, capability, technology improvement, process maturity uplift, etc. All of these examples represent solutions to underling issues/problems that impact capability, and value to shareholders, customers, partners and suppliers.

Solving business problems always involves some kind of starting point, and a finishing point in terms of where in the spectrum one lies with respect to the problem and the solution. 

Important Elements of Consideration

There are a number of important elements of problem solving which will be explored in detail later when considering the proposed overall process of problem solving. See below;

·        Problem Statement: Describes the nature of the issue at hand

·        Scope & Information: Associated information contained within boundaries of consideration

·        Association and Relationships: Linkages between information within the scope

·        Rationale: The logical deduction within the scope that links the problem to the solution

·        Solution: A defined change in the system that nullifies, the problem and/or problem driver

The following are a series of sequential phases that should occur to complete a problem solving exercise, which would result in a solution to the problem statement. The phases can be viewed as a waterfall. If however a phase cannot be completed, it means that a previous stage is incomplete and requires further exploring. Hence each phase has an optional feedback loop.

Problem Statement

The problem itself should be understood as something discrete, defined or quantifiable. It can be represented as question or a statement that describes something. Problems can also be ambiguous in that they are hard to understand or pin down as something concrete. Ambiguous problems require further exploration that can occur from proceeding to the next phase of defining the scope, and then returning to reevaluate the problem statement.

Definition of Scope

The scope of the problem is extremely important and provides the platform to which all other considerations are included and excluded. A good analogy to scope is the expressions of ‘ring fencing’. Picture yourself actually laying a fence around an area to encapsulate something. The goal of building a fence is to keep something in, and to keep something out. Seems obvious but it’s worth thinking about this in terms of information and problem solving. All information that needs to be considered is within the fence line, and everything else is outside.

This is important from a planning perspective since if one knows what information needs to be considered, one must review the information. Because the information is known one can actually plan and put constraints around this; who needs to be consulted, where the information is obtained from, what systems and resource needs to be drawn upon.

Scope itself is a constraint. The output or solution to a problem is directly dependent on the information that went into the problem solving process. Information that is critical to formulating the correct solution is essential to being included in the scope. This can be demonstrated through a mathematical equation.

Take the following equation, which the problem is to find the value of X;

X = Y + 10           

Consider for a second that the problem is X, and X cannot be determined. What can be determined is that Y has the value of 5.

Unfortunately, due to poor research Y is not considered, only X. This equation is them impossible to solve and a solution is not found.

If however, you broadened the scope to include Y (Equals 5) then you could add 5 to 10 and have the solution;

This may seem elementary but it highlights that without proper considering and scoping, one’s perspective may not be adequate to see the whole picture.

Quite often in business some information is considered, but not everything due to time constraints and economic pressure guiding a shorter term perspective on the solution. Often when this is done the depth of analysis is limited resulting in shallow or knee jerk reactions and band aid solutions that do not address the underlying cause.

In this sense scoping can be strategic since it takes into account the broader perspective including a broader more considerate base of information that is often not focused on the short term.

Resolving Ambiguity: Ambiguity factors

Resolving ambiguity is very import. When there is confusion or uncertainty statements made become imprecise approximations that fuel a culture of anxiety. People need to have the right knowledge at the right time to solve problems by making sound decisions. It’s important to note that nothing sure footed can really be achieved when there is confusion.

Resolving ambiguity or confusion is present in the following situations. Note that the following does not include any human communication dynamics.

·        Missing Information: Information that is not present

·        Incorrect information: Information that can be verified by other information to be incorrect

·        Conflicting Information: Information in at least two separate places that contradicts

·        Duplicate information: Same or similar information that is in more than one place

·        Incomplete information: Information that is present but has an unsatisfactory level of detail

How do you know if you’re missing information? Sometimes this is obvious based on the existing information. (You can see the outline of the footprint.). Other times there is no footprint, all your have is your current information, which is the best starting point for further information and traceability.

Traceability

Traceability is the art of defining concepts and their associated connection points. Consider a dot to dot drawing or a mind map; what presents is an interconnected network. This network can be used to explore its boundaries, both its breath of scope and level of scope. This two way exploration can always start with the existing information, considering other related concepts and relationships.

For example, if the word ‘Interface’ was on a mind map, I could also draw other branches with connections that say ‘client’, ‘server’, ‘api’, ‘web service’, ‘xml’, ‘meta-data’, ‘contract’, ‘data flow’ etc. The root of this exploration is the word ‘interface’.

Traceability can be explored within a mind map, or in any other conceptual model where you are connecting information, to other information through some kind of relationships.

Root Cause Analysis

Since the entire scope has now been defined, the process of identifying the problem symptoms and problem causes can begin. The symptoms are obvious effects, outcomes, metrics, sales figures, costs, performance measures; negative qualitative or quantitative measurements.

Asking the question why is the basis for root cause analysis. It considers the result of questions and then traces backwards to underlying causes. If we ask the question why, the result is the answer and potentially the basis to another question. This is an iterative process that is continued until the underlying cause is uncovered. Note, that the underlying cause should also be within the bounds of the scope already defined.

For example, the problem is a person driving a car along the highway breaks down and is stuck on the side of the road. The problem is “Car has broken down”. See below for root cause analysis.

·        Question: Why has the car broken down?

·        Answer: Engine has overheated.

·        Question: Why has the engine overheated?

·        Answer: No water in the radiator.

·        Question: Why is there no water in the radiator?

·        Answer: Didn’t get the car serviced

·        Question: Why didn’t the car get serviced?

·        Answer: Forgot to get the car serviced.

·        Question: Why did you forget to get the car serviced?

·        Answer: It was a new car and the owner never had to get the car serviced before.

·        Question: What is the servicing requirements of the car?

·        Answer: Get it serviced 6 months after purchase, then 12 months thereafter. (Stated in contract.)

·        Question: Did the owner read the contract?

·        Answer: No. Owner didn’t read the contract and was unaware of car servicing requirements.

·        Problem Symptom (Effect) = “Car broken down. Can’t go anywhere. Stranded on highway.”

·        Real Problem (Cause) = “Owner didn’t read the contract and had no idea that car needed to be serviced”

Identification and realization to solution

Once the underlying cause is attained through root cause analysis, the solution is often the formulation of a preventative action that is undertaken to resolve the problem symptom from ever occurring. This is usually obvious since it is only a single ‘jump’ to understand the resolution.

In the above example, the solution would be for the owner after they purchased the vehicle to read the contract or ask the sales dealer. That way they would have understood the responsibilities of owner the car and taken it in for service, preventing the breakdown from ever occurring.

A less savvy car owner would have opted for a more reactive solution. In this example, the owner could have just carried a jerrycan of water in the car. When the car breaks down the owner can simply fill the radiator up again with water and restart the car. (Assuming the engine is still working.)

The most challenging aspect to problem solving is having the right information and doing adequate work in scoping the issue. When the right information has been considered, mapping out the context and domain diagrams, the relationships can be defined; the problems and their causal drivers can easily be identified through logical deduction.

It’s also important to point out that sometimes it’s better not to be too focused on the actual problem, since as we have demonstrated here, the problem itself is just a single breadcrumb in the investigation; a mere starting point for exploration. This is what problem solving can be described as, a process of guided exploration within a domain, that has boundaries and has been defined to be within scope. Exploration starts at the symptom and goes backward, forward, underneath and around the problem to provide context and understanding of the bigger picture.

Often it’s the bigger picture that allows us the understanding to see the problem relative to the context and proceed in a process of questioning from a defined starting point to an ending point. This is one way to solve problems that starts by considering the problem statement, examining the scope boundaries and information, conducting logical deductions; asking questions and assessing answers, asking further questions etc, and deriving a solution that addresses the cause or root of the problem.  Sometimes root cause analysis is not required, other times there a multiple problems, seemingly interrelated with dependencies - and this is all compounded with complexity and ambiguity of course, not to mention miss communication and misinterpretation related to human factors. 

Yes, problem solving can be challenging, but it can be made less so with a methodical and logical approach that works.

Related Articles

Article/Paper Categories

Upcoming live webinars, ace the interview.

Roles and Titles

• Business Analyst
• Business Process Analyst
• IT Business Analyst
• Requirements Engineer
• Business Systems Analyst
• Systems Analyst
• Data Analyst

Career Resources

• Interview Tips
• Salary Information
• Directory of Links

Community Resources

• Project Members

Advertising Opportunities  | Contact Us  | Privacy Policy

This web app uses cookies to compile statistic information of our users visits. By continuing to browse the site you are agreeing to our use of cookies. If you wish you may change your preference or read about cookies

Problem-Solving in Business Analysis: Key Skills

Problem-solving is an important skill in business analysis. It helps professionals identify and address issues within an organization. From analyzing data to developing strategies, problem-solving is crucial for success.

In this article, we’ll explore the key skills needed for effective problem-solving in business analysis. We’ll also discuss how developing these skills can help professionals make valuable contributions to their organizations.

The Essential Role of Problem-Solving for Business Analysts

Business analysts play a crucial role in solving problems for businesses. They identify and analyze challenging issues to provide effective solutions. Methods like brainstorming, process mapping, and SWOT analysis help them address complex challenges. These techniques enable analysts to define problems, generate solutions, and identify the best one. They work collaboratively with stakeholders to ensure valuable solutions meet client needs.

Continuous improvement of problem-solving skills is important for effectively navigating work challenges.

Demonstrating Problem-Solving in Action: Business Analysis Scenarios

The business analyst uses brainstorming, process mapping, and root cause analysis to solve complex business challenges. They collaborate with stakeholders and subject matter experts to identify potential issues and conduct in-depth analysis.

For example, during a recent project, the business analyst facilitated a brainstorming session with the project team to generate innovative solutions for a critical business problem. This resulted in the development of an effective action plan to address the identified issues.

Strategic visualization, like mind mapping concepts, is used to visually organize and prioritize various ideas and concepts, providing a clear and structured approach to identifying potential solutions.

Additionally, the use of structural tools and frameworks, such as the fishbone diagram, SWOT analysis , and Pareto chart, has helped the business analyst systematically analyze data, identify key areas for improvement, and prioritize actions based on the impact.

For instance, the business analyst used the SWOT analysis to assess the company’s competitive position. This enabled the identification of specific strategies to capitalize on strengths and opportunities while addressing weaknesses and threats.

Key Techniques to Address Complex Business Challenges

Business analysts use investigative methods to uncover core issues in complex business challenges. They apply structured problem-solving techniques and various tools like root cause analysis, the Five Whys technique, SWOT analysis, and Pareto chart to aid in problem resolution. These tools help in identifying and analyzing the root causes of problems and making informed decisions based on data.

Additionally, techniques like brainstorming and process mapping can be employed to generate innovative ideas and visually represent the steps and key elements of a process. By approaching problems with a structured, analytical mindset and collaborating with stakeholders, business analysts can effectively enhance their problem-solving skills and provide valuable solutions to clients.

Investigative Methods: Uncovering the Core Issues

Brainstorming ideas.

One way to generate and brainstorm new ideas for complex business challenges is by using techniques like mind mapping , the Five Whys, and root cause analysis. These methods help business analysts visualize concepts, identify patterns, and come up with innovative solutions.

Mind mapping helps analysts visually organize ideas and concepts, leading to a better understanding of complex issues and potential solutions. The Five Whys and root cause analysis techniques allow analysts to explore the underlying causes of a problem and develop creative strategies to address it. By asking sequential “why” questions, analysts can uncover the root cause and brainstorm solutions.

These methods help develop problem-solving skills in business analysis by providing structured tools to collaboratively address complex business challenges effectively.

Process Mapping for Clarity

Process mapping is a helpful tool for business analysis. It visually represents a series of events and actions within a process. This helps analysts find inefficiencies, redundancies, or bottlenecks that affect operational performance.

By using process mapping, analysts can emphasize the importance of having a clear visualization of the operational process. This helps stakeholders understand the process better. It also helps analysts uncover core issues and address complex business challenges by identifying areas for improvement and innovation.

Additionally, process mapping aids in strategic visualization and problem resolution. It creates a framework for analysts to examine the flow of work, inputs, and outputs. This enhances decision-making and problem resolution within the organization.

Digging Deeper: Root Cause Analysis

Root cause analysis is a valuable tool for business analysts. It helps uncover the core issues in complex business challenges. By using techniques like the fishbone diagram or the Five Whys technique, they can find the underlying causes of a problem rather than just its symptoms.

For example, if a retail company faces a decrease in sales, a root cause analysis may reveal that it’s due to a shift in consumer preferences or increased competition, rather than just ineffective marketing strategies.

The Five Whys technique empowers business analysts to go beyond surface-level symptoms by repeatedly asking “why” to get to the root cause. These techniques help them dig deeper and find long-term solutions to complex business problems.

To conduct an effective root cause analysis, business analysts must use various techniques such as brainstorming, process mapping, and SWOT analysis. Each technique provides a unique perspective and helps uncover the underlying issues. These structured approaches ensure that the root cause is accurately identified, allowing for the development of targeted and effective solutions.

For example, by using SWOT analysis , business analysts can assess the strengths, weaknesses, opportunities, and threats associated with a problem, guiding their analysis to uncover the root cause.

Incisive Inquiry: The Five Whys Technique

The Five Whys Technique helps uncover the root cause of a problem in business analysis. It involves asking “why” repeatedly to reveal the true source of the issue. This approach is important for addressing complex business challenges, as it allows analysts to dig deep and identify the fundamental cause. The technique contributes to problem resolution and decision-making by providing a systematic approach to problem-solving.

It enables analysts to develop effective solutions that target the rootcause instead of just treating the symptoms. For instance, if a business deals with recurring customer complaints about a product defect, the Five Whys Technique can pinpoint the specific flaws in the production process that need addressing for a permanent resolution.

Strategic Visualization: Mind Mapping Concepts

Strategic visualization through mind mapping is a helpful tool for problem-solving in business analysis. It helps in organizing information visually, allowing analysts to see how different aspects of a problem relate to each other.

By using this technique, analysts can map out key factors, stakeholders, and potential solutions in a structured way. This encourages creativity and flexibility when approaching challenges.

Incorporating mind mapping in addressing complex business challenges involves methods like brainstorming, process mapping, and SWOT analysis. These approaches offer a systematic way of exploring and evaluating solutions, fostering collaboration with stakeholders and an analytical mindset.

Strategic visualization through mind mapping helps in uncovering core issues by focusing on critical factors and relationships. It aids in identifying patterns and potential causes, leading to a deeper understanding of the problems at hand and more informed decision-making.

Structural Tools and Frameworks for Problem Resolution

Using fishbone diagram for cause and effect.

The Fishbone Diagram is a helpful tool for business analysts. It helps identify the causes and effects of a business problem. Analysts use this technique to visualize the different factors contributing to an issue. This can help understand the root causes.

The key steps involved in using the Fishbone Diagram include:

• Defining the problem.
• Brainstorming potential causes.
• Categorizing causes into major groups.
• Analyzing the relationships between them

This process helps to organize and prioritize the key factors affecting the problem.

Moreover, the Fishbone Diagram aids in visualizing and understanding complex business challenges. It provides a structured approach to problem-solving. This enables stakeholders to identify the interdependencies between various contributing factors.

This visual representation facilitates a better understanding of the problem. It leads to effective solutions and informed decision-making.

Assessing Scenarios with SWOT Analysis

A SWOT analysis is a helpful tool for evaluating business scenarios. It identifies strengths, weaknesses, opportunities, and threats related to the current business situation. By looking at these aspects, analysts can gain a better understanding of how different factors might impact the business. They might find internal strengths to use in taking advantage of external opportunities or spot weaknesses to address potential threats.

This analysis informs strategic plans and helps with making informed business decisions.

Pareto Chart: Prioritizing Issues for Maximum Impact

The Pareto Chart is a powerful tool for business analysts. It helps prioritize issues for maximum impact. By focusing on the most significant issues, analysts can allocate resources and make strategic decisions. When using a Pareto Chart, it’s important to gather and analyze relevant data. This helps identify common or severe issues affecting the business. The chart visually represents the frequency and impact of various issues.

This aids analysts in making informed decisions about which issuesto address first.

As a result, resources can be allocated more effectively, and solutions can deliver maximum value to the business and its stakeholders.

Quantitative Decisions: Cost-Benefit Analysis Process

Quantitative analysis helps businesses make cost-benefit decisions. It looks at the costs and benefits of a decision to see if it is feasible and profitable.

For example, a manufacturing company might use it to decide if new machinery will save money and increase productivity over time. Key steps include identifying all costs and benefits, adjusting for the time value of money, and making sure all relevant factors are included. By considering both tangible and intangible factors, such as environmental impact and employee satisfaction, businesses can make better decisions. Applying this process to different scenarios helps with things like choosing a profitable market, finding a cost-effective supplier, or evaluating the return on investment for a new product or service.

Decision Matrix: Evaluating and Prioritizing Business Options

When evaluating and prioritizing business options using a decision matrix, business analysts should consider several relevant factors. These include cost, risk, potential return on investment, timeline, and resource requirements.

This approach allows for a comprehensive assessment of each option’s pros and cons, enabling them to make well-informed decisions.

A decision matrix can effectively compare and contrast various business options by assigning weights to each factor and scoring each option accordingly.

By summing up the scores, analysts can identify the most viable option that aligns with the organization’s objectives.

Implementing a decision matrix involves several key steps. These include determining evaluation criteria, gathering input from stakeholders, assigning weights to criteria, scoring each option, and calculating the final scores.

This meticulous process ensures a thorough evaluation and prioritization of business options, leading to strategic and successful decision-making.

Advanced Problem-Solving: Employing CATWOE as a Tool

CATWOE is a useful tool for business analysts. It helps analyze complex business problems thoroughly. By using CATWOE, analysts can consider the broader context of the problem and understand stakeholders’ perspectives. This includes Customers, Actors, Transformation Process, World view, and Owner/Employer. This ensures that all viewpoints are carefully examined.

For instance, if a business is facing a decline in customer satisfaction, CATWOE can help in understanding not only customer perspectives, but also the impact on employees, the transformation process, and other relevant aspects. This helps in addressing the root causes of issues rather than just symptoms.

CATWOE empowers business analysts to develop strategic and sustainable solutions for complex business challenges. This enhances their investigative and decision-making methods, leading to more effective problem-solving.

Vizologi is a revolutionary AI-generated business strategy tool that offers its users access to advanced features to create and refine start-up ideas quickly. It generates limitless business ideas, gains insights on markets and competitors, and automates business plan creation.

Mastering Problem-Solving in Business Basics

Tools to check your problem-solving skills.

Before downloading the canvas, we would like to invite you to our newsletter, from time-to-time we will send you curated content about business strategy

Table of Contents

Definition of business analysis, what are business analysis techniques, best business analysis techniques, do you want to become a business analyst, top effective business analysis techniques.

Business analysts are such an essential element for an organization’s survival and success today. By using different structured business analysis techniques, these analysts help companies identify needs, root out flaws, and sift through a flood of data and options to find the right actionable solution.

We’re here today to explore some of the top business analysis techniques and how they are successfully leveraged for an organization’s success. There are many of these proven business analysis problem-solving techniques to choose from. Still, the ones highlighted here are the more commonly used methods, and it’s reasonable to infer that their popularity stems from their effectiveness. Here is the list of the top business analysis techniques:

Business Process Modeling (BPM)

Brainstorming, moscow (must or should, could or would), most (mission, objectives, strategies, and tactics) analysis, pestle analysis, swot analysis, six thinking hats, non-functional requirement analysis, design thinking.

Business analysis is an umbrella term describing the combination of knowledge, techniques, and tasks employed for identifying business needs, then proposing changes and creating solutions that result in value for the stakeholders. Although a significant number of today’s business analysis solutions incorporate software and digital data-based elements, many professionals in the field may also end up advising on organizational changes, improving processes, developing new policies, and participating in strategic planning.

So, business analysts spur change within an organization by assessing and analyzing needs and vulnerabilities and then creating and implementing the best solutions. Much of the information used to draw these conclusions comes from data collected by various means, often falling under the term “big data.”

Become a Business and Leadership Professional

• Top 10 skills in demand Business Analysis As A Skill In 2020
• 14% Growth in Jobs Of Business Analysis Profile By 2028

Business Analyst

• Industry-recognized certifications from IBM and Simplilearn
• Masterclasses from IBM experts

Post Graduate Program in Business Analysis

• Certificate from Simplilearn in collaboration with Purdue University
• Become eligible to be part of the Purdue University Alumni Association

Here's what learners are saying regarding our programs:

Assistant Consultant at Tata Consultancy Services , Tata Consultancy Services

My experience with Simplilearn has been great till now. They have good materials to start with, and a wide range of courses. I have signed up for two courses with Simplilearn over the past 6 months, Data Scientist and Agile and Scrum. My experience with both is good. One unique feature I liked about Simplilearn is that they give pre-requisites that you should complete, before a live class, so that you go there fully prepared. Secondly, there support staff is superb. I believe there are two teams, to cater to the Indian and US time zones. Simplilearn gives you the most methodical and easy way to up-skill yourself. Also, when you compare the data analytics courses across the market that offer web-based tutorials, Simplilearn, scores over the rest in my opinion. Great job, Simplilearn!

I was keenly looking for a change in my domain from business consultancy to IT(Business Analytics). This Post Graduate Program in Business Analysis course helped me achieve the same. I am proficient in business analysis now and am looking for job profiles that suit my skill set.

Business analysis techniques are processes used to create and implement plans necessary for identifying a company’s needs and delivering the best results. There is no such thing as a “one size fits all” technique because every business or organization is different.

Here are the top business analysis techniques. Keep in mind that business analysts who want to be project managers should be familiar with most, if not all, of them.

1. Business Process Modeling (BPM)

BPM is often used during a project’s analysis phase to understand and analyze the gaps between the current business process and any future process that the business is shooting for. This technique consists of four tasks:

1. Strategic planning

2. Business model analysis

3. Defining and designing the process

4. Technical analysis for complex business solutions

Many industries, especially the IT industry, favor this technique because it’s a simple, straightforward way to present the steps of the execution process and show how it will operate in different roles.

2. Brainstorming

There’s nothing like good, old-fashioned brainstorming to generate new ideas, identify a problem’s root causes, and come up with solutions to complex business problems. Brainstorming is a group activity technique that is often used in other methods such as PESTLE and SWOT .

CATWOE identifies the leading players and beneficiaries, collecting the perceptions of different stakeholders onto one unified platform. Business analysts use this technique to thoroughly evaluate how any proposed action will affect the various parties. The acronym stands for:

• Customers: Who benefits from the business?
• Actors: Who are the players in the process?
• Transformation Process: What is the transformation at the core of the system?
• World View: What is the big picture, and what are its impacts?
• Owner: Who owns the impacted system, and what’s their relation?
• Environmental Constraints: What are the constraints, and how do they impact the solution?

4. MoSCoW (Must or Should, Could or Would)

MoSCoW prioritizes requirements by offering a framework that evaluates each demand relative to the rest. The process forces you to ask questions about the actual necessity of any given element. Is the item a must-have or a should-have? Is the demand something that could make the product better, or is it something that would be a good idea in the future?

5. MOST (Mission, Objectives, Strategies, and Tactics) Analysis

MOST is a robust business analysis framework—considered one of the best techniques for understanding an organization’s ability and purpose. This technique includes conducting a detailed, complete internal analysis of the organization’s goals and how to approach them. The acronym stands for:

• Mission: What is the organization’s purpose?
• Objectives: What are the key goals that help achieve the mission?
• Strategies: What are the options available for achieving the objectives?
• Tactics: What are the methods that the organization will follow to carry out the strategies?

6. PESTLE Analysis

Business analysts use the PESTLE model (sometimes called PEST) to identify environmental factors that can influence their company and how best to address them when making business decisions. Those influences are:

• Political: Financial support and subsidies, government initiatives, and policies.
• Economic: Labor and energy costs, inflation, and interest rates.
• Sociological: Education, culture, media, life, and population.
• Technological: New information and communication systems technologies.
• Legal: Local and national government regulations and employment standards.
• Environmental: Waste, recycling, pollution, and weather.

By analyzing and studying these factors, analysts gain a better understanding of how they will influence the organization’s narrative. This understanding, in turn, makes it easier for analysts to develop strategies on how to address them.

7. SWOT Analysis

One of the most popular techniques in the industry, SWOT identifies the strengths and weaknesses in a corporate structure, presenting them as opportunities and threats. The knowledge helps analysts make better decisions regarding resource allocation and suggestions for organizational improvement. The four elements of SWOT are:

• Strengths: The qualities of the project or business that give it an advantage over the competition.
• Weaknesses: Characteristics of the business that pose a disadvantage to the project or organization, when compared to the competition or even other projects.
• Opportunities: Elements present in the environment that the project or business could exploit.
• Threats: Elements in the environment that could hinder the project or business.

SWOT is a simple, versatile technique that is equally effective in either a quick or in-depth analysis of any sized organization. It is also useful for assessing other subjects, such as groups, functions, or individuals.

8. Six Thinking Hats

This business analysis process guides a group’s line of thinking by encouraging them to consider different ideas and perspectives. The ‘six hats’ are:

• White: Focuses on your data and logic.
• Red: Uses intuition, emotions, and gut feelings.
• Black: Consider potential negative results, and what can go wrong.
• Yellow: Focus on the positives; keep an optimistic point of view.
• Green: Uses creativity.
• Blue: Takes the big picture into account, process control.

The six thinking hats technique is often used in conjunction with brainstorming, serving as a means of directing the team’s mental processes and causing them to consider disparate viewpoints.

9. The 5 Whys

This technique is commonly found as often in Six Sigma as it is in business analysis circles. While journalism uses the “Five W’s” (Who, What, When, Where, and Why) in reporting, the 5 Whys technique just operates “Why” in a series of leading questions, this approach helps business analysts pinpoint a problem’s origin by first asking why the issue exists, then following it up by asking another “why?” question relating to the first answer, and so on. Here’s an example:

• Why? Because the wrong models were shipped.
• Why? Because the product information in the database was incorrect.
• Why? Because there are insufficient resources allocated to modernizing the database software.
• Why? Because our managers didn’t think the matter had priority.
• Why? Because no one was aware of how often this problem occurred.
• Countermeasure: Improve incident reporting, be sure managers read reports, allocate budget funds for modernizing database software.

10. Non-Functional Requirement Analysis

Analysts apply this technique to projects where a technology solution is replaced, changed, or built up from scratch. The analysis defines and captures the characteristics needed for a new or a modified system and most often deal with requirements such as data storage or performance. Non-functional requirement analysis usually covers:

• Performance
• Reliability

Non-Functional Requirement Analysis is commonly implemented during a project’s Analysis phase and put into action during the Design phase.

11. Design Thinking

Design Thinking is a business analysis technique that is primarily used for problem-solving and innovation. It's a human-centered approach that emphasizes empathy, collaboration, and creative thinking to develop solutions that meet user needs and create positive user experiences. Design Thinking is often employed to address complex, ambiguous, or user-centric problems by focusing on understanding the end-users' perspectives, motivations, and pain points.

If you’re looking for a more rewarding, better-paying career , you should consider business analysis. The higher demand for Business Analysts means security, marketability, and excellent financial gain. According to Salary.com , Business Analysts can earn a yearly average of USD 75,400. Simplilearn offers a Business Analysis Certification training course designed to make those first steps easier.

The Post Graduate Business Analysis program gives you expertise in the latest BA tools and techniques like the ones mentioned previously. You will master planning and monitoring, data analysis and statistics, visualizations, Agile Scrum methodologies, and SQL databases. The course supplements your training with real-world case studies and helps you become an AI-powered business analyst.

Our Business And Leadership Courses Duration And Fees

Business And Leadership Courses typically range from a few weeks to several months, with fees varying based on program and institution.

Get Free Certifications with free video courses

Business and Leadership

Business Analysis Basics

Data Science & Business Analytics

Business Intelligence Fundamentals

Learn from Industry Experts with free Masterclasses

From Concept to Market - How to Excel at Product Management in 2024 with SP Jain Program

Ascend the Product Management Career Ladder in 2024 with UC San Diego

Career Information Session: Find Out How to Become a Business Analyst with IIT Roorkee

Recommended Reads

The Complete Business Intelligence Tool Guide for the Modern Analyst

The Ultimate Guide To SWOT Analysis For Business And Why It Matters

Top 5 Business Intelligence Tools

Business Intelligence Career Guide: Your Complete Guide to Becoming a Business Analyst

What is Requirement Analysis: Overview, Applications, Techniques and Top Tools Used

A Holistic Look at Tesla SWOT Analysis

Get Affiliated Certifications with Live Class programs

• PMP, PMI, PMBOK, CAPM, PgMP, PfMP, ACP, PBA, RMP, SP, and OPM3 are registered marks of the Project Management Institute, Inc.

The 5 Steps in Problem Analysis

One technique that is extremely useful to gain a better understanding of the problems before determining a solution is problem analysis .

Problem analysis is the process of understanding real-world problems and user’s needs and proposing solutions to meet those needs. The goal of problem analysis is to gain a better understanding of the problem being solved before developing a solution.

There are five useful steps that can be taken to gain a better understanding of the problem before developing a solution.

• Gain agreement on the problem definition
• Understand the root-causes – the problem behind the problem
• Identify the stakeholders and the users
• Define the solution boundary
• Identify the constraints to be imposed on the solution

Table of Contents

Gain agreement on the problem definition.

The first step is to gain agreement on the definition of the problem to be solved. One of the simplest ways to gain agreement is to simply write the problem down and see whether everyone agrees.

Business Problem Statement Template

A helpful and standardised format to write the problem definition is as follows:

• The problem of – Describe the problem
• Affects – Identify stakeholders affected by the problem
• The results of which – Describe the impact of this problem on stakeholders and business activity
• Benefits of – Indicate the proposed solution and list a few key benefits

Example Business Problem Statement

There are many problems statement examples that can be found in different business domains and during the discovery when the business analyst is conducting analysis. An example business problem statement is as follows:

The problem of  having to manually maintain an accurate single source of truth for finance product data across the business, affects the finance department. The results of which has the impact of not having to have duplicate data, having to do workarounds and difficulty of maintaining finance product data across the business and key channels. A successful solution would  have the benefit of providing a single source of truth for finance product data that can be used across the business and channels and provide an audit trail of changes, stewardship and maintain data standards and best practices.

Understand the Root Causes Problem Behind the Problem

You can use a variety of techniques to gain an understanding of the real problem and its real causes. One such popular technique is root cause analysis, which is a systematic way of uncovering the root or underlying cause of an identified problem or a symptom of a problem.

Root cause analysis helps prevents the development of solutions that are focussed on symptoms alone .

To help identify the root cause, or the problem behind the problem, ask the people directly involved.

The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question “Why?” . Each answer forms the basis of the next question. The “five” in the name derives from an anecdotal observation on the number of iterations needed to resolve the problem .

Identify the Stakeholders and the Users

Effectively solving any complex problem typically involves satisfying the needs of a diverse group of stakeholders. Stakeholders typically have varying perspectives on the problem and various needs that must be addressed by the solution. So, involving stakeholders will help you to determine the root causes to problems.

Define the Solution Boundary

Once the problem statement is agreed to and the users and stakeholders are identified, we can turn our attention of defining a solution that can be deployed to address the problem.

Identify the Constraints  Imposed on Solution

We must consider the constraints that will be imposed on the solution. Each constraint has the potential to severely restrict our ability to deliver a solution as we envision it.

Some example solution constraints and considerations could be:-

• Economic – what financial or budgetary constraints are applicable?
• Environmental – are there environmental or regulatory constraints?
• Technical  – are we restricted in our choice of technologies?
• Political – are there internal or external political issues that affect potential solutions?

Conclusion – Problem Analysis

Try the five useful steps for problem solving when your next trying to gain a better understanding of the problem domain on your business analysis project or need to do problem analysis in software engineering.

The problem statement format can be used in businesses and across industries. 

Jerry Nicholas

Jerry continues to maintain the site to help aspiring and junior business analysts and taps into the network of experienced professionals to accelerate the professional development of all business analysts. He is a Principal Business Analyst who has over twenty years experience gained in a range of client sizes and sectors including investment banking, retail banking, retail, telecoms and public sector. Jerry has mentored and coached business analyst throughout his career. He is a member of British Computer Society (MBCS), International Institute of Business Analysis (IIBA), Business Agility Institute, Project Management Institute (PMI), Disciplined Agile Consortium and Business Architecture Guild. He has contributed and is acknowledged in the book: Choose Your WoW - A Disciplined Agile Delivery Handbook for Optimising Your Way of Working (WoW).

Recent Posts

Introduction to Train the Trainer for a Business Analyst

No matter the industry, modern professionals need to continuously improve themselves and work on up skilling and re-skilling to maintain satisfactory success within their field. This is particularly...

CliftonStrengths for a Business Analyst | Be You

Today, the job of a business analyst is probably more challenging than ever. The already intricate landscape of modern business analysis has recently gone through various shifts, mainly due to the...

• A Step-by-Step Guide to A3 Problem Solving Methodology
• Learn Lean Sigma
• Problem Solving

Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies.

A3 Problem solving is a structured and systematic approach to problem-solving that originated with the lean manufacturing methodology. It visualizes the problem-solving process using a one-page document known as an A3 report. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner.

A3 Problem Solving has numerous advantages, including improved communication, better decision-making, increased efficiency, and reduced waste. It is a powerful tool for businesses of all sizes and industries, and it is especially useful for solving complex and multi-faceted problems.

In this blog post, we will walk you through the A3 Problem Solving methodology step by step. Whether you are new to A3 Problem Solving or simply want to improve your skills, this guide will help you understand and apply the process in your workplace.

Table of Contents

What is a3 problem solving.

A3 Problem Solving is a structured and systematic approach to problem-solving that makes use of a one-page document called an A3 report to visually represent the process. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner. The method was created within the framework of the Lean manufacturing methodology and is based on the principles of continuous improvement and visual management.

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

A3 Problem Solving was developed by Toyota Motor Corporation and was first used in the manufacture of automobiles. The term “A3” refers to the size of the paper used to create the report, which is an ISO standard known as “A3”. The goal of the A3 report is to provide a visual representation of the problem-solving process that all members of the organisation can easily understand and share. A3 Problem Solving has been adopted by organisations in a variety of industries over the years, and it has become a widely used and recognised method for problem-solving.

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

• Define the problem clearly and concisely
• Gather and analyze data to gain a deep understanding of the problem
• Identify the root causes of the problem
• Develop and implement effective solutions
• Evaluate results and continuously improve

These principles serve as the foundation of the A3 Problem Solving methodology and are intended to assist organisations in continuously improving and achieving their objectives. Organizations can effectively solve problems, identify areas for improvement, and drive results by adhering to these principles.

Step 1: Define the Problem

Importance of clearly defining the problem.

The first step in the A3 Problem Solving process is critical because it lays the groundwork for the remaining steps. To define the problem clearly and accurately, you must first understand the problem and identify the underlying root cause. This step is critical because if the problem is not correctly defined, the rest of the process will be based on incorrect information, and the solution developed may not address the issue effectively.

The significance of defining the problem clearly cannot be overstated. It aids in the collection and analysis of relevant data, which is critical for developing effective solutions. When the problem is clearly defined, the data gathered is more relevant and targeted, resulting in a more comprehensive understanding of the issue. This will enable the development of solutions that are more likely to be effective because they are founded on a thorough and accurate understanding of the problem.

However, if the problem is not clearly defined, the data gathered may be irrelevant or incorrect, resulting in incorrect conclusions and ineffective solutions. Furthermore, the process of collecting and analysing data can become time-consuming and inefficient, resulting in resource waste. Furthermore, if the problem is not accurately defined, the solutions developed may fail to address the root cause of the problem, resulting in ongoing issues and a lack of improvement.

Techniques for Defining the Problem

The first step in the A3 Problem Solving process is to clearly and accurately define the problem. This is an important step because a clearly defined problem will help to ensure that the appropriate data is collected and solutions are developed. If the problem is not clearly defined, incorrect data may be collected, solutions that do not address the root cause of the problem, and time and resources may be wasted.

A problem can be defined using a variety of techniques, including brainstorming , root cause analysis , process mapping , and Ishikawa diagrams . Each of these techniques has its own advantages and disadvantages and can be used in a variety of situations depending on the nature of the problem.

Best Practice for Defining the Problem

In addition to brainstorming, root cause analysis, process mapping, and Ishikawa diagram s, best practices should be followed when defining a problem in A3 Problem Solving. Among these best practices are:

• Define the issue in a specific and quantifiable way: It is critical to be specific and concise when defining the problem, as well as to quantify the problem in terms of its impact. This will help to ensure that all stakeholders understand the problem and that data collection is focused on the right areas.
• Focus on the problem’s root cause: The A3 Problem Solving methodology is intended to assist organisations in identifying and addressing the root cause of a problem, rather than just the symptoms. Organizations can ensure that their solutions are effective and long-lasting by focusing on the root cause of the problem.
• Ascertain that all stakeholders agree on the problem’s definition: All stakeholders must agree on the definition of the problem for the A3 Problem Solving process to be effective. This ensures that everyone is working towards the same goal and that the solutions developed are relevant and appropriate.
• Consider the problem’s impact on the organisation and its stakeholders: It is critical to consider the impact of the problem on the organisation and its stakeholders when defining it. This will assist in ensuring that the appropriate data is gathered and that the solutions developed are relevant and appropriate.

Organizations can ensure that their problem is defined in a way that allows for effective data collection, analysis, and solution development by following these best practices. This will aid in the development of appropriate solutions and the effective resolution of the problem, resulting in improvements in the organization’s processes and outcomes.

Step 2: Gather Data

Gathering data in a3 problem solving.

Data collection is an important step in the A3 Problem Solving process because it allows organisations to gain a thorough understanding of the problem they are attempting to solve. This step entails gathering pertinent information about the problem, such as data on its origin, impact, and any related factors. This information is then used to help identify root causes and develop effective solutions.

One of the most important advantages of data collection in A3 Problem Solving is that it allows organisations to identify patterns and trends in data, which can be useful in determining the root cause of the problem. This information can then be used to create effective solutions that address the problem’s root cause rather than just its symptoms.

In A3 Problem Solving, data collection is a collaborative effort involving all stakeholders, including those directly impacted by the problem and those with relevant expertise or experience. Stakeholders can ensure that all relevant information is collected and that the data is accurate and complete by working together.

Overall, data collection is an important step in the A3 Problem Solving process because it serves as the foundation for effective problem-solving. Organizations can gain a deep understanding of the problem they are attempting to solve and develop effective solutions that address its root cause by collecting and analysing relevant data.

Data Collection Methods

In A3 Problem Solving, several data collection methods are available, including:

• Observations
• Process diagrams

The best data collection method will be determined by the problem being solved and the type of data required. To gain a complete understanding of the problem, it is critical to use multiple data collection methods.

Tools for Data Analysis and Visualization

Once the data has been collected, it must be analysed and visualised in order to gain insights into the problem. This process can be aided by the following tools:

• Excel Spreadsheets
• Flow diagrams
• Pareto diagrams
• Scatter Plots
• Control diagrams

These tools can assist in organising data and making it easier to understand. They can also be used to generate visual representations of data, such as graphs and charts, to communicate the findings to others.

Finally, the data collection and analysis step is an important part of the A3 Problem Solving process. Organizations can gain a better understanding of the problem and develop effective solutions by collecting and analysing relevant data.

Step 3: Identify Root Causes

Identifying the root causes of the problem is the third step in the A3 Problem Solving process. This step is critical because it assists organisations in understanding the root causes of a problem rather than just its symptoms. Once the underlying cause of the problem is identified, it can be addressed more effectively, leading to more long-term solutions.

Overview of the Root Cause Analysis Process

The process of determining the underlying causes of a problem is known as root cause analysis. This process can assist organisations in determining why a problem is occurring and what can be done to prevent it from recurring in the future. The goal of root cause analysis is to identify the underlying cause of a problem rather than just its symptoms, allowing it to be addressed more effectively.

To understand Root cause analysis in more detail check out RCA in our Lean Six Sigma Yellow Belt Course Root Cause Analysis section

Techniques for Identifying Root Causes

There are several techniques for determining the root causes of a problem, including:

• Brainstorming
• Ishikawa diagrams (also known as fishbone diagrams)
• Root Cause Tree Analysis

These methods can be used to investigate the issue in-depth and identify potential root causes. Organizations can gain a deeper understanding of the problem and identify the underlying causes that must be addressed by using these techniques.

Best Practices for Conducting Root Cause Analysis

It is critical to follow these best practices when conducting root cause analysis in A3 Problem Solving:

• Make certain that all stakeholders participate in the root cause analysis process.
• Concentrate on determining the root cause of the problem rather than just its symptoms.
• Take into account all potential root causes, not just the most obvious ones.
• To identify root causes, use a systematic approach, such as the 5 Whys or root cause tree analysis.

Organizations can ensure that root cause analysis is carried out effectively and that the root cause of the problem is identified by adhering to these best practises. This will aid in the development of appropriate solutions and the effective resolution of the problem.

Step 4: Develop Solutions

Developing solutions is the fourth step in the A3 Problem Solving process. This entails generating ideas and options for dealing with the problem, followed by selecting the best solution. The goal is to develop a solution that addresses the root cause of the problem and prevents it from recurring.

Solution Development in A3 Problem Solving

A3 solution development Problem solving is an iterative process in which options are generated and evaluated. The data gathered in the previous steps, as well as the insights and understanding gained from the root cause analysis, guide this process. The solution should be based on a thorough understanding of the problem and address the underlying cause.

Techniques for Developing Solutions

There are several techniques that can be used to develop solutions in A3 Problem Solving, including:

• Brainwriting
• Solution matrix
• Multi voting
• Force field analysis

These techniques can help to generate a range of options and to select the best solution.

Best Practice for Developing Solutions

It is critical to follow the following best practices when developing solutions in A3 Problem Solving:

• Participate in the solution development process with all stakeholders.
• Make certain that the solution addresses the underlying cause of the problem.
• Make certain that the solution is feasible and achievable.
• Consider the solution’s impact on the organisation and its stakeholders.

Organizations can ensure that the solutions they develop are effective and sustainable by adhering to these best practises. This will help to ensure that the problem is addressed effectively and that it does not reoccur.

Step 5: Implement Solutions

The final and most important step in the A3 Problem Solving methodology is solution implementation. This is the stage at which the identified and developed solutions are put into action to address the problem. This step’s goal is to ensure that the solutions are effective, efficient, and long-lasting.

The implementation Process

The implementation process entails putting the solutions developed in the previous step into action. This could include changes to processes, procedures, and systems, as well as employee training and education. To ensure that the solutions are effective, the implementation process should be well-planned and meticulously executed.

Techniques for Implementing Solutions

A3 Problem Solving solutions can be implemented using a variety of techniques, including:

• Piloting the solution on a small scale before broadening its application
• Participating in the implementation process with all relevant stakeholders
• ensuring that the solution is in line with the goals and objectives of the organisation
• Monitoring the solution to determine its effectiveness and make any necessary changes

Best Practice for Implementing Solutions

It is critical to follow these best practices when implementing solutions in A3 Problem Solving:

Make certain that all relevant stakeholders are involved and supportive of the solution. Have a clear implementation plan that outlines the steps, timeline, and resources required. Continuously monitor and evaluate the solution to determine its efficacy and make any necessary changes. Encourage all stakeholders to communicate and collaborate openly. Organizations can ensure that solutions are effectively implemented and problems are effectively addressed by adhering to these best practices. The ultimate goal is to find a long-term solution to the problem and improve the organization’s overall performance.

In conclusion, A3 Problem Solving is a comprehensive and structured methodology for problem-solving that can be applied in various industries and organisations. The A3 Problem Solving process’s five steps – Define the Problem, Gather Data, Identify Root Causes, Develop Solutions, and Implement Solutions – provide a road map for effectively addressing problems and making long-term improvements.

Organizations can improve their problem-solving skills and achieve better results by following the key principles, techniques, and best practices outlined in this guide. As a result, both the organisation and its stakeholders will benefit from increased efficiency, effectiveness, and satisfaction. So, whether you’re an experienced problem solver or just getting started, consider incorporating the A3 Problem Solving methodology into your work and start reaping the benefits right away.

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Free Lean Six Sigma Templates

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

The Evolution of 8D Problem-Solving: From Basics to Excellence

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

8D: Tools and Techniques

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

Plan Smarter, Grow Faster:

25% Off Annual Plans! Save Now

0 results have been found for “”

 Return to blog home

10 Step Process for Effective Business Problem Solving

Posted august 3, 2021 by harriet genever.

When you start a small business or launch a startup, the one thing you can count on is the unexpected. No matter how thoroughly you plan, forecast , and test, problems are bound to arise. This is why as an entrepreneur, you need to know how to solve business problems effectively.

What is problem solving in business?

Problem solving in business relates to establishing processes that mitigate or remove obstacles currently preventing you from reaching strategic goals . These are typically complex issues that create a gap between actual results and your desired outcome. They may be present in a single team, operational process, or throughout your entire organization, typically without an immediate or obvious solution. 

To approach problem solving successfully, you need to establish consistent processes that help you evaluate, explore solutions, prioritize execution, and measure success. In many ways, it should be similar to how you review business performance through a monthly plan review . You work through the same documentation, look for gaps, dig deeper to identify the root cause, and hash out options. Without this process, you simply cannot expect to solve problems efficiently or effectively. 

Why problem solving is important for your business

While some would say problem-solving comes naturally, it’s actually a skill you can grow and refine over time. Problem solving skills will help you and your team tackle critical issues and conflicts as they arise. It starts from the top. You as the business owner or CEO needing to display the type of level-headed problem solving that you expect to see from your employees.

Doing so will help you and your staff quickly deal with issues, establish and refine a problem solving process, turn challenges into opportunities, and generally keep a level head. Now, the best business leaders didn’t just find a magic solution to solve their problems, they built processes and leveraged tools to find success. And you can do the same.

By following this 10-step process, you can develop your problem-solving skills and approach any issue that arises with confidence. 

1. Define the problem

When a problem arises, it can be very easy to jump right into creating a solution. However, if you don’t thoroughly examine what led to the problem in the first place, you may create a strategy that doesn’t actually solve it. You may just be treating the symptoms.

For instance, if you realize that your sales from new customers are dropping, your first inclination might be to rush into putting together a marketing plan to increase exposure. But what if decreasing sales are just a symptom of the real problem? 

When you define the problem, you want to be sure you’re not missing the forest for the trees. If you have a large issue on your hands, you’ll want to look at it from several different angles:

Competition 

Is a competitor’s promotion or pricing affecting your sales? Are there new entrants in your market? How are they marketing their product or business?

Business model 

Is your business model sustainable? Is it realistic for how fast you want to grow? Should you explore different pricing or cost strategies?

Market factors

How are world events and the nation’s economy affecting your customers and your sales?

Are there any issues affecting your team? Do they have the tools and resources they need to succeed? 

Goal alignment 

Is everyone on your team working toward the same goal ? Have you communicated your short-term and long-term business goals clearly and often?

There are a lot of ways to approach the issue when you’re facing a serious business problem. The key is to make sure you’re getting a full snapshot of what’s going on so you don’t waste money and resources on band-aid solutions. 

Going back to our example, by looking at every facet of your business, you may discover that you’re spending more on advertising than your competitors already. And instead, there’s a communication gap within your team that’s leading to the mishandling of new customers and therefore lost sales. 

If you jumped into fixing the exposure of your brand, you would have been dumping more money into an area you’re already winning. Potentially leading to greater losses as more and more new customers are dropped due to poor internal communication.

This is why it’s so vital that you explore your blind spots and track the problem to its source.

2. Conduct a SWOT analysis

All good businesses solve some sort of problem for customers. What if your particular business problem is actually an opportunity, or even a strength if considered from a different angle? This is when you’d want to conduct a SWOT analysis to determine if that is in fact the case.

SWOT is a great tool for strategic planning and bringing multiple viewpoints to the table when you’re looking at investing resources to solve a problem. This may even be incorporated in your attempts to identify the source of your problem, as it can quickly outline specific strengths and weaknesses of your business. And then by identifying any potential opportunities or threats, you can utilize your findings to kickstart a solution. 

3. Identify multiple solutions with design thinking

As you approach solving your problem, you may want to consider using the design thinking approach . It’s often used by organizations looking to solve big, community-based problems. One of its strengths is that it requires involving a wide range of people in the problem-solving process. Which leads to multiple perspectives and solutions arising.

This approach—applying your company’s skills and expertise to a problem in the market—is the basis for design thinking.

It’s not about finding the most complex problems to solve, but about finding common needs within the organization and in the real world and coming up with solutions that fit those needs. When you’re solving business problems, this applies in the sense that you’re looking for solutions that address underlying issues—you’re looking at the big picture.

4. Conduct market research and customer outreach

Market research and customer outreach aren’t the sorts of things small business owners and startups can do once and then cross off the list. When you’re facing a roadblock, think back to the last time you did some solid market research or took a deep dive into understanding the competitive landscape .

Market research and the insights you get from customer outreach aren’t a silver bullet. Many companies struggle with what they should do with conflicting data points. But it’s worth struggling through and gathering information that can help you better understand your target market . Plus, your customers can be one of the best sources of criticism. It’s actually a gift if you can avoid taking the negatives personally .

The worst thing you can do when you’re facing challenges is isolating yourself from your customers and ignore your competition. So survey your customers. Put together a competitive matrix . 

5. Seek input from your team and your mentors

Don’t do your SWOT analysis or design thinking work by yourself. The freedom to express concerns, opinions, and ideas will allow people in an organization to speak up. Their feedback is going to help you move faster and more efficiently. If you have a team in place, bring them into the discussion. You hired them to be experts in their area; use their expertise to navigate and dig deeper into underlying causes of problems and potential solutions.

If you’re running your business solo, at least bring in a trusted mentor. SCORE offers a free business mentorship program if you don’t already have one. It can also be helpful to connect with a strategic business advisor , especially if business financials aren’t your strongest suit.

Quoting Stephen Covey, who said that “strength lies in differences, not in similarities,” speaking to the importance of diversity when it comes to problem-solving in business. The more diverse a team is , the more often innovative solutions to the problems faced by the organization appear.

In fact, it has been found that groups that show greater diversity were better at solving problems than groups made up specifically of highly skilled problem solvers. So whoever you bring in to help you problem-solve, resist the urge to surround yourself with people who already agree with you about everything.

6. Apply lean planning for nimble execution

So you do your SWOT analysis and your design thinking exercise. You come up with a set of strong, data-driven ideas. But implementing them requires you to adjust your budget, or your strategic plan, or even your understanding of your target market.

Are you willing to change course? Can you quickly make adjustments? Well in order to grow, you can’t be afraid to be nimble . 

By adopting the lean business planning method —the process of revising your business strategy regularly—you’ll be able to shift your strategies more fluidly. You don’t want to change course every week, and you don’t want to fall victim to shiny object thinking. But you can strike a balance that allows you to reduce your business’s risk while keeping your team heading in the right direction.

Along the way, you’ll make strategic decisions that don’t pan out the way you hoped. The best thing you can do is test your ideas and iterate often so you’re not wasting money and resources on things that don’t work. That’s Lean Planning .

7. Model different financial scenarios

When you’re trying to solve a serious business problem, one of the best things you can do is build a few different financial forecasts so you can model different scenarios. You might find that the idea that seemed the strongest will take longer than you thought to reverse a negative financial trend. At the very least you’ll have better insight into the financial impact of moving in a different direction.

The real benefit here is looking at different tactical approaches to the same problem. Maybe instead of increasing sales right now, you’re better off in the long run if you adopt a strategy to reduce churn and retain your best customers. You won’t know unless you model a few different scenarios. You can do this by using spreadsheets, and a tool like LivePlan can make it easier and quicker.

8. Watch your cash flow

While you’re working to solve a challenging business problem, pay particular attention to your cash flow and your cash flow forecast . Understanding when your company is at risk of running out of cash in the bank can help you be proactive. It’s a lot easier to get a line of credit while your financials still look good and healthy, than when you’re one pay period away from ruin.

If you’re dealing with a serious issue, it’s easy to start to get tunnel vision. You’ll benefit from maintaining a little breathing room for your business as you figure out what to do next.

9. Use a decision-making framework

Once you’ve gathered all the information you need, generated a number of ideas, and done some financial modeling, you might still feel uncertain. It’s natural—you’re not a fortune-teller. You’re trying to make the best decision you can with the information you have.

This article offers a really useful approach to making decisions. It starts with putting your options into a matrix like this one:

Use this sort of framework to put everything you’ve learned out on the table. If you’re working with a bigger team, this sort of exercise can also bring the rest of your team to the table so they feel some ownership over the outcome.

10. Identify key metrics to track

How will you know your problem is solved? And not just the symptom—how will you know when you’ve addressed the underlying issues? Before you dive into enacting the solution, make sure you know what success looks like.

Decide on a few key performance indicators . Take a baseline measurement, and set a goal and a timeframe. You’re essentially translating your solution into a plan, complete with milestones and goals. Without these, you’ve simply made a blind decision with no way to track success. You need those goals and milestones to make your plan real .

Problem solving skills to improve

As you and your team work through this process, it’s worth keeping in mind specific problem solving skills you should continue to develop. Bolstering your ability, as well as your team, to solve problems effectively will only make this process more useful and efficient. Here are a few key skills to work on.

Emotional intelligence

It can be very easy to make quick, emotional responses in a time of crisis or when discussing something you’re passionate about. To avoid making assumptions and letting your emotions get the best of you, you need to focus on empathizing with others. This involves understanding your own emotional state, reactions and listening carefully to the responses of your team. The more you’re able to listen carefully, the better you’ll be at asking for and taking advice that actually leads to effective problem solving.

Jumping right into a solution can immediately kill the possibility of solving your problem. Just like when you start a business , you need to do the research into what the problem you’re solving actually is. Luckily, you can embed research into your problem solving by holding active reviews of financial performance and team processes. Simply asking “What? Where? When? How?” can lead to more in-depth explorations of potential issues.

The best thing you can do to grow your research abilities is to encourage and practice curiosity. Look at every problem as an opportunity. Something that may be trouble now, but is worth exploring and finding the right solution. You’ll pick up best practices, useful tools and fine-tune your own research process the more you’re willing to explore.

Brainstorming

Creatively brainstorming with your team is somewhat of an art form. There needs to be a willingness to throw everything at the wall and act as if nothing is a bad idea at the start. This style of collaboration encourages participation without fear of rejection. It also helps outline potential solutions outside of your current scope, that you can refine and turn into realistic action.

Work on breaking down problems and try to give everyone in the room a voice. The more input you allow, the greater potential you have for finding the best solution.

Decisiveness

One thing that can drag out acting upon a potential solution, is being indecisive. If you aren’t willing to state when the final cutoff for deliberation is, you simply won’t take steps quickly enough. This is when having a process for problem solving comes in handy, as it purposefully outlines when you should start taking action.

Work on choosing decision-makers, identify necessary results and be prepared to analyze and adjust if necessary. You don’t have to get it right every time, but taking action at the right time, even if it fails, is almost more vital than never taking a step.  

Stemming off failure, you need to learn to be resilient. Again, no one gets it perfect every single time. There are so many factors in play to consider and sometimes even the most well-thought-out solution doesn’t stick. Instead of being down on yourself or your team, look to separate yourself from the problem and continue to think of it as a puzzle worth solving. Every failure is a learning opportunity and it only helps you further refine and eliminate issues in your strategy.

Problem solving is a process

The key to effective problem-solving in business is the ability to adapt. You can waste a lot of resources on staying the wrong course for too long. So make a plan to reduce your risk now. Think about what you’d do if you were faced with a problem large enough to sink your business. Be as proactive as you can.

Editor’s note: This article was originally published in 2016. It was updated in 2021.

Like this post? Share with a friend!

Harriet Genever

Posted in management, join over 1 million entrepreneurs who found success with liveplan, like this content sign up to receive more.

Subscribe for tips and guidance to help you grow a better, smarter business.

You're all set!

Exciting business insights and growth strategies will be coming your way each month.

We care about your privacy. See our privacy policy .

• SUGGESTED TOPICS
• The Magazine
• Newsletters
• Managing Yourself
• Managing Teams
• Work-life Balance
• The Big Idea
• Data & Visuals
• Reading Lists
• Case Selections
• HBR Learning
• Topic Feeds
• Account Settings
• Email Preferences

Is Your AI-First Strategy Causing More Problems Than It’s Solving?

• Oguz A. Acar

Consider a more balanced and thoughtful approach to AI transformation.

The problem with an AI-first strategy lies not within the “AI” but with the notion that it should come “first” aspect. An AI-first approach can be myopic, potentially leading us to overlook the true purpose of technology: to serve and enhance human endeavors. Instead, the author recommends following 3Ps during an AI transformation: problem-centric, people-first, and principle-driven.

From technology giants like Google to major management consultants like McKinsey , a rapidly growing number of companies preach an “AI-first” strategy. In essence, this means considering AI as the ultimate strategic priority , one that precedes other alternative directions. At first glance, this strategy seems logical, perhaps even inevitable. The figures speak for themselves: the sheer volume of investment flowing into AI technologies shows the confidence levels in an increasingly AI-driven future.

• Oguz A. Acar is a Chair in Marketing at King’s Business School, King’s College London.

Partner Center

Empowering Problem-solving in Computer Science: A Need Analysis for a Computational Thinking Mobile Learning Application

• Mimi Zairul Mohmad Fuzi
• Wan Ahmad Jaafar Wan Yahaya

The advancement of digital technology has revolutionized education across all levels, giving rise to digital learning as a novel pedagogical environment. Among the subjects at the forefront of this transformation is computer science, introduced in matriculation colleges to supplant traditional information technology courses. However, computer science poses inherent complexity, demanding abstract thinking and diverse problem-solving methodologies. Computational thinking (CT) emerges as a promising approach to address these challenges, recognized as a vital skillset for fostering innovation in digital technology among students. The ubiquity of smartphones and mobile internet facilitates the adoption of mobile learning, offering students the flexibility to access educational content anytime, anywhere. Consequently, this need analysis study aims to assess current teaching practices in computer science and identify the need for mobile learning applications that integrate CT as a problem-solving technique among matriculation college students. Interviews with three computer science lecturers revealed a reliance on conventional pedagogy with limited blended learning approaches through college portals. Notably, specific techniques for imparting programming problem-solving skills were lacking. Nonetheless, it is noteworthy that all instructors recognized the considerable potential of mobile learning applications in effectively engaging students and facilitating the development of problem-solving proficiency.

• EndNote - EndNote format (Macintosh & Windows)
• ProCite - RIS format (Macintosh & Windows)
• Reference Manager - RIS format (Windows only)

Full Paper Template

Publication Fees

Article Processing Charge (APC)

• For Readers
• For Authors
• For Librarians

Asian Scholars Network (002903215-H) Website:  https://asianscholarsnetwork.com/ Email: [email protected] Facebook: Asian Scholars Network