Developer Advocate

MISSION: Help developers succeed with [product/platform].
         Successful developers → adoption → business growth.

THREE PILLARS:
  1. AWARENESS: Developers know we exist and what we offer
  2. ACTIVATION: Developers have a great first experience
  3. ADVOCACY: Developers recommend us to their peers

FEEDBACK LOOP:
  Community Insights → Product Team → Better Product → Happier Community
  (DevRel is the bridge between external developers and internal teams)

## DevRel Program Plan

### Audience
**Primary**: [e.g., Backend developers building SaaS products]
**Secondary**: [e.g., Platform engineers at mid-market companies]
**Persona needs**:
  - [What problem are they trying to solve?]
  - [What tools do they currently use?]
  - [Where do they spend time online?]
  - [What conferences do they attend?]

### Content Strategy (Awareness)
- **Blog**: 2 technical posts/month (tutorials, deep dives, case studies)
- **Video**: 1 video/month (demos, explainers, live streams)
- **Social**: Daily engagement on Twitter/X, weekly on Reddit/HN
- **Talks**: 1 conference talk/quarter, 2 meetup talks/quarter

### Developer Experience (Activation)
- **Quickstart**: 5-minute getting started guide
- **Documentation**: API reference, tutorials, guides, examples
- **SDKs**: Idiomatic libraries for top 3 languages
- **Sandbox**: Free tier or playground for experimentation

### Community (Advocacy)
- **Discord/Slack**: Community space with active moderation
- **Champions program**: Recognize and reward top contributors
- **Feedback loops**: Regular surveys, feature request voting
- **Events**: Quarterly virtual meetups, annual community conference

AWARENESS (Top of Funnel):
  - Blog posts on industry trends (not product-focused)
  - Conference talks on general technical topics
  - Open source contributions and tools
  - Social media thought leadership
  - Guest posts on popular developer blogs

CONSIDERATION (Mid-Funnel):
  - Comparison guides ("X vs Y for [use case]")
  - Tutorial series showing problem-solving with your tool
  - Case studies from real users
  - Webinars with live Q&A
  - Integration guides with popular tools

ACTIVATION (Bottom of Funnel):
  - Quick start guides (< 5 minutes to first success)
  - Comprehensive documentation
  - Code samples and starter templates
  - Migration guides from competitors
  - Video walkthroughs of key features

RETENTION (Post-Adoption):
  - Advanced tutorials and best practices
  - Performance optimization guides
  - Changelog and upgrade guides
  - Community showcases and spotlights
  - Office hours and support channels

## Blog Post: [Title]

### Target reader
[Who is this for? What do they already know?]

### Goal
[What should the reader be able to DO after reading this?]

### Outline
1. **Hook** (1-2 paragraphs)
   Start with a relatable problem or surprising fact.
   NOT: "Today we are excited to announce..."
   YES: "If you have ever waited 30 seconds for a test suite to run..."

2. **Context** (2-3 paragraphs)
   Why does this matter? What is the current state of things?

3. **Solution walkthrough** (bulk of the post)
   - Step-by-step with code examples
   - Every code block should be copy-pasteable and runnable
   - Explain the WHY, not just the HOW
   - Include expected output after each step

4. **Results** (1-2 paragraphs)
   Show the before/after. Metrics if possible.

5. **Next steps** (1 paragraph)
   Where to go from here. Link to docs, related posts, community.

### Writing rules
- Every code example must work if copy-pasted
- Explain jargon the first time you use it
- Use "you" and "we", not "the user" or "one"
- Include the full code at the end (or link to repo)
- Test every tutorial on a clean environment before publishing

VIDEO TYPES:

SHORT (2-5 min): Quick tips, feature demos, "did you know"
  Platform: YouTube Shorts, Twitter, TikTok
  Production: Screen recording + voiceover, minimal editing
  Cadence: 2-4 per month

MEDIUM (10-20 min): Tutorials, deep dives, integration guides
  Platform: YouTube, blog embed
  Production: Screen recording + face cam, light editing
  Cadence: 2 per month

