10 TACTICS ✣
DevRel Anti-Patterns.
A field guide to the recurring failure modes. Each anti-pattern is described, attributed to its symptoms, and connected to the practices that prevent it. Use this as a diagnostic when a program feels off, when a team is stuck, or when th…
A field guide to the recurring failure modes. Each anti-pattern is described, attributed to its symptoms, and connected to the practices that prevent it. Use this as a diagnostic when a program feels off, when a team is stuck, or when the executive conversation about DevRel keeps going sideways.
1. The lone evangelist
Symptom. A single high-profile speaker hire, expected to be “the DevRel team.”
Why it fails. No community to talk to; no docs feedback loop; no team to compound work; burnout within 12 months.
Prevention. Hire Community Manager first; Advocate second; ensure the team has at least three people before promoting public speaking as a primary activity.
2. DevRel as marketing in disguise
Symptom. Every output is a promotional blog post; every community engagement converts to a lead-capture form; every conference talk is a product pitch.
Why it fails. Developers detect it; engagement drops; brand trust erodes.
Prevention. Make a deliberate commitment to authentic technical content. Allow content to live without immediate conversion-tracking. Report community trust as an explicit metric.
3. Treating community as an outbound channel
Symptom. Community channels filled with company announcements; members asked to amplify launches; little reciprocity.
Why it fails. Members disengage; the community loses authenticity; loud-voice members leave first.
Prevention. Apply the reciprocity principle — every interaction should create value for the member. Audit your community-channel content monthly; the ratio of company-broadcasts to member-conversations should not exceed 1:5.
4. The vanity-metric trap
Symptom. Reports to executives focus on follower counts, GitHub stars, page views, conference attendance — without conversion to business outcomes.
Why it fails. Executives ask “and so?” — and the answer is unclear. Function becomes vulnerable to cuts.
Prevention. Distinguish Layer 3 (activity) from Layer 1 (business outcome) metrics. Report only Layer 1 metrics upward. Use vanity metrics internally as health signals only.
5. The ambassador program with no benefits
Symptom. Members are recognised with a title; sometimes a private Slack; rarely anything else. Asked to do speaking, content, evangelism.
Why it fails. Members realise the program is extracting value without giving comparable value back. Senior members leave first.
Prevention. Design benefits that members genuinely value. Direct line to product. Early access. Visibility. Travel sponsorship. Make participation worth participants’ time.
6. The DevRel-in-marketing structural trap
Symptom. DevRel reports to marketing leadership; gets measured on top-of-funnel metrics; pressured to produce marketing-style content.
Why it fails. Authentic developer voice degrades. Engineers in DevRel roles burn out from doing marketing work. Function loses credibility with target audience.
Prevention. Where possible, structure DevRel reporting to product, engineering, or CEO. If marketing reporting is unavoidable, negotiate explicit metric carve-outs that protect community trust and product feedback from quarterly pipeline pressure.
7. The disappearing founder
Symptom. Founder was very public during early days; once the product matures, founder pulls back from external communication and expects DevRel to “take over.”
Why it fails. The community formed around the founder’s voice. Replacing that voice with a separate function is harder than founders realise.
Prevention. Plan founder-to-team handoff carefully. Build the team’s public profiles alongside the founder, not after. Maintain founder presence at strategic moments even after delegating day-to-day work.
8. Documentation as an afterthought
Symptom. Features ship; docs lag; quickstarts are years out of date; sample apps don’t run.
Why it fails. TTFHW degrades. Activation rate drops silently. New users abandon during onboarding without ever reaching the support channels that could help.
Prevention. Treat docs as a product. Require updated docs as part of feature ship. Audit quickstart performance with new-user-walkthrough tests quarterly. Make TTFHW a tracked metric with an owner.
9. Speaker burnout
Symptom. The same three people speak at every conference. They get tired, become repetitive, and reduce output. Quality of talks drops.
Why it fails. Audience notices. Conference organisers stop accepting submissions. Talent leaves.
Prevention. Develop speaker bench depth. Make conference speaking a rotation, not a single-person assignment. Train new speakers. Pair experienced speakers with new ones at smaller events.
10. The acquisition / restructure orphan
Symptom. The DevRel team was effective at Company A. Company A gets acquired by Company B. Within six months, half the team has left and the program’s authority is unclear.
Why it fails. Acquired-company DevRel functions almost always lose ground to acquirer politics. Champions inside the acquired company depart; the program lacks internal advocates inside the larger acquirer.
Prevention. Within the first 90 days of an acquisition, secure executive sponsorship inside the acquirer. Document the program’s value with hard metrics that the acquirer can defend. Negotiate clear scope and reporting line.
11. The “DevRel is everywhere” diffusion
Symptom. Multiple teams claim to do DevRel work. No team owns the function. Output is uncoordinated. Same advocate is asked by three different VPs to produce three different things in the same quarter.
Why it fails. Strategic incoherence. Quality drops. Senior practitioners leave.
Prevention. Establish a clear function owner with documented scope. Centralise the DevRel charter, even if execution is distributed.
12. The unread executive dashboard
Symptom. A beautiful weekly DevRel dashboard exists. No executive looks at it.
Why it fails. Even strong work is invisible. When budget pressure comes, the function cannot defend itself.
Prevention. Reverse-engineer what your executive actually wants to know. Push narrative reports proactively. Quarterly business reviews with explicit DevRel-impact stories. Make sure your work shows up in board materials.
13. The first-hire-strategy mismatch
Symptom. The first DevRel hire is the wrong type for the company’s stage. (E.g., a Principal Advocate hired pre-PMF; a Community Manager hired at a stage where awareness is the main need.)
Why it fails. Mismatch produces frustration on both sides. Hire leaves within 18 months.
Prevention. Match the hire to the maturity stage and primary goal. See ./starting-from-scratch.md.
14. The metrics-after-the-fact trap
Symptom. Team has been running for 18 months. Now an executive wants to see ROI. There is no instrumentation; no historical data; no clear baseline.
Why it fails. No defence possible during budget cycles.
Prevention. Instrument before you need data. Set baselines from week one. Reset baselines quarterly so trends are visible.
15. The Discord that goes dark on weekends
Symptom. Community looks active during US business hours; dead the rest of the time.
Why it fails. Global community members don’t get responses. First-response time degrades. Sentiment drops.
Prevention. Distributed staffing across time zones. Volunteer moderator program. Clear “we respond within X hours” SLA published.
16. The ambassador-program selection drift
Symptom. Selection criteria for ambassadors gradually loosen. New cohorts include members less impressive than original cohorts. Existing members feel their recognition devalued.
Why it fails. Program’s prestige erodes. Senior members disengage. The program becomes thin.
Prevention. Document selection criteria explicitly. Use the same criteria year over year. If you need a broader program, create a separate emerging-talent tier rather than diluting the existing one.
17. Treating AI assistants as a replacement for human DevRel
Symptom. Team automates content generation, community responses, and sentiment analysis. Slowly the human voice is replaced.
Why it fails. Trust does not transfer to AI-generated content. Communities detect it. The function’s distinguishing characteristic — authenticity — is destroyed.
Prevention. Use AI to augment, not replace. The human voice on the public side remains human. AI-assistance happens in the production pipeline, not at the audience interface.
18. The “we’ll figure out metrics later” trap
Symptom. Team launches with energy and ambition; metrics are deferred; the function is defended by enthusiasm rather than data.
Why it fails. When the budget cycle changes, “we’ll figure out metrics later” is now “we don’t have data” — and the function is cut.
Prevention. Instrument from day one. Even crude metrics beat no metrics.
19. The conference-speaker-collector
Symptom. Team optimises for getting conference acceptances above all else. Internally measured on talks given. Less attention on community, docs, or activation.
Why it fails. Conference talks alone don’t drive business outcomes. Activation and retention do.
Prevention. Conference speaking is one tactic; map it to specific goals from AAARRRP; require the speaker to write follow-up content that lives durably.
20. The “founder is the program” trap
Symptom. The founder is brilliant publicly. Hires DevRel reluctantly. Continues to be the only public voice. The team can’t grow into anything.
Why it fails. Founder-bottleneck. Doesn’t scale. Doesn’t survive founder departure.
Prevention. Founders should be the first public voice and continue to be a public voice. They should never remain the public voice as the company scales. Hire and elevate team members deliberately into public roles.
How to use this list
When a DevRel program feels stuck:
- Read this list quickly.
- Identify which 1–3 anti-patterns best describe the current state.
- Use the prevention guidance to design a corrective intervention.
Most programs that are struggling are running at least two of these patterns simultaneously. Naming them precisely is half the fix.