Insights don't ship themselves
Playtesting tools are essential -- recruiting players, running sessions, capturing clips, synthesizing themes. But they usually stop at the handoff. A clip is not a ticket. A theme is not a shipped fix.
Iridae picks up where the research deck ends: connecting findings to decisions, routing execution through your existing tools, and verifying whether the fix worked.
Where the handoff breaks
- Findings are clear. What ships next isn't.
- Tradeoffs stay implicit, so the same debates repeat.
- Ownership drifts between design, product, engineering, and production.
- Fixes ship, but nobody verifies whether they worked.
The issue is rarely insight quality. It's the loop from finding to shipped change to verification.
What Iridae adds
- Consolidate findings and confidence levels across sources.
- Frame options with tradeoffs and constraints visible.
- Produce a decision brief with an owner and success criteria.
- Route execution through existing tools.
- Verify impact after the next build or release, then feed it back.
Learning compounds. The next cycle starts from evidence, not memory.
Comparison at a glance
| Dimension | Playtesting + research tools | Iridae |
|---|---|---|
| Core question | "Where do players struggle?" (evidence) | "What ships because of it, and did it work?" (decisions) |
| Typical outputs | Findings, clips, themes, reports | Decision briefs, approved actions, verified impact |
| Best for | Understanding players and reducing blind spots | Shipping findings and verifying they worked |
| Together | Research tools capture the signal | Iridae routes execution and closes the verification loop |