Feedback Systems of Record vs Feedback Rivers: Why You Need Both
TL;DR: Rivers drive immersion and intuition. Systems of record drive tracking and accountability. Use rivers for learning, records for decisions.
The distinction
River: high-volume, mostly raw, shared, continuous
System of record: structured, deduped, trackable, decision-facing
What belongs where
River:
- verbatims
- screenshots
- quick context
- ambient signals
Record:
- themes
- feature requests
- linked accounts/segments
- status + decision notes
The right flow
River → weekly theme candidates → system of record → roadmap bet → shipped outcome → back to river (closing loop).
Takeaways
Don’t force structure too early. Don’t skip structure forever.