73 KiB
73 KiB
Business Analyst (Analyst) - Template Guide
Overview
This guide provides comprehensive templates for the Business Analyst persona in the BMAD Method. These templates support the three core working modes: Brainstorming, Research, and Project Briefing, ensuring consistent, high-quality deliverables across all analysis activities.
Template Categories
1. Research Templates
Templates for planning, executing, and documenting research activities.
2. Analysis Templates
Templates for structuring analysis work and presenting findings.
3. Brainstorming Templates
Templates for facilitating ideation sessions and capturing insights.
4. Documentation Templates
Templates for creating project briefs and formal documentation.
5. Communication Templates
Templates for stakeholder engagement and presentation materials.
6. Quality Assurance Templates
Templates for ensuring analysis quality and validation.
1. Research Templates
1.1 Research Brief Template
Purpose: Structure comprehensive research planning Usage: Research Mode - Initial planning phase
# Research Brief: [Project Name]
## Executive Summary
[2-3 sentence overview of research objectives and expected outcomes]
## Research Objectives
### Primary Objective
[Main research goal - what decision will this research inform?]
### Secondary Objectives
- [Supporting research goal 1]
- [Supporting research goal 2]
- [Supporting research goal 3]
## Key Research Questions
### Critical Questions (Must Answer)
1. [Question that directly impacts primary objective]
2. [Question that directly impacts primary objective]
3. [Question that directly impacts primary objective]
### Important Questions (Should Answer)
1. [Supporting question for deeper understanding]
2. [Supporting question for validation]
3. [Supporting question for context]
### Exploratory Questions (Nice to Answer)
1. [Question for future consideration]
2. [Question for broader context]
## Research Scope
### Included
- [Specific area/topic included]
- [Specific area/topic included]
- [Specific area/topic included]
### Excluded
- [Specific area/topic excluded and why]
- [Specific area/topic excluded and why]
## Research Methodology
### Approach
[Primary research methodology - quantitative, qualitative, mixed methods]
### Methods
- **Primary Research**: [Surveys, interviews, observations, etc.]
- **Secondary Research**: [Industry reports, academic studies, competitor analysis]
- **Data Analysis**: [Statistical analysis, thematic analysis, comparative analysis]
### Information Sources
- **Internal Sources**: [Company data, stakeholder interviews, existing research]
- **External Sources**: [Industry databases, competitor websites, expert interviews]
- **Validation Sources**: [How findings will be cross-validated]
## Success Criteria
### Research Quality Indicators
- [How we'll know the research is comprehensive]
- [How we'll know the research is reliable]
- [How we'll know the research is actionable]
### Decision Support Criteria
- [How research will support the primary decision]
- [What level of confidence is required]
- [What format findings need to be in]
## Timeline & Resources
### Research Schedule
- **Week 1**: [Research planning and setup]
- **Week 2**: [Primary data collection]
- **Week 3**: [Secondary research and analysis]
- **Week 4**: [Synthesis and reporting]
### Resource Requirements
- **Personnel**: [Research team composition]
- **Tools**: [Research tools and platforms needed]
- **Budget**: [Estimated costs for external resources]
- **Access**: [Data, systems, or people access needed]
## Deliverables
### Primary Deliverables
- [Main research report with findings and recommendations]
- [Executive summary for stakeholders]
- [Data appendix with supporting evidence]
### Supporting Deliverables
- [Presentation materials for stakeholder review]
- [Raw data files and analysis workbooks]
- [Methodology documentation for future reference]
## Risk Assessment
### Research Risks
- **Risk**: [Potential research limitation]
- **Impact**: [How this could affect findings]
- **Mitigation**: [How to address or minimize]
### Timeline Risks
- **Risk**: [Potential delay factor]
- **Impact**: [Effect on project timeline]
- **Mitigation**: [Contingency plan]
## Stakeholder Engagement
### Key Stakeholders
- **Primary**: [Decision makers who will use research]
- **Secondary**: [Teams affected by research outcomes]
- **Subject Matter Experts**: [Internal/external experts to consult]
### Communication Plan
- **Kickoff**: [Initial stakeholder alignment meeting]
- **Check-ins**: [Regular progress updates]
- **Review**: [Findings validation sessions]
- **Final Presentation**: [Results communication]
---
**Template Version**: 1.0
**Last Updated**: [Date]
**Created By**: Business Analyst
1.2 Competitive Analysis Template
Purpose: Structure competitive intelligence gathering Usage: Research Mode - Market analysis
# Competitive Analysis: [Market/Product Category]
## Analysis Overview
### Objective
[What competitive intelligence is needed and why]
### Scope
- **Geographic**: [Markets included in analysis]
- **Time Period**: [Analysis timeframe]
- **Competitor Types**: [Direct, indirect, emerging competitors]
## Competitor Identification
### Direct Competitors
| Competitor | Market Share | Key Strengths | Key Weaknesses |
|------------|--------------|---------------|----------------|
| [Name] | [%] | [Strength 1, 2, 3] | [Weakness 1, 2, 3] |
| [Name] | [%] | [Strength 1, 2, 3] | [Weakness 1, 2, 3] |
### Indirect Competitors
| Competitor | Alternative Solution | Threat Level | Notes |
|------------|---------------------|--------------|-------|
| [Name] | [How they solve same problem] | [High/Med/Low] | [Key insights] |
### Emerging Competitors
| Competitor | Innovation/Disruption | Timeline | Potential Impact |
|------------|----------------------|----------|------------------|
| [Name] | [What makes them different] | [When threat emerges] | [Potential market impact] |
## Feature Comparison Matrix
| Feature/Capability | Our Product | Competitor A | Competitor B | Competitor C |
|-------------------|-------------|--------------|--------------|--------------|
| [Core Feature 1] | [Rating/Description] | [Rating/Description] | [Rating/Description] | [Rating/Description] |
| [Core Feature 2] | [Rating/Description] | [Rating/Description] | [Rating/Description] | [Rating/Description] |
| [Pricing] | [Our pricing] | [Their pricing] | [Their pricing] | [Their pricing] |
| [User Experience] | [Rating/Notes] | [Rating/Notes] | [Rating/Notes] | [Rating/Notes] |
## Market Positioning Analysis
### Positioning Map
[Description of how competitors position themselves - price vs. features, simplicity vs. power, etc.]
### Value Propositions
- **Our Value Prop**: [How we position ourselves]
- **Competitor A**: [Their key value proposition]
- **Competitor B**: [Their key value proposition]
- **Competitor C**: [Their key value proposition]
## Strategic Insights
### Market Gaps
- [Unmet customer need 1]
- [Unmet customer need 2]
- [Unmet customer need 3]
### Competitive Advantages
- [Our unique advantage 1]
- [Our unique advantage 2]
- [Our unique advantage 3]
### Competitive Threats
- [Threat 1 and mitigation strategy]
- [Threat 2 and mitigation strategy]
- [Threat 3 and mitigation strategy]
## Recommendations
### Strategic Recommendations
1. [Strategic recommendation based on analysis]
2. [Strategic recommendation based on analysis]
3. [Strategic recommendation based on analysis]
### Tactical Recommendations
1. [Immediate action based on competitive intelligence]
2. [Immediate action based on competitive intelligence]
3. [Immediate action based on competitive intelligence]
---
**Analysis Date**: [Date]
**Next Review**: [Date]
**Analyst**: [Name]
1.3 User Research Plan Template
Purpose: Structure user research studies Usage: Research Mode - User insight gathering
# User Research Plan: [Study Name]
## Research Overview
### Research Objectives
**Primary Question**: [Main question this research will answer]
**Secondary Questions**:
- [Supporting question 1]
- [Supporting question 2]
- [Supporting question 3]
### Success Criteria
- [How we'll know the research was successful]
- [What decisions this research will inform]
- [What confidence level we need in findings]
## Research Design
### Methodology
**Research Type**: [Exploratory, Descriptive, Causal]
**Approach**: [Qualitative, Quantitative, Mixed Methods]
**Methods**: [Interviews, Surveys, Observations, Usability Testing, etc.]
### Participant Criteria
**Target Participants**: [Who we need to research]
**Sample Size**: [Number of participants needed]
**Recruitment Criteria**:
- **Include**: [Characteristics participants must have]
- **Exclude**: [Characteristics that disqualify participants]
### Research Protocol
**Session Structure**:
1. **Introduction** (5 min): [Welcome and context setting]
2. **Background Questions** (10 min): [Understanding participant context]
3. **Main Research Activities** (30 min): [Core research tasks/questions]
4. **Wrap-up** (5 min): [Final questions and next steps]
**Key Questions/Tasks**:
- [Research question/task 1]
- [Research question/task 2]
- [Research question/task 3]
## Data Collection Plan
### Data Types
- **Behavioral Data**: [What actions/behaviors we'll observe]
- **Attitudinal Data**: [What opinions/feelings we'll capture]
- **Contextual Data**: [What environmental factors we'll note]
### Collection Methods
- **Recording**: [Audio, video, screen recording permissions and setup]
- **Note-taking**: [Who takes notes, what format]
- **Artifacts**: [Any materials participants will create]
## Analysis Plan
### Analysis Approach
**Method**: [Thematic analysis, statistical analysis, comparative analysis]
**Framework**: [Any specific analysis frameworks to use]
### Key Metrics/Indicators
- [Quantitative metric 1]
- [Quantitative metric 2]
- [Qualitative theme 1]
- [Qualitative theme 2]
## Timeline & Logistics
### Research Schedule
- **Planning**: [Dates for research design and setup]
- **Recruitment**: [Dates for participant recruitment]
- **Data Collection**: [Dates for research sessions]
- **Analysis**: [Dates for data analysis]
- **Reporting**: [Dates for findings documentation]
### Logistics
- **Location**: [Where research will be conducted]
- **Technology**: [Tools and platforms needed]
- **Materials**: [Any physical or digital materials needed]
- **Team Roles**: [Who does what during research]
## Ethical Considerations
### Participant Rights
- [Informed consent process]
- [Privacy and confidentiality protections]
- [Right to withdraw participation]
- [Data handling and storage procedures]
### Bias Mitigation
- [How we'll minimize researcher bias]
- [How we'll ensure representative sample]
- [How we'll validate findings]
## Deliverables
### Research Outputs
- **Research Report**: [Comprehensive findings and recommendations]
- **Executive Summary**: [Key insights for stakeholders]
- **Presentation**: [Findings presentation for team review]
- **Raw Data**: [Organized data files for future reference]
### Success Metrics
- [How we'll measure research quality]
- [How we'll measure research impact]
- [How we'll measure stakeholder satisfaction]
---
**Research Plan Version**: 1.0
**Created By**: [Analyst Name]
**Review Date**: [Date]
2. Analysis Templates
2.1 Root Cause Analysis Template
Purpose: Structure systematic problem analysis Usage: Brainstorming Mode - Problem diagnosis
# Root Cause Analysis: [Problem Statement]
## Problem Definition
### Problem Statement
[Clear, specific description of the problem]
### Problem Impact
- **Business Impact**: [How this affects business outcomes]
- **User Impact**: [How this affects users/customers]
- **Operational Impact**: [How this affects day-to-day operations]
### Problem Scope
- **When**: [When does this problem occur?]
- **Where**: [Where does this problem occur?]
- **Who**: [Who is affected by this problem?]
- **What**: [What specifically is happening?]
## Initial Hypothesis
### Suspected Causes
1. [Initial hypothesis about cause 1]
2. [Initial hypothesis about cause 2]
3. [Initial hypothesis about cause 3]
### Assumptions to Test
- [Assumption 1 that needs validation]
- [Assumption 2 that needs validation]
- [Assumption 3 that needs validation]
## 5 Whys Analysis
### Problem: [Restate the problem]
**Why 1**: [First why - immediate cause]
**Why 2**: [Second why - cause of the immediate cause]
**Why 3**: [Third why - deeper cause]
**Why 4**: [Fourth why - even deeper cause]
**Why 5**: [Fifth why - root cause]
### Root Cause Identified
[The fundamental cause identified through 5 Whys]
## Fishbone Analysis
### Categories of Potential Causes
**People**:
- [Potential people-related cause 1]
- [Potential people-related cause 2]
**Process**:
- [Potential process-related cause 1]
- [Potential process-related cause 2]
**Technology**:
- [Potential technology-related cause 1]
- [Potential technology-related cause 2]
**Environment**:
- [Potential environment-related cause 1]
- [Potential environment-related cause 2]
**Materials/Information**:
- [Potential materials/information-related cause 1]
- [Potential materials/information-related cause 2]
**Methods**:
- [Potential methods-related cause 1]
- [Potential methods-related cause 2]
## Evidence Collection
### Data Sources
| Potential Cause | Evidence Type | Data Source | Findings |
|----------------|---------------|-------------|----------|
| [Cause 1] | [Quantitative/Qualitative] | [Where to find evidence] | [What evidence shows] |
| [Cause 2] | [Quantitative/Qualitative] | [Where to find evidence] | [What evidence shows] |
### Validation Methods
- [How we'll test hypothesis 1]
- [How we'll test hypothesis 2]
- [How we'll test hypothesis 3]
## Root Cause Validation
### Primary Root Cause
**Cause**: [The validated root cause]
**Evidence**: [Evidence that supports this as the root cause]
**Confidence Level**: [High/Medium/Low and why]
### Contributing Factors
1. [Contributing factor 1 and its role]
2. [Contributing factor 2 and its role]
3. [Contributing factor 3 and its role]
## Solution Development
### Solution Options
| Solution | Addresses Root Cause | Implementation Effort | Expected Impact |
|----------|---------------------|----------------------|-----------------|
| [Solution 1] | [Yes/Partially/No] | [High/Medium/Low] | [Expected outcome] |
| [Solution 2] | [Yes/Partially/No] | [High/Medium/Low] | [Expected outcome] |
### Recommended Solution
**Solution**: [Recommended approach]
**Rationale**: [Why this solution is recommended]
**Implementation Plan**: [High-level implementation approach]
## Prevention Strategy
### Process Improvements
- [Process change to prevent recurrence]
- [Process change to prevent recurrence]
### Monitoring & Detection
- [How to detect this problem early in future]
- [What metrics to monitor]
- [What alerts to set up]
---
**Analysis Date**: [Date]
**Analyst**: [Name]
**Validation Status**: [Pending/In Progress/Complete]
2.2 SWOT Analysis Template
Purpose: Structure strategic situation analysis Usage: Brainstorming Mode - Strategic assessment
# SWOT Analysis: [Organization/Product/Initiative]
## Analysis Overview
### Objective
[What strategic decision this SWOT analysis will inform]
### Scope
[What specifically is being analyzed - company, product, market entry, etc.]
### Analysis Date
[When this analysis was conducted]
## Internal Factors
### Strengths
**What advantages do we have?**
**What do we do well?**
**What unique resources can we draw on?**
**What do others see as our strengths?**
1. **[Strength Category 1]**
- [Specific strength 1]
- [Specific strength 2]
- [Specific strength 3]
2. **[Strength Category 2]**
- [Specific strength 1]
- [Specific strength 2]
- [Specific strength 3]
3. **[Strength Category 3]**
- [Specific strength 1]
- [Specific strength 2]
- [Specific strength 3]
### Weaknesses
**What could we improve?**
**Where do we have fewer resources than others?**
**What are others likely to see as weaknesses?**
1. **[Weakness Category 1]**
- [Specific weakness 1]
- [Specific weakness 2]
- [Specific weakness 3]
2. **[Weakness Category 2]**
- [Specific weakness 1]
- [Specific weakness 2]
- [Specific weakness 3]
3. **[Weakness Category 3]**
- [Specific weakness 1]
- [Specific weakness 2]
- [Specific weakness 3]
## External Factors
### Opportunities
**What opportunities are open to us?**
**What trends could we take advantage of?**
**How can we turn our strengths into opportunities?**
1. **[Opportunity Category 1]**
- [Specific opportunity 1]
- [Specific opportunity 2]
- [Specific opportunity 3]
2. **[Opportunity Category 2]**
- [Specific opportunity 1]
- [Specific opportunity 2]
- [Specific opportunity 3]
3. **[Opportunity Category 3]**
- [Specific opportunity 1]
- [Specific opportunity 2]
- [Specific opportunity 3]
### Threats
**What threats could harm us?**
**What is our competition doing?**
**What threats do our weaknesses expose us to?**
1. **[Threat Category 1]**
- [Specific threat 1]
- [Specific threat 2]
- [Specific threat 3]
2. **[Threat Category 2]**
- [Specific threat 1]
- [Specific threat 2]
- [Specific threat 3]
3. **[Threat Category 3]**
- [Specific threat 1]
- [Specific threat 2]
- [Specific threat 3]
## Strategic Implications
### SO Strategies (Strength-Opportunity)
**How can we use our strengths to take advantage of opportunities?**
1. [Strategy leveraging strength to capture opportunity]
2. [Strategy leveraging strength to capture opportunity]
3. [Strategy leveraging strength to capture opportunity]
### WO Strategies (Weakness-Opportunity)
**How can we overcome weaknesses to take advantage of opportunities?**
1. [Strategy to address weakness while pursuing opportunity]
2. [Strategy to address weakness while pursuing opportunity]
3. [Strategy to address weakness while pursuing opportunity]
### ST Strategies (Strength-Threat)
**How can we use our strengths to avoid threats?**
1. [Strategy using strength to mitigate threat]
2. [Strategy using strength to mitigate threat]
3. [Strategy using strength to mitigate threat]
### WT Strategies (Weakness-Threat)
**How can we minimize weaknesses and avoid threats?**
1. [Defensive strategy to address weakness and threat]
2. [Defensive strategy to address weakness and threat]
3. [Defensive strategy to address weakness and threat]
## Priority Matrix
### High Impact, High Urgency
- [Critical item requiring immediate attention]
- [Critical item requiring immediate attention]
### High Impact, Low Urgency
- [Important item for strategic planning]
- [Important item for strategic planning]
### Low Impact, High Urgency
- [Quick win or tactical item]
- [Quick win or tactical item]
### Low Impact, Low Urgency
- [Item to monitor or consider later]
- [Item to monitor or consider later]
## Action Plan
### Immediate Actions (Next 30 days)
1. [Action to address highest priority item]
2. [Action to address highest priority item]
3. [Action to address highest priority item]
### Short-term Actions (Next 90 days)
1. [Action for short-term strategic positioning]
2. [Action for short-term strategic positioning]
3. [Action for short-term strategic positioning]
### Long-term Actions (Next 12 months)
1. [Action for long-term strategic advantage]
2. [Action for long-term strategic advantage]
3. [Action for long-term strategic advantage]
## Success Metrics
### Key Performance Indicators
- [Metric to track strength enhancement]
- [Metric to track weakness improvement]
- [Metric to track opportunity capture]
- [Metric to track threat mitigation]
### Review Schedule
- **Next Review**: [Date for next SWOT analysis]
- **Review Frequency**: [How often to update this analysis]
- **Review Triggers**: [Events that would trigger an earlier review]
---
**Analysis Team**: [Who participated in this analysis]
**Validation Date**: [When findings were validated]
**Next Update**: [When this analysis should be refreshed]
3. Brainstorming Templates
3.1 Ideation Session Template
Purpose: Structure creative brainstorming sessions Usage: Brainstorming Mode - Idea generation
# Ideation Session: [Session Topic]
## Session Overview
### Objective
[What we're trying to achieve through this brainstorming session]
### Challenge Statement
[Clear articulation of the problem or opportunity we're addressing]
### Success Criteria
[How we'll know the session was successful]
## Session Details
### Participants
- **Facilitator**: [Name and role]
- **Participants**:
- [Name, role, perspective they bring]
- [Name, role, perspective they bring]
- [Name, role, perspective they bring]
### Session Logistics
- **Date**: [Session date]
- **Duration**: [Session length]
- **Location**: [Physical or virtual location]
- **Materials**: [What materials/tools are needed]
## Pre-Session Preparation
### Background Information
[Key context participants should know before the session]
### Constraints & Parameters
- **Must Have**: [Non-negotiable requirements]
- **Should Have**: [Important but flexible requirements]
- **Could Have**: [Nice-to-have features]
- **Won't Have**: [Explicitly out of scope]
### Inspiration Sources
- [Relevant examples or case studies]
- [Industry best practices to consider]
- [Analogous solutions from other domains]
## Session Structure
### 1. Warm-up (10 minutes)
**Activity**: [Warm-up exercise to get creative thinking flowing]
**Purpose**: [Why this warm-up was chosen]
### 2. Problem Framing (15 minutes)
**Activity**: [How we'll ensure everyone understands the challenge]
**Key Questions**:
- [Question to clarify the problem]
- [Question to explore assumptions]
- [Question to identify constraints]
### 3. Divergent Thinking (30 minutes)
**Technique**: [Brainstorming method - classic brainstorming, brainwriting, SCAMPER, etc.]
**Rules**:
- Defer judgment
- Strive for quantity
- Build on ideas of others
- Stay focused on topic
- Encourage wild ideas
**Prompts**:
- "What if we..."
- "How might we..."
- "What would happen if..."
### 4. Idea Clustering (15 minutes)
**Activity**: [How we'll organize and group related ideas]
**Categories**: [Themes or categories for organizing ideas]
### 5. Convergent Thinking (20 minutes)
**Activity**: [How we'll evaluate and prioritize ideas]
**Criteria**:
- Feasibility (Can we do it?)
- Viability (Should we do it?)
- Desirability (Do users want it?)
### 6. Next Steps (10 minutes)
**Activity**: [How we'll plan follow-up actions]
## Ideation Techniques
### Primary Technique: [Chosen Method]
**Description**: [How this technique works]
**Why Chosen**: [Why this technique is appropriate for this challenge]
**Instructions**: [Step-by-step guide for participants]
### Backup Techniques
1. **[Alternative Technique 1]**: [When to use this instead]
2. **[Alternative Technique 2]**: [When to use this instead]
## Idea Capture Template
### Idea: [Idea Name/Title]
**Description**: [Brief description of the idea]
**How it Works**: [Explanation of how this idea would function]
**Benefits**: [What advantages this idea provides]
**Challenges**: [What obstacles might exist]
**Next Steps**: [What would need to happen to explore this further]
## Evaluation Criteria
### Feasibility Assessment
- **Technical Feasibility**: [Can we build/implement this?]
- **Resource Feasibility**: [Do we have the resources?]
- **Timeline Feasibility**: [Can we do this in the required timeframe?]
### Impact Assessment
- **User Impact**: [How much would this help users?]
- **Business Impact**: [How much would this help the business?]
- **Strategic Alignment**: [How well does this fit our strategy?]
### Risk Assessment
- **Implementation Risk**: [What could go wrong during implementation?]
- **Market Risk**: [What market factors could affect success?]
- **Competitive Risk**: [How might competitors respond?]
## Session Outcomes
### Ideas Generated
[Total number of ideas generated]
### Top Ideas (Post-Evaluation)
1. **[Idea Name]**
- **Score**: [Evaluation score]
- **Rationale**: [Why this idea scored highly]
- **Next Steps**: [Immediate actions for this idea]
2. **[Idea Name]**
- **Score**: [Evaluation score]
- **Rationale**: [Why this idea scored highly]
- **Next Steps**: [Immediate actions for this idea]
3. **[Idea Name]**
- **Score**: [Evaluation score]
- **Rationale**: [Why this idea scored highly]
- **Next Steps**: [Immediate actions for this idea]
### Insights & Themes
- [Key insight or pattern that emerged]
- [Key insight or pattern that emerged]
- [Key insight or pattern that emerged]
## Follow-up Actions
### Immediate Actions (Next 7 days)
1. [Action item with owner and deadline]
2. [Action item with owner and deadline]
3. [Action item with owner and deadline]
### Short-term Actions (Next 30 days)
1. [Action item with owner and deadline]
2. [Action item with owner and deadline]
3. [Action item with owner and deadline]
### Research & Validation Needed
- [What needs to be researched or validated]
- [What needs to be researched or validated]
- [What needs to be researched or validated]
---
**Session Facilitator**: [Name]
**Session Date**: [Date]
**Follow-up Review**: [Date for reviewing progress]
3.2 SCAMPER Analysis Template
Purpose: Structure systematic creative thinking Usage: Brainstorming Mode - Idea development
# SCAMPER Analysis: [Product/Service/Process]
## Analysis Overview
### Subject
[What we're applying SCAMPER analysis to]
### Objective
[What we hope to achieve through this creative analysis]
### Current State
[Brief description of the current product/service/process]
## SCAMPER Framework
### S - Substitute
**Question**: What can be substituted or swapped?
**Elements to Consider**:
- Materials or components
- People or roles
- Processes or methods
- Places or locations
- Time or sequence
**Ideas Generated**:
1. [Substitution idea 1]
- **What to substitute**: [Current element]
- **Substitute with**: [New element]
- **Potential benefit**: [Expected improvement]
2. [Substitution idea 2]
- **What to substitute**: [Current element]
- **Substitute with**: [New element]
- **Potential benefit**: [Expected improvement]
### C - Combine
**Question**: What can be combined or merged?
**Elements to Consider**:
- Features or functions
- Products or services
- Processes or steps
- Teams or departments
- Technologies or tools
**Ideas Generated**:
1. [Combination idea 1]
- **What to combine**: [Elements to merge]
- **How to combine**: [Method of combination]
- **Potential benefit**: [Expected improvement]
2. [Combination idea 2]
- **What to combine**: [Elements to merge]
- **How to combine**: [Method of combination]
- **Potential benefit**: [Expected improvement]
### A - Adapt
**Question**: What can be adapted from elsewhere?
**Elements to Consider**:
- Solutions from other industries
- Processes from other departments
- Technologies from other applications
- Strategies from competitors
- Methods from other contexts
**Ideas Generated**:
1. [Adaptation idea 1]
- **Source of adaptation**: [Where this idea comes from]
- **How to adapt**: [How to modify for our context]
- **Potential benefit**: [Expected improvement]
2. [Adaptation idea 2]
- **Source of adaptation**: [Where this idea comes from]
- **How to adapt**: [How to modify for our context]
- **Potential benefit**: [Expected improvement]
### M - Modify/Magnify
**Question**: What can be modified, magnified, or emphasized?
**Elements to Consider**:
- Size or scale
- Frequency or speed
- Strength or intensity
- Height or length
- Quantity or volume
**Ideas Generated**:
1. [Modification idea 1]
- **What to modify**: [Element to change]
- **How to modify**: [Type of modification]
- **Potential benefit**: [Expected improvement]
2. [Modification idea 2]
- **What to modify**: [Element to change]
- **How to modify**: [Type of modification]
- **Potential benefit**: [Expected improvement]
### P - Put to Other Uses
**Question**: What else can this be used for?
**Elements to Consider**:
- New markets or audiences
- Different applications
- Alternative purposes
- Secondary uses
- Unexpected contexts
**Ideas Generated**:
1. [Alternative use idea 1]
- **New use**: [Different application]
- **Target audience**: [Who would benefit]
- **Potential benefit**: [Expected value]
2. [Alternative use idea 2]
- **New use**: [Different application]
- **Target audience**: [Who would benefit]
- **Potential benefit**: [Expected value]
### E - Eliminate
**Question**: What can be eliminated or reduced?
**Elements to Consider**:
- Unnecessary features
- Redundant processes
- Excessive complexity
- Wasteful steps
- Outdated components
**Ideas Generated**:
1. [Elimination idea 1]
- **What to eliminate**: [Element to remove]
- **Why eliminate**: [Reason for removal]
- **Potential benefit**: [Expected improvement]
2. [Elimination idea 2]
- **What to eliminate**: [Element to remove]
- **Why eliminate**: [Reason for removal]
- **Potential benefit**: [Expected improvement]
### R - Reverse/Rearrange
**Question**: What can be reversed or rearranged?
**Elements to Consider**:
- Order or sequence
- Roles or responsibilities
- Cause and effect
- Positive and negative
- Inside and outside
**Ideas Generated**:
1. [Reversal/rearrangement idea 1]
- **What to reverse/rearrange**: [Element to change]
- **How to reverse/rearrange**: [Method of change]
- **Potential benefit**: [Expected improvement]
2. [Reversal/rearrangement idea 2]
- **What to reverse/rearrange**: [Element to change]
- **How to reverse/rearrange**: [Method of change]
- **Potential benefit**: [Expected improvement]
## Idea Evaluation
### Top Ideas Summary
| Idea | SCAMPER Category | Feasibility | Impact | Priority |
|------|------------------|-------------|--------|----------|
| [Idea 1] | [S/C/A/M/P/E/R] | [High/Med/Low] | [High/Med/Low] | [High/Med/Low] |
| [Idea 2] | [S/C/A/M/P/E/R] | [High/Med/Low] | [High/Med/Low] | [High/Med/Low] |
| [Idea 3] | [S/C/A/M/P/E/R] | [High/Med/Low] | [High/Med/Low] | [High/Med/Low] |
### Detailed Evaluation
#### Idea 1: [Idea Name]
**Description**: [Detailed description of the idea]
**SCAMPER Origin**: [Which SCAMPER prompt generated this]
**Feasibility Analysis**:
- **Technical**: [Can we implement this technically?]
- **Resource**: [Do we have the resources?]
- **Timeline**: [How long would this take?]
**Impact Analysis**:
- **User Benefit**: [How does this help users?]
- **Business Value**: [How does this help the business?]
- **Competitive Advantage**: [Does this differentiate us?]
**Implementation Considerations**:
- **Requirements**: [What would we need to implement this?]
- **Risks**: [What could go wrong?]
- **Dependencies**: [What else needs to happen first?]
## Next Steps
### Immediate Actions
1. [Action to further develop top idea]
2. [Action to validate assumptions]
3. [Action to assess feasibility]
### Research Needed
- [What needs to be researched before proceeding]
- [What validation is required]
- [What expert input is needed]
### Decision Points
- [Key decisions that need to be made]
- [Who needs to be involved in decisions]
- [Timeline for decision making]
---
**Analysis Date**: [Date]
**Analyst**: [Name]
**Review Date**: [When to review progress]
4. Documentation Templates
4.1 Project Brief Template
Purpose: Create comprehensive project documentation Usage: Briefing Mode - Project initiation
# Project Brief: [Project Name]
## Executive Summary
[2-3 paragraph overview covering the problem, solution approach, expected outcomes, and resource requirements]
## Project Overview
### Problem Statement
**Current Situation**: [What is happening now that needs to change?]
**Pain Points**: [What specific problems are we solving?]
**Impact of Inaction**: [What happens if we don't address this?]
### Project Objectives
**Primary Objective**: [Main goal this project will achieve]
**Secondary Objectives**:
- [Supporting objective 1]
- [Supporting objective 2]
- [Supporting objective 3]
**Success Criteria**: [How we'll know the project was successful]
### Solution Approach
**Proposed Solution**: [High-level description of what we plan to build/implement]
**Key Features**: [Main capabilities or components]
**Approach Rationale**: [Why this approach was chosen]
## Business Case
### Business Value
**Quantifiable Benefits**:
- [Measurable benefit 1 with estimated value]
- [Measurable benefit 2 with estimated value]
- [Measurable benefit 3 with estimated value]
**Qualitative Benefits**:
- [Intangible benefit 1]
- [Intangible benefit 2]
- [Intangible benefit 3]
### Cost-Benefit Analysis
**Investment Required**: [Total project cost estimate]
**Expected ROI**: [Return on investment calculation]
**Payback Period**: [How long to recoup investment]
### Risk Assessment
**High-Risk Items**:
- **Risk**: [Description of risk]
- **Probability**: [High/Medium/Low]
- **Impact**: [High/Medium/Low]
- **Mitigation**: [How to address this risk]
**Medium-Risk Items**:
- **Risk**: [Description of risk]
- **Probability**: [High/Medium/Low]
- **Impact**: [High/Medium/Low]
- **Mitigation**: [How to address this risk]
## Project Scope
### In Scope
**Functional Requirements**:
- [What the system/solution will do]
- [What the system/solution will do]
- [What the system/solution will do]
**Non-Functional Requirements**:
- [Performance requirements]
- [Security requirements]
- [Usability requirements]
**Deliverables**:
- [Deliverable 1 with description]
- [Deliverable 2 with description]
- [Deliverable 3 with description]
### Out of Scope
**Explicitly Excluded**:
- [What we will NOT include and why]
- [What we will NOT include and why]
- [What we will NOT include and why]
**Future Considerations**:
- [Items for potential future phases]
- [Items for potential future phases]
## Stakeholder Analysis
### Primary Stakeholders
| Stakeholder | Role | Interest | Influence | Engagement Strategy |
|-------------|------|----------|-----------|-------------------|
| [Name/Group] | [Their role] | [What they care about] | [High/Med/Low] | [How to engage them] |
| [Name/Group] | [Their role] | [What they care about] | [High/Med/Low] | [How to engage them] |
### Secondary Stakeholders
| Stakeholder | Role | Interest | Influence | Engagement Strategy |
|-------------|------|----------|-----------|-------------------|
| [Name/Group] | [Their role] | [What they care about] | [High/Med/Low] | [How to engage them] |
| [Name/Group] | [Their role] | [What they care about] | [High/Med/Low] | [How to engage them] |
## User Analysis
### Primary Users
**User Group 1**: [User type]
- **Characteristics**: [Who they are]
- **Needs**: [What they need from this solution]
- **Pain Points**: [Current frustrations]
- **Success Criteria**: [How they'll measure success]
**User Group 2**: [User type]
- **Characteristics**: [Who they are]
- **Needs**: [What they need from this solution]
- **Pain Points**: [Current frustrations]
- **Success Criteria**: [How they'll measure success]
### User Journey Considerations
**Current State**: [How users currently accomplish their goals]
**Future State**: [How users will accomplish goals with new solution]
**Key Improvements**: [What will be better in the future state]
## Technical Considerations
### Technical Requirements
**Platform Requirements**: [What platforms/systems this needs to work with]
**Integration Requirements**: [What systems this needs to integrate with]
**Performance Requirements**: [Speed, capacity, availability requirements]
**Security Requirements**: [Security and compliance needs]
### Technical Constraints
**Technology Constraints**: [Limitations on technology choices]
**Resource Constraints**: [Limitations on technical resources]
**Timeline Constraints**: [Technical limitations due to timeline]
### Architecture Considerations
**High-Level Architecture**: [Basic architectural approach]
**Key Technical Decisions**: [Important technical choices to be made]
**Technical Risks**: [Technology-related risks and mitigation strategies]
## Project Timeline
### High-Level Phases
**Phase 1: [Phase Name]** ([Duration])
- [Key activities and deliverables]
- [Key milestones]
**Phase 2: [Phase Name]** ([Duration])
- [Key activities and deliverables]
- [Key milestones]
**Phase 3: [Phase Name]** ([Duration])
- [Key activities and deliverables]
- [Key milestones]
### Critical Milestones
| Milestone | Date | Description | Dependencies |
|-----------|------|-------------|--------------|
| [Milestone 1] | [Date] | [What will be completed] | [What needs to happen first] |
| [Milestone 2] | [Date] | [What will be completed] | [What needs to happen first] |
### Dependencies
**Internal Dependencies**:
- [Dependency on other internal projects/teams]
- [Dependency on other internal projects/teams]
**External Dependencies**:
- [Dependency on external vendors/partners]
- [Dependency on external vendors/partners]
## Resource Requirements
### Team Structure
**Project Manager**: [Name or TBD]
**Technical Lead**: [Name or TBD]
**Development Team**: [Size and skills needed]
**Design Team**: [Size and skills needed]
**Other Roles**: [Any other specialized roles needed]
### Budget Requirements
**Personnel Costs**: [Estimated cost for team]
**Technology Costs**: [Software, hardware, cloud costs]
**External Costs**: [Vendors, consultants, other external costs]
**Total Budget**: [Total estimated project cost]
### Infrastructure Requirements
**Development Environment**: [What's needed for development]
**Testing Environment**: [What's needed for testing]
**Production Environment**: [What's needed for deployment]
## Success Metrics
### Key Performance Indicators
**Business Metrics**:
- [Business KPI 1]: [Current baseline] → [Target]
- [Business KPI 2]: [Current baseline] → [Target]
- [Business KPI 3]: [Current baseline] → [Target]
**User Metrics**:
- [User KPI 1]: [Current baseline] → [Target]
- [User KPI 2]: [Current baseline] → [Target]
- [User KPI 3]: [Current baseline] → [Target]
**Technical Metrics**:
- [Technical KPI 1]: [Current baseline] → [Target]
- [Technical KPI 2]: [Current baseline] → [Target]
### Measurement Plan
**Data Collection**: [How metrics will be collected]
**Reporting Schedule**: [How often metrics will be reported]
**Review Process**: [How metrics will be reviewed and acted upon]
## Communication Plan
### Stakeholder Communication
**Executive Updates**: [Frequency and format for executive communication]
**Team Updates**: [Frequency and format for team communication]
**User Communication**: [How users will be kept informed]
### Reporting Structure
**Status Reports**: [What will be reported and when]
**Escalation Process**: [How issues will be escalated]
**Decision-Making Process**: [How project decisions will be made]
## Next Steps
### Immediate Actions (Next 2 weeks)
1. [Action item with owner and deadline]
2. [Action item with owner and deadline]
3. [Action item with owner and deadline]
### Project Initiation (Next 30 days)
1. [Action item with owner and deadline]
2. [Action item with owner and deadline]
3. [Action item with owner and deadline]
### Approval Requirements
**Required Approvals**: [Who needs to approve this project brief]
**Approval Timeline**: [When approvals are needed]
**Approval Criteria**: [What criteria will be used for approval]
---
**Document Version**: 1.0
**Created By**: [Business Analyst Name]
**Creation Date**: [Date]
**Last Updated**: [Date]
**Next Review**: [Date]
4.2 Requirements Specification Template
Purpose: Document detailed functional and non-functional requirements Usage: Briefing Mode - Detailed requirements documentation
# Requirements Specification: [Project Name]
## Document Information
**Document Version**: [Version number]
**Created By**: [Business Analyst name]
**Creation Date**: [Date]
**Last Updated**: [Date]
**Approved By**: [Approver name and date]
## Table of Contents
1. Introduction
2. Functional Requirements
3. Non-Functional Requirements
4. User Interface Requirements
5. Integration Requirements
6. Data Requirements
7. Security Requirements
8. Compliance Requirements
9. Assumptions and Dependencies
10. Acceptance Criteria
## 1. Introduction
### 1.1 Purpose
[Purpose of this requirements document]
### 1.2 Scope
[What is covered by these requirements]
### 1.3 Definitions and Acronyms
| Term | Definition |
|------|------------|
| [Term 1] | [Definition] |
| [Term 2] | [Definition] |
### 1.4 References
- [Reference document 1]
- [Reference document 2]
## 2. Functional Requirements
### 2.1 User Management
**REQ-001: User Registration**
- **Description**: [Detailed description of requirement]
- **Priority**: [High/Medium/Low]
- **Source**: [Who requested this requirement]
- **Acceptance Criteria**:
- [Specific criterion 1]
- [Specific criterion 2]
- [Specific criterion 3]
**REQ-002: User Authentication**
- **Description**: [Detailed description of requirement]
- **Priority**: [High/Medium/Low]
- **Source**: [Who requested this requirement]
- **Acceptance Criteria**:
- [Specific criterion 1]
- [Specific criterion 2]
- [Specific criterion 3]
### 2.2 Core Functionality
**REQ-003: [Core Function 1]**
- **Description**: [Detailed description of requirement]
- **Priority**: [High/Medium/Low]
- **Source**: [Who requested this requirement]
- **Business Rules**:
- [Business rule 1]
- [Business rule 2]
- **Acceptance Criteria**:
- [Specific criterion 1]
- [Specific criterion 2]
- [Specific criterion 3]
**REQ-004: [Core Function 2]**
- **Description**: [Detailed description of requirement]
- **Priority**: [High/Medium/Low]
- **Source**: [Who requested this requirement]
- **Business Rules**:
- [Business rule 1]
- [Business rule 2]
- **Acceptance Criteria**:
- [Specific criterion 1]
- [Specific criterion 2]
- [Specific criterion 3]
### 2.3 Reporting and Analytics
**REQ-005: [Reporting Requirement]**
- **Description**: [Detailed description of requirement]
- **Priority**: [High/Medium/Low]
- **Source**: [Who requested this requirement]
- **Data Sources**: [Where data comes from]
- **Acceptance Criteria**:
- [Specific criterion 1]
- [Specific criterion 2]
- [Specific criterion 3]
## 3. Non-Functional Requirements
### 3.1 Performance Requirements
**NFR-001: Response Time**
- **Requirement**: [Specific performance requirement]
- **Measurement**: [How this will be measured]
- **Acceptance Criteria**: [Specific performance targets]
**NFR-002: Throughput**
- **Requirement**: [Specific throughput requirement]
- **Measurement**: [How this will be measured]
- **Acceptance Criteria**: [Specific throughput targets]
### 3.2 Scalability Requirements
**NFR-003: User Capacity**
- **Requirement**: [Specific scalability requirement]
- **Measurement**: [How this will be measured]
- **Acceptance Criteria**: [Specific capacity targets]
### 3.3 Availability Requirements
**NFR-004: System Uptime**
- **Requirement**: [Specific availability requirement]
- **Measurement**: [How this will be measured]
- **Acceptance Criteria**: [Specific uptime targets]
### 3.4 Reliability Requirements
**NFR-005: Error Rate**
- **Requirement**: [Specific reliability requirement]
- **Measurement**: [How this will be measured]
- **Acceptance Criteria**: [Specific reliability targets]
## 4. User Interface Requirements
### 4.1 General UI Requirements
**UIR-001: Responsive Design**
- **Requirement**: [Specific UI requirement]
- **Platforms**: [Which platforms this applies to]
- **Acceptance Criteria**: [Specific UI criteria]
**UIR-002: Accessibility**
- **Requirement**: [Specific accessibility requirement]
- **Standards**: [Which accessibility standards to follow]
- **Acceptance Criteria**: [Specific accessibility criteria]
### 4.2 Specific Interface Requirements
**UIR-003: [Specific Interface]**
- **Requirement**: [Detailed interface requirement]
- **User Experience**: [Expected user experience]
- **Acceptance Criteria**: [Specific interface criteria]
## 5. Integration Requirements
### 5.1 System Integrations
**INT-001: [External System 1]**
- **Integration Type**: [API, File transfer, Database, etc.]
- **Data Exchange**: [What data is exchanged]
- **Frequency**: [How often integration occurs]
- **Error Handling**: [How errors are handled]
- **Acceptance Criteria**: [Integration success criteria]
**INT-002: [External System 2]**
- **Integration Type**: [API, File transfer, Database, etc.]
- **Data Exchange**: [What data is exchanged]
- **Frequency**: [How often integration occurs]
- **Error Handling**: [How errors are handled]
- **Acceptance Criteria**: [Integration success criteria]
### 5.2 Third-Party Services
**INT-003: [Third-Party Service]**
- **Service Provider**: [Name of service provider]
- **Service Type**: [Type of service]
- **Integration Method**: [How integration is implemented]
- **Acceptance Criteria**: [Service integration criteria]
## 6. Data Requirements
### 6.1 Data Storage Requirements
**DAT-001: Data Retention**
- **Requirement**: [Specific data retention requirement]
- **Data Types**: [What types of data this applies to]
- **Retention Period**: [How long data is retained]
- **Disposal Method**: [How data is disposed of]
**DAT-002: Data Backup**
- **Requirement**: [Specific backup requirement]
- **Backup Frequency**: [How often backups occur]
- **Recovery Time**: [How quickly data can be recovered]
- **Acceptance Criteria**: [Backup success criteria]
### 6.2 Data Quality Requirements
**DAT-003: Data Validation**
- **Requirement**: [Specific validation requirement]
- **Validation Rules**: [What validation rules apply]
- **Error Handling**: [How validation errors are handled]
- **Acceptance Criteria**: [Data quality criteria]
## 7. Security Requirements
### 7.1 Authentication and Authorization
**SEC-001: User Authentication**
- **Requirement**: [Specific authentication requirement]
- **Authentication Method**: [How users authenticate]
- **Password Policy**: [Password requirements]
- **Acceptance Criteria**: [Authentication criteria]
**SEC-002: Access Control**
- **Requirement**: [Specific authorization requirement]
- **Role-Based Access**: [How roles and permissions work]
- **Access Levels**: [Different levels of access]
- **Acceptance Criteria**: [Authorization criteria]
### 7.2 Data Protection
**SEC-003: Data Encryption**
- **Requirement**: [Specific encryption requirement]
- **Encryption Standards**: [Which encryption standards to use]
- **Key Management**: [How encryption keys are managed]
- **Acceptance Criteria**: [Encryption criteria]
**SEC-004: Data Privacy**
- **Requirement**: [Specific privacy requirement]
- **Personal Data Handling**: [How personal data is handled]
- **Consent Management**: [How user consent is managed]
- **Acceptance Criteria**: [Privacy criteria]
## 8. Compliance Requirements
### 8.1 Regulatory Compliance
**COM-001: [Regulation 1]**
- **Regulation**: [Name of regulation]
- **Requirements**: [Specific compliance requirements]
- **Implementation**: [How compliance is achieved]
- **Acceptance Criteria**: [Compliance criteria]
**COM-002: [Regulation 2]**
- **Regulation**: [Name of regulation]
- **Requirements**: [Specific compliance requirements]
- **Implementation**: [How compliance is achieved]
- **Acceptance Criteria**: [Compliance criteria]
### 8.2 Industry Standards
**COM-003: [Standard 1]**
- **Standard**: [Name of standard]
- **Requirements**: [Specific standard requirements]
- **Implementation**: [How standard is met]
- **Acceptance Criteria**: [Standard compliance criteria]
## 9. Assumptions and Dependencies
### 9.1 Assumptions
- [Assumption 1 about project context]
- [Assumption 2 about resources]
- [Assumption 3 about technology]
### 9.2 Dependencies
**Internal Dependencies**:
- [Dependency on other internal projects]
- [Dependency on internal resources]
**External Dependencies**:
- [Dependency on external vendors]
- [Dependency on external systems]
## 10. Acceptance Criteria
### 10.1 Functional Acceptance
**Criteria for functional requirements acceptance**:
- [All functional requirements are implemented as specified]
- [All business rules are correctly enforced]
- [All user workflows function as designed]
### 10.2 Non-Functional Acceptance
**Criteria for non-functional requirements acceptance**:
- [All performance targets are met]
- [All security requirements are implemented]
- [All compliance requirements are satisfied]
### 10.3 User Acceptance
**Criteria for user acceptance**:
- [Users can successfully complete all primary tasks]
- [User satisfaction meets target levels]
- [Training and documentation are adequate]
---
**Requirements Traceability**: [Reference to traceability matrix]
**Change Control**: [Process for managing requirement changes]
**Approval**: [Approval signatures and dates]
5. Communication Templates
5.1 Stakeholder Presentation Template
Purpose: Present analysis findings to stakeholders Usage: All Modes - Results communication
# Stakeholder Presentation: [Analysis Topic]
## Presentation Overview
### Objective
[What this presentation aims to achieve]
### Audience
[Who will be attending this presentation]
### Duration
[Expected presentation length]
### Desired Outcomes
[What decisions or actions should result from this presentation]
## Slide Structure
### Slide 1: Title Slide
**Title**: [Presentation title]
**Subtitle**: [Analysis focus or key question addressed]
**Presenter**: [Your name and role]
**Date**: [Presentation date]
**Audience**: [Stakeholder group]
### Slide 2: Agenda
**Presentation Flow**:
1. Executive Summary (5 minutes)
2. Analysis Overview (5 minutes)
3. Key Findings (15 minutes)
4. Recommendations (10 minutes)
5. Next Steps (5 minutes)
6. Q&A (10 minutes)
### Slide 3: Executive Summary
**Key Points**:
- [Most important finding or insight]
- [Primary recommendation]
- [Expected impact or outcome]
- [Required decision or action]
### Slide 4: Analysis Context
**Background**:
- [Why this analysis was conducted]
- [What questions we sought to answer]
- [What methods were used]
**Scope**:
- [What was included in the analysis]
- [What was excluded and why]
- [Time period covered]
### Slides 5-8: Key Findings
**Finding 1**: [Primary insight]
- **Evidence**: [Data or research supporting this finding]
- **Implication**: [What this means for the business/project]
- **Confidence Level**: [How certain we are about this finding]
**Finding 2**: [Secondary insight]
- **Evidence**: [Data or research supporting this finding]
- **Implication**: [What this means for the business/project]
- **Confidence Level**: [How certain we are about this finding]
**Finding 3**: [Additional insight]
- **Evidence**: [Data or research supporting this finding]
- **Implication**: [What this means for the business/project]
- **Confidence Level**: [How certain we are about this finding]
**Finding 4**: [Supporting insight]
- **Evidence**: [Data or research supporting this finding]
- **Implication**: [What this means for the business/project]
- **Confidence Level**: [How certain we are about this finding]
### Slides 9-11: Recommendations
**Recommendation 1**: [Primary recommendation]
- **Rationale**: [Why this recommendation is made]
- **Expected Impact**: [What outcomes this should produce]
- **Implementation Effort**: [High/Medium/Low effort required]
- **Timeline**: [When this should be implemented]
**Recommendation 2**: [Secondary recommendation]
- **Rationale**: [Why this recommendation is made]
- **Expected Impact**: [What outcomes this should produce]
- **Implementation Effort**: [High/Medium/Low effort required]
- **Timeline**: [When this should be implemented]
**Recommendation 3**: [Additional recommendation]
- **Rationale**: [Why this recommendation is made]
- **Expected Impact**: [What outcomes this should produce]
- **Implementation Effort**: [High/Medium/Low effort required]
- **Timeline**: [When this should be implemented]
### Slide 12: Implementation Roadmap
**Phase 1** (Immediate - Next 30 days):
- [Action item 1]
- [Action item 2]
**Phase 2** (Short-term - Next 90 days):
- [Action item 1]
- [Action item 2]
**Phase 3** (Long-term - Next 6-12 months):
- [Action item 1]
- [Action item 2]
### Slide 13: Resource Requirements
**Personnel**:
- [Team members or roles needed]
- [Estimated time commitment]
**Budget**:
- [Financial resources required]
- [Cost-benefit analysis summary]
**Technology/Tools**:
- [Systems or tools needed]
- [Infrastructure requirements]
### Slide 14: Success Metrics
**Key Performance Indicators**:
- [Metric 1]: [Current state] → [Target state]
- [Metric 2]: [Current state] → [Target state]
- [Metric 3]: [Current state] → [Target state]
**Measurement Plan**:
- [How success will be measured]
- [When measurements will be taken]
- [Who is responsible for tracking]
### Slide 15: Risks and Mitigation
**High-Priority Risks**:
- **Risk**: [Description of risk]
- **Probability**: [High/Medium/Low]
- **Impact**: [High/Medium/Low]
- **Mitigation**: [How to address this risk]
**Medium-Priority Risks**:
- **Risk**: [Description of risk]
- **Probability**: [High/Medium/Low]
- **Impact**: [High/Medium/Low]
- **Mitigation**: [How to address this risk]
### Slide 16: Next Steps
**Immediate Actions** (Next 2 weeks):
1. [Action item with owner]
2. [Action item with owner]
3. [Action item with owner]
**Decision Points**:
- [Decision needed and by when]
- [Who needs to make the decision]
- [Information needed for decision]
**Follow-up**:
- [Next meeting or checkpoint]
- [Additional analysis needed]
- [Progress reporting plan]
### Slide 17: Questions & Discussion
**Discussion Topics**:
- [Key topic for stakeholder input]
- [Area where feedback is needed]
- [Decision that requires stakeholder alignment]
**Contact Information**:
- [Your contact information for follow-up]
- [Team member contacts if relevant]
## Presentation Notes
### Key Messages to Emphasize
1. [Most important point to communicate]
2. [Second most important point]
3. [Third most important point]
### Potential Questions and Responses
**Q**: [Likely question from stakeholders]
**A**: [Prepared response]
**Q**: [Another likely question]
**A**: [Prepared response]
**Q**: [Potential challenging question]
**A**: [Thoughtful response addressing concerns]
### Backup Slides
**Additional Detail on Finding 1**:
[More detailed analysis for deeper questions]
**Methodology Details**:
[Detailed explanation of analysis methods]
**Data Sources**:
[Complete list of information sources used]
## Follow-up Actions
### Post-Presentation Tasks
1. [Send presentation materials to attendees]
2. [Document decisions made during presentation]
3. [Schedule follow-up meetings as needed]
4. [Begin implementation of approved recommendations]
### Communication Plan
- [How decisions will be communicated to broader team]
- [Timeline for implementation updates]
- [Process for ongoing stakeholder engagement]
---
**Presentation Date**: [Date]
**Presenter**: [Name]
**Review Status**: [Draft/Final/Approved]
5.2 Research Summary Template
Purpose: Communicate research findings concisely Usage: Research Mode - Findings communication
# Research Summary: [Research Topic]
## Research Overview
### Research Question
[Primary question this research addressed]
### Methodology
[Brief description of research approach and methods used]
### Timeline
[When research was conducted]
### Scope
[What was included/excluded in the research]
## Executive Summary
[2-3 paragraph summary of key findings, implications, and recommendations]
## Key Findings
### Finding 1: [Primary Finding]
**Summary**: [Brief description of the finding]
**Evidence**: [Key data points or research evidence]
**Confidence Level**: [High/Medium/Low and why]
**Implications**: [What this means for the business/project]
### Finding 2: [Secondary Finding]
**Summary**: [Brief description of the finding]
**Evidence**: [Key data points or research evidence]
**Confidence Level**: [High/Medium/Low and why]
**Implications**: [What this means for the business/project]
### Finding 3: [Additional Finding]
**Summary**: [Brief description of the finding]
**Evidence**: [Key data points or research evidence]
**Confidence Level**: [High/Medium/Low and why]
**Implications**: [What this means for the business/project]
## Research Insights
### Patterns and Themes
- [Key pattern or theme identified]
- [Key pattern or theme identified]
- [Key pattern or theme identified]
### Unexpected Discoveries
- [Surprising finding that wasn't anticipated]
- [Surprising finding that wasn't anticipated]
### Validation of Assumptions
**Confirmed Assumptions**:
- [Assumption that was validated by research]
- [Assumption that was validated by research]
**Challenged Assumptions**:
- [Assumption that was contradicted by research]
- [Assumption that was contradicted by research]
## Recommendations
### Immediate Actions (Next 30 days)
1. **[Recommendation 1]**
- **Rationale**: [Why this is recommended]
- **Expected Impact**: [What outcome is expected]
- **Owner**: [Who should take this action]
2. **[Recommendation 2]**
- **Rationale**: [Why this is recommended]
- **Expected Impact**: [What outcome is expected]
- **Owner**: [Who should take this action]
### Strategic Actions (Next 3-6 months)
1. **[Strategic Recommendation 1]**
- **Rationale**: [Why this is recommended]
- **Expected Impact**: [What outcome is expected]
- **Resources Needed**: [What resources are required]
2. **[Strategic Recommendation 2]**
- **Rationale**: [Why this is recommended]
- **Expected Impact**: [What outcome is expected]
- **Resources Needed**: [What resources are required]
## Research Limitations
### Scope Limitations
- [What was not covered in this research]
- [Why certain areas were excluded]
### Methodological Limitations
- [Limitations of the research methods used]
- [How these limitations might affect findings]
### Data Limitations
- [Limitations in available data]
- [How data quality might affect conclusions]
## Future Research Needs
### Priority Research Areas
1. **[Research Area 1]**
- **Why Important**: [Why this research is needed]
- **Suggested Approach**: [How this research should be conducted]
- **Timeline**: [When this research should be done]
2. **[Research Area 2]**
- **Why Important**: [Why this research is needed]
- **Suggested Approach**: [How this research should be conducted]
- **Timeline**: [When this research should be done]
### Ongoing Monitoring
- [What should be monitored on an ongoing basis]
- [How monitoring should be conducted]
- [Who should be responsible for monitoring]
## Supporting Information
### Data Sources
**Primary Sources**:
- [Source 1 with brief description]
- [Source 2 with brief description]
**Secondary Sources**:
- [Source 1 with brief description]
- [Source 2 with brief description]
### Research Team
- **Lead Researcher**: [Name and role]
- **Supporting Researchers**: [Names and roles]
- **Subject Matter Experts**: [Names and expertise areas]
### Validation Process
- [How findings were validated]
- [Who reviewed the research]
- [What validation methods were used]
## Appendices
### Appendix A: Detailed Methodology
[Detailed description of research methods, sample sizes, data collection procedures]
### Appendix B: Raw Data Summary
[Summary of key data points, statistical analyses, survey results]
### Appendix C: Interview Insights
[Key quotes and insights from interviews or focus groups]
### Appendix D: Competitive Analysis Data
[Detailed competitive analysis findings, feature comparisons, market positioning data]
---
**Research Completed**: [Date]
**Report Author**: [Business Analyst Name]
**Next Review**: [Date for follow-up or update]
6. Quality Assurance Templates
6.1 Analysis Quality Checklist
Purpose: Ensure analysis meets quality standards Usage: All Modes - Quality validation
# Analysis Quality Checklist: [Analysis Name]
## Pre-Analysis Quality Checks
### Objective Clarity
- [ ] Analysis objectives are clearly defined and measurable
- [ ] Success criteria are established and agreed upon
- [ ] Scope is well-defined with clear inclusions and exclusions
- [ ] Stakeholder expectations are documented and aligned
### Methodology Selection
- [ ] Analysis methodology is appropriate for the objectives
- [ ] Methods are scientifically sound and validated
- [ ] Potential biases have been identified and addressed
- [ ] Sample sizes and selection criteria are appropriate
### Resource Preparation
- [ ] Required data sources have been identified and accessed
- [ ] Analysis tools and technologies are available and functional
- [ ] Team members have appropriate skills and training
- [ ] Timeline is realistic and achievable
## During Analysis Quality Checks
### Data Quality
- [ ] Data sources are credible and current
- [ ] Data completeness meets minimum requirements
- [ ] Data accuracy has been validated
- [ ] Data consistency across sources has been verified
- [ ] Missing data has been identified and addressed
### Analysis Rigor
- [ ] Analysis follows established methodology consistently
- [ ] Multiple perspectives and sources are considered
- [ ] Assumptions are documented and tested where possible
- [ ] Alternative explanations are explored
- [ ] Findings are cross-validated using multiple methods
### Documentation Standards
- [ ] Analysis steps are clearly documented
- [ ] Data sources and methods are properly cited
- [ ] Interim findings are recorded with supporting evidence
- [ ] Decision points and rationale are documented
- [ ] Version control is maintained for all documents
## Post-Analysis Quality Checks
### Findings Validation
- [ ] Findings are supported by sufficient evidence
- [ ] Conclusions logically follow from the analysis
- [ ] Confidence levels are appropriately assigned
- [ ] Limitations and caveats are clearly stated
- [ ] Findings have been peer-reviewed
### Recommendation Quality
- [ ] Recommendations directly address the analysis objectives
- [ ] Recommendations are specific and actionable
- [ ] Implementation feasibility has been considered
- [ ] Expected impacts are realistic and measurable
- [ ] Risks and mitigation strategies are identified
### Communication Effectiveness
- [ ] Key messages are clear and compelling
- [ ] Technical content is appropriate for the audience
- [ ] Visual aids enhance understanding
- [ ] Executive summary captures essential points
- [ ] Next steps are clearly defined
## Stakeholder Validation
### Internal Review
- [ ] Analysis has been reviewed by subject matter experts
- [ ] Methodology has been validated by peers
- [ ] Findings have been discussed with analysis team
- [ ] Recommendations have been assessed for feasibility
- [ ] Documentation meets organizational standards
### Stakeholder Feedback
- [ ] Key stakeholders have reviewed findings
- [ ] Stakeholder concerns have been addressed
- [ ] Recommendations align with stakeholder needs
- [ ] Implementation approach is acceptable to stakeholders
- [ ] Success metrics are agreed upon
### Final Validation
- [ ] All quality criteria have been met
- [ ] Outstanding issues have been resolved
- [ ] Final approval has been obtained
- [ ] Handoff documentation is complete
- [ ] Follow-up plan is established
## Quality Metrics
### Analysis Quality Score
**Methodology Rigor**: [Score 1-10] - [Comments]
**Data Quality**: [Score 1-10] - [Comments]
**Finding Validity**: [Score 1-10] - [Comments]
**Recommendation Actionability**: [Score 1-10] - [Comments]
**Communication Clarity**: [Score 1-10] - [Comments]
**Overall Quality Score**: [Average score] - [Overall assessment]
### Improvement Areas
- [Area for improvement 1]
- [Area for improvement 2]
- [Area for improvement 3]
### Lessons Learned
- [Key lesson learned 1]
- [Key lesson learned 2]
- [Key lesson learned 3]
---
**Quality Review Date**: [Date]
**Reviewed By**: [Name and role]
**Quality Status**: [Pass/Conditional Pass/Fail]
**Next Review**: [Date if applicable]
6.2 Deliverable Review Template
Purpose: Systematic review of analysis deliverables Usage: All Modes - Final quality assurance
# Deliverable Review: [Deliverable Name]
## Review Overview
### Deliverable Information
**Deliverable Type**: [Research Report/Project Brief/Analysis Summary/etc.]
**Created By**: [Business Analyst name]
**Creation Date**: [Date]
**Review Date**: [Date]
**Reviewer**: [Reviewer name and role]
### Review Scope
**Review Objectives**: [What this review aims to achieve]
**Review Criteria**: [Standards against which deliverable is evaluated]
**Review Method**: [How the review was conducted]
## Content Review
### Structure and Organization
- [ ] Document follows appropriate template structure
- [ ] Information is logically organized and flows well
- [ ] Sections are complete and address all required elements
- [ ] Table of contents is accurate and helpful
- [ ] Executive summary effectively captures key points
**Comments**: [Specific feedback on structure and organization]
### Content Quality
- [ ] Information is accurate and up-to-date
- [ ] Analysis is thorough and comprehensive
- [ ] Findings are well-supported by evidence
- [ ] Recommendations are specific and actionable
- [ ] Conclusions logically follow from analysis
**Comments**: [Specific feedback on content quality]
### Clarity and Communication
- [ ] Writing is clear and easy to understand
- [ ] Technical terms are defined appropriately
- [ ] Audience needs are addressed effectively
- [ ] Key messages are prominent and compelling
- [ ] Visual aids enhance understanding
**Comments**: [Specific feedback on clarity and communication]
## Technical Review
### Methodology Assessment
- [ ] Analysis methodology is appropriate and sound
- [ ] Data sources are credible and sufficient
- [ ] Analysis techniques are correctly applied
- [ ] Limitations and assumptions are clearly stated
- [ ] Bias mitigation strategies are employed
**Comments**: [Specific feedback on methodology]
### Data and Evidence Review
- [ ] Data quality meets acceptable standards
- [ ] Evidence supports conclusions drawn
- [ ] Sources are properly cited and referenced
- [ ] Quantitative analysis is mathematically correct
- [ ] Qualitative analysis follows established frameworks
**Comments**: [Specific feedback on data and evidence]
### Validation and Verification
- [ ] Findings have been cross-validated where possible
- [ ] Alternative explanations have been considered
- [ ] Peer review has been conducted
- [ ] Stakeholder input has been incorporated
- [ ] Quality assurance processes have been followed
**Comments**: [Specific feedback on validation]
## Stakeholder Alignment Review
### Requirements Compliance
- [ ] Deliverable meets all stated requirements
- [ ] Scope is appropriate and complete
- [ ] Timeline commitments have been met
- [ ] Resource constraints have been respected
- [ ] Success criteria are addressed
**Comments**: [Specific feedback on requirements compliance]
### Stakeholder Needs Assessment
- [ ] Primary stakeholder needs are addressed
- [ ] Secondary stakeholder concerns are considered
- [ ] Decision-making requirements are met
- [ ] Implementation considerations are included
- [ ] Follow-up needs are identified
**Comments**: [Specific feedback on stakeholder alignment]
### Business Value Assessment
- [ ] Business objectives are clearly supported
- [ ] Value proposition is compelling
- [ ] ROI considerations are addressed
- [ ] Risk assessment is comprehensive
- [ ] Strategic alignment is demonstrated
**Comments**: [Specific feedback on business value]
## Detailed Feedback
### Strengths
1. **[Strength 1]**: [Detailed description of what was done well]
2. **[Strength 2]**: [Detailed description of what was done well]
3. **[Strength 3]**: [Detailed description of what was done well]
### Areas for Improvement
1. **[Improvement Area 1]**:
- **Issue**: [Description of the issue]
- **Impact**: [How this affects deliverable quality]
- **Recommendation**: [Specific suggestion for improvement]
- **Priority**: [High/Medium/Low]
2. **[Improvement Area 2]**:
- **Issue**: [Description of the issue]
- **Impact**: [How this affects deliverable quality]
- **Recommendation**: [Specific suggestion for improvement]
- **Priority**: [High/Medium/Low]
3. **[Improvement Area 3]**:
- **Issue**: [Description of the issue]
- **Impact**: [How this affects deliverable quality]
- **Recommendation**: [Specific suggestion for improvement]
- **Priority**: [High/Medium/Low]
### Critical Issues
**Issue 1**: [Description of critical issue requiring immediate attention]
- **Impact**: [Serious consequences if not addressed]
- **Required Action**: [What must be done to resolve]
- **Timeline**: [When this must be completed]
## Review Recommendations
### Approval Status
- [ ] **Approved**: Deliverable meets all quality standards and requirements
- [ ] **Approved with Minor Revisions**: Deliverable is acceptable with small changes
- [ ] **Conditional Approval**: Deliverable requires specific improvements before final approval
- [ ] **Requires Major Revision**: Deliverable needs significant improvements before resubmission
- [ ] **Not Approved**: Deliverable does not meet minimum standards
### Required Actions
**High Priority Actions** (Must complete before approval):
1. [Action item with specific requirements]
2. [Action item with specific requirements]
**Medium Priority Actions** (Should complete for quality improvement):
1. [Action item with specific requirements]
2. [Action item with specific requirements]
**Low Priority Actions** (Could complete for enhancement):
1. [Action item with specific requirements]
2. [Action item with specific requirements]
### Follow-up Requirements
- **Revision Timeline**: [When revisions should be completed]
- **Re-review Process**: [How revised deliverable will be reviewed]
- **Final Approval Authority**: [Who provides final approval]
- **Distribution Plan**: [How approved deliverable will be shared]
## Quality Metrics
### Quantitative Assessment
| Quality Dimension | Score (1-10) | Weight | Weighted Score |
|------------------|--------------|---------|----------------|
| Content Accuracy | [Score] | 25% | [Weighted Score] |
| Methodology Rigor | [Score] | 20% | [Weighted Score] |
| Communication Clarity | [Score] | 20% | [Weighted Score] |
| Stakeholder Alignment | [Score] | 15% | [Weighted Score] |
| Actionability | [Score] | 10% | [Weighted Score] |
| Completeness | [Score] | 10% | [Weighted Score] |
| **Total Quality Score** | | **100%** | **[Total Score]** |
### Qualitative Assessment
**Overall Quality Rating**: [Excellent/Good/Satisfactory/Needs Improvement/Poor]
**Key Quality Indicators**:
- [Most significant quality strength]
- [Most important quality concern]
- [Overall quality trajectory]
## Lessons Learned
### Process Improvements
- [Improvement to analysis process]
- [Improvement to review process]
- [Improvement to communication process]
### Template Enhancements
- [Suggested template improvement]
- [Suggested template improvement]
### Best Practices Identified
- [Best practice to replicate]
- [Best practice to replicate]
---
**Review Completed By**: [Reviewer name and signature]
**Review Date**: [Date]
**Next Review**: [Date if applicable]
**Distribution**: [Who receives this review]
Template Selection Matrix
Quick Reference Guide
| Analysis Type | Primary Template | Supporting Templates | Quality Templates |
|---|---|---|---|
| Market Research | Research Brief | Competitive Analysis, Research Summary | Analysis Quality Checklist |
| User Research | User Research Plan | Research Summary, Stakeholder Presentation | Deliverable Review |
| Problem Analysis | Root Cause Analysis | SWOT Analysis, Project Brief | Analysis Quality Checklist |
| Strategic Planning | SWOT Analysis | Research Brief, Stakeholder Presentation | Deliverable Review |
| Project Initiation | Project Brief | Requirements Specification, Stakeholder Presentation | Analysis Quality Checklist |
| Ideation Sessions | Ideation Session | SCAMPER Analysis, Research Summary | Deliverable Review |
Template Customization Guidelines
When to Customize Templates
- Industry-Specific Requirements: Adapt templates for specific industry regulations or standards
- Organizational Standards: Modify templates to match company documentation standards
- Project Complexity: Scale templates up or down based on project size and complexity
- Stakeholder Preferences: Adjust format and detail level for specific stakeholder groups
Customization Best Practices
- Maintain Core Structure: Keep essential sections while adapting details
- Preserve Quality Standards: Ensure customizations don't compromise quality requirements
- Document Changes: Track template modifications for consistency and improvement
- Validate Effectiveness: Test customized templates and gather feedback for refinement
Template Maintenance
- Regular Review: Update templates quarterly based on usage feedback
- Version Control: Maintain clear versioning for all template modifications
- Training Updates: Ensure team training reflects current template versions
- Quality Monitoring: Track template effectiveness through deliverable quality metrics
Template Guide Version: 1.0 Last Updated: [Date] Next Review: [Date] Maintained By: Business Analyst Team