—Creating solutions
Life consists primarily of solving problems; they are a normal part of life. Learn to expect them and enjoy solving them. Often “a problem is nothing more than an opportunity in work clothes.”[1] Life would be boring if there were no problems to solve. Treat them as expected rather than as anomalies.[2]
This course describes various approaches, processes, and thinking tools useful for solving problems. Although the title of this course is solving problems, the materials apply equally well to both solving problems and seizing opportunities. A problem describes the gap between the way things are now and the way we would like them to be. Solving a problem often requires taking some action to remove some troublesome deficit or deficiency. Opportunities arise when we notice that conditions have changed. Amazon, Google, Facebook, and eBay all seized opportunities when the emergence of the internet created new ways to provide new conveniences and services to customers. Whenever the word problem appears in the text, it also refers to opportunities.
A list of example problem topics is available to use throughout this course, in case you do not have enough problems of your own! A list of Thinking tools useful for solving problems is also provided.
Completion status: this resource is considered to be complete. |
Attribution: User lbeaumont created this resource and is actively using it. Please coordinate future development with this user if possible. |
The objectives of this course are to help students identify problems, solve problems, and assess the success of the solution.
This course uses many useful thinking tools, and many others exist. Please browse this inventory of problem solving thinking tools and this list of additional thinking tools to continue to improve your ability to solve problems and think creatively.
This is a course in the possibilities curriculum, currently being developed as part of the Applied Wisdom Curriculum.
If you wish to contact the instructor, please click here to send me an email or leave a comment or question on the discussion page.
The work of solving problems often proceeds through a series of stages. The nature of the tasks changes as the work proceeds from what we know today to understanding how it can be in the future. Solving problems requires several disciplined shifts between divergent thinking, which expands the number, character, and scope of ideas that are considered to convergent thinking which narrows the number of alternatives being considered and increases focus. These shifts occur within some stages, between certain stages, and across the entire problem-solving process.
In each stage there is some transformation from the unknown to known, vague to specific, concepts to actions, general to detailed, expansion and divergence to convergence, and past to future. Problems are often solved through some process of stepwise refinement. The path toward solutions requires investigation, analysis, conception, elaboration, clarification, experimentation, evaluation, iteration, refinement, verification, and sometimes breakthroughs.
Although this text is presented serially, the path forward is rarely straightforward. Solving problems requires iteration, recursion, feedback loops, retracing steps, non-linear imagination, and often more.
Several organizations and authors, including ASC[3], Xerox [4],[5], Crestcom [6], AT&T [7], McKinsey & Company [8], The Ideal Problem Solver [9], Phase-gate processes, and others describe general problem solving systems, presented as a series of stages. The number of stages and description of each stage varies across these various systems. This course uses a blend of these recommendations to identify and describe problem solving stages. These stages establish the next nine high-level headings in this course.
Adjust the level of rigor to fit the problem at hand. When deciding what to eat for lunch you are likely to speed through these stages almost instantly. Solving engineering, medical, environmental, behavioral, family, social, economic, or political problems requires more depth, more expertise, and more effort at each stage.
Persevere and a solution will appear.
The goal of this first stage is to write, refine, and agree on a problem statement that clearly defines the real problem to be solved.
Begin by considering the question, what do we want to change? Consider: What do we want to have happen? What is true? and What are we going to do about it? Because problems are often accompanied by many symptoms and may arise from many causes, it is often difficult to identify the real problem. Persevere to ask: What is the problem? What is the real problem, and what is the problem really? Iterate these questions until you are confident you have identified the real problem.
The figure on the right illustrates the many sources of problems and opportunities that are likely to exist at any time. These stimuli may include considerations of: adding value, aesthetics, benchmarking, bigger picture, business as usual, competitor analysis, complaints, context, contributing causes, cost, creative destruction, critics, cultural trends, dangers, delay, discomfort, discontent, disruptions, emerging technologies, errors, errors, expanding scope, externalities, fads, failures, false starts, inconveniences, insights, interactions, irrelevancies, market research, misfits, needs, new viewpoints, opportunities, performance, pollution, possibilities, reality, reliability, scrap, symptoms, rework, voice of the customer, and many more.
During the expansive phase of this stage, work to expand the list of problems that may be considered. This can be done using tools that assist in generating ideas. Use the ideation tools described in the thinking tools course, other thinking tools, or other approaches you find useful.
A creative environment is especially important during this problem-solving phase.
During the convergence phase, work to clarify the problem statement. Use the clarifying tools described in the thinking tools course, other thinking tools, or other approaches you find useful.
This stage is complete when there is a written and agreed to problem statement that clearly defines the real problem to be solved. The desired state to be achieved when this problem is solved should be clearly specified.
It is often helpful to deconstruct a problem into component parts to assist in the analysis.[10] This can often be done by cleaving (subdividing, disaggregating) the problem into complementary factors or subcomponents. For example, if the problem is “lose weight” then eating healthier and exercising more can both contribute to the solution. Each factor can be considered largely independently of the other.
Here are some suggested “cleaving frames”:[11]
As the problem is deconstructed, strive to identify factors that are mutually exclusive and collectively exhaustive (MECE). Creating a cause-effect diagram can help.
The deconstruction can be represented in outline form, or graphically as a tree as shown on the right.
Here is an outline showing a deconstruction of the problem “lose weight”
Problem: Lose Weight
Create a deconstruction of your problem, represented as either an outline or a graphic. Use the cleaving frames listed above, other helpful cleaving frames, and any helpful thinking tools.
If not already in place, it is likely that a team leader will have to be identified and recognized at this stage.
The goal of this stage is to identify and briefly describe several approaches that may provide a useful solution to the identified problem.
A solution approach is some high-level description of an architecture, technology, or plan for solving a problem. For example, if the problem to be solved is “what to eat for lunch”, several solution approaches are available. You can sit down at a restaurant, go to the drive through, order out, have lunch delivered, eat a sandwich at home, or eat a power bar on the go. As another example, the variety of bridge designs represent a wide variety of solution approaches to the problem of crossing a river.
During the expansive phase of this stage, work to expand the list of solution approaches that may be considered. This can be done using tools that assist in generating ideas. Use the ideation tools described in the thinking tools course, other thinking tools, or other approaches you find useful. The SCAMPER tool can provide a good starting point for this enumeration.
This stage is complete when several feasible solution approaches are identified and described in enough detail to communicate each approach to others on the team.
This stage has no convergence phase, the next stage provides convergence by evaluating the candidate solution approaches.
The goal of this stage is to choose the most suitable solution approach from several approaches described above.
Begin by establishing the most important criteria for selecting the most suitable approach. These criteria might include a few chosen from this list: accessibility, aesthetics, availability, bandwidth, benefits, competitive advantage, cost, durability, efficiency, elegance, ergonomics, externalities, feasibility, features, flexibility, leverage, lifespan, novelty, performance, profitability, reliability, risk, robustness, ruggedness, safety, scalability, security, serviceability, signal to noise ratio, size, standards, strategic fit, usability, weight, and others. Consider establishing relative weights (importance), or at least some ordering, of these criteria to identify the critical, more important, and less important criteria.
Use the tools described in the develop section of the thinking tools course to select the most suitable solution approach, based on the established criteria.
Other useful tools include focus groups, Pugh concept selection[13], the Analytic Hierarchy process [14] and other thinking tools.
This stage is complete when one solution approach that can solve the problem has been selected. In some circumstances, when resources are abundant and time is short, it may be useful to select more than one approach to be developed in parallel. This was done during the 2010 Copiapó mining accident rescue where time was critical.
The goals of this stage are to plan the remaining work, and to complete the detailed design of the chosen solution. The outputs will include a project plan along with detailed designs and specifications. Prototype models, computer aided designs, or simulations may be used to better understand, analyze, and communicate the solution.
Difficult problems are likely to require a team of people providing the range of expertise required to solve the problem. As the team grows, ensure competencies, communications, decision making, governance, teamwork skills, and working conditions are suitable to the work being performed.
Two major project approaches are possible at this stage. These are the waterfall model and the spiral model. Many other approaches are also possible that seek to blend and gain the advantages of these two major approaches. Choose the approach that is most suitable to the work being performed.
Larger project will require appointing a project manager or a program manager at this stage, or earlier.
The goal of this stage is to execute the plans created in the previous stage. This results in solutions that are verified to solve the problem.
Specification documents guide the creation of working products or services. Resources are gathered, and tasks are accomplished according to the project plan. Obstacles are identified and overcome. Replanning occurs as needed to resolve emergent or otherwise unforeseen problems.
Use the tools described in the implement section of the thinking tools course during this stage, or any other helpful thinking tools.
Samples of the solution need to be suitably verified to ensure that design output meets design input requirements.
This stage is complete when it is verified that the solution solves the identified problem.
In this stage the solution is introduced to the users. The goal of the stage is to have some planned number of users make use of the solution. Previews, beta tests, soft launches, controlled introductions, early adopter programs, friendly users, clinical trials, and other approaches to introducing the solution to users are used.
For the solution to become effective, it must be used. Tell the story of the problem as it originally existed and how the problem has been solved. Emphasize the benefits and be candid about the shortcomings. This story may become part of a sales campaign, and education campaign, investment requests, policy advocacy work, or some other work to highlight the advantages provided by this solution.
Use the skills taught in this course to solve the problem of using the solution to solve problems.
Use the tools described in the implement section of the thinking tools course, or any other useful thinking tools as you launch the solution.
Often systems are put in place to gather feedback from these first users to be used to improve the product.
This stage is complete when the planned number of users are making use of the solution and the planned feedback is gathered and acted on.
In this stage the effectiveness of the solution, as assessed by users, is evaluated. The rate of adoption, user reactions, focus group findings, unexpected problems and benefits, and other assessments of the solution effectiveness are collected and analyzed.
Is the problem solved? How do you know?
Deployment of the solution continues until each of the users who can benefit from this solution are reached.
On-going work to improve results is known as continuous improvement. The existing solution can be evaluated and improved based on the answers to these questions:
Students who are interested in learning more about solving problems may wish to read these books:
Overviews
Creating Ideas
Product Development
Decision Making
I have not yet read the following books, but they seem interesting and relevant. They are listed here to invite further research.