How we handle feedback
Every serious piece of feedback gets a trail: captured, discussed, acted on when we commit to it, and closed with the person who raised it when we ship or decide not to.
Logging
We track themes in GitHub issues (org/repo appropriate) and link back to the original email, chat, or issue so demand frequency stays visible—without pretending we have a heavyweight CRM.
Internal advocacy
When the team meets, Success brings a short read on top categories (site confusion, Neuro OS demo friction, doc gaps, partnership asks) so prioritization is shared, not siloed.
Owner sync
Whoever owns the relevant surface—site, Neuro OS experience, or content—syncs with Success on open escalations, ownership, and what will land in the next deploy versus backlog.
Lightweight digest
A periodic internal note (async is fine) captures trending requests, recurring pain, long-standing asks, and genuine praise—enough ritual to remember the human side, not enough process to block shipping.
Closing the loop
When a fix or doc update ships, we tell people who waited on it—by reply, issue comment, or release note—so trust stays tied to delivery, not slogans.