# workflows/feedback_integration.md — Closing the Developer Feedback Loop

## Purpose

This workflow ensures that every high-signal piece of developer feedback is captured, triaged, acted upon where appropriate, and — most importantly — the original developer sees the impact of their voice.

## Step-by-Step Process

**1. Capture (T+0)**
- Record in the shared “Voice of the Developer” Notion + Linear project with: verbatim quote, developer handle, date, product area, severity/frequency signal, and initial JTBD framing.
- Tag with one of: DX Friction, Missing Capability, Documentation Gap, DX Delight (positive signal), Strategic Insight.

**2. Rapid Internal Distribution (T+24h)**
- Post a concise, anonymized summary in the #dev-voice Slack channel with link to full context.
- Tag relevant engineering and product owners automatically via Linear integration.
- For top 10% signals (frequent + painful + strategic), schedule a 20-minute live review with the relevant squad within 5 business days.

**3. Acknowledgment to Developer (T+48h max)**
- Public or private reply: “Thank you — this is exactly the kind of signal we need. I’ve logged it and the retrieval squad is looking at it this week. I’ll keep you updated here.”
- This step is non-negotiable for trust.

**4. Decision & Action**
- Options: quick win (ship in <2 weeks), planned (roadmap), needs research (design partner program), or conscious non-prioritization with explanation.
- Update the original Linear ticket and the public thread with the decision and reasoning.

**5. Close the Loop (The Most Important Step)**
- When the improvement ships (or a decision is made), return to the original developer first: “Your feedback on the 200k context retrieval cliff directly led to the hybrid reranker we just shipped. Here’s the before/after data and the PR. Would love to hear how it behaves on your corpus.”
- Publicly credit the developer (with permission) in release notes, blog posts, or Discord.
- Ask for a follow-up quote or 5-minute call to validate the improvement — this turns reporters into champions.

## Instrumentation & Reporting

- Weekly “Developer Signal Report” to exec team (max 2 pages): top 5 frictions, top 5 delights, % of roadmap items with direct developer origin, and closed-loop statistics (what % of feedback received a visible response or change).
- Quarterly review of feedback-to-roadmap conversion rate and developer satisfaction with the process itself.

This workflow is how Astra turns individual complaints into durable competitive advantage and turns developers into lifelong advocates.