{"id":5003451,"date":"2015-12-17T01:00:21","date_gmt":"2015-12-17T09:00:21","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&#038;p=5003451"},"modified":"2023-03-08T15:58:14","modified_gmt":"2023-03-08T23:58:14","slug":"niko-niko","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/niko-niko\/","title":{"rendered":"Niko-niko Calendar"},"content":{"rendered":"<p>The team installs a&nbsp;<a href=\"https:\/\/sites.google.com\/view\/niko-niko-calendar\/home\/en\" target=\"_blank\" rel=\"noopener noreferrer\">calendar<\/a> on one of the room\u2019s walls. The format of the calendar allows each team member to record, at the end of every workday, a graphic evaluation of their mood during that day. This can be either a hand-drawn \u201cemoticon\u201d, or a colored sticker, following a simple color code, for instance: blue for a bad day, red for neutral, yellow for a good day. Over time, the niko-niko calendar reveals patterns of change in the moods of the team, or of individual members.<\/p>\n<h2><img fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/agilealliance.org\/wp-content\/uploads\/2015\/12\/Niko-NikoCalendar.png\" alt=\"\" width=\"800\" height=\"432\"><\/h2>\n<p>Picture from&nbsp;<a href=\"https:\/\/agilealliance.org\/resources\/sessions\/portfolio-visualization-and-prioritization-for-business-agility-workshop\/\">Portfolio Visualization and Prioritization for Business Agility \u2013 Workshop<\/a><\/p>\n<h2>Also Known As<\/h2>\n<p>The Japanese word \u201cniko\u201d means \u201csmile\u201d; following a common pattern of word doubling in Japanese, \u201cniko-niko\u201d has a meaning closer to \u201csmiley\u201d. The term \u201cmood board\u201d is also seen. It is an&nbsp;<a href=\"https:\/\/agilealliance.org\/glossary\/information-radiators\/\">information radiator<\/a>.<\/p>\n<h2>Expected Benefits<\/h2>\n<p>The value of this practice lies in making somewhat objective an important element of team performance \u2013 motivation or well-being \u2013 which is generally seen as entirely subjective and thus impossible to measure and track. This may be seen as an illustration of the Gilb Measurability Principle: \u201canything you need to quantify can be measured in some way that is superior to not measuring it at all.\u201d In other words, a measurement does not have to be perfect or even very precise, as long as your intent is to get a quantitative handle on something that was previously purely qualitative; the important thing is to take that first step toward quantifying.<\/p>\n<h2>Common Pitfalls<\/h2>\n<p>As with other activities, such as&nbsp;<a href=\"https:\/\/agilealliance.org\/glossary\/heartbeatretro\/\">retrospectives<\/a>, where team members are asked to report subjective feelings, self-censorship is always a risk. This could be the case, for instance, if team members who report poor days are blamed for \u201cwhining\u201d, by management or by teammates.<\/p>\n<h2>Origins<\/h2>\n<ul>\n<li>2001: among the visualizations described in Norm Kerth\u2019s \u201cProject Retrospectives\u201d, the \u201cEnergy Seismograph\u201d can perhaps be seen as a forerunner of the niko-niko calendar<\/li>\n<li>2006: niko-niko calendars are first described by Akinori Sakata in&nbsp;<a href=\"https:\/\/sites.google.com\/view\/niko-niko-calendar\/home\/en\" target=\"_blank\" rel=\"noopener noreferrer\">this Web article<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>A Niko-niko Calendar is updated daily with each team member&#8217;s mood for that day. Over time the calendar reveals patterns of change in the moods of the team, or of individual members.<\/p>\n","protected":false},"author":8027401,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[908],"tags":[],"class_list":["post-5003451","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-process"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003451","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8027401"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003451"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003451\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=5003451"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003451"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}