define problem solving in the context of a project

Project Management

Home » Free Resources » »

What Is Problem Solving in Project Management? Here’s Everything You Need to Know

Written by Contributing Writer
Updated on August 4, 2023

In project management , problem-solving is a crucial and necessary skill. Whether you have failed to consider every possible factor impacting a project, a problem arises through no fault of your own, or conditions change that create issues, problems must be addressed promptly to keep projects on track.

In this article, we will define problem-solving and how it impacts projects, provide real-world examples of problem-solving, and give you a structured, step-by-step process to solve problems. We’ll also show you how earning a project management certification can help you gain practical experience in problem-solving methods.

What Is Problem-Solving?

Problem-solving is a process to identify roadblocks or defects that arise during a project. A structured system to define problems, identify root causes, brainstorm and test solutions, and monitor results can affect change to improve performance and overcome challenges.

Effective problem-solving enables teams to deal with uncertainties or gaps in planning to minimize the impact on outcomes.

The Importance of Problem-Solving in Project Management

During a project and operation, problems can arise at any time. You may find that your planning before launching a product, for example, did not consider all the factors that impact results. You may find that you were too optimistic about project timelines, performance, or workforce. Or, as many of us discovered over the past few years, supply chain disruption may make even the best project plans obsolete.

Regardless, your job is identifying, solving, and overcoming these problems. Project managers must be skilled in leading team members through a structured approach to resolving problems.

Proactive problem-solving requires careful consideration of all the variables in a project, including preparation to:

Achieve project objectives
Address obstacles before they arise
Manage project risks and contingency plans
Manage communication and collaboration
Provide a framework for time and cost management
Provide a pathway for continuous improvement

Also Read: 10 Tips on How to Increase Productivity in the Workplace

Problem-Solving Steps in Project Management

While the process you choose to solve problems may vary, here is a seven-step framework many project managers use. This problem-solving method combines primary and secondary problem-solving steps.

#1. Define the Problem

Gather data and information from key stakeholders, team members, and project documentation. Include any relevant reporting or data analysis
Itemized key details, such as a description of the problem, timelines, outcomes, and impact
Frame the issue as a problem statement

A good example of a problem statement might be: An unexpected demand spike has exceeded our current production capacity. How can we still meet customer deadlines for delivery?

#2. Analyze Root Causes

Break down issues into smaller components to diagnose bottlenecks or problems
Identify the organizational, mechanical, environmental, or operational factors that contribute
Distinguish between one-time issues vs. systematic, ongoing areas that need improvement

When analyzing root causes, it’s common to find multiple factors contributing to a problem. As such, it is essential to prioritize issues that have the most significant impact on outcomes.

#3. Brainstorm Potential Solutions

Holding specific sessions focused on brainstorming ideas to resolve root causes
Build on ideas or suggest combinations or iterations
Categorize solutions by types, such as process or input changes, adding additional resources, outsourcing, etc.)

In brainstorming, you should refrain from immediately analyzing suggestions to keep ideas coming.

#4. Evaluate Potential Solutions

Reframe the problem and concern for team members, providing a framework for evaluation such as cost, timing, and feasibility
With ideas in hand, it is time to evaluate potential solutions. Project managers often employ strategies such as weighted scoring models to rank ideas.
Consider the pros and cons in relation to project objectives

As you narrow the list, getting additional insight from subject matter experts to evaluate real-world viability is helpful. For example, if you are proposing a process change in operating a machine, get feedback from skilled operators before implementing changes.

#5. Decide on a Plan of Action

Make a decision on which course of action you want to pursue and make sure the solution aligns with your organizational goals
Create an action plan to implement the changes, including key milestones
Assign project ownership, deadlines, resources, and budgets

Defining what outcomes you need to achieve to declare success is also essential. Are you looking for incremental change or significant improvements, and what timeline are you establishing for measurement?

#6. Implement the Action Plan

Communicate the plan with key stakeholders
Provide any training associated with the changes
Allocate resources necessary for implementation

As part of the action plan, you will also want to detail the measures and monitoring you will put in place to assess process outcomes.

#7. Monitor and Track Results

Track solution performance against the action plan and key milestones
Solicit feedback from the project team on problem-solving effectiveness
Ensure the solution resolves the root cause, creating the desired results without negatively impacting other areas of the operation

You should refine results or start the process over again to increase performance. For example, you may address the root cause but find a need for secondary problem-solving in project management, focusing on other factors.

These problem-solving steps are used repeatedly in lean management and Six Sigma strategies for continuous improvement.

Also Read: 5 Project Management Steps You Need to Know

How Project Management Tools Can Help You in Problem-Solving

Project management software can guide teams through problem-solving, acting as a central repository to provide visibility into the stages of a project.

The best project management software will include the following:

Issue tracking to capture problems as they arise
Chat and real-time collaboration for discussion and brainstorming
Templates for analysis, such as fishbone diagrams
Action plans, assigning tasks, ownership, and accountability
Dashboards for updates to monitor solutions
Reporting on open issues, mitigation, and resolution

Examples of Problem-Solving

Here are some examples of the problem-solving process demonstrating how team members can work through the process to achieve results.

Sign-ups for a New Software Solution Were Well Below First-Month Targets

After analyzing the data, a project team identifies the root cause as inefficient onboarding and account configurations. They then brainstorm solutions. Ideas include re-architecting the software, simplifying onboarding steps, improving the initial training and onboarding process, or applying additional resources to guide customers through the configuration process.

After weighing alternatives, the company invests in streamlining onboarding and developing software to automate configuration.

A Project Was at Risk of Missing a Hard Deadline Due to Supplier Delays

In this case, you already know the root cause: Your supplier cannot deliver the necessary components to complete the project on time. Brainstorming solutions include finding alternative sources for components, considering project redesigns to use different (available) components, negotiating price reductions with customers due to late delivery, or adjusting the scope to complete projects without this component.

After evaluating potential solutions, the project manager might negotiate rush delivery with the original vendor. While this might be more expensive, it enables the business to meet customer deadlines. At the same time, project schedules might be adjusted to account for later-than-expected part delivery.

A Construction Project Is Falling Behind Due to Inclement Weather

Despite months of planning, a major construction project has fallen behind schedule due to bad weather, preventing concrete and masonry work. The problem-solving team brainstorms the problem and evaluates solutions, such as constructing temporary protection from the elements, heating concrete to accelerate curing, and bringing on additional crews once the weather clears.

The project team might decide to focus on tasks not impacted by weather earlier in the process than expected to postpone exterior work until the weather clears.

Also Read: Understanding KPIs in Project Management

Improve Your Problem-Solving and Project Management Skills

This project management course delivered by Simpliearn, in collaboration wiht the University of Massachusetts, can boost your career journey as a project manager. This 24-week online bootcamp aligns with Project Management Institute (PMI) practices, the Project Management Professional (PMP®) certification, and IASSC-Lean Six Sigma.

This program teaches skills such as:

Agile management
Customer experience design
Design thinking
Digital transformation
Lean Six Sigma Green Belt

You might also like to read:

5 Essential Project Management Steps You Need to Know

Project Management Frameworks and Methodologies Explained

13 Key Project Management Principles and How to Use Them

Project Management Phases: A Full Breakdown

How To Develop a Great Project Management Plan in 2023

What is Project Resource Management? Everything You Need to Know

If you’re asking, “What is project resource management,” and want to learn the tools, techniques, and best practices involved, our comprehensive guide covers everything you need.

Best Apps for Project Management You Should Know in 2024

Every project needs a manager, especially in today’s fast-paced digital world. And every project manager needs tools to manage projects. Learn about some of the best project management apps you can choose from today in this blog.

20 Best Practices in Project Management [2024 Guide]

Explore our guide to the top best practices in project management. Strengthen your foundation and take your career to new heights.

How to Measure Project Success? A 2024 Guide

One person’s definition of success can vary wildly from another’s. That’s why project managers need definitive ways to measure project success. This article will share tips, best practices, and methods to determine whether you are hitting the mark.

Remote Project Management: How to Manage Remote Teams Effectively

Remote working became a harsh reality during the COVID-19 pandemic. Yet, many employers and their employees adapted to it quickly and still prefer it, making remote project management an essential skill for professionals.

What are Project Management Skills? Here are Top Skills You should Know in 2024

Here are the top project management skills you will need to master project management in 2024. This article will help you get started with both hard and soft skills.

Project Management Bootcamp

Learning Format

Online Bootcamp

Program benefits.

25 in-demand tools covered
Aligned with PMI-PMP® and IASSC-Lean Six Sigma
Masterclasses from top faculty of UMass Amherst
UMass Amherst Alumni Association membership

Become a Project Manager
Certification

Problem Solving Techniques for Project Managers

Learn which problem solving techniques and strategies can help you effectively handle the challenges you face in your projects.

Problem Solving Techniques: A 5-Step Approach

Some problems are small and can be resolved quickly. Other problems are large and may require significant time and effort to solve. These larger problems are often tackled by turning them into formal projects.

"A project is a problem scheduled for solution."

- Joseph M. Juran

Problem Solving is one of the Tools & Techniques used for Managing Quality and Controlling Resources.

Modules 8 and 9 of the PM PrepCast cover Project Quality Management and Project Resource Management.

Consider this study program if you're preparing to take your CAPM or PMP Certification exam.

Disclosure: I may receive a commission if you purchase the PM PrepCast with this link.

Whether the problem you are focusing on is small or large, using a systematic approach for solving it will help you be a more effective project manager.

This approach defines five problem solving steps you can use for most problems...

Define the Problem

Determine the causes, generate ideas, select the best solution, take action.

The most important of the problem solving steps is to define the problem correctly. The way you define the problem will determine how you attempt to solve it.

For example, if you receive a complaint about one of your project team members from a client, the solutions you come up with will be different based on the way you define the problem.

If you define the problem as poor performance by the team member you will develop different solutions than if you define the problem as poor expectation setting with the client.

Once you have defined the problem, you are ready to dig deeper and start to determine what is causing it. You can use a fishbone diagram to help you perform a cause and effect analysis.

If you consider the problem as a gap between where you are now and where you want to be, the causes of the problem are the obstacles that are preventing you from closing that gap immediately.

This level of analysis is important to make sure your solutions address the actual causes of the problem instead of the symptoms of the problem. If your solution fixes a symptom instead of an actual cause, the problem is likely to reoccur since it was never truly solved.

Once the hard work of defining the problem and determining its causes has been completed, it's time to get creative and develop possible solutions to the problem.

Two great problem solving methods you can use for coming up with solutions are brainstorming and mind mapping .

After you come up with several ideas that can solve the problem, one problem solving technique you can use to decide which one is the best solution to your problem is a simple trade-off analysis .

To perform the trade-off analysis, define the critical criteria for the problem that you can use to evaluate how each solution compares to each other. The evaluation can be done using a simple matrix. The highest ranking solution will be your best solution for this problem.

define problem solving in the context of a project

Pass your PMP Exam!

The PM Exam Simulator is an online exam simulator.

Realistic exam sample questions so you can pass your CAPM or PMP Certification exam.

Disclosure: I may receive a commission if you purchase the PM Exam Simulator with this link.

Once you've determined which solution you will implement, it's time to take action. If the solution involves several actions or requires action from others, it is a good idea to create an action plan and treat it as a mini-project.

Using this simple five-step approach can increase the effectiveness of your problem solving skills .

For more problem solving strategies and techniques, subscribe to my newsletter below.

Do You Want More Project Management Tips?

Subscribe to Project Success Tips , my FREE Project Management Newsletter where I share tips and techniques that you can use to get your Project Management Career off to a great start .

As a BONUS for signing up, you'll receive access to my Subscribers Only Download Page ! This is where you can download my " Become A Project Manager Checklist " and other project management templates.

Don't wait...

Become a PM
Problem Solving Techniques

New! Comments

Home Privacy Policy About Contact

Project-Management-Skills.com

An Introduction to Problem Solving in Project Management

5 Steps to Identify and Eliminate Project-Halting Problems

Problem solving is a process for analysing a problem, and then developing and executing a solution. It is a task at which project managers must excel. There are many techniques that can be used for problem solving. The nature of the problem determines which is selected.

In this article, I describe a five-step process for problem solving that provides a systematic approach and helps improve the effectiveness of project management.

Step #1: Define the Problem

If you don’t understand the nature of the problem, then you cannot develop a sustainable solution.

For example, let’s say that a project team continuously misses deadlines. You may believe that the problem is caused by poor performance. On the other hand, the deadlines set may be too restrictive. The nature of the problem will determine the approach you take to solving it.

Step #2: Discover the Causes

Once you understand the problem, you can analyse it more deeply to discover the cause. The cause of a problem acts as a barrier to achieving your goals. Only by analysing the problem and determining the cause can you move to the next step in developing a solution.

It is important not to confuse cause with symptoms. If you only treat the symptoms, the underlying cause remains and will create more problems in the future.

Step #3: Develop Ideas for Solutions

Now it’s time to develop ideas to solve the problem. The wider the range of ideas, the more likely you are to choose a solution that is achievable and actionable.

This step is often achieved through a brainstorming process.

Step #4: Solution Selection

Of course, the point of developing a range of ideas for solutions is to ensure that the best is selected. One way to do this would be to conduct a trade-off analysis.

To do this, you must define the criteria for deciding which solution is best, usually as a series of weighted pros and cons. For each potential solution, the pros and cons are listed and its ranking is scored. The solution with the best ranking is the one that is selected.

Step #5: Put the Solution into Action

Having determined which is the solution of choice, the project manager should develop an action plan. This should include resources needed, budget, timetables, and all those involved. The solution is often run as a mini-project.

Despite PRINCE2’s framework and planning process – which seeks to anticipate risks and problems so that mitigating action can be taken ahead of potential problems becoming issues – all projects may suffer from unforeseen events and circumstances.

This five-step process for problem solving will increase a project manager’s capability to handle problems should they arise during a project – and project managers who react swiftly and decisively to problems have greater success in delivering expected project outcomes.

In our next article, I discuss several techniques which might be used to run effective problem-solving meetings in project management. In the meantime, for project management and project management training that motivates your employees, contact Your Project Manager:

On-Site Project Management Training/Coaching
PRINCE2® Training and Implementation in Brisbane
PMBOK Training

What can we help you with?

Problem solving

Regular task for project managers.

Problem solving is a basic task for the project management . It is a process for developing and applying a solution for the occurred problems. The probability of the success rises, if a particular method is implemented to the project work. The problem solving can be described in the following steps. First of all it is necessary to determine the actual status or problem definition. The next step is the applying of the solution process. And the last step is the achievement of the wanted actual status.

First, a clear picture of the situation to be changed is necessary. It should be thereby clearly defined, which objective should be achieved. And the question is: “Why this project is to be performed; which objective it serves?” The initial situation, objects, purpose and scenario of the project are to be analyzed to answer this question and to define therefore the project. The initial situation illustrates the project situation. The project purpose places the project in the subordinated context. The object description enables project measurability and transparency of the target tracking. The scenario or project structure plan divides the whole project into work packages to effectively accomplish project objects.

Would you like to receive regular info on project management topics?

Key has already been sent, account limit exceeded, project management newsletter, read more about project management on our blog, our project management software inloox helps you to make a success of your project the fast, easy and secure way, other terms.

Problem Solving Skills for the Digital Age

Lucid Content

Reading time: about 6 min

Let’s face it: Things don’t always go according to plan. Systems fail, wires get crossed, projects fall apart.

Problems are an inevitable part of life and work. They’re also an opportunity to think critically and find solutions. But knowing how to get to the root of unexpected situations or challenges can mean the difference between moving forward and spinning your wheels.

Here, we’ll break down the key elements of problem solving, some effective problem solving approaches, and a few effective tools to help you arrive at solutions more quickly.

So, what is problem solving?

