Creative Intelligence Suite: Innovation and Design Thinking for Developers (Part 4)

npx bmad-method install

You: /cis-innovation

Innovation Strategist: Let's identify opportunities for disruption.

                       What market or industry are you exploring?

You: Developer productivity tools

Strategist: Interesting space! Let me guide you through the analysis:

            🎯 MARKET ANALYSIS
            Current pain points in developer tools:
            - Tool fragmentation
            - Context switching costs
            - Configuration complexity

            📊 DISRUPTION OPPORTUNITIES
            1. AI-native development environments
            2. Zero-config tooling
            3. Intent-based programming

            Which angle interests you most?

You: /cis-design-thinking

Design Coach: Welcome to the design thinking journey!

              We'll work through 5 phases:
              1. 🎯 Empathize - Understand your users
              2. 🔍 Define - Frame the problem
              3. 💡 Ideate - Generate solutions
              4. 🔧 Prototype - Build to learn
              5. ✅ Test - Validate assumptions

              Let's start with empathy.
              Who are your target users?

You: Senior developers who mentor junior team members

Coach: Great! Let's understand their world:

       🎤 INTERVIEW QUESTIONS
       - What's most frustrating about mentoring?
       - How do you currently share knowledge?
       - What takes up most of your mentoring time?

       🔍 OBSERVATION PROMPTS
       - Watch a mentoring session
       - Review their code review comments
       - Analyze their documentation patterns

       What insights have you gathered?

You: /cis-brainstorm

Brainstorming Coach: Ready to generate ideas!

                     What would you like to brainstorm about?

You: Ways to improve user onboarding

Coach: Let's use the SCAMPER technique!

       📝 SCAMPER ANALYSIS

       🔄 SUBSTITUTE
       - What if signup required no password?
       - Replace forms with conversation?

       🔗 COMBINE  
       - Merge onboarding with first use?
       - Combine tutorial with real tasks?

       🔧 ADAPT
       - How does gaming handle new players?
       - What can we learn from social apps?

       ✨ MODIFY
       - Make it 10x shorter?
       - Make it 10x more personal?

       🎯 PUT TO OTHER USE
       - Use onboarding for ongoing education?
       - Use it for feature discovery?

       ❌ ELIMINATE
       - Remove ALL steps - what happens?
       - No onboarding - users figure it out?

       🔃 REVERSE
       - End with signup, start with value?
       - User teaches the system?

       Which angle resonates? Let's dive deeper.

You: /cis-problem-solve

Problem Solver: Let's diagnose this systematically.

                What problem are you facing?

You: Our API response times are inconsistent

Solver: I'll guide you through root cause analysis.

        📊 SYMPTOM MAPPING
        - When did this start?
        - What changed recently?
        - Is it all endpoints or specific ones?

        🔍 5 WHYS ANALYSIS
        Why are response times inconsistent?
        → [Your answer leads to next why]

        🐟 FISHBONE DIAGRAM
        Potential causes by category:

        PEOPLE: Team changes? Knowledge gaps?
        PROCESS: Deployment changes? Monitoring gaps?
        TECHNOLOGY: Dependencies? Infrastructure?
        ENVIRONMENT: Traffic patterns? External services?

        Let's explore each branch...

You: /cis-creative-solve

Creative Solver: Let's think sideways!

                 What conventional problem are you trying to solve?

You: Users forget to complete their profiles

Solver: 🔀 LATERAL THINKING TECHNIQUES

        REVERSAL: What if incomplete profiles were the goal?
        → Maybe minimal profiles are faster to scan?
        → Progressive disclosure as relationships form?

        ANALOGY: How does nature handle incomplete information?
        → Trees grow toward light - profiles grow toward value
        → Caterpillar → butterfly - staged transformation

        RANDOM ENTRY: [Picking random concept: "music"]
        → Playlists build over time through use
        → Profile as a "greatest hits" that evolves

        PROVOCATION: "Profiles should be invisible"
        → What if actions spoke louder than descriptions?
        → Infer profile from behavior?

        Which direction excites you?

You: /cis-storytelling

Storyteller: Every great product has a story.

             What product or feature needs a narrative?

You: Our new AI code review feature

