Niko-Niko Calendar

When to use

When you genuinely want to track mood over time — a stretch of difficult work, a new team finding its rhythm, a project the leadership team needs honest signal on. Run it for a fixed window (a sprint, a quarter), look at the pattern, then retire it. Skip it if you only plan to run it once or for a few days; one-shot Niko-Niko is the most common failure mode and produces nothing. Use Temperature Check or ESVP for single-meeting reads.

How it runs

1. Decide the window before you start

   A sprint is the minimum useful run. A quarter is the maximum before fatigue sets in. State the end date out loud — 'we're running this until the end of November' — and stick to it. Permanent installs go stale within weeks.

2. Pick public or anonymous

   Public-by-default is the historical version and produces the strongest signal because the patterns are visible. Anonymous works if your team won't be honest publicly — but then the format becomes a private dashboard, not a wall calendar. Pick one before day one; switching mid-run breaks the data.

3. Two minutes at end of day

   Each person places a dot — great, good, bad, horrible — at the same time each day. Slack reaction, shared sheet, Miro board. Consistency matters more than the tool; a missing day for half the team is more damaging than a scrappy interface.

4. Read the patterns weekly

   Look at the calendar at the same time each week. Three reds in a row from the same person is a signal — check in privately. A team-wide red Wednesday three weeks running is a structural thing — meeting overload, deploy day, whatever. The pattern is what you came for.

5. Retire it on schedule

   At the end of the window, look at the whole record together, decide what you learned, and stop. Either the team has the data (act on it) or they don't (the format wasn't fit for purpose). Permanent Niko-Niko is a sticker chart.

Why it works

Mood is a slow signal — one bad day means nothing, six bad days mean something structural. Niko-Niko gives the team a low-cost daily ritual that aggregates into a real pattern over weeks. The two-minute cost is small enough to sustain; the calendar visibility creates a soft accountability that surfaces patterns the team would otherwise miss. Public-by-default is what makes it work historically; anonymous trades signal for safety.

Variations

• Slack reactions — :smile: / :neutral_face: / :slightly_frowning_face: in a daily channel post. Lowest-friction remote version.
• Shared spreadsheet with cells coloured by person and day. Cleanest for trend reading; clunky to update.
• Anonymous version: each person submits via a private form, facilitator aggregates the daily totals. Loses individual patterns; preserves team-level trend.
• Three-colour variant: drop the four-state scale to good / okay / bad. Simpler, slightly less granular.

Facilitator notes

If three reds appear in a row from one person, check in privately — not publicly, not at the standup. The format's value is the early warning; weaponising it kills the team's willingness to be honest. If the team starts forgetting to dot, that itself is data — the format has stopped earning its place. Retire it sooner rather than later in that case.

Pitfalls

• Running it for a week and quitting. One week is noise; the format only justifies itself longitudinally.
• Treating it as permanent. Three months is generous; past that, the team's dotting on autopilot.
• Public-by-default on a team that won't be honest. Better to run anonymous than to collect performative greens.
• Ignoring the patterns. A wall of red that nobody acts on is worse than not asking — it tells the team their mood doesn't matter.

Remote tips

A Slack daily-mood channel with emoji reactions is the lowest-friction remote version. Pin a sheet that aggregates the reactions weekly so the trend is readable without scrolling. Avoid tools that require login or extra clicks — friction kills the cadence faster than anything else.

Example outputs

• Six weeks of dots, mostly green, two amber Wednesdays. Wednesday is the all-hands; the team's mood dips on meeting day. Move the meeting.
• Two weeks of solid red from one person; the rest of the team mostly green. Quiet conversation that week — they're underwater on something nobody else has noticed.
• Four weeks of declining greens, rising ambers, no reds yet. The trend is the warning shot; intervene before reds appear.

FAQ

Niko-Niko or Temperature Check?

Niko-Niko is daily-cadence longitudinal — answers 'is the team's mood declining over weeks?'. Temperature Check is single-meeting — answers 'is the room ready for this meeting?'. Different jobs. Don't substitute one for the other; they answer different questions on different timescales.

How long should I run it?

A sprint is the minimum useful run. A quarter is the practical maximum. Past three months, the team is dotting on autopilot and you're running a sticker chart. Set an end date before you start.

Public or anonymous?

Public if the team will be honest publicly — the format's historical strength. Anonymous if they won't — but then you lose individual pattern reading and only get the team aggregate. Pick once, before day one; switching mid-run nukes the data.

Related activities

Recommended use cases