| We’ve all been there — mid-conversation on a bad cell connection, your own voice bouncing back through the line half a second late. You pause, stumble, and lose your train of thought. You’re not missing data — you’re missing clarity.
That’s the same problem organizations face when their feedback loops are slow or distorted. Signals exist — adoption rates, satisfaction scores, defect trends, value delivery — but by the time we “hear” them, the context has changed. It’s not a silence problem, it’s an echo problem. |
 |
The fix isn’t to shout louder. It’s to listen better.
We Already Have Feedback — We Just Aren’t Listening
“Delays in feedback loops are critical determinants of system behavior. A delay too long can cause oscillations, instability, or collapse.” — Donella Meadows, *Thinking in Systems*
Feedback loops are present everywhere — retrospectives, dashboards, customer analytics, portfolio reviews — yet we treat them as reports, not sensors.
In a recent Outcome Metrics Workshop I delivered, teams discovered that their systems weren’t silent; they were just out of sync. Diagnostic metrics (velocity, cycle time) were loud, frequent, and local — like an echo chamber. Outcome metrics (customer adoption, satisfaction, impact) were faint, slow, and distant. The result? Everyone talking, but no one hearing the same conversation.
The Cell Phone Delay
When you hear your own voice repeating back, it’s disorienting. You can’t focus on the message — only the delay.
That’s what it’s like when outcome data arrives months after delivery. Teams keep speaking (shipping stories, closing tickets), but the organization reacts to an outdated signal. We’re answering questions the customer asked last quarter.
“Controlling a system with long feedback delays guarantees instability. The longer the delay, the larger and more violent the oscillations.” — Donald Reinertsen, *The Principles of Product Development Flow*
Sonar vs. Static
Another way to think about this is in a military submarine. A submarine doesn’t wait three minutes for an echo; it pings continuously. The quicker and clearer the return, the better the navigation.
Metrics behave the same way. Diagnostic metrics are the pings; outcome metrics are the interpretation of the echo. If we only track output (“number of features delivered”), we are only generating noise. But when we link diagnostics to outcomes (“feature adoption increased 20% after we reduced cycle time”), the feedback becomes sonar — directional, useful, alive.
“The faster you can close the feedback loop between action and understanding, the faster the organization learns.” — Peter Senge, *The Fifth Discipline*
The Echo in the Empty Room
One more way to think of this is to picture a large, empty room, no furniture, just hard walls. You try to speak to someone at the other side of the room, but every word bounces back. You can’t tell which voice is yours and which is theirs.
That’s what happens when feedback has nowhere to land. Without dashboards, visualizations, or reflection cadences, feedback loops reverberate endlessly — loud but unintelligible. We don’t need to create more sound; we need to move closer to the source to limit the echo..
“Without data, you’re just another person with an opinion. But data without context or timely interpretation is just noise.” — W. Edwards Deming
Improving Your Reception: How to Listen Better
The data signals are already there. The goal is to hear them clearly and act before they fade. Here are seven ways to improve your organizational listening skills:
1. Make Feedback Visible — Blend diagnostic and outcome metrics on the same dashboard. Don’t put the speedometer in the backseat.
2. Shorten the Distance Between Signal and Response — Move from quarterly retrospectives to weekly metric touchpoints.
3. Use the Outcome Clock — Align team, ART, portfolio, and enterprise feedback speeds.
4. Correlate, Don’t Cascade — Tell the story between diagnostics and outcomes.
5. Balance Outcome and Diagnostic Metrics — One shows how, the other shows why.
6. Listen for Patterns and Trends, Not Endpoints — Look for changes, responses from the ‘system’, and trends, not snapshots.
7. Treat Feedback as a Sensor, Not a Scorecard — As Diana Larsen says, “Metrics should act like sensors in a feedback loop—not scorecards.”
Closing Reflection
Improving feedback isn’t about turning up the volume; it’s about reducing the echo.
We already have the signals we need — in our dashboards, retrospectives, adoption data, and customer sentiment. The art is in listening sooner, listening smarter, and acting faster.
Learn to listen and tune. Remember, sometimes to get rid of that echo on the cell call, we need to hang up and reconnect.