RankLabPractice Questions →
AFH 1 · Chapter 13 · Section 13.13

Practical Problem-Solving Method

Part of Developing Organizations · 3 sections · ~1308 words · WAPS PFE study material

📝 Practice 3,000+ WAPS questions on RankLab — free for E-5 and E-6 prep.
Try Free →

Practical Problem-Solving Method — Foundation and Steps 1-3 (Clarify, Break Down, Set Targets)

Foundation

PPSM Foundation
At the core of USAF CI is the practical problem-solving method, a standardized and structured approach to problem solving:
  • Used by global industry leaders
  • Adopted by DoD

Eight-Step Process

8-Step Process
The practical problem-solving method is an eight-step process used to:
  • Clarify problems
  • Identify root causes
  • Develop appropriate countermeasures to achieve change

Osborn-Parnes Integration

Osborn-Parnes Integration
The Osborn-Parnes convergent and divergent thinking techniques described in the Developing Ideas chapter can be useful during many steps in this process.

Step 1: Clarify and Validate the Problem

Step 1 Foundation
The first step to effective problem-solving is to clearly understand the problem, often best accomplished by developing a problem statement.

Well-Defined Problem Statement

Problem Statement Standards
A well-defined problem statement uses data to:
  • Identify where the problem is occurring
  • Determine the impact of the problem
  • Compare performance against a standard with scope and direction

What Problem Statement Doesn't Do

What Problem Statement Doesn't Do
A problem statement does NOT assume:
  • A root cause
  • A solution
  • A countermeasure

…but should include visual tools to depict the current state.

Validate the 5 Ws + Significance

Validate 5 Ws + Significance
The who, what, when, where, and significance of the problem statement should be validated by data.

Data Validation

Data Validation
This is done by collecting and analyzing data to validate the existence and magnitude of the problem.

Pause If No Data

Pause If No Data
If data does not exist, the effort should be paused to collect and analyze the needed data before moving forward.

Osborn-Parnes Mapping

Step 1 Osborn-Parnes
This step incorporates the Mess Finding, Data Finding, and Problem Finding aspects of the Osborn-Parnes model.

Step 2: Break Down Problem and Identify Performance Gaps

Step 2 Foundation
Understanding what appropriate data is required and the ability to interpret that data is paramount to performance gap analysis.
Step 2 Function
Step 2 effectively frames and supports the problem in Step 1.

Analyze Against Expected Outcome

Analyze Against Expected
Once the problem statement has been identified and answers the who, what, when, where, and significance of the problem, further analyze the data in comparison to the expected outcome.

Performance Gap Defined

Performance Gap Defined
The expected outcome is the objective from which to measure:
  • The gap between the current state and end state (the expected outcome)
  • Highlight opportunities for improvements (also called the performance gap)

Step 3: Set Improvement Targets

Step 3 Foundation
USAF leaders establish a vision of what an organization will strive to become (the ideal state).

Process Owner Targets

Process Owner Targets
In Step 3, process owners or project managers set improvement targets based on:
  • Expected outcomes
  • Strategic goals and objectives

Targets Define Performance

Targets Define Performance
Targets help define the required performance levels to achieve the desired end state.

Target Standard

Target Standard
Targets should be:
  • Challenging
  • But achievable

Practical Problem-Solving Method — Steps 4-6 (Root Cause, Countermeasures, See Through)

Step 4: Determine Root Cause

Step 4 Foundation
USAF leaders often find themselves addressing problems which have been solved many times when previous problem-solving efforts were directed at:

- Symptoms of a problem

rather than root causes.

Root Cause Tradeoff

Root Cause Tradeoff
Root cause analysis often involves applying a tradeoff between:
  • Digging as deeply as possible
  • Finding the deepest point within the team's sphere of influence

Validate Root Cause with Data

Validate with Data
The correct root cause should be validated by using the same data used to define the problem in Step 1.

Step 5: Develop Countermeasures

Step 5 Foundation
Step 5 is where potential root causes are addressed with countermeasures.

Countermeasure Considerations

