Creative Problem Solving Workflow

last-redoc-date: 2025-09-28

Problem Solving Workflow

Type: Interactive Document Workflow Module: Creative Intelligence System (CIS)

Purpose

Applies systematic problem-solving methodologies to crack complex challenges. Guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven analytical frameworks.

Distinctive Features

• Root Cause Focus: Relentlessly drills past symptoms to identify true underlying issues
• Method Library: Comprehensive solving methods in solving-methods.csv (TRIZ, Theory of Constraints, Systems Thinking, Five Whys)
• Detective Approach: Methodical and curious investigation treating challenges as elegant puzzles
• Framework-Driven: Combines divergent and convergent thinking systematically

Usage

# Basic invocation
workflow problem-solving

# With problem context
workflow problem-solving --data /path/to/problem-brief.md

Inputs

• problem_description: Challenge being addressed with symptoms and context
• previous_attempts: Prior solution attempts and their outcomes
• constraints: Boundaries and limitations for solutions
• success_criteria: How solution effectiveness will be measured

Outputs

File: {output_folder}/problem-solution-{date}.md

Structure:

• Problem diagnosis and symptom analysis
• Root cause identification using analytical frameworks
• Solution ideation across multiple methodologies
• Solution evaluation matrix with pros/cons
• Implementation plan with risk mitigation
• Success metrics and validation approach

Workflow Components

• workflow.yaml - Configuration with solving_methods CSV reference
• instructions.md - Systematic problem-solving facilitation guide
• template.md - Structured analysis output format
• solving-methods.csv - Problem-solving methodology library

Workflow Instructions

Problem Solving Workflow Instructions

The workflow execution engine is governed by: {project_root}/.faos/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/.faos/cis/workflows/problem-solving/workflow.yaml Load and understand solving methods from: {solving_methods} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. ⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.

Load any context data provided via the data attribute.

Gather problem information by asking:

• What problem are you trying to solve?
• How did you first notice this problem?
• Who is experiencing this problem?
• When and where does it occur?
• What's the impact or cost of this problem?
• What would success look like?

Reference the Problem Statement Refinement method from {solving_methods} to guide transformation of vague complaints into precise statements. Focus on:

• What EXACTLY is wrong?
• What's the gap between current and desired state?
• What makes this a problem worth solving?

problem_title problem_category initial_problem refined_problem_statement problem_context success_criteria

Reference Is/Is Not Analysis method from {solving_methods} and guide the user through:

• Where DOES the problem occur? Where DOESN'T it?
• When DOES it happen? When DOESN'T it?
• Who IS affected? Who ISN'T?
• What IS the problem? What ISN'T it?

Help identify patterns that emerge from these boundaries.

problem_boundaries

Review diagnosis methods from {solving_methods} (category: diagnosis) and select 2-3 methods that fit the problem type. Offer these to the user with brief descriptions of when each works best.

Common options include:

• Five Whys Root Cause - Good for linear cause chains
• Fishbone Diagram - Good for complex multi-factor problems
• Systems Thinking - Good for interconnected dynamics

Walk through chosen method(s) to identify:

• What are the immediate symptoms?
• What causes those symptoms?
• What causes those causes? (Keep drilling)
• What's the root cause we must address?
• What system dynamics are at play?

root_cause_analysis contributing_factors system_dynamics

Apply Force Field Analysis:

• What forces drive toward solving this? (motivation, resources, support)
• What forces resist solving this? (inertia, cost, complexity, politics)
• Which forces are strongest?
• Which can we influence?

Apply Constraint Identification:

• What's the primary constraint or bottleneck?
• What limits our solution space?
• What constraints are real vs assumed?

Synthesize key insights from analysis.

driving_forces restraining_forces constraints key_insights

Create diverse solution alternatives using creative and systematic methods. Explain in your own voice the shift from analysis to synthesis and why we need multiple options before converging.

Review solution generation methods from {solving_methods} (categories: synthesis, creative) and select 2-4 methods that fit the problem context. Consider:

• Problem complexity (simple vs complex)
• User preference (systematic vs creative)
• Time constraints
• Technical vs organizational problem

Offer selected methods to user with guidance on when each works best. Common options:

• Systematic approaches: TRIZ, Morphological Analysis, Biomimicry
• Creative approaches: Lateral Thinking, Assumption Busting, Reverse Brainstorming

Walk through 2-3 chosen methods to generate:

