# DevRel Autonomy Requires Leadership Trust Not Just Budget ## Claim Experimentation-friendly DevRel work — cornerstone content, unmeasured "folly" projects, resisting quota pressure — only survives when leadership already trusts the practitioner's judgment, so the real prerequisite for this strategy is a trust relationship, not a line item in the budget. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds in organizations where DevRel has a named executive sponsor willing to defend unmeasured work against pressure for fast, attributable ROI. - Breaks down in organizations that fund only what's immediately attributable to pipeline, or where the sponsoring executive turns over — the strategy has a single point of failure, not a structural guarantee. - Doesn't claim budget is irrelevant, only that budget alone doesn't produce the autonomy; a well-funded team under a metrics-only mandate still can't protect folly time. ## Evidence Joel Hans (ngrok DevRel Lead) describes negotiating with leadership to replace fixed content-cadence quotas with long-term brand-impact framing, naming rigid weekly/monthly output targets as "really dangerous" because they "lead to burnout." He credits his ability to keep making the case less to inventing the idea than to leadership (particularly his CRO) already sensing the brand-perception problem before he pitched anything — and to building a track record of unsolicited positive feedback he could point back to. Both he and host Frédéric Harper converge on the same conclusion from separate companies: without that pre-existing trust, DevRel reverts to KPI-bound content-mill work, which they describe as a common industry failure mode. ## Links - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — because contrasts; that note gives the measurement structure (Awareness/Activation/Engagement/Retention) DevRel teams should map metrics to, this note names the precondition (trust) that lets a team protect work that resists mapping to any of those four cleanly. - [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] — because applies-in; folly-time autonomy is plausibly a Stage 3–4 luxury, not something a Stage 1 team can negotiate for yet — worth testing against the maturity model directly. - [[3. Resources/MOCs/DevRel MOC]] — because applies-in; a recurring practitioner-level finding about what actually protects experimental DevRel work. - [[3. Resources/Permanent Notes/A Metric Nobody Else Acts On Is a Diary]] — applied in: a DevRel metric earns its place when someone outside DevRel changes a decision because of it (Gorton). ## Tests / falsifiers - Find a DevRel team that sustained cornerstone-content or folly-style unmeasured work through an executive-sponsor departure without losing the mandate — would show the single-point-of-failure framing is too pessimistic. - Survey DevRel practitioners on whether budget size or leadership trust better predicts whether their team can resist fixed content quotas — would test whether trust is actually doing more work than resources, as claimed. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/devrelshow episode 52 - Joel Hans from ngrok]] — Joel Hans's account of negotiating quota-free cadence and "folly" time with ngrok leadership.