Broadly defined, problem solving is the process of finding solutions to difficult or complex issues. But you already knew that. Understanding problem solving frameworks, however, requires a deeper dive.

Think about a recent problem you faced. Maybe it was an interpersonal issue. Or it could have been a major creative challenge you needed to solve for a client at work. How did you feel as you approached the issue? Stressed? Confused? Optimistic? Most importantly, which problem solving techniques did you use to tackle the situation head-on? How did you organize thoughts to arrive at the best possible solution?

Solve your problem-solving problem

Here’s the good news: Good problem solving skills can be learned. By its nature, problem solving doesn’t adhere to a clear set of do’s and don’ts—it requires flexibility, communication, and adaptation. However, most problems you face, at work or in life, can be tackled using four basic steps.

First, you must define the problem . This step sounds obvious, but often, you can notice that something is amiss in a project or process without really knowing where the core problem lies. The most challenging part of the problem solving process is uncovering where the problem originated.

Second, you work to generate alternatives to address the problem directly. This should be a collaborative process to ensure you’re considering every angle of the issue.

Third, you evaluate and test potential solutions to your problem. This step helps you fully understand the complexity of the issue and arrive at the best possible solution.

Finally, fourth, you select and implement the solution that best addresses the problem.

Following this basic four-step process will help you approach every problem you encounter with the same rigorous critical and strategic thinking process, recognize commonalities in new problems, and avoid repeating past mistakes.

In addition to these basic problem solving skills, there are several best practices that you should incorporate. These problem solving approaches can help you think more critically and creatively about any problem:

You may not feel like you have the right expertise to resolve a specific problem. Don’t let that stop you from tackling it. The best problem solvers become students of the problem at hand. Even if you don’t have particular expertise on a topic, your unique experience and perspective can lend itself to creative solutions.

Challenge the status quo

Standard problem solving methodologies and problem solving frameworks are a good starting point. But don’t be afraid to challenge assumptions and push boundaries. Good problem solvers find ways to apply existing best practices into innovative problem solving approaches.

Think broadly about and visualize the issue

Sometimes it’s hard to see a problem, even if it’s right in front of you. Clear answers could be buried in rows of spreadsheet data or lost in miscommunication. Use visualization as a problem solving tool to break down problems to their core elements. Visuals can help you see bottlenecks in the context of the whole process and more clearly organize your thoughts as you define the problem.

Hypothesize, test, and try again

It might be cliche, but there’s truth in the old adage that 99% of inspiration is perspiration. The best problem solvers ask why, test, fail, and ask why again. Whether it takes one or 1,000 iterations to solve a problem, the important part—and the part that everyone remembers—is the solution.

Consider other viewpoints

Today’s problems are more complex, more difficult to solve, and they often involve multiple disciplines. They require group expertise and knowledge. Being open to others’ expertise increases your ability to be a great problem solver. Great solutions come from integrating your ideas with those of others to find a better solution. Excellent problem solvers build networks and know how to collaborate with other people and teams. They are skilled in bringing people together and sharing knowledge and information.

4 effective problem solving tools

As you work through the problem solving steps, try these tools to better define the issue and find the appropriate solution.

Root cause analysis

Similar to pulling weeds from your garden, if you don’t get to the root of the problem, it’s bound to come back. A root cause analysis helps you figure out the root cause behind any disruption or problem, so you can take steps to correct the problem from recurring. The root cause analysis process involves defining the problem, collecting data, and identifying causal factors to pinpoint root causes and arrive at a solution.

Less structured than other more traditional problem solving methods, the 5 Whys is simply what it sounds like: asking why over and over to get to the root of an obstacle or setback. This technique encourages an open dialogue that can trigger new ideas about a problem, whether done individually or with a group. Each why piggybacks off the answer to the previous why. Get started with the template below—both flowcharts and fishbone diagrams can also help you track your answers to the 5 Whys.

Brainstorming

A meeting of the minds, a brain dump, a mind meld, a jam session. Whatever you call it, collaborative brainstorming can help surface previously unseen issues, root causes, and alternative solutions. Create and share a mind map with your team members to fuel your brainstorming session.

Gap analysis

Sometimes you don’t know where the problem is until you determine where it isn’t. Gap filling helps you analyze inadequacies that are preventing you from reaching an optimized state or end goal. For example, a content gap analysis can help a content marketer determine where holes exist in messaging or the customer experience. Gap analysis is especially helpful when it comes to problem solving because it requires you to find workable solutions. A SWOT analysis chart that looks at a problem through the lens of strengths, opportunities, opportunities, and threats can be a helpful problem solving framework as you start your analysis.

A better way to problem solve

Beyond these practical tips and tools, there are myriad methodical and creative approaches to move a project forward or resolve a conflict. The right approach will depend on the scope of the issue and your desired outcome.

Depending on the problem, Lucidchart offers several templates and diagrams that could help you identify the cause of the issue and map out a plan to resolve it. Learn more about how Lucidchart can help you take control of your problem solving process .

Lucidchart, a cloud-based intelligent diagramming application, is a core component of Lucid Software's Visual Collaboration Suite. This intuitive, cloud-based solution empowers teams to collaborate in real-time to build flowcharts, mockups, UML diagrams, customer journey maps, and more. Lucidchart propels teams forward to build the future faster. Lucid is proud to serve top businesses around the world, including customers such as Google, GE, and NBC Universal, and 99% of the Fortune 500. Lucid partners with industry leaders, including Google, Atlassian, and Microsoft. Since its founding, Lucid has received numerous awards for its products, business, and workplace culture. For more information, visit lucidchart.com.

Sometimes you're faced with challenges that traditional problem solving can't fix. Creative problem solving encourages you to find new, creative ways of thinking that can help you overcome the issue at hand more quickly.

Root cause analysis refers to any problem-solving method used to trace an issue back to its origin. Learn how to complete a root cause analysis—we've even included templates to get you started.

Bring your bright ideas to life.

or continue with

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

The Power of Defining the Problem

Dwayne Spradlin

Before you start solving a problem, you have to ask the right questions.

Well-defined problems lead to breakthrough solutions. When developing new products, processes, or even businesses, most companies aren’t sufficiently rigorous in defining the problems they’re attempting to solve and articulating why those issues are important. Without that rigor, organizations miss opportunities, waste resources, and end up pursuing innovation initiatives that aren’t aligned with their strategies. How many times have you seen a project go down one path only to realize in hindsight that it should have gone down another? How many times have you seen an innovation program deliver a seemingly breakthrough result only to find that it can’t be implemented or it addresses the wrong problem? Many organizations need to become better at asking the right questions so that they tackle the right problems.

DS Dwayne Spradlin is the president and CEO of InnoCentive , an online marketplace that connects organizations with freelance problem solvers in a multitude of fields. He is a coauthor, with Alpheus Bingham, of The Open Innovation Marketplace: Creating Value in the Challenge Driven Enterprise (FT Press, 2011).

Partner Center

What is Problem Solving? (Steps, Techniques, Examples)

By Status.net Editorial Team on May 7, 2023 — 5 minutes to read

What Is Problem Solving?

Definition and importance.

Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal and professional growth, leading to more successful outcomes and better decision-making.

Problem-Solving Steps

The problem-solving process typically includes the following steps:

Identify the issue : Recognize the problem that needs to be solved.
Analyze the situation : Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.
Generate potential solutions : Brainstorm a list of possible solutions to the issue, without immediately judging or evaluating them.
Evaluate options : Weigh the pros and cons of each potential solution, considering factors such as feasibility, effectiveness, and potential risks.
Select the best solution : Choose the option that best addresses the problem and aligns with your objectives.
Implement the solution : Put the selected solution into action and monitor the results to ensure it resolves the issue.
Review and learn : Reflect on the problem-solving process, identify any improvements or adjustments that can be made, and apply these learnings to future situations.

Defining the Problem

To start tackling a problem, first, identify and understand it. Analyzing the issue thoroughly helps to clarify its scope and nature. Ask questions to gather information and consider the problem from various angles. Some strategies to define the problem include:

Brainstorming with others
Asking the 5 Ws and 1 H (Who, What, When, Where, Why, and How)
Analyzing cause and effect
Creating a problem statement

Generating Solutions

Once the problem is clearly understood, brainstorm possible solutions. Think creatively and keep an open mind, as well as considering lessons from past experiences. Consider:

Creating a list of potential ideas to solve the problem
Grouping and categorizing similar solutions
Prioritizing potential solutions based on feasibility, cost, and resources required
Involving others to share diverse opinions and inputs

Evaluating and Selecting Solutions

Evaluate each potential solution, weighing its pros and cons. To facilitate decision-making, use techniques such as:

SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
Decision-making matrices
Pros and cons lists
Risk assessments

After evaluating, choose the most suitable solution based on effectiveness, cost, and time constraints.

Implementing and Monitoring the Solution

Implement the chosen solution and monitor its progress. Key actions include:

Communicating the solution to relevant parties
Setting timelines and milestones
Assigning tasks and responsibilities
Monitoring the solution and making adjustments as necessary
Evaluating the effectiveness of the solution after implementation

Utilize feedback from stakeholders and consider potential improvements. Remember that problem-solving is an ongoing process that can always be refined and enhanced.

Problem-Solving Techniques

During each step, you may find it helpful to utilize various problem-solving techniques, such as:

Brainstorming : A free-flowing, open-minded session where ideas are generated and listed without judgment, to encourage creativity and innovative thinking.
Root cause analysis : A method that explores the underlying causes of a problem to find the most effective solution rather than addressing superficial symptoms.
SWOT analysis : A tool used to evaluate the strengths, weaknesses, opportunities, and threats related to a problem or decision, providing a comprehensive view of the situation.
Mind mapping : A visual technique that uses diagrams to organize and connect ideas, helping to identify patterns, relationships, and possible solutions.

Brainstorming

When facing a problem, start by conducting a brainstorming session. Gather your team and encourage an open discussion where everyone contributes ideas, no matter how outlandish they may seem. This helps you:

Generate a diverse range of solutions
Encourage all team members to participate
Foster creative thinking

When brainstorming, remember to:

Reserve judgment until the session is over
Encourage wild ideas
Combine and improve upon ideas

Root Cause Analysis

For effective problem-solving, identifying the root cause of the issue at hand is crucial. Try these methods:

5 Whys : Ask “why” five times to get to the underlying cause.
Fishbone Diagram : Create a diagram representing the problem and break it down into categories of potential causes.
Pareto Analysis : Determine the few most significant causes underlying the majority of problems.

SWOT Analysis

SWOT analysis helps you examine the Strengths, Weaknesses, Opportunities, and Threats related to your problem. To perform a SWOT analysis:

List your problem’s strengths, such as relevant resources or strong partnerships.
Identify its weaknesses, such as knowledge gaps or limited resources.
Explore opportunities, like trends or new technologies, that could help solve the problem.
Recognize potential threats, like competition or regulatory barriers.

SWOT analysis aids in understanding the internal and external factors affecting the problem, which can help guide your solution.

Mind Mapping

A mind map is a visual representation of your problem and potential solutions. It enables you to organize information in a structured and intuitive manner. To create a mind map:

Write the problem in the center of a blank page.
Draw branches from the central problem to related sub-problems or contributing factors.
Add more branches to represent potential solutions or further ideas.

Mind mapping allows you to visually see connections between ideas and promotes creativity in problem-solving.

Examples of Problem Solving in Various Contexts

In the business world, you might encounter problems related to finances, operations, or communication. Applying problem-solving skills in these situations could look like:

Identifying areas of improvement in your company’s financial performance and implementing cost-saving measures
Resolving internal conflicts among team members by listening and understanding different perspectives, then proposing and negotiating solutions
Streamlining a process for better productivity by removing redundancies, automating tasks, or re-allocating resources

In educational contexts, problem-solving can be seen in various aspects, such as:

Addressing a gap in students’ understanding by employing diverse teaching methods to cater to different learning styles
Developing a strategy for successful time management to balance academic responsibilities and extracurricular activities
Seeking resources and support to provide equal opportunities for learners with special needs or disabilities

Everyday life is full of challenges that require problem-solving skills. Some examples include:

Overcoming a personal obstacle, such as improving your fitness level, by establishing achievable goals, measuring progress, and adjusting your approach accordingly
Navigating a new environment or city by researching your surroundings, asking for directions, or using technology like GPS to guide you
Dealing with a sudden change, like a change in your work schedule, by assessing the situation, identifying potential impacts, and adapting your plans to accommodate the change.
How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
How to Write Inspiring Core Values? 5 Steps with Examples
30 Employee Feedback Examples (Positive & Negative)

How it works

For Business

Join Mind Tools

Article • 10 min read

The Problem-Definition Process

Developing the right solution.

By the Mind Tools Content Team

When we try to solve business problems, we can often pressurize ourselves to find solutions quickly.

The problem with this is that we can end up only partially solving the problem, or we can solve the wrong problem altogether, with all of the delay, expense, and lost business opportunity that goes with this.

The Problem-Definition Process helps you avoid this. In this article, we'll look at this process and we'll see how to apply it.

Dwayne Spradlin published the Problem-Definition Process in September 2012's Harvard Business Review . (We refer to this with permission.)

Spradlin was the President and CEO of Innocentive, an organization that connected organizations with freelance problem solvers. He developed the process over 10 years, while working with a community of more than 25,000 "problem solvers" such as engineers, scientists, and industry experts.

The process gives you four steps that help you better understand complex problems. These steps are:

Establish the need.
Justify the need.
Understand the problem and its wider context.
Write a problem statement.

The Problem-Definition Process encourages you to define and understand the problem that you're trying to solve, in detail. It also helps you confirm that solving the problem contributes towards your organization's objectives.

This stops you spending time, energy, and resources on unimportant problems, or on initiatives that don't align with your organization's overall strategy.

It also encourages you to fully define the problem and its boundaries. You can then use this information to justify the need for change, brief designers and contractors, and kick-off new projects successfully.

Use the Problem-Definition Process alongside tools such as Simplex and Hurson's Productive Thinking Model . These will guide you through the full problem-solving process .

Using the Problem-Definition Process

The four main steps in the Problem-Definition Process contain several smaller questions that, once answered, help you define and clarify the problem thoroughly.

Let's look at each step in more detail.

The process we present below is an adaptation of Spradlin's original model. We’ve included additional questions and sub-steps where appropriate.

1. Establish the Need

The first step is to identify why you need a solution to the problem. To do this, answer these questions:

a. What is the basic need? First, write your problem down in simple terms. Then, identify the basic need that you'll fulfill once you've solved the problem.

For example:

b. What is the ideal outcome? Next, identify the outcome that you want to see once you've implemented a solution.

Don't think of any particular solutions at this point – your aim is to visualize the result of a successful solution, not the solution itself.

It helps to be specific here: "Increase weekly sign-ups by 20 percent" is more useful than "Increase weekly sign-ups."

