17 lines
1.1 KiB
HTML
17 lines
1.1 KiB
HTML
<p>A creator ops dashboard is a decision surface, not a wallpaper of charts. If you cannot say what you will do when a number moves, remove the number.</p>
|
|
<h2>Four tiles that earn their space</h2>
|
|
<ul>
|
|
<li>Current viewers versus the session median</li>
|
|
<li>Gifts in the last five minutes</li>
|
|
<li>Chat rate versus baseline</li>
|
|
<li>Connection health (last event age)</li>
|
|
</ul>
|
|
<h2>Baselines beat raw counts</h2>
|
|
<p>2,000 viewers means nothing without the usual range for that creator and timeslot. Compute a rolling median from previous sessions and show deviation, not vanity totals.</p>
|
|
<h2>Stale data is a bug</h2>
|
|
<p>If events stop, the dashboard must look broken on purpose: a red last-seen timer beats a frozen pretty chart that implies the room is still live.</p>
|
|
<h2>Role-specific views</h2>
|
|
<p>The person on camera needs gifts and comments. The producer needs connection and queue. One layout for both roles produces ignored panels.</p>
|
|
<h2>End of session</h2>
|
|
<p>Lock the dashboard into a recap mode: peak viewers, top gifters, disconnect count. That recap is the only slide most clients will read.</p>
|