Kinn for DevRel teams
Developer relations runs on a signal most teams never capture: the questions people ask.
A recurring question isn't idle chatter. It's a documentation gap, a confusing API, or a missing example — and unlike a bug report, nobody files it. It gets answered in a Discord thread, in a GitHub discussion, in a YouTube comment, and then it's gone. The next person asks it again, and someone answers it again, and nothing structural ever changes.
Kinn's most useful trick for DevRel is treating those questions as data.
What changes
- Recurring questions become a ranked list. Which means your docs roadmap is evidence-based instead of a guess about what's confusing.
- You can prove the friction is real. "The auth flow confuses people" is an opinion. Forty distinct people asking the same thing in ninety days is a finding.
- You can tell whether content worked. Did the questions actually stop after you published the guide?
- You catch problems in languages your team doesn't read. Search matches across languages, so a stream of confusion in one community doesn't stay invisible.
Your week with Kinn
Weekly — what are people asking? Not what's broken. What's confusing. These are different lists with different owners.
What questions came up repeatedly across our community and discussions this week? Group them by topic, ranked by how often each was asked, and tell me which ones already have documentation.
That last clause is the important one — it splits "we never wrote this" from "we wrote it and nobody can find it," which need completely different fixes.
After publishing — check whether it landed. Two to three weeks after a guide or video ships, ask whether the questions it was meant to answer have dropped off.
Monthly — find the conversations you're not in. Community discussion about developer tools happens in places nobody told you about.
Before a product conversation — bring the aggregate. You're often the only person who sees the pattern across every channel. Bring it with numbers.
Start with these
- Social listening — including the "asking questions" bucket, which is usually the highest-value one for DevRel.
- Build great Discord reports — the weekly read on your community.
- Size how widespread something is — turning "people find this confusing" into something the product team acts on.
- Discovering new content — finding the conversations happening without you.
The questions worth making routine
What are people asking that our documentation doesn't answer?
Which topics generate the most back-and-forth before someone gets a working answer?
Are people asking the same questions in non-English channels that they are in English ones, or different ones?
Since we published the migration guide, have questions about migration decreased?
What to connect
- GitHub — issues and discussions, where developers report precisely and at length.
- Discord or Slack — where questions actually get asked.
- Reddit — where people go when they've given up on your channels, which makes it a particularly honest source.
- YouTube — connect your whole channel, not just recent videos. Tutorial comments are full of "I got stuck at step 4," which is the clearest friction signal you'll find anywhere.
- Website — your own docs and changelog, so Kinn can tell whether something is documented.