c. Who will (and won't) benefit? Finally in this step, identify all of the stakeholders who will benefit, both directly and indirectly, once you've solved the problem and reached your desired outcome. Write down who these people or groups are, and the advantages that they'll see.

Also consider who may be at a disadvantage if you solve the problem.

Tools like Impact Analysis and the Futures Wheel are useful here, as they help identify the possible consequences of a change.

As you work through the next steps of this process and get more of an understanding of your problem, you may find it useful to go back and refine your answers to previous questions.

2. Justify the Need

Once you understand the need for solving the problem, you must then justify why you should solve it. To do this, answer these questions:

a. Is effort aligned with your overall strategy? This problem, and the effort that you'll be putting into solving it, must align with your organization's strategic priorities , as well as its mission and values .

b. What benefits do we want, and how can we measure these? Identify what benefits your organization, as a whole, will see when you solve this problem, and think about how you can measure these in relation to its overall strategy and objectives. Be as specific as possible.

c. Are we likely to be able to implement a solution? Think about factors such as how you'll get support from stakeholders and decision-makers, and how you'll access the required resources and expertise. This may involve speaking with senior managers in your organization to understand what resources may be available.

3. Understand the Problem and Its Wider Context

In steps 1 and 2, you identified why you need a solution, and why it's important to your strategy and mission.

The three questions in this third step encourage you to look at the problem in more depth, and to look back into the past to see what you can learn from past efforts.

a. What's the cause? First in this step, make sure that you've identified all of the causes of your problem, using tools like CATWOE , Root Cause Analysis , Cause and Effect Analysis , Systems Diagrams , and Interrelationship Diagrams .

b. What solutions already exist? Have other people in your organization tried to solve this or a similar problem in the past? If so, what did they do? What worked and what didn't work?

Next you need to find out if people outside of your organization have already tried to do something about this problem. Widen your search to include trade journals, field studies, past research, competitors, industry experts, and your personal network.

Your goal is to look at what's been done already, and what hasn't worked, so that you don't waste time working on a solution that already exists, or working on a solution that's likely to fail.

c. What are the constraints? By now, you're starting to have a deeper understanding of the problem and how it relates to your organization. Now you can brainstorm factors that might prevent you from implementing a solution. (Use your answers from question c in step 2 to help with this.)

First, look at internal constraints. Will you have access to enough people, money, and other resources to solve this problem? Are there any stakeholders who might try to block your efforts? Are there any rules or procedures that you must follow? (For instance, a new website would need to align with your organization's brand guidelines.)

Next, look externally. Are there any government regulations or laws that might stall or block your solutions? Is the technology available?

d. What requirements must a solution meet? Write down the requirements that the solution must meet in order to solve the problem successfully. As part of this, also identify other factors that, while not essential for solving the problem successfully, would add value to the final solution. For example, you might want "quiet machinery," or a "database that you can access from anywhere with an Internet connection."

e. How will we define success? Identify how you'll define success once you've implemented a solution.

4. Write a Problem Statement

The final step is to pull together all of the information that you've gathered into a clear, comprehensive problem statement. This should provide a thorough overview of the problem, and outline a plan for how you will go about solving it.

If someone else (for example, a contractor, outside organization, or other department) will be tasked with solving the problem, also work through the following questions, and include the answers to these in your problem statement:

a. Which problem solvers should we use? Identify who, specifically, is best placed to help solve this problem. This could be a person, a team, or an outside firm.

b. What information and language should the problem statement include? The problem statement needs to be clear, specific, and understood by the people who should solve it. Avoid industry jargon , and make sure that it relates to its intended audience.

c. What do problem solvers need to produce? What will you or your organization need from them? For instance, will you need a comprehensive report, or a presentation on the proposed solution? Do you want a prototype? Is there a deadline? Spell the details out here.

d. What incentives do solvers need? This question addresses motivation. If an internal team will be working on the solution, how will they be rewarded? If an external team or firm will be addressing this problem, what incentives are you offering?

e. How will we evaluate the solutions? Who will be responsible for analyzing proposals, and what evaluation method will you use?

Dwayne Spradlin published the Problem-Definition Process in the September 2012 Harvard Business Review.

The process presents four steps that help you better understand complex problems. These four steps are:

The main advantage of using the process is that it helps you to define and understand the problem in detail, and helps you understand how important a problem is in relation to your organization's mission and strategy. From this, you can determine whether or not it's worth developing a solution.

Spradlin, D. (2012) 'Are You Solving the Right Problem?' Harvard Business Review . Available here . [Accessed November 8, 2018.]

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

The problem-solving process.

Looking at the Basic Problem-Solving Process to Help Keep You on the Right Track

Problem-Solving Sabotage

Tips to Make You Aware of Self-Sabotage Increasing Your Chance of a Positive Solution

Add comment

Comments (0)

Be the first to comment!

Get 20% off your first year of Mind Tools

Our on-demand e-learning resources let you learn at your own pace, fitting seamlessly into your busy workday. Join today and save with our limited time offer!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Discover something new today

Pain points podcast - what is ai.

Exploring Artificial Intelligence

Pain Points Podcast - How Do I Get Organized?

It's Time to Get Yourself Sorted!

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

How to create a wiki.

Collecting and Sharing Knowledge at Work

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Encyclopedia of the Sciences of Learning pp 2680–2683 Cite as

Problem Solving

David H. Jonassen 2 &
Woei Hung 3
Reference work entry

1835 Accesses

11 Citations

Cognition ; Problem typology ; Problem-based learning ; Problems ; Reasoning

Problem solving is the process of constructing and applying mental representations of problems to finding solutions to those problems that are encountered in nearly every context.

Theoretical Background

Problem solving is the process of articulating solutions to problems. Problems have two critical attributes. First, a problem is an unknown in some context. That is, there is a situation in which there is something that is unknown (the difference between a goal state and a current state). Those situations vary from algorithmic math problems to vexing and complex social problems, such as violence in society (see Problem Typology ). Second, finding or solving for the unknown must have some social, cultural, or intellectual value. That is, someone believes that it is worth finding the unknown. If no one perceives an unknown or a need to determine an unknown, there is no perceived problem. Finding...

This is a preview of subscription content, log in via an institution .

Buying options

Available as PDF
Read on any device
Instant download
Own it forever
Available as EPUB and PDF
Durable hardcover edition
Dispatched in 3 to 5 business days
Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Bransford, J., & Stein, B. S. (1984). The IDEAL problem solver: A guide for improving thinking, learning, and creativity . New York: WH Freeman.

Google Scholar

Frensch, P. A., & Funke, J. (Eds.). (1995). Complex problem solving: The European perspective . Hillsdale: Erlbaum.

Gick, M. L., & Holyoak, K. J. (1983). Schema induction and analogical transfer. Cognitive Psychology, 15 , 1–38.

Article Google Scholar

Jonassen, D. H. (2010). Learning to solve problems: A handbook . New York: Routledge.

Jonassen, D. H., & Hung, W. (2008). All problems are not equal: Implications for PBL. Interdisciplinary Journal of Problem-Based Learning, 2 (2), 6–28.

Jonassen, D. H. (2000). Toward a design theory of problem solving. Educational Technology: Research & Development, 48 (4), 63–85.

Jonassen, D. H. (2011). Learning to solve problems: A handbook for designing problem-solving learning environments . New York: Routledge.

Klein, G. A. (1998). Sources of power: How people make decisions . Cambridge, MA: MIT Press.

Lehman, D., Lempert, R., & Nisbett, R. E. (1988). The effects of graduate training on reasoning: Formal discipline and thinking about everyday-life events. Educational Psychologist, 43 , 431–442.

Newell, A., & Simon, H. (1972). Human problem solving . Englewood Cliffs: Prentice Hall.

Rumelhart, D. E., & Norman, D. A. (1988). Representation in memory. In R. C. Atkinson, R. J. Herrnstein, G. Lindzey, & R. D. Luce (Eds.), Steven’s handbook of experimental psychology (Learning and cognition 2nd ed., Vol. 2, pp. 511–587). New York: Wiley.

Sinnott, J. D. (1989). Everyday problem solving: Theory and applications (pp. 72–99). New York: Praeger.

Wood, P. K. (1983). Inquiring systems and problem structures: Implications for cognitive development. Human Development, 26 , 249–265.

Download references

Author information

Authors and affiliations.

School of Information Science and Learning Technologies, University of Missouri, 221C Townsend Hall, 65211, Columbia, MO, USA

Dr. David H. Jonassen

College of Education and Human Development, University of North Dakota, 231 Centennial Drive, Stop 7189, 58202, Grand Forks, ND, USA

Dr. Woei Hung

You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to David H. Jonassen .

Editor information

Editors and affiliations.

Faculty of Economics and Behavioral Sciences, Department of Education, University of Freiburg, 79085, Freiburg, Germany

Norbert M. Seel

Rights and permissions

Reprints and permissions

Copyright information

About this entry

Cite this entry.

Jonassen, D.H., Hung, W. (2012). Problem Solving. In: Seel, N.M. (eds) Encyclopedia of the Sciences of Learning. Springer, Boston, MA. https://doi.org/10.1007/978-1-4419-1428-6_208

Download citation

DOI : https://doi.org/10.1007/978-1-4419-1428-6_208

Publisher Name : Springer, Boston, MA

Print ISBN : 978-1-4419-1427-9

Online ISBN : 978-1-4419-1428-6

eBook Packages : Humanities, Social Sciences and Law

Share this entry

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

Publish with us

Policies and ethics

Find a journal
Track your research

6.1 Problem Solving to Find Entrepreneurial Solutions

Portions of the material in this section are based on original work by Geoffrey Graybeal and produced with support from the Rebus Community. The original is freely available under the terms of the CC BY 4.0 license at https://press.rebus.community/media-innovation-and-entrepreneurship/.

Learning Objectives

By the end of this section, you will be able to:

Define problem solving in the context of entrepreneurship
Describe and compare the adaptive model and the innovative model of problem solving
Identify the skills entrepreneurs need for effective problem solving
Identify types of problem solvers

As you’ve learned, entrepreneurs often visualize an opportunity gap, a gap between what exists and what could exist, as Hirabayashi and Lidey did with Shine. Entrepreneurial problem solving is the process of using innovation and creative solutions to close that gap by resolving societal, business, or technological problems. Sometimes, personal problems can lead to entrepreneurial opportunities if validated in the market. The entrepreneur visualizes the prospect of filling the gap with an innovative solution that might entail the revision of a product or the creation of an entirely new product. In any case, the entrepreneur approaches the problem-solving process in various ways. This chapter is more about problem solving as it pertains to the entrepreneur’s thought process and approach rather than on problem solving in the sense of opportunity recognition and filling those gaps with new products.

For example, as we read in Identifying Entrepreneurial Opportunity , Sara Blakely (as shown in Figure 6.2 ) saw a need for body contouring and smoothing undergarments one day in the late 1990s when she was getting dressed for a party and couldn’t find what she needed to give her a silhouette she’d be pleased with in a pair of slacks. She saw a problem: a market need. But her problem-solving efforts are what drove her to turn her solution (Spanx undergarments) into a viable product. Those efforts came from her self-admitted can-do attitude: “It’s really important to be resourceful and scrappy—a glass half-full mindset.” 1 Her efforts at creating a new undergarment met resistance with hosiery executives, most of whom were male and out of touch with their female consumers. The hosiery owner who decided to help Blakely initially passed on the idea until running it by his daughters and realizing she was on to something. That something became Spanx , and today, Blakely is a successful entrepreneur. 2

Before getting into the heart of this chapter, we need to make a distinction: Decision making is different from problem solving . A decision is needed to continue or smooth a process affecting the operation of a firm. It can be intuitive or might require research and a long period of consideration. Problem solving , however, is more direct. It entails the solution of some problem where a gap exists between a current state and a desired state. Entrepreneurs are problem solvers who offer solutions using creativity or innovative ventures that exploit opportunities. This chapter focuses on different approaches to problem solving and need recognition that help potential entrepreneurs come up with ideas and refine those ideas.

Two Problem Solving Models: Adaptive and Innovative

There are two prominent established problem-solving models: adaptive and innovative . A renowned British psychologist, Michael Kirton , developed the Kirton Adaption-Innovation (KAI) Inventory to measure an individual’s style of problem solving. 3 Problem-solving preferences are dependent on the personality characteristics of originality, conformity, and efficiency, according to Kirton. The KAI inventory identifies an individual’s problem-solving approach by measuring agreement with statements that align with characteristics, such as the ability to produce many novel ideas, to follow rules and get along in groups, and to systematically orient daily behavior. The results categorize an individual as an innovator or an adaptor. Innovators are highly original, do not like to conform, and value efficiency less than adaptors.

The first and more conservative approach an entrepreneur may use to solve problems is the adaptive model. The adaptive model seeks solutions for problems in ways that are tested and known to be effective. An adaptive model accepts the problem definition and is concerned with resolving problems rather than finding them. This approach seeks greater efficiency while aiming at continuity and stability. The second and more creative approach is the innovative model of entrepreneurial problem solving, which uses techniques that are unknown to the market and that bring advantage to an organization. An innovative problem-solving style challenges the problem definition, discovers problems and avenues for their solutions, and questions existing assumptions—in a nutshell, it does things differently. It uses outside-the-box thinking and searches for novel solutions. Novelty is a shared trait of creative entrepreneurship, and it’s why entrepreneurs gravitate toward this method of problem solving. According to Dr. Shaun M. Powell , a senior lecturer at the University of Wollongong, Australia: “Creative entrepreneurs are notable for a distinctive management style that is based on intuition, informality and rapid decision making, whereas the more conventional thinking styles are not in accord with the unique attributes of creative entrepreneurs.” 4 This way of problem solving doesn’t alter an existing product. It is the creation of something entirely new.

For example, healthcare facilities have long been known as a source of methicillin-resistant Staphylococcus aureus (MRSA), a deadly infection that can have long-term effects on patients. Vital Vio , led by Colleen Costello , has developed white light technology that effectively disinfects healthcare facilities by targeting a molecule specific to bacteria. The light, safe to humans, can burn constantly to kill regenerative bacteria. An adaptive problem-solving model would seek to minimize harm of MRSA within a hospital—to respond to it—whereas the Vital Vio is an entirely new technique that seeks to eliminate it. Adaptive solutions to MRSA include established processes and protocols for prevention, such as having doctors, nurses, and other healthcare providers clean their hands with soap and water, or an alcohol-based hand rub before and after patient care, testing patients to see if they have MRSA on their skin, cleaning hospital rooms and medical equipment, and washing and drying clothes and bed linens in the warmest recommended temperatures. 5

Link to Learning

Visit Inc. Magazine for support and advice for up-and-coming startups to learn more. Examples of how “Dorm Room” entrepreneurs spot and pursue opportunities are shared along with tips and advice for making your startup a success.

Problem-Solving Skills

While identifying problems is a necessary part of the origin of the entrepreneurial process, managing problems is an entirely different aspect once a venture is off the ground and running. An entrepreneur does not have the luxury of avoiding problems and is often responsible for all problem solving in a startup or other form of business. There are certain skills that entrepreneurs possess that make them particularly good problem solvers. Let’s examine each skill (shown in Figure 6.3 ) .

Critical Thinking

Critical thinking is the complex analysis of a problem or issue with the goal of solving the problem or making a decision. The entrepreneur analyzes and peels away the layers of a problem to find the core of an issue facing a business. The entrepreneur focuses on the heart of the problem and responds reasonably and openly to suggestions for solving it. Critical thinking is not only important for developing entrepreneurial ideas: it is a sought-after asset in education and employment. Entrepreneur Rebecca Kantar dropped out of Harvard in 2015 to found the tech startup Imbellus , which aims to replace standardized college admissions tests like the SAT with interactive scenarios that test critical-thinking skills. Many standardized tests may include multiple choice questions asking for the answer to a straightforward knowledge question or math problem. Kantar seeks to create tests that are more concerned with the analytic ability and reasoning that goes into the process of solving the problem. Imbellus says it aims to test “how people think,” not just what they know. The platform, which has not yet launched, will use simulations for its user assessments. 6

Read more about problem solving and EnterpriseWorks/Vita’s story at Harvard Business Review .

Communication

Communication skills , the ability to communicate messages effectively to an intended recipient, are the skills entrepreneurs use to pool resources for the purposes of investigating solutions leading to innovative problem solving and competitive advantage. Good communication allows for the free association of ideas between entrepreneurs and businesses. It can illustrate a problem area or a shared vision, and seeks stakeholder buy-in from various constituencies. Networking and communication within an industry allow the entrepreneur to recognize the position of an enterprise in the market and work toward verbalizing solutions that move an organization beyond its current state. By “verbalizing,” we mean communication from and with the company/entity. Internal communications include company emails, newsletters, presentations, and reports that can set strategic goals and objectives, and report on what has been accomplished and what goals and objectives remain, so that employees within an organization are knowledgeable and can work on solving problems that remain within the organization. External communications could include press releases, blogs and websites, social media, public speeches, and presentations that explain the company’s solutions to problems. They could also be investor pitches complete with business plans and financial projections.

Ideation exercises, such as brainstorming sessions (discussed in Creativity, Innovation, and Invention , are good communication tools that entrepreneurs can use to generate solutions to problems. Another such tool is a hackathon —an event, usually hosted by a tech company or organization, which brings together programmers and workers with other degrees of specialization within the company, community, or organization to collaborate on a project over a short period of time. These can last from twenty-four hours to a few days over a weekend. A hackathon can be an internal company-wide initiative or an external event that brings community participants together. A business model canvas , which is covered in Business Model and Plan and other activities outlined in other chapters can be used internally or externally to identify problems and work toward creating a viable solution.

Networking is an important manifestation of useful communication. What better method is there of presenting one’s concept, gaining funding and buy-in, and marketing for the startup than through building a network of individuals willing to support your venture? A network may consist of potential employees, customers, board members, outside advisors, investors, or champions (people who just love your product) with no direct vested interest. Social networks consist of weak ties and strong ties. Sociologist Mark Granovetter studied such networks back in the 1970s, and his findings still apply today, even if we include social media networks in the definition too. Weak ties facilitate flow of information and community organization, he said, whereas strong ties represent strong connections among close friends, family members, and supportive coworkers. 7 Strong ties require more work to maintain than weak ties (as illustrated by the strong lines and weak dotted lines in Figure 6.4 ) and in a business context, they don’t lead to many new opportunities. Weak ties, in contrast, do open doors in that they act as bridges to other weak ties within functional areas or departments that you might not have had access to directly or through strong ties. 8

In fact, many young entrepreneurs, including tech entrepreneur Oliver Isaacs , realize college is a great place to begin building teams. Isaacs is the founder of viral opinion network Amirite.com , which is widely credited as the place where Internet memes started and online slang got a foothold. 9 Amirite.com consists of a large network of pages and partnerships on Facebook and Instagram that reach 15 million users each month. Isaacs recommends using your alumni network to build a team and customer base for your own venture because you never know if you’re talking to a future employee or partner.

Sharing of ideas and resources is highly valued in the entrepreneurial process. Communication is a vital skill in problem solving because the ability to identify and articulate the problem (define the problem space) is necessary to adequately address a problem. A problem can be too vague or broad or narrow. Thus, communicating the problem is important, as is conveying the solution.

Decisiveness

Decisiveness is as it sounds: the ability to make a quick, effective decision, not letting too much time go by in the process. Entrepreneurs must be productive, even in the face of risk. They often rely on intuition as well as on hard facts in making a choice. They ask what problem needs to be solved, think about solutions, and then consider the means necessary to implement an idea. And the decisions must be informed with research.

For example, as explained in Adam Grant’s book The Originals , the co-founders of Warby Parker, a venture-backed startup focused on the eyewear industry, started their company while they were graduate students. At the time they knew little about the industry, but after conducting some detailed research, they learned that the industry was dominated by one major player—Luxottica. They used this information and other data to refine their strategy and business model (focusing mainly on value, quality, and convenience via an online channel). By the time they decided to launch the business, they had thought through the key details, and they attained rapid early success. Today Warby Parker has over 100 retail stores in the US, is profitable, and is valued at almost $2 billion.

Decisiveness is the catapult to progress. Amazon founder Jeff Bezos preaches the importance of decisiveness throughout his organization. Bezos believes that decisiveness can even lead to innovation. Bezos advocates for making decisions after obtaining 70 percent of the information you need to do so: “Being wrong may be less costly than you think, whereas being slow is going to be expensive for sure,” Bezos wrote in a 2017 annual letter to stockholders. 10

Read this LinkedIn blog post on decisiveness to learn more.

Ability to Analyze Data

Data analysis is the process of analyzing data and modeling it into a structure that leads to innovative conclusions. Identifying Entrepreneurial Opportunity covered much of the sources of data that entrepreneurs might seek. But it is one thing to amass information and statistics. It is another to make sense of that data, to use it to fill a market need or forecast a trend to come. Successful founders know how to pose questions about and make meaning out of information. And if they can’t do that themselves, they know how to bring in experts who can.

In addition to public sources of broad data, a business can collect data on customers when they interact with the company on social media or when they visit the company website, especially if they complete a credit card transaction. They can collect their own specific data on their own customers, including location, name, activity, and how they got to the website. Analyzing these data will give the entrepreneur a better idea about the interested audience’s demographic.

In entrepreneurship, analyzing data can help with opportunity recognition, creation, and assessment by analyzing data in a variety of ways. Entrepreneurs can explore and leverage different data sources to identify and compare “attractive” opportunities, since such analyses can describe what has happened, why it happened, and how likely it is to happen again in the future. In business in general, analytics is used to help managers/entrepreneurs gain improved insight about their business operations/emerging ventures and make better, fact-based decisions.

Analytics can be descriptive, predictive, or prescriptive. Descriptive analytics involves understanding what has happened and what is happening; predictive analytics uses data from past performance to estimate future performance; and prescriptive analytics uses the results of descriptive and predictive analytics to make decisions. Data analysis can be applied to manage customer relations, inform financial and marketing activities, make pricing decisions, manage the supply chain, and plan for human resource needs, among other functions of a venture. In addition to statistical analysis, quantitative methods, and computer models to aid decision-making, companies are also increasingly using artificial intelligence algorithms to analyze data and make quick decisions.

Understanding of Business and Industry

Entrepreneurs need sound understanding of markets and industries. Often times, they are already working in a large organization when they see growth opportunities or inefficiencies in a market. The employee gains a deep understanding of the industry at hand. If the employee considers a possible solution for a problem, this solution might become the basis for a new business.

For example, consider a marketing agency that used traditional marketing for thirty years. This agency had an established clientele. An executive in the organization began studying social media analytics and social media. The executive approached the owner of the business to change processes and begin serving clients through social media, but the owner refused. Clients within the agency began to clamor for exposure on social media. The marketing executive investigated the possibility of building an agency in her locale servicing clients who wish to utilize social media. The marketing executive left the organization and started her own agency (providing, of course, that this is in compliance with any noncompete clauses in her contract). Her competitive advantage was familiarity with both traditional and social media venues. Later, the original agency started floundering because it did not offer social media advertising. Our intrepid executive purchased the agency to gain the clientele and serve those wishing to move away from traditional marketing.

A similar experience occurred for entrepreneur Katie Witkin . After working in traditional marketing roles, the University of Wisconsin-Madison graduate, pictured in Figure 6.5 , left agency life behind four years out of college to cofound her own company, AGW Group . In 2009, Witkin had been interning at a music marketing agency that didn’t have a social media department. She knew, both from her time at college and from observing industry trends, that social media was changing the way companies connected with customers. For her own venture, she expanded the focus to all supporting brands to manage all things digital. Today, the cultural and marketing communications agency has fifteen employees and big-name clients ranging from HBO to Red Bull. 11

Resourcefulness

“There is not a more useful or important trait to possess than resourcefulness in the pursuit of success. Resourcefulness is a mindset, and is especially relevant when the goals you have set are difficult to achieve or you cannot envision a clear path to get to where you desire to go. With a resourcefulness mindset you are driven to find a way. An attitude of resourcefulness inspires out-of-the-box thinking, the generation of new ideas, and the ability to visualize all the possible ways to achieve what you desire. Resourcefulness turns you into a scrappy, inventive and enterprising entrepreneur. It places you a cut above the rest.” 12

Entrepreneurs start thinking about a business venture or startup by talking to people and procuring experts to help create, fund, and begin a business. Entrepreneurs are risk takers, passionate about new endeavors. If they don’t have a college degree or a great deal of business experience, they understand there are many resources available to support them in the endeavor, such as the Service Corps of Retired Executives (SCORE) and the Small Business Administration (SBA) . There are many sources available to fund the business with little or no debt and options, as you will see in the chapter on Entrepreneurial Finance and Accounting . The entrepreneur follows a vision and researches opportunities to move toward a dream.

For example, in the late 1990s, Bill McBean and his business partner Billy Sterett had an opportunity to buy an underperforming auto dealership that would make their company the dominant one in the market. Neither wanting to take cash from other ventures nor wanting to borrow more money and tie themselves to more debt, the entrepreneurs were resourceful by finding another path forward to obtaining the money necessary for the acquisition they both coveted. They changed banks and renegotiated their banking payback requirements, lowering their interest payments, reducing fees, and lowering their monthly payments, ultimately freeing up a significant amount of cash that allowed them to buy the new company. 13

Types of Problem Solvers

Entrepreneurs have an insatiable appetite for problem solving. This drive motivates them to find a resolution when a gap in a product or service occurs. They recognize opportunities and take advantage of them. There are several types of entrepreneurial problem solvers, including self-regulators, theorists, and petitioners.

Self-Regulating Problem Solvers

Self-regulating problem solvers are autonomous and work on their own without external influence. They have the ability to see a problem, visualize a possible solution to the problem, and seek to devise a solution, as Figure 6.6 illustrates. The solution may be a risk, but a self-regulating problem solver will recognize, evaluate, and mitigate the risk. For example, an entrepreneur has programmed a computerized process for a client, but in testing it, finds the program continually falls into a loop, meaning it gets stuck in a cycle and doesn’t progress. Rather than wait for the client to find the problem, the entrepreneur searches the code for the error causing the loop, immediately edits it, and delivers the corrected program to the customer. There is immediate analysis, immediate correction, and immediate implementation. The self-regulating problem solvers’ biggest competitive advantage is the speed with which they recognize and provide solutions to problems.

Theorist Problem Solvers

Theorist problem solvers see a problem and begin to consider a path toward solving the problem using a theory. Theorist problem solvers are process oriented and systematic. While managers may start with a problem and focus on an outcome with little consideration of a means to an end, entrepreneurs may see a problem and begin to build a path with what is known, a theory, toward an outcome. That is, the entrepreneur proceeds through the steps to solve the problem and then builds on the successes, rejects the failures, and works toward the outcome by experimenting and building on known results. At this point, the problem solver may not know the outcome, but a solution will arise as experiments toward a solution occur. Figure 6.7 shows this process.

For example, if we consider Marie Curie as an entrepreneur, Curie worked toward the isolation of an element. As different approaches to isolating the element failed, Curie recorded the failures and attempted other possible solutions. Curie’s failed theories eventually revealed the outcome for the isolation of radium. Like Curie, theorists use considered analysis, considered corrective action, and a considered implementation process. When time is of the essence, entrepreneurs should understand continual experimentation slows the problem-solving process.

Petitioner Problem Solvers

Petitioner problem solvers ( Figure 6.8 ) see a problem and ask others for solution ideas. This entrepreneur likes to consult a person who has “been there and done that.” The petitioner might also prefer to solve the problem in a team environment. Petitioning the entrepreneurial team for input ensures that the entrepreneur is on a consensus-driven path. This type of problem solving takes the longest to complete because the entrepreneur must engage in a democratic process that allows all members on the team to have input. The process involves exploration of alternatives for the ultimate solution. In organizational decision-making, for example, comprehensiveness is a measure of the extent a firm attempts to be inclusive or exhaustive in its decision-making. Comprehensiveness can be gauged by the number of scheduled meetings, the process by which information is sought, the process by which input is obtained from external sources, the number of employees involved, the use of specialized consultants and the functional expertise of the people involved, the years of historical data review, and the assignment of primary responsibility, among other factors. Comprehensive decision-making would be an example of a petitioner problem-solving style, as it seeks input from a vast number of team members.

A charette —a meeting to resolve conflicts and identify solutions—is another example that employs a petitioner problem-solving approach. Often times, a developer of a new project might hold a community charette to aid in the design of a project, hoping to gain approval from elected officials. In the building example, this could consist of the developer and his team of architects, project designers, and people with expertise in the project working alongside community members, business executives, elected officials, or representatives like staff members or citizen-appointed boards like a planning board. Such an activity is representative of a petitioner problem-solving approach, as opposed to a developer representative designing the project with no input from anyone else.

In summary, there is no right or wrong style of problem solving; each problem solver must rely on the instincts that best drive innovation. Further, they must remember that not all problem-solving methods work in every situation. They must be willing to adapt their own preference to the situation to maximize efficiency and ensure they find an effective solution. Attempting to force a problem-solving style may prevent an organization from finding the best solution. While general entrepreneurial problem-solving skills such as critical thinking, decisiveness, communication, and the ability to analyze data will likely be used on a regular basis in your life and entrepreneurial journey, other problem-solving skills and the approach you take will depend on the problem as it arises.

There are a number of resources online that can help analyze your problem-solving abilities. Mindtools.com is one such resource. These are useful to learn your general problem-solving tendencies before being called upon to apply them in a real-world setting. One of the problem-solving techniques available from mindtools.com offers that problems can be addressed from six different perspectives. Called CATWOE , the approach is an acronym for Customers, Actors (people within the organization), Transformative, Worldwide, Owner, and Environment (organizational).

Learn more about the CATWOE technique for problem solving.

1 Helen Lock. “‘I Put My Butt on the Line’: How Spanx Took Over the World.” The Guardian. July 11, 2016. https://www.theguardian.com/small-business-network/2016/jul/11/put-butt-on-the-line-how-spanx-world
2 Gary Keller. “Business Success Series, Part 1: Sara Blakely-Spanx.” The One Thing. n.d. https://www.the1thing.com/blog/the-one-thing/business-success-series-part-1-sara-blakely-spanx/
3 “Characteristics of Adaptors and Innovators.” Kirton KAI Inventory Tool . n.d. http://pubs.acs.org/subscribe/archive/ci/31/i11/html/11hipple_box3.ci.html
4 Shaun Powell. “The Management and Consumption of Organisational Creativity.” Journal of Consumer Marketing 25, no. 3 (2008): 158–166.
5 N.C Healthcare-Associated Infections Prevention Program. Healthcare-Associated Infections in North Carolina: 2014 Annual Report, Healthcare Consumer Version. April 2015. https://epi.dph.ncdhhs.gov/cd/hai/figures/hai_apr2015_consumers_annual.pdf
6 Romesh Ratnesar. “What If Instead of Taking the SAT You Got to Play a Video Game?” Bloomberg BusinessWeek. March 19, 2019. https://www.bloomberg.com/news/features/2019-03-19/a-harvard-dropout-s-plan-to-fix-college-admissions-with-video-games
7 Mark Granovetter. “The Strength of Weak Ties.” American Journal of Sociology 5 (1973): 1360–1380.
8 Jacob Morgan. “Why Every Employee Should Be Building Weak Ties at Work.” Forbes. March 11, 2014. https://www.forbes.com/sites/jacobmorgan/2014/03/11/every-employee-weak-ties-work/#277851063168
9 John White. “Top UK Influencer Oliver Isaacs Reveals What It Takes to Go Viral.” Inc . August 6, 2017. https://www.inc.com/john-white/top-uk-influencer-oliver-isaacs-reveals-what-it-ta.html
10 Erik Larson. “How Jeff Bezos Uses Faster Better Decisions to Keep Amazon Innovating.” Forbes . September 24, 2018. https://www.forbes.com/sites/eriklarson/2018/09/24/how-jeff-bezos-uses-faster-better-decisions-to-keep-amazon-innovating/#492c351b7a65
11 Stephanie Schomer. “How Getting Laid Off Empowered This Entrepreneur to Start Her Own Award-Winning Marketing Agency.” Entrepreneur. January 15, 2019. https://www.entrepreneur.com/article/326212
12 Sherrie Campbell. “6 Characteristics of Resourceful People That Bring Them Success.” Entrepreneur. March 10, 2016. https://www.entrepreneur.com/article/272171
13 “Resourcefulness Is More Important Than Resources.” The Ecommerce Mindset: How Successful Store Owners Think. n.d. https://www.oberlo.com/ebooks/mindset/resourceful-entrepreneur

As an Amazon Associate we earn from qualifying purchases.

This book may not be used in the training of large language models or otherwise be ingested into large language models or generative AI offerings without OpenStax's permission.

Want to cite, share, or modify this book? This book uses the Creative Commons Attribution License and you must attribute OpenStax.

Access for free at https://openstax.org/books/entrepreneurship/pages/1-introduction

Authors: Michael Laverty, Chris Littel
Publisher/website: OpenStax
Book title: Entrepreneurship
Publication date: Jan 16, 2020
Location: Houston, Texas
Book URL: https://openstax.org/books/entrepreneurship/pages/1-introduction
Section URL: https://openstax.org/books/entrepreneurship/pages/6-1-problem-solving-to-find-entrepreneurial-solutions

© Jan 4, 2024 OpenStax. Textbook content produced by OpenStax is licensed under a Creative Commons Attribution License . The OpenStax name, OpenStax logo, OpenStax book covers, OpenStax CNX name, and OpenStax CNX logo are not subject to the Creative Commons license and may not be reproduced without the prior and express written consent of Rice University.

Bipolar Disorder
Therapy Center
When To See a Therapist
Types of Therapy
Best Online Therapy
Best Couples Therapy
Best Family Therapy
Managing Stress
Sleep and Dreaming
Understanding Emotions
Self-Improvement
Healthy Relationships
Student Resources
Personality Types
Guided Meditations
Verywell Mind Insights
2023 Verywell Mind 25
Mental Health in the Classroom
Editorial Process
Meet Our Review Board
Crisis Support

Overview of the Problem-Solving Mental Process

Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

Rachel Goldman, PhD FTOS, is a licensed psychologist, clinical assistant professor, speaker, wellness expert specializing in eating behaviors, stress management, and health behavior change.

Identify the Problem
Define the Problem
Form a Strategy
Organize Information
Allocate Resources
Monitor Progress
Evaluate the Results

Frequently Asked Questions

Problem-solving is a mental process that involves discovering, analyzing, and solving problems. The ultimate goal of problem-solving is to overcome obstacles and find a solution that best resolves the issue.

The best strategy for solving a problem depends largely on the unique situation. In some cases, people are better off learning everything they can about the issue and then using factual knowledge to come up with a solution. In other instances, creativity and insight are the best options.

It is not necessary to follow problem-solving steps sequentially, It is common to skip steps or even go back through steps multiple times until the desired solution is reached.

In order to correctly solve a problem, it is often important to follow a series of steps. Researchers sometimes refer to this as the problem-solving cycle. While this cycle is portrayed sequentially, people rarely follow a rigid series of steps to find a solution.

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

While it may seem like an obvious step, identifying the problem is not always as simple as it sounds. In some cases, people might mistakenly identify the wrong source of a problem, which will make attempts to solve it inefficient or even useless.

Some strategies that you might use to figure out the source of a problem include :

Asking questions about the problem
Breaking the problem down into smaller pieces
Looking at the problem from different perspectives
Conducting research to figure out what relationships exist between different variables

2. Defining the Problem

After the problem has been identified, it is important to fully define the problem so that it can be solved. You can define a problem by operationally defining each aspect of the problem and setting goals for what aspects of the problem you will address

At this point, you should focus on figuring out which aspects of the problems are facts and which are opinions. State the problem clearly and identify the scope of the solution.

3. Forming a Strategy

After the problem has been identified, it is time to start brainstorming potential solutions. This step usually involves generating as many ideas as possible without judging their quality. Once several possibilities have been generated, they can be evaluated and narrowed down.

The next step is to develop a strategy to solve the problem. The approach used will vary depending upon the situation and the individual's unique preferences. Common problem-solving strategies include heuristics and algorithms.

Heuristics are mental shortcuts that are often based on solutions that have worked in the past. They can work well if the problem is similar to something you have encountered before and are often the best choice if you need a fast solution.
Algorithms are step-by-step strategies that are guaranteed to produce a correct result. While this approach is great for accuracy, it can also consume time and resources.

Heuristics are often best used when time is of the essence, while algorithms are a better choice when a decision needs to be as accurate as possible.

4. Organizing Information

Before coming up with a solution, you need to first organize the available information. What do you know about the problem? What do you not know? The more information that is available the better prepared you will be to come up with an accurate solution.

When approaching a problem, it is important to make sure that you have all the data you need. Making a decision without adequate information can lead to biased or inaccurate results.

5. Allocating Resources

Of course, we don't always have unlimited money, time, and other resources to solve a problem. Before you begin to solve a problem, you need to determine how high priority it is.

If it is an important problem, it is probably worth allocating more resources to solving it. If, however, it is a fairly unimportant problem, then you do not want to spend too much of your available resources on coming up with a solution.

At this stage, it is important to consider all of the factors that might affect the problem at hand. This includes looking at the available resources, deadlines that need to be met, and any possible risks involved in each solution. After careful evaluation, a decision can be made about which solution to pursue.

6. Monitoring Progress

After selecting a problem-solving strategy, it is time to put the plan into action and see if it works. This step might involve trying out different solutions to see which one is the most effective.

It is also important to monitor the situation after implementing a solution to ensure that the problem has been solved and that no new problems have arisen as a result of the proposed solution.

Effective problem-solvers tend to monitor their progress as they work towards a solution. If they are not making good progress toward reaching their goal, they will reevaluate their approach or look for new strategies .

7. Evaluating the Results

After a solution has been reached, it is important to evaluate the results to determine if it is the best possible solution to the problem. This evaluation might be immediate, such as checking the results of a math problem to ensure the answer is correct, or it can be delayed, such as evaluating the success of a therapy program after several months of treatment.

Once a problem has been solved, it is important to take some time to reflect on the process that was used and evaluate the results. This will help you to improve your problem-solving skills and become more efficient at solving future problems.

A Word From Verywell

It is important to remember that there are many different problem-solving processes with different steps, and this is just one example. Problem-solving in real-world situations requires a great deal of resourcefulness, flexibility, resilience, and continuous interaction with the environment.

Get Advice From The Verywell Mind Podcast

Hosted by therapist Amy Morin, LCSW, this episode of The Verywell Mind Podcast shares how you can stop dwelling in a negative mindset.

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

Practicing brainstorming and coming up with multiple potential solutions to problems
Being open-minded and considering all possible options before making a decision
Breaking down problems into smaller, more manageable pieces
Asking for help when needed
Researching different problem-solving techniques and trying out new ones
Learning from mistakes and using them as opportunities to grow

It's important to communicate openly and honestly with your partner about what's going on. Try to see things from their perspective as well as your own. Work together to find a resolution that works for both of you. Be willing to compromise and accept that there may not be a perfect solution.

Take breaks if things are getting too heated, and come back to the problem when you feel calm and collected. Don't try to fix every problem on your own—consider asking a therapist or counselor for help and insight.

If you've tried everything and there doesn't seem to be a way to fix the problem, you may have to learn to accept it. This can be difficult, but try to focus on the positive aspects of your life and remember that every situation is temporary. Don't dwell on what's going wrong—instead, think about what's going right. Find support by talking to friends or family. Seek professional help if you're having trouble coping.

Davidson JE, Sternberg RJ, editors. The Psychology of Problem Solving . Cambridge University Press; 2003. doi:10.1017/CBO9780511615771

Sarathy V. Real world problem-solving . Front Hum Neurosci . 2018;12:261. Published 2018 Jun 26. doi:10.3389/fnhum.2018.00261

By Kendra Cherry, MSEd Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

Soft skills
What is a credential?
Why do a credential?
How do credentials work?
Selecting your level
How will I be assessed?
Benefits for professionals
Benefits for organisations
Benefits for postgraduates

Problem solving techniques: Steps and methods

Posted on May 29, 2019

Constant disruption has become a hallmark of the modern workforce and organisations want problem solving skills to combat this. Employers need people who can respond to change – be that evolving technology, new competitors, different models for doing business, or any of the other transformations that have taken place in recent years.

In addition, problem solving techniques encompass many of the other top skills employers seek . For example, LinkedIn’s list of the most in-demand soft skills of 2019 includes creativity, collaboration and adaptability, all of which fall under the problem-solving umbrella.

Despite its importance, many employees misunderstand what the problem solving method really involves.

What constitutes effective problem solving?

Effective problem solving doesn’t mean going away and coming up with an answer immediately. In fact, this isn’t good problem solving at all, because you’ll be running with the first solution that comes into your mind, which often isn’t the best.

Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are:

Define the problem
List all the possible solutions
Evaluate the options
Select the best solution
Create an implementation plan
Communicate your solution

Let’s look at each step in a little more detail.

It's important you take the time to brainstorm and consider all your options when solving problems.

1. Define the problem

The first step to solving a problem is defining what the problem actually is – sounds simple, right? Well no. An effective problem solver will take the thoughts of everyone involved into account, but different people might have different ideas on what the root cause of the issue really is. It’s up to you to actively listen to everyone without bringing any of your own preconceived notions to the conversation. Learning to differentiate facts from opinion is an essential part of this process.

An effective problem solver will take the opinions of everyone involved into account

The same can be said of data. Depending on what the problem is, there will be varying amounts of information available that will help you work out what’s gone wrong. There should be at least some data involved in any problem, and it’s up to you to gather as much as possible and analyse it objectively.

2. List all the possible solutions

Once you’ve identified what the real issue is, it’s time to think of solutions. Brainstorming as many solutions as possible will help you arrive at the best answer because you’ll be considering all potential options and scenarios. You should take everyone’s thoughts into account when you’re brainstorming these ideas, as well as all the insights you’ve gleaned from your data analysis. It also helps to seek input from others at this stage, as they may come up with solutions you haven’t thought of.

Depending on the type of problem, it can be useful to think of both short-term and long-term solutions, as some of your options may take a while to implement.

One of the best problem solving techniques is brainstorming a number of different solutions and involving affected parties in this process.

3. Evaluate the options

Each option will have pros and cons, and it’s important you list all of these, as well as how each solution could impact key stakeholders. Once you’ve narrowed down your options to three or four, it’s often a good idea to go to other employees for feedback just in case you’ve missed something. You should also work out how each option ties in with the broader goals of the business.

There may be a way to merge two options together in order to satisfy more people.

4. Select an option

Only now should you choose which solution you’re going to go with. What you decide should be whatever solves the problem most effectively while also taking the interests of everyone involved into account. There may be a way to merge two options together in order to satisfy more people.

5. Create an implementation plan

At this point you might be thinking it’s time to sit back and relax – problem solved, right? There are actually two more steps involved if you want your problem solving method to be truly effective. The first is to create an implementation plan. After all, if you don’t carry out your solution effectively, you’re not really solving the problem at all.

Create an implementation plan on how you will put your solution into practice. One problem solving technique that many use here is to introduce a testing and feedback phase just to make sure the option you’ve selected really is the most viable. You’ll also want to include any changes to your solution that may occur in your implementation plan, as well as how you’ll monitor compliance and success.

6. Communicate your solution

There’s one last step to consider as part of the problem solving methodology, and that’s communicating your solution . Without this crucial part of the process, how is anyone going to know what you’ve decided? Make sure you communicate your decision to all the people who might be impacted by it. Not everyone is going to be 100 per cent happy with it, so when you communicate you must give them context. Explain exactly why you’ve made that decision and how the pros mean it’s better than any of the other options you came up with.

Prove your problem solving skills with Deakin

Employers are increasingly seeking soft skills, but unfortunately, while you can show that you’ve got a degree in a subject, it’s much harder to prove you’ve got proficiency in things like problem solving skills. But this is changing thanks to Deakin’s micro-credentials. These are university-level micro-credentials that provide an authoritative and third-party assessment of your capabilities in a range of areas, including problem solving. Reach out today for more information .

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.

school Campus Bookshelves
menu_book Bookshelves
perm_media Learning Objects
login Login
how_to_reg Request Instructor Account
hub Instructor Commons
Download Page (PDF)
Download Full Book (PDF)
Periodic Table
Physics Constants
Scientific Calculator
Reference & Cite
Tools expand_more
Readability

selected template will load here

This action is not available.

3.2: Problem-Solving to Find Entrepreneurial Solutions

Last updated
Save as PDF
Page ID 62755

LEARNING OBJECTIVES

By the end of this section, you will be able to:

Define problem-solving in the context of entrepreneurship
Describe and compare the adaptive model and the innovative model of problem-solving
Identify the skills entrepreneurs need for effective problem solving
Identify types of problem solvers

As you’ve learned, entrepreneurs often visualize an opportunity gap, a gap between what exists and what could exist, as Hirabayashi and Lidey did with Shine. Entrepreneurial problem-solving is the process of using innovation and creative solutions to close that gap by resolving societal, business, or technological problems. Sometimes, personal problems can lead to entrepreneurial opportunities if validated in the market. The entrepreneur visualizes the prospect of filling the gap with an innovative solution that might entail the revision of a product or the creation of an entirely new product. In any case, the entrepreneur approaches the problem-solving process in various ways. This chapter is more about problem-solving as it pertains to the entrepreneur’s thought process and approach rather than on problem-solving in the sense of opportunity recognition and filling those gaps with new products.

For example, Sara Blakely (as shown in Figure 3.2.1) saw a need for body contouring and smoothing undergarments one day in the late 1990s when she was getting dressed for a party and couldn’t find what she needed to give her a silhouette she’d be pleased with in a pair of slacks. She saw a problem: a market need. But her problem-solving efforts are what drove her to turn her solution (Spanx undergarments) into a viable product. Those efforts came from her self-admitted can-do attitude: “It’s really important to be resourceful and scrappy—a glass-half-full mindset.” 1 Her efforts at creating a new undergarment met resistance with hosiery executives, most of whom were male and out of touch with their female consumers. The hosiery owner who decided to help Blakely initially passed on the idea until running it by his daughters and realizing she was on to something. That something became Spanx, and today, Blakely is a successful entrepreneur. 2

Before getting into the heart of this chapter, we need to make a distinction: Decision making is different from problem-solving . A decision is needed to continue or smooth a process affecting the operation of a firm. It can be intuitive or might require research and a long period of consideration. Problem-solving, however, is more direct. It entails the solution of some problem where a gap exists between a current state and a desired state. Entrepreneurs are problem solvers who offer solutions using creativity or innovative ventures that exploit opportunities. This chapter focuses on different approaches to problem-solving and need recognition that help potential entrepreneurs come up with ideas and refine those ideas.

Two Problem Solving Models: Adaptive and Innovative

There are two prominent established problem-solving models: adaptive and innovative . A renowned British psychologist, Michael Kirton, developed the Kirton Adaption-Innovation (KAI) Inventory to measure an individual’s style of problem-solving. 3 Problem-solving preferences are dependent on the personality characteristics of originality, conformity, and efficiency, according to Kirton. The KAI inventory identifies an individual’s problem-solving approach by measuring agreement with statements that align with characteristics, such as the ability to produce many novel ideas, to follow rules and get along in groups, and to systematically orient daily behavior. The results categorize an individual as an innovator or an adaptor. Innovators are highly original, do not like to conform, and value efficiency less than adaptors.

The first and more conservative approach an entrepreneur may use to solve problems is the adaptive model. The adaptive model seeks solutions for problems in ways that are tested and known to be effective. An adaptive model accepts the problem definition and is concerned with resolving problems rather than finding them. This approach seeks greater efficiency while aiming at continuity and stability. The second and more creative approach is the innovative model of entrepreneurial problem solving, which uses techniques that are unknown to the market and that bring advantage to an organization. An innovative problem-solving style challenges the problem definition, discovers problems and avenues for their solutions, and questions existing assumptions—in a nutshell, it does things differently. It uses outside-the-box thinking and searches for novel solutions. Novelty is a shared trait of creative entrepreneurship, and it’s why entrepreneurs gravitate toward this method of problem-solving. According to Dr. Shaun M. Powell, a senior lecturer at the University of Wollongong, Australia: “Creative entrepreneurs are notable for a distinctive management style that is based on intuition, informality and rapid decision making, whereas the more conventional thinking styles are not in accord with the unique attributes of creative entrepreneurs.” 4 This way of problem-solving doesn’t alter an existing product. It is the creation of something entirely new.

For example, healthcare facilities have long been known as a source of methicillin-resistant Staphylococcus aureus (MRSA), a deadly infection that can have long-term effects on patients. Vital Vio, led by Colleen Costello, has developed white light technology that effectively disinfects healthcare facilities by targeting a molecule specific to bacteria. The light, safe to humans, can burn constantly to kill regenerative bacteria. An adaptive problem-solving model would seek to minimize harm of MRSA within a hospital—to respond to it—whereas the Vital Vio is an entirely new technique that seeks to eliminate it. Adaptive solutions to MRSA include established processes and protocols for prevention, such as having doctors, nurses, and other healthcare providers clean their hands with soap and water, or an alcohol-based hand rub before and after patient care, testing patients to see if they have MRSA on their skin, cleaning hospital rooms and medical equipment, and washing and drying clothes and bed linens in the warmest recommended temperatures. 5

LINK TO LEARNING

Problem-Solving Skills

While identifying problems is a necessary part of the origin of the entrepreneurial process, managing problems is an entirely different aspect once a venture is off the ground and running. An entrepreneur does not have the luxury of avoiding problems and is often responsible for all problem-solving in a startup or other form of business. There are certain skills that entrepreneurs possess that make them particularly good problem solvers. Let’s examine each skill (shown in Figure 3.2.2).

Critical Thinking

Critical thinking is the complex analysis of a problem or issue with the goal of solving the problem or making a decision. The entrepreneur analyzes and peels away the layers of a problem to find the core of an issue facing a business. The entrepreneur focuses on the heart of the problem and responds reasonably and openly to suggestions for solving it. Critical thinking is not only important for developing entrepreneurial ideas: it is a sought-after asset in education and employment. Entrepreneur Rebecca Kantar dropped out of Harvard in 2015 to found the tech startup Imbellus, which aims to replace standardized college admissions tests like the SAT with interactive scenarios that test critical-thinking skills. Many standardized tests may include multiple-choice questions asking for the answer to a straightforward knowledge question or math problem. Kantar seeks to create tests that are more concerned with the analytic ability and reasoning that goes into the process of solving the problem. Imbellus says it aims to test “how people think,” not just what they know. The platform, which has not yet launched, will use simulations for its user assessments. 6

Read more about problem-solving and EnterpriseWorks/Vita’s story at Harvard Business Review .

Communication

Ideation exercises, such as brainstorming sessions, are good communication tools that entrepreneurs can use to generate solutions to problems. Another such tool is a hackathon —an event, usually hosted by a tech company or organization, which brings together programmers and workers with other degrees of specialization within the company, community, or organization to collaborate on a project over a short period of time. These can last from twenty-four hours to a few days over a weekend. A hackathon can be an internal company-wide initiative or an external event that brings community participants together. A business model canvas and other activities, outlined in other chapters, can be used internally or externally to identify problems and work toward creating a viable solution.

Networking is an important manifestation of useful communication. What better method is there of presenting one’s concept, gaining funding and buy-in, and marketing for the startup than through building a network of individuals willing to support your venture? A network may consist of potential employees, customers, board members, outside advisors, investors, or champions (people who just love your product) with no direct vested interest. Social networks consist of weak ties and strong ties. Sociologist Mark Granovetter studied such networks back in the 1970s, and his findings still apply today, even if we include social media networks in the definition too. Weak ties facilitate flow of information and community organization, he said, whereas strong ties represent strong connections among close friends, family members, and supportive coworkers. 7 Strong ties require more work to maintain than weak ties (as illustrated by the strong lines and weak dotted lines in Figure 3.2.3) and in a business context, they don’t lead to many new opportunities. Weak ties, in contrast, do open doors in that they act as bridges to other weak ties within functional areas or departments that you might not have had access to directly or through strong ties. 8

In fact, many young entrepreneurs, including tech entrepreneur Oliver Isaacs, realize college is a great place to begin building teams. Isaacs is the founder of viral opinion network Amirite.com, which is widely credited as the place where Internet memes started and online slang got a foothold. 9 Amirite.com consists of a large network of pages and partnerships on Facebook and Instagram that reach 15 million users each month. Isaacs recommends using your alumni network to build a team and customer base for your own venture because you never know if you’re talking to a future employee or partner.

Sharing of ideas and resources is highly valued in the entrepreneurial process. Communication is a vital skill in problem-solving because the ability to identify and articulate the problem (define the problem space) is necessary to adequately address a problem. A problem can be too vague or broad or narrow. Thus, communicating the problem is important, as is conveying the solution.

Decisiveness

Read this LinkedIn blog post on decisiveness to learn more.

Ability to Analyze Data

Data analysis is the process of analyzing data and modeling it into a structure that leads to innovative conclusions. It is one thing to amass information and statistics. It is another to make sense of that data, to use it to fill a market need or forecast a trend to come. Successful founders know how to pose questions about and make meaning out of information. And if they can’t do that themselves, they know how to bring in experts who can.

Understanding of Business and Industry

Entrepreneurs need a sound understanding of markets and industries. Often times, they are already working in a large organization when they see growth opportunities or inefficiencies in a market. The employee gains a deep understanding of the industry at hand. If the employee considers a possible solution for a problem, this solution might become the basis for a new business.

A similar experience occurred for entrepreneur Katie Witkin. After working in traditional marketing roles, the University of Wisconsin-Madison graduate, pictured in Figure 3.2.4, left agency life behind four years out of college to cofound her own company, AGW Group. In 2009, Witkin had been interning at a music marketing agency that didn’t have a social media department. She knew, both from her time at college and from observing industry trends, that social media was changing the way companies connected with customers. For her own venture, she expanded the focus to all supporting brands to manage all things digital. Today, the cultural and marketing communications agency has fifteen employees and big-name clients ranging from HBO to Red Bull. 11

Resourcefulness

Resourcefulness is the ability to discover clever solutions to obstacles. Sherrie Campbell, a psychologist, author, and frequent contributor to Entrepreneur magazine on business topics, put it this way: “There is not a more useful or important trait to possess than resourcefulness in the pursuit of success. Resourcefulness is a mindset, and is especially relevant when the goals you have set are difficult to achieve or you cannot envision a clear path to get to where you desire to go. With a resourcefulness mindset you are driven to find a way. An attitude of resourcefulness inspires out-of-the-box thinking, the generation of new ideas, and the ability to visualize all the possible ways to achieve what you desire. Resourcefulness turns you into a scrappy, inventive, and enterprising entrepreneur. It places you a cut above the rest.” 12

Entrepreneurs start thinking about a business venture or startup by talking to people and procuring experts to help create, fund, and begin a business. Entrepreneurs are risk-takers, passionate about new endeavors. If they don’t have a college degree or a great deal of business experience, they understand there are many resources available to support them in the endeavor, such as the Service Corps of Retired Executives (SCORE) and the Small Business Administration (SBA). There are many sources available to fund the business with little or no debt and options. The entrepreneur follows a vision and researches opportunities to move toward a dream.

Types of Problem-Solvers

Entrepreneurs have an insatiable appetite for problem-solving. This drive motivates them to find a resolution when a gap in a product or service occurs. They recognize opportunities and take advantage of them. There are several types of entrepreneurial problem solvers, including self-regulators, theorists, and petitioners.

Self-Regulating Problem-Solvers

Self-regulating problem solvers are autonomous and work on their own without external influence. They have the ability to see a problem, visualize a possible solution to the problem, and seek to devise a solution, as Figure 3.2.5 illustrates. The solution may be a risk, but a self-regulating problem solver will recognize, evaluate, and mitigate the risk. For example, an entrepreneur has programmed a computerized process for a client, but in testing it, finds the program continually falls into a loop, meaning it gets stuck in a cycle and doesn’t progress. Rather than wait for the client to find the problem, the entrepreneur searches the code for the error causing the loop, immediately edits it, and delivers the corrected program to the customer. There is immediate analysis, immediate correction, and immediate implementation. The self-regulating problem solvers’ biggest competitive advantage is the speed with which they recognize and provide solutions to problems.

Theorist Problem Solvers

Theorist problem-solvers see a problem and begin to consider a path toward solving the problem using a theory. Theorist problem solvers are process-oriented and systematic. While managers may start with a problem and focus on an outcome with little consideration of a means to an end, entrepreneurs may see a problem and begin to build a path with what is known, a theory, toward an outcome. That is, the entrepreneur proceeds through the steps to solve the problem and then builds on the successes, rejects the failures, and works toward the outcome by experimenting and building on known results. At this point, the problem solver may not know the outcome, but a solution will arise as experiments toward a solution occur. Figure 3.2.6 shows this process.

Petitioner Problem-Solvers

Petitioner problem-solvers (Figure 3.2.7) see a problem and ask others for solution ideas. This entrepreneur likes to consult a person who has “been there and done that.” The petitioner might also prefer to solve the problem in a team environment. Petitioning the entrepreneurial team for input ensures that the entrepreneur is on a consensus-driven path. This type of problem-solving takes the longest to complete because the entrepreneur must engage in a democratic process that allows all members on the team to have input. The process involves exploration of alternatives for the ultimate solution. In organizational decision-making, for example, comprehensiveness is a measure of the extent a firm attempts to be inclusive or exhaustive in its decision-making. Comprehensiveness can be gauged by the number of scheduled meetings, the process by which information is sought, the process by which input is obtained from external sources, the number of employees involved, the use of specialized consultants and the functional expertise of the people involved, the years of historical data review, and the assignment of primary responsibility, among other factors. Comprehensive decision-making would be an example of a petitioner problem-solving style, as it seeks input from a vast number of team members.

In summary, there is no right or wrong style of problem-solving; each problem solver must rely on the instincts that best drive innovation. Further, they must remember that not all problem-solving methods work in every situation. They must be willing to adapt their own preference to the situation to maximize efficiency and ensure they find an effective solution. Attempting to force a problem-solving style may prevent an organization from finding the best solution. While general entrepreneurial problem-solving skills such as critical thinking, decisiveness, communication, and the ability to analyze data will likely be used on a regular basis in your life and entrepreneurial journey, other problem-solving skills and the approach you take will depend on the problem as it arises.

There are a number of resources online that can help analyze your problem-solving abilities. Mindtools.com is one such resource. These are useful to learn your general problem-solving tendencies before being called upon to apply them in a real-world setting. One of the problem-solving techniques available from mindtools.com offers that problems can be addressed from six different perspectives. Called CATWOE, the approach is an acronym for Customers, Actors (people within the organization), Transformative, Worldwide, Owner, and Environment (organizational).

Learn more about the CATWOE technique for problem-solving.

Stage 2 in the Design Thinking Process: Define the Problem

Once you’ve empathized with your users, you can move on to the second stage of the design thinking process and define the problem your users need you to solve..

If you’ve read our introduction to User Experience (UX) Design , you’ll know that UX is essentially about solving the problems that prevent users from accomplishing what they want to do with our product.

Before you can go into problem-solving mode, however, there is one very crucial step that you need to complete—one that will shape your entire design project from start to finish. In the Design Thinking process , this step is what’s known as the “define” stage.

As the second step in the Design Thinking process, the define stage is where you’ll establish a clear idea of exactly which problem you will solve for the user. You’ll then shape this into a problem statement which will act as your northern star throughout the design process.

In this guide, we’ll tell you everything you need to know about this stage in the Design Thinking process, as well as how to define a meaningful problem statement.

Here’s what we’ll cover:

What is the define stage and why is it necessary?
What is a problem statement?
How to define a meaningful problem statement
What comes after the define phase?

Before we dive in, though, if you’d like an overview of the entire Design Thinking process, check out this video:

1. What is the define stage and why is it necessary?

As the second step in the Design Thinking process, the define stage is dedicated to defining the problem: what user problem will you be trying to solve? In other words, what is your design challenge?

The define stage is preceded by the empathize phase , where you’ll have learned as much about your users as possible, conducting interviews and using a variety of immersion and observation techniques. Once you have a good idea of who your users are and, most importantly, their wants, needs, and pain-points, you’re ready to turn this empathy into an actionable problem statement.

The relationship between the empathize and define stages can best be described in terms of analysis and synthesis. In the empathize phase, we use analysis to break down everything we observe and discover about our users into smaller, more manageable components—dividing their actions and behaviour into “what”, “why” and “how” categories, for example. In the define stage, we piece these components back together, synthesising our findings to create a detailed overall picture.

Why is the define stage so important?

The define stage ensures you fully understand the goal of your design project. It helps you to articulate your design problem, and provides a clear-cut objective to work towards. A meaningful, actionable problem statement will steer you in the right direction, helping you to kick-start the ideation process (see Stage Three of the Design Thinking process ) and work your way towards a solution.

Without a well-defined problem statement, it’s hard to know what you’re aiming for. Your work will lack focus, and the final design will suffer. Not only that: in the absence of a clear problem statement, it’s extremely difficult to explain to stakeholders and team members exactly what you are trying to achieve.

With this in mind, let’s take a closer look at problem statements and how you can go about defining them.

2. What is a problem statement?

A problem statement identifies the gap between the current state (i.e. the problem) and the desired state (i.e. the goal) of a process or product . Within the design context, you can think of the user problem as an unmet need. By designing a solution that meets this need, you can satisfy the user and ensure a pleasant user experience.

A problem statement, or point of view (POV) statement, frames this problem (or need) in a way that is actionable for designers. It provides a clear description of the issue that the designer seeks to address, keeping the focus on the user at all times.

Problem or POV statements can take various formats, but the end goal is always the same: to guide the design team towards a feasible solution. Let’s take a look at some of the ways you might frame your design problem:

From the user’s perspective: “I am a young working professional trying to eat healthily, but I’m struggling because I work long hours and don’t always have time to go grocery shopping and prepare my meals. This makes me feel frustrated and bad about myself.”
From a user research perspective: “Busy working professionals need an easy, time-efficient way to eat healthily because they often work long hours and don’t have time to shop and meal prep.”
Based on the four Ws—who, what, where, and why: “Our young working professional struggles to eat healthily during the week because she is working long hours. Our solution should deliver a quick and easy way for her to procure ingredients and prepare healthy meals that she can take to work.”

As you can see, each of these statements addresses the same issue—just in a slightly different way. As long as you focus on the user, what they need and why, it’s up to you how you choose to present and frame your design problem.

We’ll look at how to form your problem statement a little later on. Before we do, let’s consider some problem statement “do”s and “don’t”s.

What makes a good problem statement?

A good problem statement is human-centered and user-focused. Based on the insights you gathered in the empathize phase, it focuses on the users and their needs—not on product specifications or business outcomes. Here are some pointers that will help you create a meaningful problem statement:

Focus on the user: The user and their needs should be front and center of your problem statement. Avoid statements that start with “we need to…” or “the product should”, instead concentrating on the user’s perspective: “Young working professionals need…”, as in the examples above.
Keep it broad: A good problem statement leaves room for innovation and creative freedom. It’s important to keep it broad enough to invite a range of different ideas; avoid any references to specific solutions or technical requirements, for example.
Make it manageable: At the same time, your problem statement should guide you and provide direction. If it’s too broad in terms of the user’s needs and goals, you’ll struggle to hone in on a suitable solution. So, don’t try to address too many user needs in one problem statement; prioritize and frame your problem accordingly.

Bearing these things in mind, let’s explore some useful methods for creating a meaningful problem statement.

3. How to write a meaningful problem statement

Writing a meaningful problem statement can be extremely challenging. How do you condense all the complexities of the user’s conscious and unconscious desires into one simple, actionable statement? Fortunately, there are some tried-and-tested methods that will help you do just that.

Space saturation and group

One of the first steps in defining a problem statement is to organize your findings from the empathize phase. Space saturation and group is a popular method used by design thinkers to collect and visually present all observations made in the empathize phase in one space. As the name suggests, you will literally “saturate” a wall or whiteboard with Post-It notes and images, resulting in a collage of artifacts from your user research.

As the Stanford d.school explains: “You space saturate to help you unpack thoughts and experiences into tangible and visual pieces of information that you surround yourself with to inform and inspire the design team. You group these findings to explore what themes and patterns emerge, and strive to move toward identifying meaningful needs of people and insights that will inform your design solutions.”

This method should involve anyone who took part in the empathize stage of the design project, and should take no longer than 20-30 minutes.

The four Ws

Asking the right questions will help you put your finger on the right problem statement. With all your findings from the empathize phase in one place, ask yourself the four Ws: Who , what , where , and why?

Who is experiencing the problem? In other words, who is your target user; who will be the focus of your problem statement?
What is the problem? Based on the observations you made during the empathize phase, what are the problems and pain-points that frequently came up? What task is the user trying to accomplish, and what’s standing in their way?
Where does the problem present itself? In what space (physical or digital), situation or context is the user when they face this problem? Are there any other people involved?
Why does it matter? Why is it important that this problem be solved? What value would a solution bring to the user, and to the business?

Approaching your observations with these four questions in mind will help you to identify patterns within your user research. In identifying the most prevalent issues, you’ll be one step closer to formulating a meaningful problem statement.

The five whys

Another question-based strategy, the five whys technique can help you delve deeper into the problem and drill down to the root cause. Once you’ve identified the root cause, you have something that you can act upon; somewhere specific to focus your problem-solving efforts.

Let’s take our previous example of the young working professional who wants to eat healthily, but finds it difficult to do so. Here’s how you might use the five whys to break the problem down and get to the root cause:

Why is she not eating healthily? → She orders takeaway everyday.
Why does she order takeaway everyday? → Her fridge and cupboards are empty.
Why are the fridge and cupboards empty? → She hasn’t been grocery shopping in over a week.
Why hasn’t she been grocery shopping? → She doesn’t have time to go to the supermarket.
Why doesn’t she have time? → She works long hours and is exhausted.

The root cause here is a lack of time, so your solution might focus on efficiency and convenience. Your final problem statement might look something like this: “Young working professionals need a quick, convenient solution to eating healthily.”

4. What comes after the define phase?

By the end of the define phase, you’ll have turned your findings from the empathize stage into a meaningful, actionable problem statement. With your problem statement to hand, you’ll be ready to move on to the ideation phase , where you’ll turn your problem statement into “how might we” questions and generate as many potential solutions as possible.

As you move through the Design Thinking process, you’ll constantly refer back to your problem statement to make sure you’re moving in the right direction. A well-thought-out problem statement will keep you on track, help you communicate your objectives to key stakeholders, and ultimately lead you to that all-important user solution.

Want to learn more about designing user-friendly solutions? Check out these articles:

UX Best Practices: How Can You Become A Better Designer?
What Is User Experience Design? Everything You Need To Know To Get Started
This Is Why Empathy Matters As A UX Designer
What is lean UX?

Have a language expert improve your writing

Run a free plagiarism check in 10 minutes, generate accurate citations for free.

Knowledge Base
Starting the research process
How to Write a Problem Statement | Guide & Examples

How to Write a Problem Statement | Guide & Examples

Published on November 6, 2022 by Shona McCombes and Tegan George. Revised on November 20, 2023.

A problem statement is a concise and concrete summary of the research problem you seek to address. It should:

Contextualize the problem. What do we already know?
Describe the exact issue your research will address. What do we still need to know?
Show the relevance of the problem. Why do we need to know more about this?
Set the objectives of the research. What will you do to find out more?

When should you write a problem statement, step 1: contextualize the problem, step 2: show why it matters, step 3: set your aims and objectives.

Problem statement example

Here's why students love Scribbr's proofreading services

Discover proofreading & editing

The problem statement should frame your research problem, giving some background on what is already known.

Practical research problems

For practical research, focus on the concrete details of the situation:

Where and when does the problem arise?
Who does the problem affect?
What attempts have been made to solve the problem?

Theoretical research problems

For theoretical research, think about the scientific, social, geographical and/or historical background:

What is already known about the problem?
Is the problem limited to a certain time period or geographical area?
How has the problem been defined and debated in the scholarly literature?

The problem statement should also address the relevance of the research. Why is it important that the problem is addressed?

Don’t worry, this doesn’t mean you have to do something groundbreaking or world-changing. It’s more important that the problem is researchable, feasible, and clearly addresses a relevant issue in your field.

Practical research is directly relevant to a specific problem that affects an organization, institution, social group, or society more broadly. To make it clear why your research problem matters, you can ask yourself:

What will happen if the problem is not solved?
Who will feel the consequences?
Does the problem have wider relevance? Are similar issues found in other contexts?

Sometimes theoretical issues have clear practical consequences, but sometimes their relevance is less immediately obvious. To identify why the problem matters, ask:

How will resolving the problem advance understanding of the topic?
What benefits will it have for future research?
Does the problem have direct or indirect consequences for society?

Finally, the problem statement should frame how you intend to address the problem. Your goal here should not be to find a conclusive solution, but rather to propose more effective approaches to tackling or understanding it.

The research aim is the overall purpose of your research. It is generally written in the infinitive form:

The aim of this study is to determine …
This project aims to explore …
This research aims to investigate …

The research objectives are the concrete steps you will take to achieve the aim:

Qualitative methods will be used to identify …
This work will use surveys to collect …
Using statistical analysis, the research will measure …

The aims and objectives should lead directly to your research questions.

Learn how to formulate research questions

You can use these steps to write your own problem statement, like the example below.

Step 1: Contextualize the problem A family-owned shoe manufacturer has been in business in New England for several generations, employing thousands of local workers in a variety of roles, from assembly to supply-chain to customer service and retail. Employee tenure in the past always had an upward trend, with the average employee staying at the company for 10+ years. However, in the past decade, the trend has reversed, with some employees lasting only a few months, and others leaving abruptly after many years.

Step 2: Show why it matters As the perceived loyalty of their employees has long been a source of pride for the company, they employed an outside consultant firm to see why there was so much turnover. The firm focused on the new hires, concluding that a rival shoe company located in the next town offered higher hourly wages and better “perks”, such as pizza parties. They claimed this was what was leading employees to switch. However, to gain a fuller understanding of why the turnover persists even after the consultant study, in-depth qualitative research focused on long-term employees is also needed. Focusing on why established workers leave can help develop a more telling reason why turnover is so high, rather than just due to salaries. It can also potentially identify points of change or conflict in the company’s culture that may cause workers to leave.

Step 3: Set your aims and objectives This project aims to better understand why established workers choose to leave the company. Qualitative methods such as surveys and interviews will be conducted comparing the views of those who have worked 10+ years at the company and chose to stay, compared with those who chose to leave.

If you want to know more about the research process , methodology , research bias , or statistics , make sure to check out some of our other articles with explanations and examples.

Methodology

Sampling methods
Simple random sampling
Stratified sampling
Cluster sampling
Likert scales
Reproducibility

Statistics

Null hypothesis
Statistical power
Probability distribution
Effect size
Poisson distribution

Research bias

Optimism bias
Cognitive bias
Implicit bias
Hawthorne effect
Anchoring bias
Explicit bias

Once you’ve decided on your research objectives , you need to explain them in your paper, at the end of your problem statement .

Keep your research objectives clear and concise, and use appropriate verbs to accurately convey the work that you will carry out for each one.

I will compare …

All research questions should be:

Focused on a single problem or issue
Researchable using primary and/or secondary sources
Feasible to answer within the timeframe and practical constraints
Specific enough to answer thoroughly
Complex enough to develop the answer over the space of a paper or thesis
Relevant to your field of study and/or society more broadly

Research objectives describe what you intend your research project to accomplish.

They summarize the approach and purpose of the project and help to focus your research.

Your objectives should appear in the introduction of your research paper , at the end of your problem statement .

Your research objectives indicate how you’ll try to address your research problem and should be specific:

Cite this Scribbr article

If you want to cite this source, you can copy and paste the citation or click the “Cite this Scribbr article” button to automatically add the citation to our free Citation Generator.

McCombes, S. & George, T. (2023, November 20). How to Write a Problem Statement | Guide & Examples. Scribbr. Retrieved April 3, 2024, from https://www.scribbr.com/research-process/problem-statement/

Is this article helpful?

Shona McCombes

Other students also liked, how to choose a dissertation topic | 8 steps to follow, how to define a research problem | ideas & examples, writing strong research questions | criteria & examples, "i thought ai proofreading was useless but..".

I've been using Scribbr for years now and I know it's a service that won't disappoint. It does a good job spotting mistakes”

Reference management. Clean and simple.

How to write a problem statement

What is a problem statement?

Why write a problem statement, when are problem statements commonly written, how do i write a problem statement, the format of a problem statement, the trademarks of a good problem statement, an example of a problem statement, frequently asked questions about problem statements, related articles.

A problem statement is a clear and concise description of the problem or issue a team aims to address in a project.

A problem statement identifies a problem’s current state, desired future state, and the gaps that lie between the two. It doesn't define the solution to the problem or provide a road map for solving the problem; it only gives an outline of what the problem is.

However, the researcher or team can later use the problem statement to validate that their work delivered an outcome that resulted in the solution.

A problem statement is a useful communication tool, as it keeps the whole team on track and tells them why the project is important. A problem statement helps someone to define and understand the problem, identify the goals of the project, and outline the scope of work.

A problem statement is especially relevant for projects that aim to improve processes, as it allows for the easier development of solutions. Referencing it helps guide the activities carried out and aids the research team in staying focused. The information in a problem statement also helps a team make important decisions.

When the desired solution is implemented later on, a problem statement can help make sure that steps are put into place to prevent the original problem from recurring in the future.

Problem statements are used in both academic and business contexts. In a business environment, project managers can use them to help execute process improvement projects.

But in an academic setting, they can help researchers to contextualize and understand the significance of the problem in a research project. This guide focuses on academic problem statements.

Before planning or writing out your academic problem statement, ask yourself some important questions, and make notes with your answers:

What is the problem?
How often does the problem occur?
Where does the problem occur?
When does the problem occur?
Who does the problem impact?
What causes the problem?
How would things ideally work if the problem wasn't present?
Why is this a problem, and why does it matter?
What impact does the problem cause?
Which possible solution/s to the problem are you going to propose?
What are the predicted benefits or outcomes of your solutions?

When you write your problem statement, split it into four sections:

Problem: Here, simply define what your problem is, clearly and concisely. Make it no longer than one or two sentences.
Background: This is the section where you can describe what causes the problem, how often it occurs, where and when it occurs, and who the problem impacts.
Relevance: You'll want to show how the problem is relevant, as well as why it matters and requires a solution. This is a great space to specify why it's a problem and what impacts it causes. If it fits comfortably, you can also articulate how things would ideally work if the problem wasn't present.
Objectives: This section doesn't require great detail or length, as the problem statement isn't the area of your research project in which to specifically problem-solve. However, you should lay out a brief plan of what you're going to do to investigate and how that should help you formulate solutions. You can also hypothesize on possible solutions you're going to propose, and the benefits you predict from these.

A quality problem statement should be:

Concise: You should be able to summarize your problem, as well as the different elements of how and why it's a problem, in succinct sentences. If you can't, revisit your initial notes and clarify what you want to achieve with your project.
Specific: Only write about one issue in a problem statement, even if there's more than one impact of that issue. Your research and actions then only have to focus on solving the one problem, and there's no confusion.
Measurable: Be clear about how you're able to measure and convey both the problem and your proposed objectives. This is usually by communicating the problem in terms of degree and frequency.

Below is an academic problem statement example. You don't need to include any headers in your real problem statement, but we'll do so here to show you how the sections of the document function in practice.

There is worryingly low uptake of free cervical cancer screening in the UK amongst women aged 25 to 35.

According to an assessment conducted by X Health Trust, only 60% of 25- to 35-year-old female patients attended cervical cancer screening appointments within the last two years.

This could be due to several contributing factors:

Female patients in this age group may be more likely to believe they are not susceptible to cervical cancer due to their younger age.
There has been an absence of regular and informative public health announcements on this subject within the last seven years.
Cervical cancer screening has a reputation for being an unpleasant experience, which could be off-putting for patients due to attend one.

Cervical cancer is the 14th most common cancer in females in the UK, representing a notable health risk. As of 2017, there were around 3,200 new cervical cancer cases, with 850 consequent deaths, in the UK every year.

Although mortality rates in the UK for cervical cancer are highest in females aged 85 to 89, incidence rates for the disease are still highest in females aged 30 to 34.

When cervical cancer is diagnosed at its earliest stage, 96% of people diagnosed will survive their disease for one year or more. This is compared with only 50% of people when the disease is diagnosed at the latest stage.

Screening is a vital health service as many cervical cancer patients will be symptomless until they are in a later stage of the disease.

We are going to conduct a survey of 10,000 females in the UK between the ages of 25 and 35. We will first ask them the question of whether they have attended a cervical screening appointment in the last five years. For those who answer “no,” we will then present them with multiple-choice options that answer the question, “why not?”

From the results we gather, we should be able to accurately assess the most common reasons why there is a low uptake in cervical cancer screening in this age group. We will then propose interventions to the medical community based on our findings.

Our ultimate goal is to increase the uptake of cervical cancer screening by females between 25 and 35 in the UK over the next five years.

🔲 Background

🔲 Relevance

🔲 Objectives

A problem statement helps you define and understand a problem, identify the goals of your project, and outline the scope of your work. A problem statement is especially important for projects that aim to improve processes, as it allows for the easier development of solutions.

A good problem statement is concise, specific and measurable. It summarizes the different elements of how and why it's a problem. It focusses on solving this one problem, and there is no confusion as to what the problem is and how it is solved. It is clear how the problem can be solved and how this can be measured.

To start a problem statement, first ask yourself some important questions to define the problem, like:

Which possible solutions to the problem are you going to propose?

When you write your problem statement, split it into these sections:

A smart problem statement is concise, specific and measurable. It should briefly describe the problem, where it is occurring, the timeframe over which it has been occurring, and the size and magnitude of the problem.

Problem Solving

Foundations course, introduction.

Before we start digging into some pretty nifty JavaScript, we need to begin talking about problem solving : the most important skill a developer needs.

Problem solving is the core thing software developers do. The programming languages and tools they use are secondary to this fundamental skill.

From his book, “Think Like a Programmer” , V. Anton Spraul defines problem solving in programming as:

Problem solving is writing an original program that performs a particular set of tasks and meets all stated constraints.

The set of tasks can range from solving small coding exercises all the way up to building a social network site like Facebook or a search engine like Google. Each problem has its own set of constraints, for example, high performance and scalability may not matter too much in a coding exercise but it will be vital in apps like Google that need to service billions of search queries each day.

New programmers often find problem solving the hardest skill to build. It’s not uncommon for budding programmers to breeze through learning syntax and programming concepts, yet when trying to code something on their own, they find themselves staring blankly at their text editor not knowing where to start.

The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you’ll be prepared to solve real world problems.

In this lesson we will walk through a few techniques that can be used to help with the problem solving process.

Lesson overview

This section contains a general overview of topics that you will learn in this lesson.

Explain the three steps in the problem solving process.
Explain what pseudocode is and be able to use it to solve problems.
Be able to break a problem down into subproblems.

Understand the problem

The first step to solving a problem is understanding exactly what the problem is. If you don’t understand the problem, you won’t know when you’ve successfully solved it and may waste a lot of time on a wrong solution .

To gain clarity and understanding of the problem, write it down on paper, reword it in plain English until it makes sense to you, and draw diagrams if that helps. When you can explain the problem to someone else in plain English, you understand it.

Now that you know what you’re aiming to solve, don’t jump into coding just yet. It’s time to plan out how you’re going to solve it first. Some of the questions you should answer at this stage of the process:

Does your program have a user interface? What will it look like? What functionality will the interface have? Sketch this out on paper.
What inputs will your program have? Will the user enter data or will you get input from somewhere else?
What’s the desired output?
Given your inputs, what are the steps necessary to return the desired output?

The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.

Pseudocode is writing out the logic for your program in natural language instead of code. It helps you slow down and think through the steps your program will have to go through to solve the problem.

Here’s an example of what the pseudocode for a program that prints all numbers up to an inputted number might look like:

This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.

Divide and conquer

From your planning, you should have identified some subproblems of the big problem you’re solving. Each of the steps in the algorithm we wrote out in the last section are subproblems. Pick the smallest or simplest one and start there with coding.

It’s important to remember that you might not know all the steps that you might need up front, so your algorithm may be incomplete -— this is fine. Getting started with and solving one of the subproblems you have identified in the planning stage often reveals the next subproblem you can work on. Or, if you already know the next subproblem, it’s often simpler with the first subproblem solved.

Many beginners try to solve the big problem in one go. Don’t do this . If the problem is sufficiently complex, you’ll get yourself tied in knots and make life a lot harder for yourself. Decomposing problems into smaller and easier to solve subproblems is a much better approach. Decomposition is the main way to deal with complexity, making problems easier and more approachable to solve and understand.

In short, break the big problem down and solve each of the smaller problems until you’ve solved the big problem.

Solving Fizz Buzz

To demonstrate this workflow in action, let’s solve a common programming exercise: Fizz Buzz, explained in this wiki article .

Understanding the problem

Write a program that takes a user’s input and prints the numbers from one to the number the user entered. However, for multiples of three print Fizz instead of the number and for the multiples of five print Buzz . For numbers which are multiples of both three and five print FizzBuzz .

This is the big picture problem we will be solving. But we can always make it clearer by rewording it.

Write a program that allows the user to enter a number, print each number between one and the number the user entered, but for numbers that divide by 3 without a remainder print Fizz instead. For numbers that divide by 5 without a remainder print Buzz and finally for numbers that divide by both 3 and 5 without a remainder print FizzBuzz .

Does your program have an interface? What will it look like? Our FizzBuzz solution will be a browser console program, so we don’t need an interface. The only user interaction will be allowing users to enter a number.

What inputs will your program have? Will the user enter data or will you get input from somewhere else? The user will enter a number from a prompt (popup box).

What’s the desired output? The desired output is a list of numbers from 1 to the number the user entered. But each number that is divisible by 3 will output Fizz , each number that is divisible by 5 will output Buzz and each number that is divisible by both 3 and 5 will output FizzBuzz .

Writing the pseudocode

What are the steps necessary to return the desired output? Here is an algorithm in pseudocode for this problem:

Dividing and conquering

As we can see from the algorithm we developed, the first subproblem we can solve is getting input from the user. So let’s start there and verify it works by printing the entered number.

With JavaScript, we’ll use the “prompt” method.

The above code should create a little popup box that asks the user for a number. The input we get back will be stored in our variable answer .

We wrapped the prompt call in a parseInt function so that a number is returned from the user’s input.

With that done, let’s move on to the next subproblem: “Loop from 1 to the entered number”. There are many ways to do this in JavaScript. One of the common ways - that you actually see in many other languages like Java, C++, and Ruby - is with the for loop :

If you haven’t seen this before and it looks strange, it’s actually straightforward. We declare a variable i and assign it 1: the initial value of the variable i in our loop. The second clause, i <= answer is our condition. We want to loop until i is greater than answer . The third clause, i++ , tells our loop to increment i by 1 every iteration. As a result, if the user inputs 10, this loop would print numbers 1 - 10 to the console.

Most of the time, programmers find themselves looping from 0. Due to the needs of our program, we’re starting from 1

With that working, let’s move on to the next problem: If the current number is divisible by 3, then print Fizz .

We are using the modulus operator ( % ) here to divide the current number by three. If you recall from a previous lesson, the modulus operator returns the remainder of a division. So if a remainder of 0 is returned from the division, it means the current number is divisible by 3.

After this change the program will now output this when you run it and the user inputs 10:

The program is starting to take shape. The final few subproblems should be easy to solve as the basic structure is in place and they are just different variations of the condition we’ve already got in place. Let’s tackle the next one: If the current number is divisible by 5 then print Buzz .

When you run the program now, you should see this output if the user inputs 10:

We have one more subproblem to solve to complete the program: If the current number is divisible by 3 and 5 then print FizzBuzz .

We’ve had to move the conditionals around a little to get it to work. The first condition now checks if i is divisible by 3 and 5 instead of checking if i is just divisible by 3. We’ve had to do this because if we kept it the way it was, it would run the first condition if (i % 3 === 0) , so that if i was divisible by 3, it would print Fizz and then move on to the next number in the iteration, even if i was divisible by 5 as well.

With the condition if (i % 3 === 0 && i % 5 === 0) coming first, we check that i is divisible by both 3 and 5 before moving on to check if it is divisible by 3 or 5 individually in the else if conditions.

The program is now complete! If you run it now you should get this output when the user inputs 20:

Read How to Think Like a Programmer - Lessons in Problem Solving by Richard Reis.
Watch How to Begin Thinking Like a Programmer by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
Read this Pseudocode: What It Is and How to Write It article from Built In.

Knowledge check

This section contains questions for you to check your understanding of this lesson on your own. If you’re having trouble answering a question, click it and review the material it links to.

What are the three stages in the problem solving process?
Why is it important to clearly understand the problem first?
What can you do to help get a clearer understanding of the problem?
What are some of the things you should do in the planning stage of the problem solving process?
What is an algorithm?
What is pseudocode?
What are the advantages of breaking a problem down and solving the smaller problems?

Additional resources

This section contains helpful links to other content. It isn’t required, so consider it supplemental.

Read the first chapter in Think Like a Programmer: An Introduction to Creative Problem Solving ( not free ). This book’s examples are in C++, but you will understand everything since the main idea of the book is to teach programmers to better solve problems. It’s an amazing book and worth every penny. It will make you a better programmer.
Watch this video on repetitive programming techniques .
Watch Jonathan Blow on solving hard problems where he gives sage advice on how to approach problem solving in software projects.

Support us!

The odin project is funded by the community. join us in empowering learners around the globe by supporting the odin project.

IMAGES

8 Steps For Effective Problem Solving
The 5 Steps of Problem Solving
What Is Problem-Solving? Steps, Processes, Exercises to do it Right
39 Best Problem-Solving Examples (2024)
Introduction to Problem Solving Skills
7 Steps to Improve Your Problem Solving Skills

VIDEO

Are You Solving a Problem Worth Solving?
Math 1 U4 L4 (Part I)
Problem solving
No Context Project
What is problem Solving?
Problem is when and where by Riaz Farooqi#youtubeshorts #ytshorts #viral #shortvideo #riazfarooqi

COMMENTS

What Is Problem Solving in Project Management? Here's Everything You
Problem-Solving Steps in Project Management. While the process you choose to solve problems may vary, here is a seven-step framework many project managers use. This problem-solving method combines primary and secondary problem-solving steps. #1. Define the Problem. Gather data and information from key stakeholders, team members, and project ...
Problem Solving Techniques & Strategies for Project Managers
Learn how to define the problem correctly and use a 5-step approach to solve it using problem solving techniques and strategies. Find out how to use a fishbone diagram, brainstorming, mind mapping, trade-off analysis and more to handle the challenges of your projects.
What is Problem Solving? Steps, Process & Techniques
1. Define the problem. Diagnose the situation so that your focus is on the problem, not just its symptoms. Helpful problem-solving techniques include using flowcharts to identify the expected steps of a process and cause-and-effect diagrams to define and analyze root causes. The sections below help explain key problem-solving steps.
An Introduction to Problem Solving in Project Management
Step #1: Define the Problem. If you don't understand the nature of the problem, then you cannot develop a sustainable solution. For example, let's say that a project team continuously misses deadlines. You may believe that the problem is caused by poor performance. On the other hand, the deadlines set may be too restrictive.
What is problem solving in project management?
Problem solving is a process for developing and applying a solution for the occurred problems in the project context. It involves determining the actual status, applying the solution and achieving the wanted actual status of the project. Learn more about the steps, methods and benefits of problem solving in project management.
How to Approach Problem-Solving in Project Management
1 Define the problem. The first step in problem-solving is to clearly define the problem you are facing, and why it is important to solve it. This will help you narrow down the scope, identify the ...
How to master the seven-step problem-solving process
Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don't know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there's a lot of divergent thinking initially.
Problem Solving Definition and Methodology
Broadly defined, problem solving is the process of finding solutions to difficult or complex issues. But you already knew that. Understanding problem solving frameworks, however, requires a deeper dive. Think about a recent problem you faced. Maybe it was an interpersonal issue.
The Problem-Solving Process
The Problem-Solving Process. Problem-solving is an important part of planning and decision-making. The process has much in common with the decision-making process, and in the case of complex decisions, can form part of the process itself. We face and solve problems every day, in a variety of guises and of differing complexity.
The McKinsey guide to problem solving
The McKinsey guide to problem solving. Become a better problem solver with insights and advice from leaders around the world on topics including developing a problem-solving mindset, solving problems in uncertain times, problem solving with AI, and much more.
The Power of Defining the Problem
The Power of Defining the Problem. by. Dwayne Spradlin. September 25, 2012. Well-defined problems lead to breakthrough solutions. When developing new products, processes, or even businesses, most ...
What is Problem Solving? (Steps, Techniques, Examples)
Definition and Importance. Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal and professional ...
The Problem-Definition Process
Justify the need. Understand the problem and its wider context. Write a problem statement. The Problem-Definition Process encourages you to define and understand the problem that you're trying to solve, in detail. It also helps you confirm that solving the problem contributes towards your organization's objectives.
Problem Solving
Problem solving is the process of articulating solutions to problems. Problems have two critical attributes. First, a problem is an unknown in some context. That is, there is a situation in which there is something that is unknown (the difference between a goal state and a current state). Those situations vary from algorithmic math problems to ...
6.1 Problem Solving to Find Entrepreneurial Solutions
Define problem solving in the context of entrepreneurship; ... Often times, a developer of a new project might hold a community charette to aid in the design of a project, hoping to gain approval from elected officials. In the building example, this could consist of the developer and his team of architects, project designers, and people with ...
The Problem-Solving Process
Problem-solving is a mental process that involves discovering, analyzing, and solving problems. The ultimate goal of problem-solving is to overcome obstacles and find a solution that best resolves the issue. The best strategy for solving a problem depends largely on the unique situation. In some cases, people are better off learning everything ...
Problem solving techniques: Steps and methods
Learn how to define, list, evaluate, select and implement a solution for a problem in a project context. The web page explains the steps involved in problem solving and the importance of involving everyone in the process. It also offers a micro-credential to prove your problem solving skills.
How to Define a Problem and Generate Solutions
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.
3.2: Problem-Solving to Find Entrepreneurial Solutions
Define problem-solving in the context of entrepreneurship; ... Often times, a developer of a new project might hold a community charette to aid in the design of a project, hoping to gain approval from elected officials. In the building example, this could consist of the developer and his team of architects, project designers, and people with ...
Stage 2 in the Design Thinking Process: Define the Problem
In the Design Thinking process, this step is what's known as the "define" stage. As the second step in the Design Thinking process, the define stage is where you'll establish a clear idea of exactly which problem you will solve for the user. You'll then shape this into a problem statement which will act as your northern star ...
How to Write a Problem Statement
Step 3: Set your aims and objectives. Finally, the problem statement should frame how you intend to address the problem. Your goal here should not be to find a conclusive solution, but rather to propose more effective approaches to tackling or understanding it. The research aim is the overall purpose of your research.
How to write a problem statement
The format of a problem statement. When you write your problem statement, split it into four sections: Problem: Here, simply define what your problem is, clearly and concisely. Make it no longer than one or two sentences. Background: This is the section where you can describe what causes the problem, how often it occurs, where and when it ...
Problem Solving
In this lesson we will walk through a few techniques that can be used to help with the problem solving process. Lesson overview. This section contains a general overview of topics that you will learn in this lesson. Explain the three steps in the problem solving process. Explain what pseudocode is and be able to use it to solve problems.

What Is Problem Solving in Project Management? Here’s Everything You Need to Know

What Is Problem-Solving?

The Importance of Problem-Solving in Project Management

Problem-Solving Steps in Project Management

#1. Define the Problem

#2. Analyze Root Causes

#3. Brainstorm Potential Solutions

#4. Evaluate Potential Solutions

#5. Decide on a Plan of Action

#6. Implement the Action Plan

#7. Monitor and Track Results

How Project Management Tools Can Help You in Problem-Solving

Examples of Problem-Solving

Sign-ups for a New Software Solution Were Well Below First-Month Targets

A Project Was at Risk of Missing a Hard Deadline Due to Supplier Delays

A Construction Project Is Falling Behind Due to Inclement Weather

Improve Your Problem-Solving and Project Management Skills

You might also like to read:

Leave a Comment Cancel Reply

Recommended Articles

What is Project Resource Management? Everything You Need to Know

Best Apps for Project Management You Should Know in 2024

20 Best Practices in Project Management [2024 Guide]

How to Measure Project Success? A 2024 Guide

Remote Project Management: How to Manage Remote Teams Effectively

What are Project Management Skills? Here are Top Skills You should Know in 2024

Project Management Bootcamp

Online Bootcamp

Problem Solving Techniques for Project Managers

Problem Solving Techniques: A 5-Step Approach

Define the Problem

Related Articles About Problem Solving Techniques

Do You Want More Project Management Tips?

New! Comments

An Introduction to Problem Solving in Project Management

5 Steps to Identify and Eliminate Project-Halting Problems

Step #1: Define the Problem

Step #2: Discover the Causes

Step #3: Develop Ideas for Solutions

Step #4: Solution Selection

Step #5: Put the Solution into Action

Problem solving

More Like This

Would you like to receive regular info on project management topics?

Problem Solving Skills for the Digital Age

So, what is problem solving?

Solve your problem-solving problem

Challenge the status quo

Think broadly about and visualize the issue

Hypothesize, test, and try again

Consider other viewpoints

4 effective problem solving tools

Root cause analysis

Brainstorming

Gap analysis

A better way to problem solve

Related articles

Bring your bright ideas to life.

The Power of Defining the Problem

Partner Center

What is Problem Solving? (Steps, Techniques, Examples)

What Is Problem Solving?

Problem-Solving Steps

Defining the Problem

Generating Solutions

Evaluating and Selecting Solutions

Implementing and Monitoring the Solution

Problem-Solving Techniques

Brainstorming

Root Cause Analysis

SWOT Analysis

Mind Mapping

Examples of Problem Solving in Various Contexts

The Problem-Definition Process

Using the Problem-Definition Process

1. Establish the Need

2. Justify the Need

3. Understand the Problem and Its Wider Context

4. Write a Problem Statement

Discover more content

A Word From Verywell