{"id":"res-mgr-no-meeting-day-research","audience":"managers","category":"research","technique":"audience","title":"Share what a no-meeting-day study found, in a Slack post","free":false,"task":"Your team asked whether you'll try no-meeting Wednesdays, and you found one study on it. You want a Slack post of at most 3 sentences in plain text that gives the study's main finding, the study limit that matters most for your customer operations team, and that you'll decide at the Nov 20 team meeting. Use only the study summary, not the blog post that cited it, and don't promise the change.","materialLabel":"The study summary and a blog post about it (attached to your prompt automatically)","material":"STUDY SUMMARY - \"Meeting-Free Days and Self-Reported Productivity\"\nKessler Institute for Work Design, 2025\nSample: 76 companies, mostly tech and finance firms with 200-5,000 employees, surveyed before and 6 months after adopting one or more meeting-free days per week.\nFindings:\n- With one meeting-free day a week, self-reported productivity rose 35% on average.\n- Self-reported stress fell 26%.\n- Companies with three or more meeting-free days saw collaboration scores drop.\nLimits: All results are self-reported. Companies chose to adopt the policy, so the study cannot show the policy caused the changes. No customer service or operations teams were included.\n\n-----\nBLOG POST - \"No-Meeting Days Double Productivity!\" (WorkHacks Daily)\n\"A big new study shows no-meeting days double productivity and cut stress in half. Every team should do it.\"\n\n-----\nShared by a reader in the comments: \"we tried it and loved it.\"","rules":[{"type":"maxSentences","max":3},{"type":"plainText"}],"mistakes":[{"title":"Repeating the blog's spin","why":"The blog headline is catchy and the AI may use its 'double productivity' claim.","fix":"Say: \"Use only the study summary, not the blog post.\"","checks":["r0"]},{"title":"Skipping the fine print","why":"A short post drops limits first, but the study didn't include teams like yours.","fix":"Add: \"Name one limit of the study.\"","checks":["r1"]},{"title":"Sounding like a promise","why":"The AI writes an upbeat announcement, and your team reads it as a done deal.","fix":"Say: \"We'll decide on Nov 20. Don't promise the change.\"","checks":["r2"]},{"title":"Not capping the length","why":"The AI writes several paragraphs by default, far more than the reader will take in.","fix":"Say: \"at most 3 sentences.\"","checks":["maxSentences"]},{"title":"Getting markdown back","why":"AI defaults to bold labels and headings, which show up as stray symbols in Slack.","fix":"Ask for \"plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Picks the right source","patterns":["study summary","not the blog","ignore.{0,20}blog","only.{0,20}study"]},{"label":"Asks for a limit","patterns":["limit","caveat","self.?reported","can't prove"]},{"label":"Says what's next","patterns":["nov(ember)?\\.? 20","decide","team meeting"]},{"label":"Caps the number of sentences","patterns":["\\d+\\s*sentences","(two|three|four|five) sentences","sentence"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"Secondhand write-ups inflate research. Point the AI at the original, ask for a limit that matters to your team, and say what happens next.","rubricLabels":["Gives the study's own finding (self-reported productivity up about 35% and/or stress down 26% with one meeting-free day), not the blog's 'double productivity' or 'cut stress in half'","Says the study did not include customer service or operations teams (the limit that matters for this team)","Mentions deciding at the Nov 20 team meeting and does not promise the team will adopt no-meeting Wednesdays"]}