Storyteller: Let's build your product story.

             📖 STORY STRUCTURE

             THE HERO (Your User):
             A developer drowning in pull requests...

             THE STRUGGLE:
             Hours spent on tedious reviews, missing
             critical issues while catching style nits...

             THE DISCOVERY:
             An AI assistant that understands context,
             catches bugs, and learns team preferences...

             THE TRANSFORMATION:
             From code reviewer to code mentor,
             focusing on architecture and growth...

             THE NEW WORLD:
             Faster releases, fewer bugs, happier teams...

             Want me to develop any section further?

You: /cis-presentation

Presentation Master: Let's build a compelling deck.

                     What's your presentation about?

You: Pitching our startup to investors

Master: 🎯 INVESTOR PITCH STRUCTURE

        1. HOOK (30 sec)
           One sentence that makes them lean in

        2. PROBLEM (1 min)
           Pain so real they feel it

        3. SOLUTION (2 min)
           Your unique insight

        4. TRACTION (1 min)
           Proof it's working

        5. MARKET (1 min)
           Why this can be huge

        6. TEAM (30 sec)
           Why you'll win

        7. ASK (30 sec)
           Specific and confident

        Let's craft your hook first.
        What's the one sentence?

You: /cis-brainstorm
     We need a new feature for our project management tool.
     Users are asking for "something to help with planning."

Coach: Let's explore what "help with planning" means to users.

       DIVERGENT PHASE 🌊
       Generate as many ideas as possible:

       1. AI that predicts project timelines
       2. Visual roadmap builder
       3. Automatic dependency detection
       4. Team capacity planning
       5. Risk forecasting
       6. Meeting scheduler optimizer
       7. Sprint recommendation engine
       8. "What-if" scenario modeling
       9. Stakeholder communication templates
       10. Progress prediction vs actual

       [Generates 20+ ideas...]

       CONVERGENT PHASE 🎯
       Let's evaluate against criteria:

       | Idea | User Value | Feasibility | Differentiation |
       |------|------------|-------------|----------------|
       | AI timeline prediction | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐ |
       | What-if modeling | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
       | Capacity planning | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ |

       Top candidates: What-if modeling + AI predictions

       Want to validate these with design thinking?

You: Yes, let's do design thinking on what-if modeling

Coach: Switching to Design Thinking mode...

Design Coach: 🎯 PHASE 1: EMPATHIZE

              Who would use what-if modeling?

              PERSONA HYPOTHESES:

              "Project Paula" - PM at a startup
              - Manages 3-5 concurrent projects
              - Constantly asked "when will this ship?"
              - Burned by scope creep before

              "Executive Eric" - VP of Engineering  
              - Needs to commit to quarterly goals
              - Balances multiple team requests
              - Lives in spreadsheets currently

              Which persona should we focus on?

You: Project Paula - she's our core user

Coach: 🔍 PHASE 2: DEFINE

       Based on empathy work, here's the problem statement:

       "Project Paula needs a way to CONFIDENTLY answer
       timeline questions because her current tools only
       show ONE path forward, hiding the uncertainty
       she knows exists."

       Key insight: She KNOWS there's uncertainty,
       but has no way to COMMUNICATE it.

       💡 PHASE 3: IDEATE

       How might we help Paula communicate uncertainty?

       IDEAS:
       1. Probability ranges instead of dates
       2. "Optimistic / Realistic / Pessimistic" views
       3. Risk-adjusted timelines
       4. Shareable scenarios for stakeholders
       5. Historical accuracy tracking

       🔧 PHASE 4: PROTOTYPE

       Let's sketch the simplest test:

       Low-fidelity prototype:
       - Add "best case / worst case" to any date
       - Show range visually on timeline
       - One-click share with stakeholders

       Want to define the test criteria?

You: /cis-problem-solve
     Our trial-to-paid conversion dropped 20% last month.

Problem Solver: Let's diagnose systematically.

                📊 SYMPTOM ANALYSIS

                First, some clarifying questions:
                1. Did trial signups change?
                2. Which plans saw the biggest drop?
                3. Any changes to pricing or features?
                4. What does the funnel look like?

You: Signups are stable. Drop is across all plans.
     We added a new onboarding flow 6 weeks ago.

