Developer products generate signal in two public places: Stack Overflow (how people phrase errors and "how do I…" questions) and GitHub (issues, discussions, releases, dependents). This merged guide covers both - for PMs, founders, and developer relations at API-first B2B companies.
Best for: teams with public SDKs, open repos, or docs-heavy onboarding.
Quick answer
Use Stack Overflow as a precision layer (error messages, SDK usage, version quirks). Use GitHub as a workflow layer (issues, milestones, dependents). Roadmap signal appears when the same structural gap repeats across tags, repos, or quarters - not when one user has a broken laptop.
Stack Overflow: what to search
| Search pattern | Reveals |
|---|---|
[your-sdk] + error message |
Docs gaps, breaking changes |
alternative to [incumbent] |
Switching intent (pair with Reddit/HN) |
[your-tag] + best practices |
Maturity of user base |
[api-name] + rate limit |
Scale pain → enterprise upsell |
Voting bias: SO votes measure answer helpfulness, not revenue. Use vote count to sort, not to prioritize roadmap alone. Read Stack Overflow's tagging guidance when interpreting tag volume.
Weekly habit: Save three searches; review new questions every Monday; tag internally as DOC / ENV / CAP / REL (below).
GitHub: what to read beyond stars
Stars are bookmarks - see OSS metrics vs sentiment. For product research, prioritize:
| Surface | Signal |
|---|---|
| Open issues | Recurring CAP tags, old bugs with +1 storms |
| Discussions | Feature debates, self-hosting pain |
| Releases | Changelog gaps users still complain about |
| Dependents / forks | Real adoption vs curiosity |
| PR velocity | Whether community fixes docs before you do |
Shared taxonomy (route signal correctly)
| Tag | Meaning | Owner | Action |
|---|---|---|---|
| DOC | Confusing docs / examples | DevRel + docs | Fix samples, CLI walkthrough |
| ENV | Local setup, CI, laptop | Support | Playbook, docker compose |
| CAP | Missing capability | PM + eng | Roadmap candidate |
| REL | Regression | Engineering | Hotfix, postmortem |
Rule: If three unrelated accounts report the same CAP theme in 60 days across SO + GitHub, schedule roadmap review. If it's one ENV ticket, close the support loop.
Cross-community workflow
- SO: Export weekly top questions for your tags.
- GitHub: Label new issues with DOC/ENV/CAP/REL.
- Reddit / HN: Search "self-host [category]", "[your tool] vs [competitor]".
- Compare: Does public phrasing match your marketing copy?
Needle Search runs the same queries across Stack Overflow, GitHub, Reddit, and HN on eligible plans - useful when you repeat this weekly. Platform limits: plans and docs.
Handoff to PM (one-pager template)
Title: [CAP] Short description
Evidence: SO link(s), GitHub issue(s), # of unique reporters
Customer segment: hobby / startup / enterprise
Workaround today: …
Revenue risk if ignored: …
Recommendation: build | document | wontfix (with reason)
Common mistakes
| Mistake | Fix |
|---|---|
| Roadmap from one viral HN post | Wait for recurrence across SO + issues |
| Closing issues without docs update | DOC debt compounds into SO duplicates |
| Debating scope in GitHub comments | Move to internal triage |
| Ignoring closed duplicates on SO | Duplicates are demand signal - count them |