Skip to content
Docs · The office scoreboard

The floor

The office scoreboard

Screens on the office walls with the numbers your team cares about, pushed from your tools or counted from a board, and a small celebration when they move.

Updated

On this page

Screens hang on the office walls. Each shows up to three numbers a team cares about: releases today, tickets done this week, tickets in review. When one moves, the office notices.

Every workspace starts with one screen, Hall, above the Support desks. Owners and admins can put more on fixed spots around the floor:

Spot Where
Hall Above the Support desks
Platform Above the Platform desks, on the Standup wing’s wall
Standup On Standup’s north wall, in place of its screen
Meeting rooms 1, 2 and 3 On each room’s north wall, in place of its screen
Kitchen On the kitchen’s north wall

One screen per spot. A spot without a scoreboard shows an ordinary wall screen with charts, like the others around the office.

Yomenie is a scoreboard, not an analytics tool. Your tools push finished numbers; Yomenie stores them, shows them and celebrates when they go up. The only counting it does itself is of your own tickets.

Read it

  • On the floor: each column is a label, the number and an arrow (up or down since yesterday or last week). Numbers are drawn in pixels, so they stay sharp at every zoom. A screen with nothing on it shows its name. Hover a screen to see its name.
  • Click a screen for its card: the screen’s metrics, then every other metric you’re allowed to see, each with its value, the change, the last 14 days, progress towards its target, where it comes from, when it was last updated and which screens show it (“On Hall, Platform”, or “Not on a screen”). A number that hasn’t been updated for a day (or its own limit) is shown as stale. Owners and admins see Edit in Settings and a link to fix a metric’s screens; an empty screen says “Nothing on this screen yet”.

Who sees what

Screens are public. Everyone on the floor sees every screen, and the same numbers on it, so a screen only shows metrics everyone in the workspace can see. A screen can belong to a team; that says where it belongs (and which boards Settings suggests for counting), and hides nothing.

Each metric is visible to everyone in the workspace, to owners and admins only (it carries a lock chip), or to one team. Metrics for owners and admins or for one team never go on a screen: they’re in Settings and in the screen cards’ lists, for the people allowed. Owners and admins see every metric, since they set them up. Agents never see metrics. The server sends each person only the metrics they may see.

A metric that’s on a screen stays visible to everyone: to make it more private, take it off its screens first.

Celebrations

A metric can celebrate when it goes up, when it first reaches its target in the current period, or when it beats its record. Your browser decides how to show it, from things that never leave your device:

  • On the floor page: every screen showing the metric glows amber and shows what happened, confetti falls in front of it, and a short gong plays. If none of those screens is near your view, you just get the pill.
  • Your status: focusing silences the gong; in a meeting or away, there’s no gong and no confetti.
  • Your sound: the speaker button (Shift+M) mutes the gong too.
  • Inside a private meeting room, or with reduced motion turned on in your system: no confetti.
  • On other pages: only a small pill above the dock, like “v0.1.33 · Releases today: 4 · Hall”, naming the screens it played on.

At most one celebration per metric every 10 seconds. Celebrations aren’t stored. A metric can also post a short message in a channel as Scoreboard (“Releases today: 4 (v0.1.31)”).

Set it up

Owners and admins manage screens and metrics in Settings → Scoreboard. Everyone else can read the page.

Screens

The Screens section lists every screen with its spot, its team and its metrics. New screen asks for a name, a free spot (by place, like “Hall, above the Support desks”), a team or the whole workspace, and up to three metrics in order (move them up and down). Count from board adds a counted metric for one board, the screen’s team’s boards first. Editing and deleting ask you to confirm. Changes show on the floor at once and are in the audit log.

Metrics

  1. Choose Add a metric: a name, a key (what tools push by, like releases_today), a format (number, currency with a three-letter code, or percent) and a source:
    • Push URL: your tools send the number.
    • Board: counted from your tickets: done today, done this week, or in review now, on every board or on one (Count from board).
    • By hand: you type the value in Settings.
  2. Pick when it resets (never, daily at midnight, weekly on Monday) and its timezone. A count that resets starts again from 0 after the boundary; yesterday’s number stays in its history.
  3. Add a target if you like (“10 per week”: for a daily count, the week’s days are added up), who can see it, which screens show it and what to celebrate. A new metric visible to everyone starts ticked for the Hall screen when it has room; leaving every screen unticked says so (“Add metric, not on a screen”). A screen has room for about ten letters per column: give it a short label for the screen (“IN REVIEW”), or it shows as many whole words of the name as fit.

Your AI tool can do all of this too, through MCP, if you’re an owner or admin and allowed “Manage workspace settings”. The push URL stays here.

Push numbers from your tools

The workspace has one push URL. Make it in Settings → Scoreboard → Push URL (confirm it’s you with your passkey or an email link). It’s shown once: copy it into your CI’s secrets.

curl -fsS -X POST "$YOMENIE_METRICS_URL" \
  -H 'content-type: application/json' \
  -d '{"key":"releases_today","increment":1,"note":"v0.1.31"}'
  • Send increment to add to the number, or value to set it.
  • note (or label), up to 120 characters, shows with the celebration.
  • An unknown key is a 404: pushes never create metrics. Board and by-hand metrics can’t be pushed (409).
  • Up to 60 pushes a minute per URL (429 with Retry-After beyond that).
  • Treat the URL like a password. Regenerate it if it leaks (the old one stops at once) or Revoke it. Changes to metrics and to the URL are in the audit log; pushed values aren’t.

Releases from a deploy job

Add the push as the last step of your deploy, after the health check, so it never fails a deploy:

if [ -n "$YOMENIE_METRICS_URL" ]; then
  curl -fsS -X POST "$YOMENIE_METRICS_URL" -H 'content-type: application/json' \
    -d "{\"key\":\"releases_today\",\"increment\":1,\"note\":\"$CI_COMMIT_TAG\"}" || echo "scoreboard push skipped"
fi

Store YOMENIE_METRICS_URL as a masked, protected CI/CD variable.