Anthology Idea Exchange — Backlog & Responsiveness Analysis

Executive Summary

The Idea Exchange functions well as a collection mechanism but poorly as a resolution mechanism. Ideas are triaged quickly out of "Not Assigned," but from there the overwhelming majority land in a holding pattern — regardless of how popular or actively discussed they are.

80.6%

of all ideas sit in "Future consideration" or "Unlikely to implement" — the two non-committal statuses

2.2 yrs

median age of an idea in the system (some active discussions stretch to 4 years)

4.7%

of ideas have ever reached "Planning to implement" — the only status suggesting real forward motion

0.22 yrs

median time an idea spends "Not Assigned" — triage itself is fast; resolution is not

Core finding: there is no status in this system that means "done." The seven possible states — Not Assigned, Researching, Future consideration, Planning to implement, Follow up is needed, Already exists, Unlikely to implement — describe a triage pipeline, not a delivery pipeline. Combined with the data below, this is consistent with a developer/product process that classifies requests quickly but lacks a clear, forcing mechanism to decide and communicate final outcomes, especially for larger or more contentious asks.

Where Ideas End Up

Status is assigned almost immediately (median 82 days from "Not Assigned"), but the destination status rarely changes again. Two-thirds of all submissions are parked in "Future consideration" alone.

Status distribution (n = 6,556)

Age of ideas at time of export

Where the Backlog Is Heaviest

Ranked by total votes cast (a proxy for institutional demand). "% stuck" = share of that category's ideas sitting in Future consideration / Unlikely to implement. Gradebook and grading alone accounts for nearly a quarter of all votes cast across the entire exchange, and 86% of its ideas are stalled.

Top 25 Most-Voted Ideas

The ideas the community has weighted most heavily — and how the platform has responded to that signal. Note how few of the highest-vote items have moved past "Future consideration," despite ages of 3–4 years and dozens of comments each.

Votes	Idea	Category	Age	Comments	Status

The Clarity Gap: Evidence in the Data

The clearest sign of inconsistent triage isn't the backlog size — it's the contrast between two groups of ideas that received very different treatment for reasons the data doesn't explain.

High-signal ideas, still stuck

Years, no movement

3–4 years old, dozens of votes and comments, discussion continuing into 2026 — yet still "Future consideration" or "Unlikely to implement." These are not obscure requests; commenters are actively re-engaging years after submission and getting no status change.

Idea	Votes	Cmts	Age	Last comment

Low-signal ideas, resolved in days

Weeks, closed out

By contrast, these ideas — mostly single-digit vote counts with little or no discussion — moved to "Planning to implement" or "Already exists" within 12–60 days of submission. Small, unambiguous asks clear the queue fast; larger or more contested ones don't.

Idea	Votes	Days to status	Outcome

What this pattern suggests: the gating factor for resolution doesn't appear to be community demand (votes) or engagement (comments) — both groups above span the same status vocabulary. Ideas that are cheap/unambiguous to adjudicate ("this already exists," "we'll build this small thing") get closed quickly. Ideas that require a real product decision — especially ones with active back-and-forth discussion, meaning the ask itself may be contested or complex — stall indefinitely in "Future consideration," which functions less as a real status and more as a holding queue with no re-evaluation trigger. That's the lack-of-clarity signature: fast, confident answers for easy calls, and silence for the hard ones.

Ongoing Activity Doesn't Move Status

328 ideas received a comment within 90 days of this export — and 227 of them (69%) are still sitting in "Future consideration." Active community engagement is not, on its own, sufficient to trigger a status change or a developer response, reinforcing that the bottleneck is a decision process rather than a lack of visibility.