• 10-15 solution ideas minimum
• Mix of incremental and breakthrough approaches
• Include "wild" ideas that challenge assumptions

solution_methods generated_solutions creative_alternatives

Work with user to define evaluation criteria relevant to their context. Common criteria:

• Effectiveness - Will it solve the root cause?
• Feasibility - Can we actually do this?
• Cost - What's the investment required?
• Time - How long to implement?
• Risk - What could go wrong?
• Other criteria specific to their situation

Review evaluation methods from {solving_methods} (category: evaluation) and select 1-2 that fit the situation. Options include:

• Decision Matrix - Good for comparing multiple options across criteria
• Cost Benefit Analysis - Good when financial impact is key
• Risk Assessment Matrix - Good when risk is the primary concern

Apply chosen method(s) and recommend solution with clear rationale:

• Which solution is optimal and why?
• What makes you confident?
• What concerns remain?
• What assumptions are you making?

evaluation_criteria solution_analysis recommended_solution solution_rationale

Define implementation approach:

• What's the overall strategy? (pilot, phased rollout, big bang)
• What's the timeline?
• Who needs to be involved?

Create action plan:

• What are specific action steps?
• What sequence makes sense?
• What dependencies exist?
• Who's responsible for each?
• What resources are needed?

Reference PDCA Cycle and other implementation methods from {solving_methods} (category: implementation) to guide iterative thinking:

• How will we Plan, Do, Check, Act iteratively?
• What milestones mark progress?
• When do we check and adjust?

implementation_approach action_steps timeline resources_needed responsible_parties

Define how you'll know the solution is working and what to do if it's not.

Create monitoring dashboard:

• What metrics indicate success?
• What targets or thresholds?
• How will you measure?
• How frequently will you review?

Plan validation:

• How will you validate solution effectiveness?
• What evidence will prove it works?
• What pilot testing is needed?

Identify risks and mitigation:

• What could go wrong during implementation?
• How will you prevent or detect issues early?
• What's plan B if this doesn't work?
• What triggers adjustment or pivot?

success_metrics validation_plan risk_mitigation adjustment_triggers

Facilitate reflection:

• What worked well in this process?
• What would you do differently?
• What insights surprised you?
• What patterns or principles emerged?
• What will you remember for next time?

key_learnings what_worked what_to_avoid

Output Template

Problem Solving Session: {{problem_title}}

Date: {{date}} Problem Solver: {{user_name}} Problem Category: {{problem_category}}

🎯 PROBLEM DEFINITION

Initial Problem Statement

{{initial_problem}}

Refined Problem Statement

{{refined_problem_statement}}

Problem Context

{{problem_context}}

Success Criteria

{{success_criteria}}

🔍 DIAGNOSIS AND ROOT CAUSE ANALYSIS

Problem Boundaries (Is/Is Not)

{{problem_boundaries}}

Root Cause Analysis

{{root_cause_analysis}}

Contributing Factors

{{contributing_factors}}

System Dynamics

{{system_dynamics}}

📊 ANALYSIS

Force Field Analysis

Driving Forces (Supporting Solution): {{driving_forces}}

Restraining Forces (Blocking Solution): {{restraining_forces}}

Constraint Identification

{{constraints}}

Key Insights

{{key_insights}}

💡 SOLUTION GENERATION

Methods Used

{{solution_methods}}

Generated Solutions

{{generated_solutions}}

Creative Alternatives

{{creative_alternatives}}

⚖️ SOLUTION EVALUATION

Evaluation Criteria

{{evaluation_criteria}}

Solution Analysis

{{solution_analysis}}

Recommended Solution

{{recommended_solution}}

Rationale

{{solution_rationale}}

🚀 IMPLEMENTATION PLAN

Implementation Approach

{{implementation_approach}}

Action Steps

{{action_steps}}

Timeline and Milestones

{{timeline}}

Resource Requirements

{{resources_needed}}

Responsible Parties

{{responsible_parties}}

📈 MONITORING AND VALIDATION

Success Metrics

{{success_metrics}}

Validation Plan

{{validation_plan}}

Risk Mitigation

{{risk_mitigation}}

Adjustment Triggers

{{adjustment_triggers}}

📝 LESSONS LEARNED

Key Learnings

{{key_learnings}}

What Worked

{{what_worked}}

What to Avoid

{{what_to_avoid}}

Generated using BMAD Creative Intelligence Suite - Problem Solving Workflow