You do get to see the average size of cohorts, and you will need to explain why your team doesn’t meet them - for example if the entire team project is going exceedingly well, or the team is really made out if a lot of extraordinarily talented people - then you can argue why you have more than the average rate of excellent rankings.
Anyway, even if it honestly for "extraordinarily talented" people, that's still stupid stack-ranking.
The same you’d rank a person’s work, you would rank a team or org’s work.
If that team is doing really well, it’s likely they will have a distribution of higher rankings than the average. If they’re doing really bad, it can be the opposite.
The point is that if you finished ranking some team and your rankings are higher than average, you need to have a reason why.
What makes a ranking into a stack ranking?
But well, stack ranking is not only about sorting (the name is a lie), it's about placing people in fixed sized cohorts. The real question is if there is a limitation on the number of raises or a minimum on the number of people treated as "low performant".