It is tempting to build a leaderboard of bounce rates by developer. It is also wrong, in a way that is expensive and quick to learn. The developer who is handed the vaguest tickets bounces the most. The leaderboard then rewards the developers who got the clearest tickets and punishes the ones who were set up to fail.
Pyloq tracks bounces per ticket and per PM. A ticket that bounces twice is data about that ticket. A PM whose tickets bounce at three times the workspace rate is data about that PM's writing. The developer is not in the metric, because the developer is not the cause.
Instrument the work. Trust the people. It is the only quality policy that does not quietly turn into a game.