Countermeasure Considerations
Consideration should be given to the most:
  • Practical countermeasures
  • Efficient countermeasures
  • Effective countermeasures

Valid Countermeasures

Valid Countermeasures
Valid countermeasures:
  • Will close performance gaps
  • Should move the organization closer to the ideal state

Sustainable + Repeatable

Sustainable + Repeatable
When developing countermeasures, strive for process improvement change that is:
  • Sustainable
  • Repeatable

Vector Check

Vector Check
At the end of Step 5, obtain a vector check to ensure strategic alignment with the desired outcome is still moving in the appropriate direction.

Solution Impact Formula

Solution Impact
Remember, the impact of a solution is a combination of:
  • The quality of the solution
  • The acceptance of the solution by people who implement it

Involve Employees

Involve Employees
Judiciously involving employees in the development of countermeasures generates:
  • Buy-in
  • Ownership of the solution and its success

Osborn-Parnes Mapping

Step 5 Osborn-Parnes
This step incorporates the Idea Finding, Solution Finding, and Acceptance Finding aspects of the Osborn-Parnes model.

Defer Judgment

Defer Judgment
Techniques discussed in the Developing Ideas chapter can be particularly useful when developing countermeasures. Defer judgment and allow a period of time to let ideas flow freely:
  • Brainstorm potential countermeasures, even those that may seem odd or unusual
  • Before evaluating and selecting a solution

Step 6: See Countermeasures Through

Step 6 Foundation
Step 6 is seeing countermeasures through to:
  • Execution
  • Tracking detailed implementation plans for each countermeasure approved in Step 5

Regular Reviews

Regular Reviews
Reviews and progress checks should be updated regularly on all tasks:
  • Until countermeasures have been implemented
  • Or until deemed unnecessary

Practical Problem-Solving Method — Steps 7-8 (Confirm Results, Standardize)

Step 7: Confirm Results and Process

Step 7 Foundation
Step 7 compares the results of implemented countermeasures to:
  • The identified performance gaps
  • Improvement objectives/targets
  • The expected outcome

Sustainability + Repeatability

Sustainability + Repeatability
Sustainability and repeatability of the improved process should be verified.

Measure Results

Measure Results
Results are:
  • Measured by data
  • Analyzed to confirm the project's intent

Monitor Performance

Monitor Performance
Processes should be monitored for performance relative to:
  • The baseline developed in Steps 1 and 2
  • Targets established in Step 3
  • The solution implementation

Illustrate Confirmed Results

Illustrate Confirmed Results
Illustrate confirmed results with appropriate data tools which link back to:
  • Performance gaps
  • Improvement targets

Most Common Mistake

Most Common Mistake
Incorrect root-cause determination is the MOST common mistake made during CI efforts.
Return to Step 4
If targets are not met, it may be necessary to return to Step 4.

Step 8: Standardize Successful Processes

Step 8 Most Neglected
Step 8 is the MOST commonly neglected step of the entire practical problem-solving method; however, it is important to ensure the results of the efforts made in previous steps are codified.

Three Standardization Questions

3 Standardization Questions
In Step 8, consider the answers to following three questions:
  1. What is needed to standardize the improvements?
  2. How should improvements and lessons learned be communicated?
  3. Were other opportunities or problems identified by the problem-solving model?

What Is Needed to Standardize

What Standardize
Possible answers may include:
  • A submission to the Airmen Powered by Innovation Program
  • Change requests for technical orders, instructions, manuals, materiel, and suppliers

How to Communicate

How to Communicate
The wing process manager should be made aware of the success. Methods include:
  • Inputting information into the USAF CI portal
  • Conducting key meetings
  • Writing publications
  • Utilizing public affairs
  • Informing the chain of command
  • Populating data collection sites

Other Opportunities Identified

Other Opportunities
This project may have identified additional problem-solving opportunities that should be:
  • Recognized
  • Addressed

Ready to test what you've learned?

RankLab has 3,000+ WAPS-style practice questions covering every AFH 1 chapter.

Start Free Practice →