Nw Stakeholder EngagementSAFE

AI agents that guide you from idea to working code, with you in control at every step.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: nw-stakeholder-engagement
description: Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.
user-invocable: false
disable-model-invocation: true
---

# Stakeholder Engagement

## Demonstration Preparation

### Audience Analysis

Tailor presentation content and depth to audience type:

| Audience | Focus | Style | Success Criteria |
|----------|-------|-------|-----------------|
| Executive | Business value, ROI, strategic alignment | High-level outcomes, success metrics, roadmap | Business objective achievement, ROI demonstration |
| Business | Functional capability, process improvement, UX | Feature walkthrough, workflow demo, benefit realization | Requirement satisfaction, process efficiency |
| Technical | Implementation quality, architecture, ops readiness | Technical deep-dive, architecture review, operational metrics | Technical excellence, operational readiness |

### Demonstration Script Development
Structure as problem-solution narratives:
1. **Before state**: current pain point with quantitative evidence
2. **Feature walkthrough**: end-to-end workflow with realistic data
3. **After state**: measurable improvement with before/after comparison
4. **Business impact**: translate technical metrics to business outcomes

### Preparation Checklist
- [ ] Demo environment set up with realistic data
- [ ] Backup plan for demo failures (screenshots, recorded fallback)
- [ ] Stakeholder briefing sent with agenda and expectations
- [ ] Interactive participation points identified
- [ ] Time budget allocated per section

## Feedback Collection

### Structured Feedback Process
1. Real-time feedback during demonstration (capture questions and concerns)
2. Post-demonstration survey with structured questions
3. Follow-up interviews for deeper insights (optional, for major features)

### Feedback Categories
- **Functional**: does the feature meet requirements?
- **Usability**: is the user experience intuitive?
- **Performance**: does speed/responsiveness meet expectations?
- **Priority**: what enhancements should come next?

### Feedback Action Workflow
1. Categorize feedback items
2. Prioritize by business impact
3. Assign ownership for each action item
4. Communicate response plan with timelines
5. Track resolution to completion

## Business Outcome Measurement

### Quantitative Metrics

| Category | Metrics |
|----------|---------|
| Performance | Response time improvement | throughput gains | error rate reduction |
| Business | Revenue impact | cost reduction | user adoption rate | conversion changes |
| Operational | Deployment frequency | MTTR | support ticket reduction | availability |

### Qualitative Assessments
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.

### Success Validation Process
1. **Baseline**: collect pre-implementation measurements
2. **Monitor**: track metrics post-deployment (minimum 2 weeks)
3. **Validate**: compare against success thresholds with statistical rigor
4. **Report**: present results framed in business value terms
5. **Iterate**: identify continuous improvement opportunities

## Retrospective and Lessons Learned

### Delivery Effectiveness Assessment
Feature delivery timeline vs plan | Quality gate effectiveness (false positives/negatives) | Stakeholder satisfaction scores | Implementation quality metrics.

### Knowledge Capture
Successful practices to replicate | Challenges encountered and resolution strategies | Process improvements identified | Tool/technology effectiveness observations.

### Integration into Future Iterations
Update process templates and checklists | Share learnings across teams | Adjust estimation models based on actuals | Feed enhancement requests into backlog.

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.