Continuous delivery makes it easy to ship fast and easy to lose track of what any given release actually did for users. This talk covers how one team instrumented feedback directly into their release process, including lightweight in-product signals, feature-flag-tied surveys, and telemetry that reports back on the same cadence as the code ships, so feedback stops trailing releases by weeks. Key takeaways: - Practical instrumentation for tying feedback collection to individual releases or flags - How to keep feedback lightweight enough not to slow down a fast release cadence - What to do differently when feedback finally arrives at the same speed as the code