{{ c.pilaresTitulo }}
{{ c.pilaresTxt }}
- {{ pi.nome }}{{ pi.texto }}
{{ b.nome }}
{{ t.t }}
- {{ s.t }}
{{ fase.nome }}. {{ fase.t }}
- {{ ci.n }} {{ ci.nome }}
{{ cicloFecho }}
- {{ it.t }}
- {{ f.k }}
- {{ f.v }}
- {{ dc.t }}
- {{ dc.d2 }}
Previous work · Signals
A common model for data from Twitch, YouTube and the games themselves, and dashboards that update while the broadcast is running.
Each platform with its own dashboard and its own numbers. The totals were added up by hand the next day. Four sources, one model, one dashboard. Reading the event now happens during the event.
During a broadcast, the brand team saw different numbers on Twitch, YouTube and in the games themselves. They combined them by hand the next day, and the reading of the event arrived late.
Game broadcasts on several platforms at once, audiences changing minute by minute and content decisions made during the event.
Before any chart, we worked out what each source provided and with what limits.
A single reading while the broadcast is running. The team stopped adding up numbers the next day and started deciding during the event.
API limits define the design before any dashboard. And a common model is worth more than a pretty chart.
{{ c.lede }}
{{ c.pilaresTxt }}
{{ t.t }}
{{ fase.nome }}. {{ fase.t }}
{{ cicloFecho }}