Focus Group & Feedback Integration Plan (RFQ Stage 5)
Version: 1.0Status: Draft
Date: 2025-10-10
Estimated Reading Time: 30-40 minutes
Table of Contents
- Introduction
- Focus Group Facilitation Plan
- Participant Selection Criteria
- Feedback Collection Mechanisms
- Feedback Integration Process
- Success Metrics
- Timeline for Stage 5 Activities
- Stakeholder Communication Plan
- Documentation Update Procedures
- Appendices
1. Introduction
1.1 Purpose
This Focus Group & Feedback Integration Plan outlines the approach for conducting focus groups with pilot NGOs (RFQ Stage 5) and incorporating feedback into the final deliverables of the NGO SRM ROI Calculator. Objective: Conduct ≥3 NGO focus groups within a 4-week window to validate calculator usability, gather actionable feedback, and integrate improvements into the Methods Note, Data Schema, Pilot Pack, and calculator implementation.1.2 Scope
This plan covers:- Focus group facilitation: Agendas, participant selection, logistics
- Feedback collection: Surveys, interviews, observation protocols, usage analytics
- Feedback integration: Categorization, prioritization, and incorporation into deliverables
- Timeline: 4-week window for focus groups + 2-week integration period
- Stakeholder communication: How findings will be shared with GISF, NGOs, and development team
1.3 Alignment with RFQ Requirements
RFQ Stage 5: Focus Group & Feedback Integration Requirements:- Conduct ≥3 NGO focus groups
- Mix of roles: security managers, finance staff, field operations coordinators
- Structured feedback collection mechanisms (surveys, interviews, analytics)
- Documented feedback integration process
- Timeline for activities within 4-week window
- Stakeholder communication plan
2. Focus Group Facilitation Plan
2.1 Focus Group Structure
Format: 2-hour virtual or in-person facilitated session with 5-10 NGO participants per group Objectives:- Validate calculator usability (can participants complete core ROI workflow independently?)
- Assess documentation clarity (Methods Note, Data Schema, Pilot Pack)
- Identify pain points, confusing terminology, and workflow barriers
- Gather feature requests and enhancement ideas
- Collect qualitative insights on calculator value and relevance
2.2 Focus Group Agenda (2 Hours)
| Time | Activity | Duration | Facilitator Actions | Participant Actions |
|---|---|---|---|---|
| 00:00-00:10 | Welcome & Introductions | 10 min | Introduce purpose, outline agenda, set expectations | Introduce themselves, share role and organization |
| 00:10-00:25 | Calculator Demo | 15 min | Walk through 8-step workflow with Baseline scenario | Observe demo, ask clarifying questions |
| 00:25-00:55 | Hands-On Exercise | 30 min | Guide participants through entering their own data (or using Low-Risk scenario) | Input data, navigate workflow, run calculation |
| 00:55-01:15 | Structured Discussion | 20 min | Facilitate discussion using Discussion Guide (Appendix A) | Share experiences, pain points, suggestions |
| 01:15-01:30 | Documentation Review | 15 min | Present Methods Note, Data Schema, Pilot Pack; ask targeted questions | Review excerpts, provide feedback on clarity |
| 01:30-01:50 | Feature Prioritization | 20 min | Present P2 roadmap (scenario modeling); gather priorities | Rank features by importance, suggest enhancements |
| 01:50-02:00 | Wrap-Up & Next Steps | 10 min | Summarize key feedback, explain integration process, distribute post-session survey | Complete post-session survey, provide contact for follow-up interviews |
2.3 Facilitator Roles
Lead Facilitator (1):- Guides agenda, manages time, moderates discussion
- Ensures all voices heard, prevents dominant participants from monopolizing
- Documents key feedback, quotes, pain points, feature requests
- Tracks consensus themes and outlier perspectives
- Manages screen sharing, breakout rooms, chat
- Troubleshoots technical issues (login, audio, video)
2.4 Materials Required
- Pre-Session (1 Week Before)
- During Session
- Post-Session (Within 24 Hours)
Pre-Session (1 Week Before):
- Participant invitation email with agenda and pre-work (Appendix B)
- Calculator access credentials (if using shared demo instance)
- Pre-session survey to gather participant background (Appendix C)
3. Participant Selection Criteria
3.1 Target Participant Profile
Roles (Mix Required Per Focus Group):- Security Managers/Focal Points (40%): Primary users responsible for security planning and budgeting
- Finance Staff (30%): Provide cost data, validate NPV/ROI calculations, support donor reporting
- Field Operations Coordinators (20%): Provide incident data, assess qualitative benefits (access, continuity)
- Executive Leadership (10%, optional): Validate strategic relevance and decision-making utility
- Small NGOs (less than 50 staff): 1 per focus group
- Medium NGOs (50-200 staff): 1-2 per focus group
- Large NGOs (>200 staff): 1 per focus group
- Stable Contexts (urban offices, low-risk): 1 per focus group
- Moderate-Risk Contexts (field operations, moderate insecurity): 1-2 per focus group
- High-Risk Contexts (conflict zones, high insecurity): 1 per focus group
3.2 Recruitment Strategy
1
Phase 1: GISF Partner Outreach (Week 1)
Phase 1: GISF Partner Outreach (Week 1)
- GISF sends invitation to member NGOs via mailing list
- Invitation includes purpose, time commitment, and participant criteria
- NGOs self-nominate or nominate staff members
2
Phase 2: Screening & Selection (Week 2)
Phase 2: Screening & Selection (Week 2)
- Review nominations for role mix and geographic diversity
- Confirm availability for 2-hour focus group + 1-hour follow-up
- Send pre-session survey to gather background data
3
Phase 3: Confirmation & Scheduling (Week 3)
Phase 3: Confirmation & Scheduling (Week 3)
- Confirm final participant list (5-10 per group)
- Schedule 3 focus group sessions (spread across 2-week window)
- Send calendar invitations with Zoom/Teams links
3.3 Incentives & Commitments
Participant Commitments:- Attend 2-hour focus group session
- Complete pre-session and post-session surveys (15 min each)
- Optional: Participate in 1-hour follow-up interview
- Early access to calculator and documentation
- Recognition in final report as pilot contributors
- Certificate of participation for professional development
4. Feedback Collection Mechanisms
4.1 Pre-Session Survey
4.1 Pre-Session Survey
4.1 Pre-Session Survey
Purpose: Gather participant background and pre-existing perceptionsQuestions (5-10 minutes):- What is your role in your organization?
- How familiar are you with ROI calculations? (1=Not familiar, 5=Very familiar)
- What challenges do you face in justifying security investments?
- What would make a security ROI calculator most useful for your work?
- Have you used similar tools before? If so, which ones?
4.2 Post-Session Survey
4.2 Post-Session Survey
4.2 Post-Session Survey
Purpose: Capture structured feedback on calculator usability and documentation clarityQuestions (10-15 minutes):Usability (5-point Likert scale: Strongly Disagree to Strongly Agree):- The calculator workflow (8 steps) was easy to follow.
- The data gathering templates were helpful for preparing my inputs.
- The validation messages helped me correct errors.
- I understand how ROI, EAL, NPV, and Payback Period are calculated.
- The results are credible and useful for my organization.
4.3 Observation Protocol
4.3 Observation Protocol
4.3 Observation Protocol
Purpose: Capture behavioral insights during hands-on exerciseObserver Actions:- Note where participants hesitate, get stuck, or ask for help
- Record common error patterns (e.g., ARO entered as percentage instead of decimal)
- Track time to complete each step (target: core ROI workflow in ≤30 minutes)
- Document instances of terminology confusion or workflow navigation issues
- Participant ID (anonymized)
- Step where participant encountered difficulty
- Error type (data entry, navigation, conceptual misunderstanding)
- Resolution (self-resolved, facilitator assistance, unresolved)
4.4 Follow-Up Interviews (Optional, 1:1)
4.4 Follow-Up Interviews (Optional, 1:1)
4.4 Follow-Up Interviews (Optional, 1:1)
Purpose: Deep-dive into specific feedback themes or use casesTarget Participants: 3-5 participants per focus group (selected based on unique insights or role diversity)Duration: 30-60 minutesTopics:- Detailed walkthrough of participant’s own data and results
- Specific pain points or feature requests
- Comparison to other tools or methodologies used
- Long-term usage intentions and organizational adoption barriers
4.5 Usage Analytics (If Applicable)
4.5 Usage Analytics (If Applicable)
4.5 Usage Analytics (If Applicable)
Purpose: Quantitative data on calculator usage patternsMetrics to Track:- Time spent on each step
- Number of validation errors encountered
- Export format preferences (PDF, Excel, CSV)
- Drop-off points (where users abandon workflow)
5. Feedback Integration Process
1
Feedback Categorization
5.1 Feedback Categorization
Step 1: Aggregate Feedback- Compile survey responses, observation notes, interview transcripts
- Consolidate usage analytics (if available)
| Category | Description | Examples |
|---|---|---|
| Usability | UI/UX issues, workflow clarity, navigation | ”Unclear how to duplicate a scenario”, “Validation errors are confusing” |
| Methodology | Formula questions, edge case handling, calculation transparency | ”Why is payback N/A?”, “How is qualitative value calculated?” |
| Documentation | Template clarity, Methods Note comprehension, Pilot Pack usability | ”Data Schema needs more examples”, “Pilot Pack agenda is too long” |
| Features | Requested enhancements, P2 scenario modeling priorities | ”Need sensitivity sliders”, “Want to export comparison table to Excel” |
| Bugs | Functional errors, incorrect calculations, broken links | ”Calculator crashes on large datasets”, “CSV import fails for UTF-8 files” |
2
Feedback Prioritization
5.2 Feedback Prioritization
Step 3: Prioritize Using MoSCoW Framework| Priority | Definition | Action |
|---|---|---|
| Must Have | Blocks successful pilot completion; critical usability issue | Fix immediately (within 1 week) |
| Should Have | Impacts multiple users; significant workflow improvement | Address in next release (within 4 weeks) |
| Could Have | Quality-of-life improvement; nice-to-have feature | Backlog for future (within 3 months) |
| Won’t Have (Now) | Out of scope; low impact; deferred to future phase | Document for P3 or beyond |
- Impact: How many users affected?
- Frequency: How often does this issue occur?
- Severity: Does it block task completion or just cause inconvenience?
- Effort: How much time required to implement fix?
3
Feedback Integration Actions
5.3 Feedback Integration Actions
Step 4: Assign Feedback to Deliverables| Feedback Category | Target Deliverable | Responsible Party |
|---|---|---|
| Usability issues | Calculator UI (P2 implementation) | Development Team |
| Methodology questions | Methods Note (Section 8: Edge Cases & FAQ) | Documentation Team |
| Template clarity | Pilot Pack (Section 5: Data Gathering Templates) | Documentation Team |
| Schema questions | Data Schema (Section 9: Error Handling & Recovery) | Documentation Team |
| Bugs | Calculator Implementation (src/roi-calculator) | Development Team |
- Incorporate clarifications into Methods Note, Data Schema, Pilot Pack
- Add FAQ items addressing common questions
- Update templates based on user feedback
- Revise example scenarios to reflect real-world use cases
- Create GitHub Issues or task tracker entries for each action item
- Assign owners and deadlines
- Link feedback to issues for traceability
4
Feedback Loop Closure
5.4 Feedback Loop Closure
Step 7: Communicate Updates to Participants- Email all focus group participants summarizing:
- Top feedback themes identified
- Actions taken or planned
- Timeline for implementation
- How their feedback improved the calculator
- Document all changes in release notes (e.g., “v1.1 Release Notes”)
- Highlight feedback-driven improvements
- Provide links to updated documentation
6. Success Metrics
6.1 Focus Group Participation Metrics
| Metric | Target | Actual | Status |
|---|---|---|---|
| Number of Focus Groups | ≥3 | TBD | Pending |
| Total Participants | 15-30 | TBD | Pending |
| Role Mix | 40% security, 30% finance, 20% ops, 10% exec | TBD | Pending |
| Geographic Diversity | ≥2 risk contexts per group | TBD | Pending |
| Participation Rate | ≥80% invited participants attend | TBD | Pending |
| Survey Completion | ≥75% participants complete post-session survey | TBD | Pending |
6.2 Feedback Quality Metrics
| Metric | Target | Actual | Status |
|---|---|---|---|
| Actionable Feedback Items | ≥50 distinct items across all groups | TBD | Pending |
| Must Have Issues Identified | ≥5 critical usability issues | TBD | Pending |
| Feature Requests | ≥10 P2-relevant feature suggestions | TBD | Pending |
| Positive Feedback Ratio | ≥70% participants rate calculator as “useful” or “very useful” | TBD | Pending |
6.3 Integration Effectiveness Metrics
| Metric | Target | Actual | Status |
|---|---|---|---|
| Must Have Fixes | 100% implemented within 1 week | TBD | Pending |
| Should Have Fixes | ≥80% implemented within 4 weeks | TBD | Pending |
| Documentation Updates | All deliverables updated within 2 weeks | TBD | Pending |
| Participant Communication | 100% participants receive feedback summary email | TBD | Pending |
7. Timeline for Stage 5 Activities
7.1 Phase Timeline (6 Weeks Total)
| Phase | Activities | Duration | Responsible |
|---|---|---|---|
| Phase 1: Recruitment | GISF outreach, screening, selection | Weeks 1-2 | GISF + Project Lead |
| Phase 2: Focus Groups | Conduct 3 focus group sessions | Weeks 3-4 | Facilitator Team |
| Phase 3: Analysis | Aggregate feedback, categorize, prioritize | Week 5 | Analysis Team |
| Phase 4: Integration | Update documentation, implement fixes | Week 6 | Documentation + Dev Teams |
7.2 Detailed Schedule (Weeks 1-6)
Week 1: Recruitment Launch
Week 1: Recruitment Launch
Week 1: Recruitment Launch
- Day 1-2: GISF sends invitation to member NGOs
- Day 3-5: NGOs nominate participants
- Day 6-7: Review nominations, screen for criteria
Week 2: Confirmation & Scheduling
Week 2: Confirmation & Scheduling
Week 2: Confirmation & Scheduling
- Day 1-2: Confirm final participant list
- Day 3-4: Schedule 3 focus group sessions (spread across Weeks 3-4)
- Day 5: Send pre-session survey to all participants
- Day 6-7: Send calendar invitations and materials
Week 3: Focus Groups 1-2
Week 3: Focus Groups 1-2
Week 3: Focus Groups 1-2
- Day 1: Focus Group 1 (5-10 participants)
- Day 2: Debrief, compile notes
- Day 4: Focus Group 2 (5-10 participants)
- Day 5: Debrief, compile notes
Week 4: Focus Group 3 & Follow-Up Interviews
Week 4: Focus Group 3 & Follow-Up Interviews
Week 4: Focus Group 3 & Follow-Up Interviews
- Day 1: Focus Group 3 (5-10 participants)
- Day 2: Debrief, compile notes
- Day 3-5: Conduct follow-up interviews (3-5 participants)
Week 5: Feedback Analysis
Week 5: Feedback Analysis
Week 5: Feedback Analysis
- Day 1-2: Aggregate all feedback (surveys, notes, interviews, analytics)
- Day 3-4: Categorize and prioritize using MoSCoW framework
- Day 5: Assign feedback to deliverables and create action items
Week 6: Integration & Communication
Week 6: Integration & Communication
Week 6: Integration & Communication
- Day 1-3: Update Methods Note, Data Schema, Pilot Pack based on feedback
- Day 4: Implement Must Have fixes in calculator
- Day 5: Draft feedback summary email and release notes
- Day 6: Send feedback summary to all participants
- Day 7: Publish updated documentation and release notes
7.3 Contingency Planning
Risk: Insufficient NGO participation (less than 15 participants)- Mitigation: Extend recruitment window by 1 week; offer flexible scheduling; conduct smaller groups (3-5 participants)
- Mitigation: Pre-test Zoom/Teams setup; provide technical support contact; record sessions for later review
- Mitigation: Allocate 2 team members to analysis; use automated categorization tools (e.g., NVivo, Dedoose)
8. Stakeholder Communication Plan
8.1 Stakeholder Groups
| Stakeholder | Interest | Communication Frequency | Channel |
|---|---|---|---|
| GISF Leadership | RFQ fulfillment, pilot success | Weekly during focus groups | Email updates + final report |
| Pilot NGO Participants | Feedback incorporation, calculator access | Post-session + post-integration | Email summaries + access links |
| Development Team | Bug reports, feature requests | Real-time during analysis | GitHub Issues, Slack |
| Documentation Team | Documentation updates | Weekly | Shared document reviews |
| Donor/Funder (if applicable) | Impact, methodology validation | Milestone completion | Formal reports |
8.2 Communication Templates
Template 1: Weekly Update Email (to GISF) Subject: Focus Group Progress Update - Week [X] Body:Status: [On track / Delayed / Ahead of schedule] This Week:Template 2: Feedback Summary Email (to Participants) Subject: Thank You - Your Feedback is Improving the NGO SRM ROI Calculator Body:Next Week:
- Focus Group [N] completed with [X] participants ([roles])
- Key themes emerging: [list 3-5 themes]
- Notable feedback: [1-2 quotes or insights]
Risks/Issues: [None / List any concerns] Action Required: [None / List if GISF assistance needed]
- Focus Group [N+1] scheduled for [date]
- Follow-up interviews with [X] participants
Dear [Participant Name], Thank you for participating in the NGO SRM ROI Calculator focus group on [date]. Your insights were invaluable in helping us improve the tool for the broader NGO community. What We Heard:Template 3: Final Report (to GISF & Stakeholders) Subject: RFQ Stage 5 Complete - Focus Group & Feedback Integration Report Contents:Actions We’re Taking:
- [Top 3-5 feedback themes]
- [Notable feature requests or pain points]
Updated Materials:
- [Must Have fixes implemented]
- [Documentation updates completed]
- [Features added to P2 roadmap]
Next Steps:
- [Links to updated Methods Note, Data Schema, Pilot Pack]
- [Link to release notes]
Thank you again for your time and expertise! Best regards,
- We’ll keep you updated on P2 scenario modeling implementation
- You’ll receive early access to new features as they’re released
[Project Team]
- Executive Summary: Participation metrics, top feedback themes, actions taken
- Methodology: Focus group structure, participant selection, feedback collection
- Findings: Categorized feedback with quotes and examples
- Integration Actions: Documentation updates, bug fixes, feature roadmap
- Success Metrics: Participation, feedback quality, integration effectiveness
- Recommendations: Lessons learned, next steps for P2 implementation
9. Documentation Update Procedures
9.1 Version Control
Semantic Versioning:- Major (X.0): Breaking changes, major methodology updates
- Minor (X.Y): Additive changes, new sections, feedback-driven enhancements
- Patch (X.Y.Z): Clarifications, typo fixes, no substantive changes
- Methods Note v1.0 (initial release) → v1.1 (post-focus group updates)
9.2 Change Tracking
Change Log Format (in each document):| Date | Version | Changes | Author |
|---|---|---|---|
| 2025-10-10 | 1.0 | Initial release | Shayan Seyedi |
9.3 Approval Process
Step 1: Draft Updates- Documentation Team drafts changes based on feedback
- Technical Lead reviews for accuracy
- UX Lead reviews for clarity
- Share updated sections with 2-3 focus group participants for validation
- Confirm updates address their feedback
- Project Lead approves and merges to main branch
- Publish updated documentation on website/repository
- Send feedback summary email to all participants
- Publish release notes
9.4 Archive & Traceability
Archive Original Feedback:- Store survey responses, interview transcripts, observation notes in
/specs/002-close-rfq-driven/focus-groups/ - Anonymize participant identifiers (use P1, P2, P3, etc.)
- Each documentation change references originating feedback (e.g., “Added FAQ item per P7 request”)
- GitHub Issues link to feedback items for traceability
10. Appendices
Appendix A: Discussion Guide
Section 1: Calculator Usability (10 minutes)- What was your first impression of the calculator?
- Which steps in the workflow were easy? Which were confusing?
- Did you encounter any errors? Were error messages helpful?
- How long did it take you to gather your data (or would it take)?
- Were the templates helpful? What would improve them?
- Did you have all the data required, or were there gaps?
- Do the ROI, EAL, NPV, and Payback Period results make sense?
- How would you explain these results to your executive team or donors?
- What additional metrics or breakdowns would be useful?
- Did the Methods Note help you understand the calculations? (Show excerpt)
- Was the Data Schema clear about required fields? (Show excerpt)
- Would the Pilot Pack enable you to run a pilot independently? (Show excerpt)
- What features would make the calculator more useful for your work?
- How important is scenario comparison (baseline vs. intervention)?
- Would sensitivity analysis (testing different assumptions) be valuable?
Appendix B: Participant Invitation Email
Subject: Invitation: NGO SRM ROI Calculator Focus Group Body:Dear [Participant Name], You are invited to participate in a focus group to help us improve the NGO Security Risk Management ROI Calculator, a new tool designed to help NGOs quantify the financial value of security investments. Purpose: Gather feedback on calculator usability, documentation clarity, and feature priorities to ensure the tool meets NGO practitioner needs. Time Commitment:What You’ll Do:
- 2-hour focus group session (virtual via Zoom)
- 15-minute pre-session survey (sent 1 week before)
- 15-minute post-session survey (sent 24 hours after)
- Optional: 1-hour follow-up interview
Benefits:
- Participate in a live demo of the calculator
- Complete a hands-on exercise using sample or your own data
- Share feedback on usability, clarity, and usefulness
Dates: [List 3 available dates/times] RSVP: Please confirm your availability by [date] by replying to this email. Questions? Contact [Project Lead Name] at [email]. We look forward to your participation! Best regards,
- Early access to the calculator and documentation
- Opportunity to shape the tool’s future development
- Recognition in final report as a pilot contributor
[GISF / Project Team]
Appendix C: Pre-Session Survey
[See Section 4.1 for full survey questions]Appendix D: Feature Prioritization Matrix
Instructions: Rank the following P2 features by importance (1=Most important, 5=Least important)| Feature | Ranking | Notes |
|---|---|---|
| Scenario comparison (baseline vs. intervention) | ___ | Side-by-side ROI, EAL, NPV, Payback |
| Sensitivity sliders (ARO, SLE, discount rate, qualitative proxy values) | ___ | Test how assumptions affect ROI |
| Export comparison table to Excel | ___ | For further analysis |
| Pre-loaded example scenarios (Low-Risk, High-Risk, Conflict Zone) | ___ | Quick start with sample data |
| Qualitative mapping toggle (shadow-price vs. parameter-delta) | ___ | Switch between valuation methods |
Appendix E: Post-Session Survey
[See Section 4.2 for full survey questions]Appendix F: Observation Template
| Participant ID | Step | Error Type | Resolution | Time to Resolve |
|---|---|---|---|---|
| P1 | Incidents | ARO entered as percentage (30 instead of 0.30) | Facilitator assistance | 2 min |
| P2 | Costs | Period exceeds time horizon | Self-resolved after validation message | 1 min |
| P3 | Assumptions | Confused about discount rate selection | Facilitator explanation | 3 min |
Appendix G: Follow-Up Interview Guide
Section 1: Deep-Dive on Participant’s Data (20 min)- Walk through participant’s actual incident data
- Discuss ARO/SLE estimation challenges
- Review cost data and categorization
- How do results compare to expectations?
- What surprised you?
- How will you use results in your organization?
- What additional features would be most valuable?
- How would you prioritize P2 scenario modeling features?
- What integrations or exports would be helpful?
- Will you continue using the calculator?
- What barriers to adoption exist in your organization?
- How can we support broader NGO community adoption?
Document Control
Version: 1.0Status: Draft
Date: 2025-10-10
Next Review: Upon completion of focus groups (Week 6) Change Log:
| Date | Version | Changes | Author |
|---|---|---|---|
| 2025-10-10 | 1.0 | Initial release - Focus Group & Feedback Integration Plan for RFQ Stage 5 | Shayan Seyedi |
- ✅ Technical Lead - Feedback integration process validated
- ⏳ Product Owner - RFQ Stage 5 requirements fulfilled (pending review)
- ⏳ GISF Stakeholder - Focus group plan approved for execution (pending review)
End of Focus Group & Feedback Integration Plan For calculation methodologies, see the Methods Note. For data preparation, see the Pilot Pack & Data Readiness Guide.