By the time they're reading the docs, it's already too late
0 likes•129 views
The document discusses the importance of documentation in developer relations, emphasizing that developers typically research and evaluate technology before accessing docs. It highlights the interconnectedness of marketing, education, and documentation in shaping developer perceptions and experiences. Additionally, it stresses the need for cross-team coordination to provide a seamless developer experience.
By the time they're reading the docs, it's already too late
- 1. hoopy.io hoopy.io By the time they're reading the docs, it's already too late Matthew Revell, Hoopy [email protected]
- 2. hoopy.io Matthew Revell Founder and Principal Consultant SHROPSHIRE, UK [email protected] hoopy.io
- 5. hoopy.io Developer Content production hoopy.io Industry analysis Strategic consulting EVENTS
- 8. hoopy.io Bigger journey Documentation is just one stop on a hoopy.io
- 9. Measuring This is important
- 10. But it is a Tree > Forest situation
- 11. Developer Relations book, Caroline Lewko and James Parton
- 12. Developer Relations book, Caroline Lewko and James Parton
- 13. Developer Relations book, Caroline Lewko and James Parton
- 14. Developer Relations book, Caroline Lewko and James Parton AWARENESS MARKETING CONSIDERATION DECISION
- 16. AWARENESS MARKETING CONSIDERATION DECISION BUYING PROBLEM IDENTIFICATION SOLUTION EXPLORATION REQUIREMENTS BUILDING SUPPLIER SELECTION DEVREL AWARENESS ACQUISITION ACTIVATION RETENTION REFERRAL REVENUE PRODUCT
- 17. AWARENESS MARKETING CONSIDERATION DECISION BUYING PROBLEM IDENTIFICATION SOLUTION EXPLORATION REQUIREMENTS BUILDING SUPPLIER SELECTION DEVREL AWARENESS ACQUISITION ACTIVATION RETENTION REFERRAL REVENUE PRODUCT LEARNING UNCONSCIOUS INCOMPETENCE CONSCIOUS INCOMPETENCE CONSCIOUS COMPETENCE UNCONSCIOUS COMPETENCE
- 18. WHAT DOES THIS HAVE TO DO WITH MEASURING DOCUMENTATION?
- 19. No one comes to your docs cold
- 20. Whatever model we look at, Developers have already: • Thought about the problem • Tried solutions • Formed opinions
- 21. 1. Google to assess landscape 2. Talk to peers 3. Check if the tech has an active community 4. Evaluate the docs How do developers evaluate tech?
- 23. Marketing, education, docs, community are different aspects of the same thing
- 26. DEVELOPER MARKETING DEVELOPER ADVOCACY DEVELOPER DOCS PRE-SIGNUP DEVELOPER SUCCESS DEVELOPER COMMUNITY POST-SIGNUP CONFERENCE TALKS ONE ON ONE SAMPLE CODE COLLABORATIONS BLOG POSTS PODCASTS & STREAMS EBOOKS TUTORIALS GUIDES QUICK-STARTS LEARNING PATHS PRO-ACTIVE SUPPORT PROOFS OF CONCEPT FORUMS ACHIEVEMENTS EVENTS FRIENDSHIP
- 28. 1. Market making and education 2. Establish the language that you’ll later use 3. Set the context Developer marketing + Docs
- 29. 1. Direct link to real developers 2. Generate use cases and code 3. Content, content, content Developer Advocacy + Docs
- 30. 1. Real feedback on how customers use the docs and product Developer SUCCESS + Docs
- 31. 1. Observation 2. Contribution 3. Tough love Developer Community + Docs
- 33. Docs don’t stand in isolation
- 34. Docs don’t begin and end on your dev portal
- 35. Coordinate across teams to deliver a coherent developer experience
- 36. BEGIN SOONER