LONG (30-60 min): Live coding, workshops, conference talks
  Platform: YouTube, Twitch
  Production: Live stream with post-production cleanup
  Cadence: 1 per month

LIVE STREAMS: Community coding, Q&A, office hours
  Platform: YouTube Live, Twitch, Discord Stage
  Production: Minimal -- authenticity over polish
  Cadence: Weekly or biweekly

DISCORD:
  Best for: Real-time chat, gaming/OSS communities, async support
  Pros: Free, rich features, bot ecosystem, voice channels
  Cons: Not great for long-form discussions, hard to search

SLACK:
  Best for: Enterprise, professional communities
  Pros: Familiar to developers, threaded conversations
  Cons: Expensive at scale, 90-day message limit on free tier

GITHUB DISCUSSIONS:
  Best for: Open source projects, technical Q&A
  Pros: Integrated with code, searchable, free
  Cons: Lower engagement than chat, slower pace

DISCOURSE:
  Best for: Long-form Q&A, knowledge base building
  Pros: Great search, topic organization, moderation tools
  Cons: Less real-time, requires hosting

RECOMMENDATION:
  OSS project: GitHub Discussions + Discord
  SaaS product: Discord (community) + dedicated support channel
  Enterprise: Slack community or private Discourse

GROWTH:
  - New members per month
  - Active members (posted in last 30 days) / total members
  - Member retention (% still active after 90 days)

ENGAGEMENT:
  - Messages per day / per week
  - Questions asked and answered
  - Average response time to questions
  - Ratio of questions answered by community vs staff

QUALITY:
  - Helpful content created (guides, solutions)
  - Community-generated tutorials or blog posts
  - Bug reports that led to fixes
  - Feature requests that were implemented

HEALTH RATIOS:
  - Lurker ratio: < 90% lurkers is healthy
  - Staff ratio: Staff should be < 20% of active posters
  - Answer ratio: > 80% of questions should get an answer
  - Sentiment: Track via periodic surveys

## Champions Program Design

### What Champions Get
- Early access to new features and betas
- Direct line to product team (private channel)
- Free conference tickets or travel sponsorship
- Exclusive swag and recognition
- Co-authoring opportunities on official content
- Speaking opportunity at company events

### What Champions Do
- Answer community questions (3-5 per week)
- Create content (1 blog post or video per month)
- Provide product feedback and beta testing
- Speak at meetups about their experience
- Mentor new community members

### Selection Criteria
- Active in community for 3+ months
- Demonstrated technical depth
- Helpful and respectful communication style
- Passion for helping others succeed
- Not required: big following or influencer status

### Program Structure
- Cohort of 10-20 champions (rotate annually)
- Monthly virtual meetup with product team
- Quarterly in-person event (if budget allows)
- Dedicated Slack/Discord channel
- Annual review and re-nomination

## Developer Experience Audit

### First Contact (0-5 minutes)
[ ] Can a developer understand what the product does in 30 seconds?
[ ] Is the value proposition clear on the homepage?
[ ] Is the pricing/free tier immediately visible?
[ ] Can they sign up without a credit card?

### Getting Started (5-30 minutes)
[ ] Is there a quickstart guide on the first page after signup?
[ ] Can they get a "Hello World" working in under 5 minutes?
[ ] Are code examples copy-pasteable and correct?
[ ] Is the quickstart available in their preferred language?
[ ] Do error messages point to solutions?

### Building (30 min - 1 day)
[ ] Is the API reference complete and accurate?
[ ] Are there tutorials for common use cases?
[ ] Is there a working example app they can fork?
[ ] Can they find answers through search (docs, community, Stack Overflow)?
[ ] Is the SDK idiomatic for their language?

### Going to Production (1 day - 1 week)
[ ] Is there a migration/upgrade guide?
[ ] Are there best practices for production use?
[ ] Is monitoring and debugging well-documented?
[ ] Is there a clear support path for production issues?
[ ] Is the SLA and status page accessible?

### Staying (Ongoing)
[ ] Are changelogs clear and timely?
[ ] Are breaking changes communicated well in advance?
[ ] Is there a community for peer support?
[ ] Are feature requests tracked and visible?
[ ] Does the developer feel heard?

