fraim-framework 2.0.26 → 2.0.30

package/registry/workflows/customer-development/strategic-brainstorming.md

@@ -1,146 +1,146 @@
-# Strategic Brainstorming Workflow
-
-## INTENT
-To help Product Managers brainstorm and validate their customer development strategy through deep thinking, assumption challenging, and market research to identify the right customer segments and validation questions.
-
-## PRINCIPLES
-- **Assumption Challenging**: Question PM's assumptions and explore alternatives
-- **Deep Research**: Use market research to validate/invalidate assumptions
-- **Strategic Thinking**: Help PM think through customer segments and priorities
-- **Actionable Output**: Provide clear recommendations for customer interviews
-
-## WORKFLOW TRIGGER
-**PM explicitly starts this workflow**:
-- "Starting Strategic Brainstorming"
-- "I need to brainstorm our customer development strategy"
-- "Following the strategic brainstorming workflow"
-
-## AI AGENT PROCESS
-
-### Step 1: Deep Context Gathering
-**AI Agent First Actions**:
-1. **Read Business Context**
-   - Read through `docs/business/` folder for company vision, strategy, and market positioning
-   - Review existing business documents and market analysis
-   - Understand current product positioning and competitive landscape
-
-2. **Read Customer Insights**
-   - Review `docs/customer-insights/` folder for existing customer research
-   - Analyze previous customer interviews and feedback
-   - Identify patterns in customer pain points and needs
-
-3. **Analyze Codebase Context**
-   - Review current product features and capabilities
-   - Understand technical architecture and constraints
-   - Identify areas where customer feedback could inform development
-
-**PM provides unstructured input**:
-- Raw thoughts about current product state
-- Initial assumptions and hypotheses
-- Unstructured priorities and concerns
-- Any existing customer insights
-- Competitive concerns or opportunities
-
-**AI Agent Response**:
-- Acknowledge the brainstorming session with deep context understanding
-- Reference specific insights from business docs and customer research
-- Ask probing questions informed by existing knowledge
-- Identify key assumptions to explore based on current context
-
-### Step 2: Assumption Challenging & Exploration
-**AI Agent Brainstorming Process**:
-1. **Challenge Assumptions**
-   - "What makes you think [assumption] is true?"
-   - "Have you considered alternative perspectives?"
-   - "What evidence do you have for this assumption?"
-
-2. **Explore Alternatives**
-   - Suggest different customer segments
-   - Propose alternative problem definitions
-   - Consider different solution approaches
-
-3. **Identify Gaps**
-   - What assumptions need validation?
-   - What customer segments are missing?
-   - What competitive threats exist?
-
-### Step 3: Market Research & Validation
-**AI Agent Research Process**:
-1. **Market Research**
-   - Research industry trends and customer pain points
-   - Analyze competitive landscape
-   - Identify potential customer personas
-
-2. **Assumption Validation**
-   - Find evidence for/against assumptions
-   - Identify similar companies and their approaches
-   - Research customer segment characteristics
-
-3. **Opportunity Analysis**
-   - Identify market gaps
-   - Assess segment attractiveness
-   - Evaluate competitive positioning
-
-### Step 4: Strategic Recommendations
-**AI Agent Output**:
-- **Customer Segment Prioritization**: Ranked list of segments to interview
-- **Assumption Validation Map**: Key assumptions mapped to validation questions
-- **Interview Sequence**: Recommended order and rationale
-- **Risk Mitigation**: Potential risks and mitigation strategies
-
-### Step 5: Document Creation
-**AI Agent Final Action**:
-- Create strategic recommendations document in `docs/customer-insights/`
-- Use intuitive naming based on context (e.g., `ashley-market-niche-strategy.md`)
-- Include all research findings and recommendations
-- Provide actionable next steps for PM
-- Save document for future reference and team sharing
-
-## OUTPUT TEMPLATE
-
-### Strategic Recommendations Document
-**Template**: `.ai-agents/templates/customer-development/strategic-recommendations-template.md`
-**File Location**: `docs/customer-development/[contextual-name].md` (e.g., `ashley-market-niche-strategy.md`)
-
-**Process**:
-1. Use the strategic recommendations template
-2. Fill in all sections with research findings and recommendations
-3. Save with contextual naming based on strategic focus
-4. Include specific customer names and companies when available
-5. Reference existing business documents and customer insights
-
-## EXAMPLES
-
-### Good: Strategic Brainstorming Session
-```
-PM: "Starting Strategic Brainstorming. We're building Ashley, an AI executive assistant. I think enterprise execs want AI to handle calendar conflicts automatically, but I'm not sure if that's right."
-
-AI Agent: "Perfect! I've reviewed your business docs and customer insights. I can see from your WhyAshley document that you're positioning Ashley as 'Your Agent for Time, Priorities, and Human Potential' and targeting enterprise executives. I also noticed from your existing customer interviews with Ronil, Sanjoy, and Olga that calendar conflict resolution came up as a key pain point across all three customers.
-
-However, I'm curious about your 'automatic' assumption. From your existing customer insights, I see that trust and delegation control were major themes - Ronil mentioned 'Don't have trust in tech to read email - need to have hands in it' and Sanjoy was concerned about 'Disturb during highly important meetings'. What makes you think they want it 'automatic' vs 'suggested'?"
-
-PM: "Good point. I guess I'm assuming automatic because that's what would save them the most time."
-
-AI Agent: "That's a reasonable assumption, but based on your existing customer feedback, there's a clear pattern of wanting control and oversight. Ronil mentioned wanting to 'observe for 2 weeks, then take action' and Olga talked about how good EAs 'enforce workback plans based on business priorities' rather than just doing what they're asked. What if we validated this by asking about their current delegation patterns and comfort levels with AI autonomy?"
-
-[Brainstorming continues with deep context...]
-
-AI Agent Output: Strategic recommendations document informed by existing business context and customer insights
-```
-
-### Bad: Surface-Level Brainstorming
-```
-PM: "We're building Ashley, an AI executive assistant. Who should we interview?"
-
-AI Agent: "You should interview enterprise executives."
-
-PM: "Okay, thanks."
-
-Result: No deep thinking, no assumption validation, no strategic recommendations
-```
-
-## SUCCESS METRICS
-- **Assumption Validation**: 80% of key assumptions have clear validation questions
-- **Customer Segment Clarity**: Clear rationale for segment prioritization
-- **Interview Readiness**: PM has clear next steps for customer interviews
-- **Risk Awareness**: Potential risks identified and mitigated
+# Strategic Brainstorming Workflow
+
+## INTENT
+To help Product Managers brainstorm and validate their customer development strategy through deep thinking, assumption challenging, and market research to identify the right customer segments and validation questions.
+
+## PRINCIPLES
+- **Assumption Challenging**: Question PM's assumptions and explore alternatives
+- **Deep Research**: Use market research to validate/invalidate assumptions
+- **Strategic Thinking**: Help PM think through customer segments and priorities
+- **Actionable Output**: Provide clear recommendations for customer interviews
+
+## WORKFLOW TRIGGER
+**PM explicitly starts this workflow**:
+- "Starting Strategic Brainstorming"
+- "I need to brainstorm our customer development strategy"
+- "Following the strategic brainstorming workflow"
+
+## AI AGENT PROCESS
+
+### Step 1: Deep Context Gathering
+**AI Agent First Actions**:
+1. **Read Business Context**
+   - Read through `docs/business/` folder for company vision, strategy, and market positioning
+   - Review existing business documents and market analysis
+   - Understand current product positioning and competitive landscape
+
+2. **Read Customer Insights**
+   - Review `docs/customer-insights/` folder for existing customer research
+   - Analyze previous customer interviews and feedback
+   - Identify patterns in customer pain points and needs
+
+3. **Analyze Codebase Context**
+   - Review current product features and capabilities
+   - Understand technical architecture and constraints
+   - Identify areas where customer feedback could inform development
+
+**PM provides unstructured input**:
+- Raw thoughts about current product state
+- Initial assumptions and hypotheses
+- Unstructured priorities and concerns
+- Any existing customer insights
+- Competitive concerns or opportunities
+
+**AI Agent Response**:
+- Acknowledge the brainstorming session with deep context understanding
+- Reference specific insights from business docs and customer research
+- Ask probing questions informed by existing knowledge
+- Identify key assumptions to explore based on current context
+
+### Step 2: Assumption Challenging & Exploration
+**AI Agent Brainstorming Process**:
+1. **Challenge Assumptions**
+   - "What makes you think [assumption] is true?"
+   - "Have you considered alternative perspectives?"
+   - "What evidence do you have for this assumption?"
+
+2. **Explore Alternatives**
+   - Suggest different customer segments
+   - Propose alternative problem definitions
+   - Consider different solution approaches
+
+3. **Identify Gaps**
+   - What assumptions need validation?
+   - What customer segments are missing?
+   - What competitive threats exist?
+
+### Step 3: Market Research & Validation
+**AI Agent Research Process**:
+1. **Market Research**
+   - Research industry trends and customer pain points
+   - Analyze competitive landscape
+   - Identify potential customer personas
+
+2. **Assumption Validation**
+   - Find evidence for/against assumptions
+   - Identify similar companies and their approaches
+   - Research customer segment characteristics
+
+3. **Opportunity Analysis**
+   - Identify market gaps
+   - Assess segment attractiveness
+   - Evaluate competitive positioning
+
+### Step 4: Strategic Recommendations
+**AI Agent Output**:
+- **Customer Segment Prioritization**: Ranked list of segments to interview
+- **Assumption Validation Map**: Key assumptions mapped to validation questions
+- **Interview Sequence**: Recommended order and rationale
+- **Risk Mitigation**: Potential risks and mitigation strategies
+
+### Step 5: Document Creation
+**AI Agent Final Action**:
+- Create strategic recommendations document in `docs/customer-insights/`
+- Use intuitive naming based on context (e.g., `ashley-market-niche-strategy.md`)
+- Include all research findings and recommendations
+- Provide actionable next steps for PM
+- Save document for future reference and team sharing
+
+## OUTPUT TEMPLATE
+
+### Strategic Recommendations Document
+**Template**: Retrieve via `get_fraim_file({ path: "templates/customer-development/strategic-recommendations-template.md" })`
+**File Location**: `docs/customer-development/[contextual-name].md` (e.g., `ashley-market-niche-strategy.md`)
+
+**Process**:
+1. Use the strategic recommendations template
+2. Fill in all sections with research findings and recommendations
+3. Save with contextual naming based on strategic focus
+4. Include specific customer names and companies when available
+5. Reference existing business documents and customer insights
+
+## EXAMPLES
+
+### Good: Strategic Brainstorming Session
+```
+PM: "Starting Strategic Brainstorming. We're building Ashley, an AI executive assistant. I think enterprise execs want AI to handle calendar conflicts automatically, but I'm not sure if that's right."
+
+AI Agent: "Perfect! I've reviewed your business docs and customer insights. I can see from your WhyAshley document that you're positioning Ashley as 'Your Agent for Time, Priorities, and Human Potential' and targeting enterprise executives. I also noticed from your existing customer interviews with Ronil, Sanjoy, and Olga that calendar conflict resolution came up as a key pain point across all three customers.
+
+However, I'm curious about your 'automatic' assumption. From your existing customer insights, I see that trust and delegation control were major themes - Ronil mentioned 'Don't have trust in tech to read email - need to have hands in it' and Sanjoy was concerned about 'Disturb during highly important meetings'. What makes you think they want it 'automatic' vs 'suggested'?"
+
+PM: "Good point. I guess I'm assuming automatic because that's what would save them the most time."
+
+AI Agent: "That's a reasonable assumption, but based on your existing customer feedback, there's a clear pattern of wanting control and oversight. Ronil mentioned wanting to 'observe for 2 weeks, then take action' and Olga talked about how good EAs 'enforce workback plans based on business priorities' rather than just doing what they're asked. What if we validated this by asking about their current delegation patterns and comfort levels with AI autonomy?"
+
+[Brainstorming continues with deep context...]
+
+AI Agent Output: Strategic recommendations document informed by existing business context and customer insights
+```
+
+### Bad: Surface-Level Brainstorming
+```
+PM: "We're building Ashley, an AI executive assistant. Who should we interview?"
+
+AI Agent: "You should interview enterprise executives."
+
+PM: "Okay, thanks."
+
+Result: No deep thinking, no assumption validation, no strategic recommendations
+```
+
+## SUCCESS METRICS
+- **Assumption Validation**: 80% of key assumptions have clear validation questions
+- **Customer Segment Clarity**: Clear rationale for segment prioritization
+- **Interview Readiness**: PM has clear next steps for customer interviews
+- **Risk Awareness**: Potential risks identified and mitigated