View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Product Strategy ICE Scoring |  Product Strategy RICE Scoring |
|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 30-60 min | 60-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Team API Document | ICE Table, Top Idea List | RICE Scores, Ranked List, Assumption Log |
Tagsno overlap | TeamAlignmentCommunicationService | PrioritizationScoringGrowthDecision | PrioritizationScoringRoadmapTradeoffs |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
