Could a public ranking site become a safe classroom feedback tool?
I run Rankiwiki, a public community ranking site where people create topics,
add opinions, and vote.
While operating it, I started wondering whether the ranking mechanic could be
useful in classrooms. Students could choose the next book to read, rank project
themes, compare arguments from a lesson, or submit ideas that a teacher can
select from at random.
The difficult part is not the voting UI. It is safety.
A classroom version must never encourage students to rank identifiable
classmates by appearance, popularity, intelligence, behavior, or other personal
traits. It should rank ideas and answers, not children.
Rankiwiki is public today, so I am not presenting it as classroom-ready. Before
testing this use case, I think it would need:
- private or unlisted classroom topics;
- teacher-controlled join codes;
- participation without student names or email addresses;
- teacher approval, hiding, and deletion controls;
- configurable closing and result-release times;
- safeguards against topics that target real students;
- minimal data retention and clear deletion controls.
For teachers, which matters more: ranked results, random selection from student
answers, or a combination of both? What safety or workflow requirement would
make this idea immediately unusable in a real classroom?
Rankiwiki: https://rankiwiki.com/
I think the bigger question for Rankiwiki may not be how many pages to publish or clean up.it’s more like: what kind of page actually deserves to exist in the product at all?
from the outside, the strongest signal I see isn’t “anyone can rank anything.” it’s that rankings seem to come alive when they’re attached to a community that already loves arguing — like football fans debating players, overrated midfielders, defenders, etc.
so I’d be careful treating Rankiwiki as a broad SEO/content site too early.
my instinct would be to test one narrow wedge first:can 10 football ranking pages create real participation, sharing, and repeat visits in 14 days?
if yes, maybe Rankiwiki is less of a general ranking site, and more of a ranking/debate layer for passionate communities.
if no, publishing more pages probably won’t fix the core problem.
happy to put together a tighter validation read if useful.
The safety questions are important, but what stood out to me is the shift in purpose.
A public ranking site rewards participation differently from a classroom tool.
I'd be curious what the teacher is actually "buying" here. Better discussions, faster decisions, more engagement, or something else.
That answer could shape the product just as much as the safety features.
That framing is useful. My current hypothesis is that the teacher is buying broader participation before consensus, not a more exciting leaderboard. Randomly surfacing an anonymous answer can bring a quieter student's reasoning into the discussion; ranking ideas can happen later to synthesize the tradeoffs. Faster decisions would be secondary. This is still a product-direction hypothesis: Rankiwiki is public today and not classroom-ready, so I would validate the facilitation sequence with teachers and adult participants before building classroom features.
That's exactly the part I was hoping you'd unpack.
Your reply left me with a question about that facilitation sequence, and I think the answer depends on the direction you ultimately want Rankiwiki to take rather than on classroom software in general.
What's the best email to reach you on?
Thanks. I'd rather keep this early validation thread public for now so the assumptions can be challenged in context.
The thing I'm trying to validate is whether random anonymous answer surfacing before idea-ranking solves a real facilitation problem, before building any classroom-specific version.
If you're open to it, the most useful read would be: what would you ask teachers first, and what answer would make this direction a no-go?
That's a fair approach.
I have a perspective on the validation question, but I don't think I could do it justice in a couple of comments. I'll keep following the thread with interest, and I'm curious to see what you learn from those conversations.