The engaged developer funnel
🔗 **Source:** [The engaged developer funnel](https://www.youtube.com/watch?v=qDZxlnk95e4)
> [!note]+ Document Notes
> tags: [Developer-Relations, DevRel, Marketing, Metrics, Funnel]
> author: [MISSING]
> source: YouTube
> reference: [https://www.youtube.com/watch?v=qDZxlnk95e4]
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> # 🏷️ Title: The engaged developer funnel
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- DevRelCon conference series: https://www.devrelcon.dev/
- Neo4j GraphAcademy: https://graphacademy.neo4j.com/
- Developer education research, “Developers prefer self-serve”: https://segment.com/academy/collecting-data/developer-experience/
- Product-led growth primer: https://www.productled.org/blog/what-is-product-led-growth
- YouTube video: https://www.youtube.com/watch?v=qDZxlnk95e4
## 📝 Summary
- **What happened.** A DevRel leader proposes an engaged developer funnel over classic marketing funnels. He explains measurement and executive alignment using owned signals. ([video](https://www.youtube.com/watch?v=qDZxlnk95e4))
- **Why it matters.** Classic funnels misread developer learning and behavior. Hands-on education and communities drive durable adoption. ([PLG primer](https://www.productled.org/blog/what-is-product-led-growth))
- **Key stakeholders.** DevRel teams, executives, boards, investors, product, education, and community managers.
- **Risks and tradeoffs.** Overfitting metrics to owned platforms can bias results. Cross-org attribution remains hard. ([Segment DX](https://segment.com/academy/collecting-data/developer-experience/))
- **Bottom line.** Measure engaged developers across three pillars: basics, appropriate use, and top-of-mind re-engagement. Tie work to revenue motions through champions.
## 📖 Main Content
- **Problem.** Traditional funnels optimize lead volume, not developer learning. This sets DevRel up to miss executive expectations. ([video](https://www.youtube.com/watch?v=qDZxlnk95e4))
- **Core proposal.** Track an engaged developer state. Require three signals: knows basics, knows when to use, stays top-of-mind. Map programs to acquisition, progression, re-engagement, and education.
- **How developers learn.** They learn by doing, workshops, peers, and hackathons. Cold outreach underperforms. Evidence supports self-serve, PLG tactics. ([Segment DX](https://segment.com/academy/collecting-data/developer-experience/), [PLG](https://www.productled.org/blog/what-is-product-led-growth))
- **Executive alignment.** CEOs and boards care about champions behind deals. Report engaged counts and growth from owned education and cloud telemetry. ([video](https://www.youtube.com/watch?v=qDZxlnk95e4))
- **Data design.** Normalize platform metrics into a warehouse. Favor high-intent actions over vanity metrics for reliability.
### 🗒️ Notes
#### ⏱️ [00:14](https://www.youtube.com/watch?v=qDZxlnk95e4&t=14) Context and audience framing
- The talk targets DevRel leaders and executives.
- Goal: explain DevRel value to CEO and board.
### [H1] Traditional funnel metrics fail DevRel goals
> “When your metrics… are tied to this funnel, you are doomed to failure.”
- Rationale: funnels reward volume, not learning. This misses developer reality.
#### ⏱️ [06:39](https://www.youtube.com/watch?v=qDZxlnk95e4&t=399) How developers actually learn
- Doing, classes, peers, and hackathons lead learning.
- Outreach-centric tactics underperform for developers.
### [H2] Developers prefer hands-on, self-serve education
> “They don’t want to be called by an SDR… They actually want to learn by doing.”
- Evidence aligns with PLG research and practice.
#### ⏱️ [08:44](https://www.youtube.com/watch?v=qDZxlnk95e4&t=524) Engaged developer funnel overview
- Three pillars: basics, appropriate use, top-of-mind.
- Convert programs into acquisition, progression, and re-engagement.
### [H3] Engagement requires three concrete capability signals
> “First you want developers to know the basics… know when to use it… and top-of-mind.”
- Each pillar maps to measurable actions.
#### ⏱️ [10:57](https://www.youtube.com/watch?v=qDZxlnk95e4&t=657) Business alignment and scale
- CEOs champion engaged developers as deal catalysts.
- Treat engaged developers as a company metric.
### [H4] Champions propel deals more than contacts do
> “Every deal starts with a passionate engaged developer.”
- Champions correlate with adoption and expansion.
#### ⏱️ [19:15](https://www.youtube.com/watch?v=qDZxlnk95e4&t=1155) Data normalization story
- Normalize daily snapshots across APIs into a warehouse.
- Favor owned properties for consistent telemetry.
### [H5] High-intent actions beat vanity metrics
> “The type of metrics I’m talking about… are high engagement activities.”
- Track queries run, course completion, and forum contributions.
## 📚 References
- DevRelCon: https://www.devrelcon.dev/
- Neo4j GraphAcademy: https://graphacademy.neo4j.com/
- PLG overview: https://www.productled.org/blog/what-is-product-led-growth
- Developer experience best practices: https://segment.com/academy/collecting-data/developer-experience/
- Video: https://www.youtube.com/watch?v=qDZxlnk95e4
## 🗣️ Paraphrase
- **Paragraph A.** The speaker argues traditional funnels miss how developers learn and evaluate tools. DevRel should track education and capability. ([video](https://www.youtube.com/watch?v=qDZxlnk95e4))
- **Paragraph B.** Measure engaged developers with three signals. Then align programs and executive reporting to those signals. Use owned telemetry.
## 📰 Newsletter
- **Lead.** Developers learn by building, not by inbox nudges.
- **Why now.** Boards ask for DevRel impact. Funnels alone fail this moment.
- **What to do.** Define “engaged developer” with three signals and ship programs that raise each one.
- **Links.** Talk: https://www.youtube.com/watch?v=qDZxlnk95e4 • PLG: https://www.productled.org/blog/what-is-product-led-growth • DX: https://segment.com/academy/collecting-data/developer-experience/
## ✅ Action Items
#### DevRel
- Define engaged developer criteria across docs, training, and product telemetry.
- Build workshops that move users from basics to appropriate use.
- Publish an engagement dashboard using warehouse snapshots.
- Launch community clinics for re-engagement cohorts.
#### OSPO
- Document event data governance and privacy for telemetry.
- Clarify education licensing for course assets and samples.
- Establish contributor pathways for curriculum updates.
#### Community
- Operate mentor circles and peer-led architecture sessions.
- Run hackathons with post-event adoption tracking.
- Expand forum badges tied to learning milestones.
#### WordPress
- Training: add capability-based pathways and progress checks.
- Playground: craft labs aligned to engaged signals.
- Marketing: link case studies to champion stories and time-to-first-success.
#### The WPCC
- Fund microgrants for course authors and mentors.
- Publish transparent impact reports on learning outcomes.
### FAIR
- Define provenance for engagement events and audit trails.
- Publish a scorecard for high-intent vs vanity metrics.
## 🧪 Hypotheses
- Engagement-based programs increase qualified champions by 30% in two quarters.
- Workshops double conversion from basics to appropriate use within 60 days.
- Re-engagement campaigns lift monthly active developers by 20%.
- Normalized telemetry improves forecast accuracy for adoption by 15%.
### 📊 Methodology
- Instrument product and training with event schemas.
- Run cohort analyses across acquisition, progression, and re-engagement.
- Use difference-in-differences to estimate impact of workshops.
- Validate champions against opportunity notes and win stories.
### ❓ Questions
- Which signals best predict internal champion activity?
- How much owned telemetry suffices before bias rises?
- What program design moves users fastest between pillars?
### 🔮 Future Research
- Map community reputation signals to sales influence.
- Study workshop formats that maximize progression speed.
- Test doc patterns that reduce time-to-first-success.
### 💡 Implications
- **Practice.** Focus on high-intent learning signals, not raw reach.
- **Policy.** Align privacy and telemetry with clear developer notice.
- **Education.** Treat courses as product, with SLAs and KPIs.
### 🧠 Learning Styles Assessment
- **Reading level.** Flesch-Kincaid estimates ~10th grade based on sentence length.
#### 👀 Visual learners
- Present: slides and diagrams likely in talk.
- Improve: funnel state diagrams and event schemas.
#### 🔊 Aural learners
- Present: recorded talk.
- Improve: 3–5 minute audio recaps of each pillar.
#### 🗣️ Verbal learners
- Present: definitions for pillars and states.
- Improve: glossary and side-by-side examples.
#### 🧩 Kinesthetic learners
- Present: hackathons and labs references.
- Improve: sandbox tasks with checklists and rubrics.
#### 🧠 Logical learners
- Present: state model and metrics.
- Improve: causal diagrams and regression outputs.
#### 🧑🤝🧑 Social learners
- Present: peer learning and Q&A.
- Improve: cohort challenges and peer review prompts.
#### 🧘♀️ Solitary learners
- Present: self-paced courses.
- Improve: reflection prompts and self-check quizzes.
#### 🌿 Naturalistic learners
- Present: limited.
- Improve: sustainability angles for local dev environments.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: headings in slides likely vary.
- Improve: transcript and semantic HTML for companion pages.
#### Keyboard navigation
- Present: N/A for live talk.
- Improve: accessible event pages and focus states.
#### Contrast and readability
- Present: unknown slide contrast.
- Improve: adhere to 4.5:1 and avoid dense text.
#### Text resizing and reflow
- Present: N/A live.
- Improve: responsive pages for recorded materials.
#### Media and captions
- Present: YouTube captions available.
- Improve: downloadable transcript and audio description.
#### Forms and interactions
- Present: event feedback forms vary.
- Improve: labeled fields and inline error guidance.
#### Standards reference
- Map to WCAG 2.2 AA for event and docs sites.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: community examples; global reach unclear.
- Improve: multi-region case studies and translation links.
#### Inclusive language
- Present: mostly neutral.
- Improve: define jargon and avoid insider acronyms.
#### Neurodiversity support
- Present: structured outline.
- Improve: icon+text labels and predictable navigation.
#### Representation
- Present: mentions of panels and communities.
- Improve: visible diversity in examples and imagery.
#### Psychological safety
- Present: encourages stories of failure and success.
- Improve: publish a clear code of conduct for events.
### ✅ Logical Validity
#### Strong reasoning
- **Causal.** Hands-on learning improves capability; capability predicts advocacy. This aligns with PLG literature. ([PLG](https://www.productled.org/blog/what-is-product-led-growth))
- **Inductive.** Owned telemetry offers consistent measurement across programs. This supports reliable trend tracking.
#### Fallacies
- **Overgeneralization risk.** “Every deal starts with a passionate developer.” Safer: “Most technical deals involve a developer champion.” ([video](https://www.youtube.com/watch?v=qDZxlnk95e4))
- **Survivorship bias risk.** Only measuring owned platforms may miss external influence. Mitigate with surveys and community scraping.
#### Tone of voice
- Confident, anecdotal, pragmatic. Humor eases executive topics. Skepticism targets vanity metrics, not people.
### 🛡️ DARVO Analysis
- **Deny.** No denial tactics present.
- **Attack.** Jokes at marketing’s expense remain light, not hostile.
- **Reverse victim/offender.** Not observed; the talk invites collaboration.
## 🎯 Conclusion
- **Bottom line.** Measure what matters for developers: capability and relevance.
- **Next steps.** Define engaged signals, wire telemetry, and align executives on targets and timelines.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] Traditional funnel metrics fail DevRel goals
> [!quote] [The engaged developer funnel](https://www.youtube.com/watch?v=qDZxlnk95e4) by an unnamed author via [[YouTube]]. Published [MISSING]. Accessed {{date:YYYY-MM-DD}}.
> “When your metrics… are tied to this funnel, you are doomed to failure.”
Two lines: move metrics from volume to capability. Validate with PLG evidence.
[view highlight](https://www.youtube.com/watch?v=qDZxlnk95e4&t=260) #xref #articleseed ID:rw_[MISSING]
### [H2] Developers prefer hands-on, self-serve education
> [!quote] [The engaged developer funnel](https://www.youtube.com/watch?v=qDZxlnk95e4)
> “They don’t want to be called by an SDR… They actually want to learn by doing.”
Two lines: prioritize labs, sandboxes, and free tiers.
[view highlight](https://www.youtube.com/watch?v=qDZxlnk95e4&t=420) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Engaged developer state predicts account wins
- Scope: enterprise deals with technical adoption.
- Links: [[Product-Led-Growth]] [[Developer-Champions]]
#### [Z2] Owned telemetry outperforms vanity metrics
- Scope: course completion and product queries.
- Links: [[DX-Metrics]] [[Engagement-Signals]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- [F1] Draft engaged-developer KPI spec with three pillars — context/https://www.youtube.com/watch?v=qDZxlnk95e4 #fleeting #inbox
- [F2] Instrument workshop events for progression signals — context/https://segment.com/academy/collecting-data/developer-experience/ #fleeting #inbox
- [F3] Propose board-ready dashboard for engaged counts — context/https://www.productled.org/blog/what-is-product-led-growth #fleeting #inbox
<!-- deep-read:sections end -->