When PMs talk about Feedback Cycles, this is what they mean. I told you something, you tell me that you received it and whether there will be any action on it (although that's secondary to the "I received the message" portion of the cycle).
As a developer, feedback cycles to me imply recursion. But I think a PM would be mighty pissed if I told them, "Why don't you just give the message to yourself until you run out of memory."
Unrelated to the post, I read some good developer jokes in the last week at Web Dev .NET. How can you go wrong with:
...and in the comments by Daniel Morales:
"Why the Java developers does not have glasses? Because they see sharp."
Snarky: Our PM said I needed a more concrete feedback loop. I added an Outlook rule that will forward her messages to you.
Title: So you've moved from endpoint to gap in the communication process?