Solver: 🔍 HYPOTHESIS FORMATION

        Timing correlates with onboarding change.

        Possible causes:
        H1: New onboarding is confusing users
        H2: New onboarding attracts wrong users
        H3: New onboarding front-loads value (no need to pay)
        H4: Technical issues in new flow

        Let's test H1 first:

        DATA TO CHECK:
        - Onboarding completion rates: old vs new
        - Time to first value: old vs new
        - Support tickets mentioning onboarding
        - User feedback/NPS scores

        What do you have access to?

You: Completion is UP 40%, but time-to-first-value
     increased from 5 min to 25 min.

Solver: 🎯 ROOT CAUSE IDENTIFIED

        The new onboarding is more thorough but
        DELAYS the "aha moment".

        Users who converted before:
        - Hit value quickly (5 min)
        - Explored on their own
        - Asked for features = signal to upgrade

        Users now:
        - Complete comprehensive tutorial (25 min)
        - Feel "trained" on free features
        - Don't discover premium value naturally

        💡 SOLUTION DIRECTIONS:
        1. Shorter path to first value, detailed training later
        2. Include premium feature preview in onboarding
        3. Guide toward premium use cases during trial

        Want to brainstorm implementations?

┌──────────────────────────────────────────────────────────────┐
│                    FULL INNOVATION FLOW                       │
│                                                               │
│  CIS Phase                    BMAD Phase                     │
│  ─────────                    ──────────                     │
│  /cis-brainstorm      →      Product ideas generated        │
│  /cis-design-thinking →      User needs validated           │
│  /cis-innovation      →      Market opportunity confirmed   │
│                               ↓                              │
│                        /create-product-brief                 │
│                        /create-prd                           │
│                        /create-architecture                  │
│                        /dev-story                            │
│                               ↓                              │
│  /cis-storytelling    →      Launch narrative ready         │
│  /cis-presentation    →      Stakeholder buy-in secured     │
└──────────────────────────────────────────────────────────────┘

# Phase 1: Discover (CIS)
/cis-brainstorm
# Generate and evaluate feature ideas

/cis-design-thinking
# Validate with user empathy

# Phase 2: Define (BMAD)
/create-product-brief
# Capture the validated idea

/create-prd
# Full requirements with PM agent

# Phase 3: Design (BMAD)
/create-architecture
# Technical solution

# Phase 4: Build (BMAD)
/sprint-planning
/dev-story
/code-review

# Phase 5: Launch (CIS)
/cis-storytelling
# Craft the launch narrative

/cis-presentation
# Prepare stakeholder communications

You: /party-mode Innovation, Design, Storyteller

Innovation: 🚀 Looking at this from a market disruption angle...

Design: 🎨 Let me consider the user experience implications...

Storyteller: 📖 Here's how we might frame this for users...

You: /party-mode Problem-Solver, Creative-Solver

Problem-Solver: 🔍 Systematically, the issue stems from...

Creative-Solver: 💡 But what if we flip that assumption...

CIS: /cis-brainstorm → Generate feature ideas
CIS: /cis-innovation → Identify market opportunities  
BMAD: /create-product-brief → Capture validated direction

CIS: /cis-design-thinking → Validate user needs
CIS: /cis-problem-solve → Clarify problem space
BMAD: /create-prd → Document requirements

CIS: /cis-creative-solve → Explore novel architectures
BMAD: /create-architecture → Document technical decisions

CIS: /cis-storytelling → Craft product narrative
CIS: /cis-presentation → Prepare launch materials

❌ "That won't work because..." (during brainstorm)
✅ "Let's generate 20 ideas, then evaluate" (process)

❌ Skipping empathy to jump to solutions
✅ Completing all design thinking phases

/cis-brainstorm
→ Save promising ideas to _bmad-output/brainstorm-results.md

/cis-design-thinking
→ Save personas to _bmad-output/user-personas.md

Vague problem → /cis-problem-solve first
Clear problem → /cis-brainstorm directly
User-facing → /cis-design-thinking required
Technical → /cis-creative-solve useful

/bmad-help I'm stuck on a problem and don't know where to start

BMAD: Based on your situation, I recommend:
      - /cis-problem-solve for diagnosis
      - /cis-brainstorm once problem is clear

npx bmad-method install