Problem-Solving Strategies Cheat Sheet

Root Cause Analysis Techniques

The Five Whys

• Ask “why” at least five times to dig deeper
• Each answer forms the basis of the next question
• Moves from symptoms to underlying causes
• Example:
• Why did the project fail? The material broke.
• Why did the material break? It was too brittle.
• Why was it too brittle? We chose the wrong type.
• Why did we choose the wrong type? We didn’t test it first.
• Why didn’t we test it? We didn’t know how it would behave under stress.
• Solution addresses the root cause, not just symptoms

Fishbone Diagram (Ishikawa)

• Visual tool for categorizing potential causes
• Main categories: Materials, Methods, Machinery, Measurement, People, Environment
• Branch out from each category to specific causes
• Helps identify multiple contributing factors
• Especially useful for complex problems with many variables

Component Breakdown

• Separate system into individual components
• Test each component independently
• Identify which specific elements are problematic
• Rebuild system with fixed components
• Prevents “everything is broken” overwhelm

Creative Problem-Solving Approaches

SCAMPER Method

• Substitute: Replace elements with alternatives
• Combine: Merge elements or ideas
• Adapt: Modify for new conditions
• Modify/Magnify/Minimize: Change scale or properties
• Put to other uses: Find new applications
• Eliminate: Remove elements to simplify
• Reverse/Rearrange: Change order or orientation

Lateral Thinking

• Approach problems from unexpected angles
• Challenge assumptions about the problem
• Use random stimuli to spark new connections
• Consider absurd or impossible solutions first
• Look for solutions in unrelated fields

Constraint Shifting

• Identify current constraints limiting solutions
• Temporarily remove or modify one constraint
• Explore solutions under these new conditions
• Return to original constraints with fresh insights
• Often reveals self-imposed limitations

Systematic Testing Methods

A/B Testing

• Create two versions with only one difference
• Test both versions under identical conditions
• Measure results objectively
• Select better-performing version
• Repeat process with new variations

Controlled Variables

• Change only one variable at a time
• Keep all other factors constant
• Document exact conditions and results
• Build knowledge systematically
• Prevents confusing which change caused which result

Minimum Viable Tests

• Create simplified versions of potential solutions
• Test core functionality without full implementation
• Gather feedback on essential elements
• Iterate based on test results
• Saves resources while gaining key insights

Adaptation Strategies

Redirection Framework

1. Acknowledge current reality without judgment
2. Identify viable aspects of original vision
3. Consider how unexpected developments offer new opportunities
4. Establish revised direction incorporating these insights
5. Adjust expectations and timeline accordingly

Essence Preservation

• Identify the essential purpose of your project
• Distinguish between purpose and specific form
• Brainstorm alternative forms serving same purpose
• Select most promising alternative given circumstances
• Maintains meaning while changing approach

Scale Adjustment

• Assess whether original scope remains feasible
• Consider scaling down to more manageable version
• Identify minimum viable version that remains meaningful
• Adjust timeline and resources accordingly
• Plan for potential expansion if circumstances improve

Learning from Failure

Failure Analysis Protocol

1. Document exactly what happened without judgment
2. Identify specific contributing factors
3. Distinguish between controllable and uncontrollable factors
4. Determine what you would do differently with current knowledge
5. Implement insights in next attempt

Success-Failure Reframe

• Identify aspects of “failures” that were actually successful
• Recognize elements of “successes” that could be improved
• Acknowledge learning value of unsuccessful attempts
• Consider how current “failures” enable future successes
• Focus on progress rather than perfection

Iteration Mindset

• Expect multiple attempts for complex projects
• Plan for iteration rather than immediate perfection
• Set learning goals alongside outcome goals
• Document improvements between iterations
• Celebrate progress even when final goals aren’t yet achieved

Collaborative Problem-Solving

Diverse Perspective Gathering

• Seek input from people with different backgrounds
• Present problem without suggesting solutions
• Ask specific questions rather than general feedback
• Look for patterns across multiple perspectives
• Combine insights from different viewpoints

Structured Brainstorming

• Set clear problem statement before beginning
• Establish “no criticism” rule during idea generation
• Generate quantity before evaluating quality
• Build on others’ ideas with “yes, and” approach
• Organize and evaluate ideas after generation phase

Expert Consultation

• Identify specific knowledge gaps
• Find experts in relevant domains
• Prepare specific questions in advance
• Apply expert advice with appropriate adaptation
• Document insights for future reference

Emotional Aspects of Problem-Solving

Frustration Management

• Recognize frustration as normal part of process
• Take short breaks when emotions run high
• Use physical activity to reset mental state
• Return with specific, smaller next steps
• Focus on progress rather than perfection

Confidence Building

• Start with small, solvable aspects of the problem
• Document previous successful problem-solving
• Recognize that all makers face similar challenges
• Use structured approaches rather than relying on inspiration
• Celebrate small wins along the way

Persistence Strategies

• Break problems into smaller, manageable parts
• Set time limits for focused problem-solving sessions
• Alternate between different types of problems
• Create external accountability for progress
• Connect problem-solving to meaningful purpose