MEASURE AND OPTIMIZE:

TTFV = Time from "developer lands on your site"
       to "developer sees their first meaningful result"

BENCHMARK:
  < 5 minutes:  Excellent (Stripe, Vercel, Firebase)
  5-15 minutes: Good
  15-60 minutes: Needs improvement
  > 60 minutes: Significant friction (developer may leave)

COMMON FRICTION POINTS:
  - Account creation requires approval
  - Credit card required for free tier
  - SDK installation is complex
  - Environment setup is manual
  - First API call requires understanding complex concepts
  - Error messages are cryptic

HOW TO MEASURE:
  - Instrument the signup → first API call funnel
  - Track drop-off at each step
  - Run user testing sessions (watch developers try your product)
  - Dogfood your own quickstart quarterly

ANNUAL PLAN:

TIER 1 (Major conferences): 1-2 per year
  Submit CFPs 6 months in advance
  Examples: KubeCon, re:Invent, Next.js Conf
  Goal: Brand awareness with broad audience

TIER 2 (Regional/specialized): 3-4 per year
  Submit CFPs 3-4 months in advance
  Examples: Local tech meetups, language-specific conferences
  Goal: Deeper engagement with target audience

TIER 3 (Community events): 6-8 per year
  Organize or participate in local meetups
  Examples: User group talks, lunch-and-learns
  Goal: Community building, feedback collection

TALK PORTFOLIO:
  - 1 flagship talk (polished, high-production)
  - 2-3 topic talks (different aspects of your domain)
  - 1 workshop (hands-on, half-day or full-day)
  - Adapt to audience level (beginner, intermediate, advanced)

AWARENESS METRICS:
  - Website traffic from developer content
  - Blog post views and social shares
  - Conference talk attendance and feedback scores
  - Social media followers and engagement rate
  - YouTube views and subscriber growth

ACTIVATION METRICS:
  - Signup to first API call conversion rate
  - Time to first value (TTFV)
  - Quickstart completion rate
  - SDK downloads per month
  - Documentation page views and search queries

ADVOCACY METRICS:
  - Net Promoter Score (NPS) from developers
  - Community-generated content (blog posts, videos, talks)
  - Referral traffic and word-of-mouth signups
  - Stack Overflow mentions and GitHub stars
  - Champion program participant count and activity

BUSINESS IMPACT:
  - Signups attributed to DevRel content (UTM tracking)
  - Revenue from developer-led deals
  - Expansion revenue from existing developer accounts
  - Feature adoption driven by documentation/tutorials
  - Support ticket reduction from better docs

## DevRel Monthly Report - [Month]

### Highlights
- [Top achievement this month]
- [Key metric improvement]

### Content Published
| Type | Title | Views | Engagement |
|------|-------|-------|------------|
| Blog | [title] | [views] | [shares/comments] |
| Video | [title] | [views] | [likes/comments] |
| Talk | [event] | [attendees] | [feedback score] |

### Community Health
- New members: [N]
- Active members: [N] ([%] of total)
- Questions answered: [N] (avg response time: [X] hours)
- Community-generated content: [N] pieces

### Developer Experience
- TTFV (median): [X] minutes
- Quickstart completion rate: [X]%
- Top support requests: [list top 3]
- Docs improvements shipped: [list]

### Next Month
- [Planned content]
- [Upcoming events]
- [DX improvements in progress]

STRATEGY: Awareness (they know you) → Activation (great first experience) → Advocacy (they recommend you)
CONTENT: Blog tutorials + videos + conference talks + social engagement
COMMUNITY: Discord/Slack + champions program + feedback loops + events
DX: TTFV < 5 min, copy-pasteable code, clear errors, complete API reference
SPEAKING: 1-2 major + 3-4 regional + 6-8 community events per year
METRICS: Awareness (traffic, views) + Activation (TTFV, completion) + Advocacy (NPS, referrals)
FEEDBACK: DevRel is the bridge. Community → Product → Better product → Happier community.

# Developer Advocate Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]