[{"data":1,"prerenderedAt":522},["ShallowReactive",2],{"article-en-resources_en-town-hall-internal-communication-campaign":3},{"id":4,"title":5,"author":6,"body":7,"category":476,"cta":477,"description":504,"documentId":505,"extension":506,"featured":507,"image":508,"keywords":509,"locales":510,"meta":513,"metaTitle":514,"navigation":515,"path":516,"published":515,"publishedAt":517,"rawbody":518,"readingTime":490,"seo":519,"stem":512,"subtitle":520,"tags":509,"updatedAt":517,"__hash__":521},"resources_en/town-hall-internal-communication-campaign.md","One event, four weeks of impact: how to turn your town hall into a content campaign","Tim Adelmann",{"type":8,"value":9,"toc":456},"minimark",[10,14,17,20,25,28,31,39,48,52,55,58,61,65,68,75,78,89,95,101,105,112,115,118,131,139,143,146,149,152,157,160,171,176,179,190,195,198,209,219,223,226,360,363,371,375,378,384,390,396,403,407,410,413,416,420,425,428,432,435,439,442,446,449,453],[11,12,13],"p",{},"The all-hands ends. You send the recording to everyone who missed it. The slides go\ninto the intranet. You close your laptop and move on.",[11,15,16],{},"Three weeks later, a manager asks you what was actually decided at that meeting.",[11,18,19],{},"This isn't a story about one forgetful colleague. It's a description of how most\ninternal events end — not with a bang, but with a quiet disappearance. And it\npoints to where most internal communications investment silently goes to waste:\nnot in the planning of the event, but in everything that doesn't happen afterward.",[21,22,24],"h2",{"id":23},"the-effort-to-impact-gap","The effort-to-impact gap",[11,26,27],{},"Think about the last major all-hands your team ran. The prep time alone — speaker\nbriefings, leadership alignment, technical rehearsals, design iterations — likely\nspanned two to three weeks. The event itself: sixty minutes. The post-event\ncommunication: one email, one recording link, maybe a summary document written\nunder pressure the following morning.",[11,29,30],{},"The ratio is striking. Weeks of input for one hour of output, followed by a\nfollow-up strategy that's largely improvised.",[11,32,33,34,38],{},"This isn't a resourcing problem. It's a framing problem. Most internal teams think\nof an all-hands as an event with a beginning and an end. The more useful frame\nis to think of it as the ",[35,36,37],"strong",{},"centrepiece of a communication cycle"," — with a\nbefore, a during, and an after that each deserve deliberate attention.",[40,41,42],"callout",{},[11,43,44,47],{},[35,45,46],{},"The question worth asking:"," One week after your last town hall, how many\nemployees could name the three core messages? If the answer is uncertain, the\nproblem is rarely lack of interest. It's almost always that the message was\nsent once, through one channel, at one moment in time.",[21,49,51],{"id":50},"why-messages-dont-stick-after-a-single-broadcast","Why messages don't stick after a single broadcast",[11,53,54],{},"Memory research offers a useful frame here. Ebbinghaus's forgetting curve —\none of the most replicated findings in cognitive psychology — shows that under\npassive conditions, people forget roughly 70% of new information within 24\nhours and up to 90% within a week. Without active reinforcement, a message\ndelivered once is a message largely lost.",[11,56,57],{},"Internal communications adds a layer of complexity on top of this. Employees\naren't sitting in a quiet room absorbing your town hall. They're half-watching\non a laptop, fielding messages in another window, managing the reality of their\nactual workday at the same time. The live event is already competing for\nattention. The single follow-up email is competing with everything else in an\ninbox that's already full.",[11,59,60],{},"The solution isn't to shout louder or send more messages. It's to design a\ncommunication architecture that distributes the message across time and formats —\nso it finds employees where they are, not just when the calendar says the event happened.",[21,62,64],{"id":63},"phase-1-before-the-event-building-anticipation-not-just-logistics-week-2-to-0","Phase 1 — Before the event: building anticipation, not just logistics (week −2 to 0)",[11,66,67],{},"Most pre-event communication treats the town hall as a scheduling problem:\nget it on calendars, send a reminder, done. From a logistics perspective, that's\nsufficient. From a communication perspective, it's a significant missed opportunity.",[11,69,70,71,74],{},"The two weeks before an event are the only window you have to shape the mindset\nemployees bring with them. And that mindset has a direct effect on how much they\nretain. Cognitive research on the ",[35,72,73],{},"pre-exposure effect"," shows that people\nprocess and remember information more deeply when they've encountered the topic\nbeforehand — even briefly, even casually.",[11,76,77],{},"Three pre-event formats that actually move the needle:",[11,79,80,83,84,88],{},[35,81,82],{},"A teaser with real substance:"," Not \"we look forward to seeing you\" — but a\nshort clip from a senior leader that raises a genuine question without answering\nit. ",[85,86,87],"em",{},"\"We've made a decision this quarter that changes how we think about X.\nWe'll walk through the reasoning live on Thursday.\""," This creates genuine\ncuriosity rather than a compliance-driven obligation to attend.",[11,90,91,94],{},[35,92,93],{},"A pre-event survey with a visible payoff:"," Two or three questions that show\nthe agenda was shaped around what employees are actually thinking about — not\nonly what leadership wants to communicate. Opening the event by showing the\nsurvey results is one of the simplest trust signals in internal communications:\nwe listened before we spoke.",[11,96,97,100],{},[35,98,99],{},"Advance question submissions:"," Employees who've already submitted a question\narrive invested. They have a personal stake in the event before it begins.\nAnd they're far less likely to drift if their question is still unanswered.",[21,102,104],{"id":103},"phase-2-during-the-event-producing-content-not-just-delivering-it","Phase 2 — During the event: producing content, not just delivering it",[11,106,107,108,111],{},"The live event is your communication moment. It's also your ",[35,109,110],{},"content\nproduction window"," for everything that comes after.",[11,113,114],{},"The difference between teams that extract three assets from a town hall and\nthose that extract ten rarely comes down to budget or team size. It comes\ndown to whether someone decided beforehand which content would be repurposed —\nand planned for it.",[11,116,117],{},"In practice, that means three things decided before the event goes live:",[119,120,121,125,128],"ul",{},[122,123,124],"li",{},"Identify two or three segments that will work as standalone short clips —\na CEO statement, a key announcement, a moment of unusual clarity on a\ncomplex topic",[122,126,127],{},"Structure the Q&A documentation in real time as categorisable units\n(topic, question, answer, any open items) rather than freeform notes",[122,129,130],{},"Designate one person whose only job during the event is structured\ncontent capture — not moderation, not technical support, just\nsystematic documentation",[40,132,133],{},[11,134,135,138],{},[35,136,137],{},"One role change, significant return:"," The content capture role sounds\nminor. In practice, it's the difference between a post-event summary that\ntakes 30 minutes to write and one that takes three hours of reconstructive\nwork the day after.",[21,140,142],{"id":141},"phase-3-after-the-event-this-is-where-the-campaign-begins-weeks-14","Phase 3 — After the event: this is where the campaign begins (weeks 1–4)",[11,144,145],{},"This is where most teams stop thinking strategically — and where the\nhighest-leverage communication work actually happens.",[11,147,148],{},"The challenge isn't motivation. Most IC professionals know they should do\nmore after an event. The challenge is structure: what gets created, for whom,\nthrough which channel, by when. Without a clear framework, post-event\ncommunication either gets skipped or becomes reactive, rushed, and under-resourced.",[11,150,151],{},"Here's a concrete four-week model — scalable to your team size and cadence.",[11,153,154],{},[35,155,156],{},"Days 1–2: the immediate package",[11,158,159],{},"This window is the most critical. Employees who attended are still in context.\nEmployees who missed it are wondering what they need to know. Both represent\na communication opportunity — but only if you move quickly.",[119,161,162,165,168],{},[122,163,164],{},"Three headline takeaways from the event (not a full summary — half a\nscreen at most, written for someone who wasn't there)",[122,166,167],{},"The top five Q&A questions with written answers — in plain language,\nnot meeting-speak",[122,169,170],{},"Recording link with chapter markers, so no one needs to scrub through\n60 minutes to find what's relevant to them",[11,172,173],{},[35,174,175],{},"Week 1–2: the depth layer",[11,177,178],{},"Not every message needs immediate depth. But the topics that generated the\nmost questions in the room deserve a second communication wave — one that goes\nbeyond \"here's the recording.\"",[119,180,181,184,187],{},[122,182,183],{},"A 60–90 second clip of the event's strongest content moment, packaged\nas a standalone asset that works without the surrounding context",[122,185,186],{},"A short intranet post or follow-up article on the topic that raised the\nmost questions — with an explicit invitation to continue the conversation",[122,188,189],{},"A manager briefing document: not the full event replay, but a one-page\ntranslation of the key messages into team-level language. \"What does this\nmean for us, specifically?\" is the only question employees ultimately care\nabout — and only their direct manager can credibly answer it",[11,191,192],{},[35,193,194],{},"Weeks 3–4: the long tail",[11,196,197],{},"Most internal teams have mentally moved on by this point. That's precisely\nwhy content in this window is disproportionately effective.",[119,199,200,203,206],{},[122,201,202],{},"A concrete progress update on whatever was announced or committed to in\nthe event. \"We said we'd do X. Here's where we are.\" This is one of\nthe most powerful trust signals in internal communications — and one\nof the most consistently underused",[122,204,205],{},"Targeted surface of on-demand content for employees who've since hit\na relevant moment in their own work — a new team member who just joined,\nsomeone now working on a project that was announced at the event",[122,207,208],{},"Early teaser for the next event, with an explicit callback to the last one:\n\"At the last all-hands, many of you asked about Y. Here's what's happened\nsince — and what we'll be covering next.\"",[11,210,211,212],{},"→ ",[213,214,218],"a",{"href":215,"rel":216},"https://contenthub.meetyoo.com/ai-features",[217],"nofollow","How MEETYOO automatically generates chapters, summaries and a searchable\narchive from a single live event",[21,220,222],{"id":221},"what-one-well-documented-town-hall-actually-produces","What one well-documented town hall actually produces",[11,224,225],{},"To make this concrete:",[227,228,229,248],"table",{},[230,231,232],"thead",{},[233,234,235,239,242,245],"tr",{},[236,237,238],"th",{},"Asset",[236,240,241],{},"Format",[236,243,244],{},"Channel",[236,246,247],{},"Timing",[249,250,251,266,279,293,307,320,333,346],"tbody",{},[233,252,253,257,260,263],{},[254,255,256],"td",{},"Three-point summary",[254,258,259],{},"Text",[254,261,262],{},"Email / intranet",[254,264,265],{},"Day 1",[233,267,268,271,273,276],{},[254,269,270],{},"Top 5 Q&A in writing",[254,272,259],{},[254,274,275],{},"Intranet / FAQ",[254,277,278],{},"Day 2",[233,280,281,284,287,290],{},[254,282,283],{},"Recording with chapter markers",[254,285,286],{},"Video",[254,288,289],{},"On-demand",[254,291,292],{},"Day 1–2",[233,294,295,298,301,304],{},[254,296,297],{},"CEO / leadership clip",[254,299,300],{},"Short video (60–90s)",[254,302,303],{},"Intranet / team chat",[254,305,306],{},"Week 1",[233,308,309,312,314,317],{},[254,310,311],{},"Deep-dive post on key topic",[254,313,259],{},[254,315,316],{},"Intranet",[254,318,319],{},"Week 1–2",[233,321,322,325,328,331],{},[254,323,324],{},"Manager briefing doc",[254,326,327],{},"One-pager",[254,329,330],{},"Internal",[254,332,306],{},[233,334,335,338,341,343],{},[254,336,337],{},"Progress update on commitments",[254,339,340],{},"Short update",[254,342,262],{},[254,344,345],{},"Week 3–4",[233,347,348,351,354,357],{},[254,349,350],{},"Teaser for next event",[254,352,353],{},"Text / clip",[254,355,356],{},"Email",[254,358,359],{},"Week 4",[11,361,362],{},"None of this is hypothetical. Every asset in this list is extractable from a single\n60-minute event — if you decide in advance to extract it.",[40,364,365],{},[11,366,367,370],{},[35,368,369],{},"The key shift:"," you're not creating new content. You're curating and\ndistributing content that was produced during the event anyway. The\ninvestment is in structure, not in additional production.",[21,372,374],{"id":373},"why-this-works-for-everyone-not-just-the-communications-team","Why this works for everyone, not just the communications team",[11,376,377],{},"It's easy to read this framework as more work for an already stretched\nIC function. In practice, when it's built into the workflow rather than\nadded on top of it, it reduces reactive work significantly.",[11,379,380,383],{},[35,381,382],{},"For employees:"," the message reaches them when and where it's relevant to\ntheir actual work — not only when the calendar said the event was happening.\nCommunication finds them, rather than requiring them to find it.",[11,385,386,389],{},[35,387,388],{},"For senior leaders:"," their statements work harder. A clear position from\nthe CEO, pulled as a standalone clip and shared a week after the town hall,\nlands with more focus and attention than the same words delivered mid-event\nto a partially distracted audience.",[11,391,392,395],{},[35,393,394],{},"For the IC function itself:"," a structured content strategy is far easier to\ndefend than a collection of reactive one-offs. When leadership asks why the\nmessage didn't land, \"we communicated it across eight touchpoints over four\nweeks\" is a credible answer. \"We sent it at the all-hands\" is not.",[11,397,211,398],{},[213,399,402],{"href":400,"rel":401},"https://contenthub.meetyoo.com/engagement",[217],"How to make your internal event engagement and reach measurable",[21,404,406],{"id":405},"conclusion-the-event-is-the-beginning-not-the-destination","Conclusion: the event is the beginning, not the destination",[11,408,409],{},"A town hall that ends when the stream goes offline was always going to\nunderperform. Not because the content was poor or the production was inadequate —\nbut because a single broadcast moment was never designed to do the work of\na sustained communication strategy.",[11,411,412],{},"The teams that treat internal events as the centrepiece of a deliberate campaign —\nwith structured phases before, during, and after the live moment — don't just\nreach more employees. They build something harder to manufacture and more\nvaluable than any single event: the expectation that internal communication means\nsomething. That announcements have follow-through. That the next event is worth\nshowing up for, because the last one was.",[11,414,415],{},"One event. Four weeks. A campaign worth running.",[21,417,419],{"id":418},"faq","FAQ",[421,422,424],"h3",{"id":423},"how-much-additional-time-does-this-approach-realistically-require","How much additional time does this approach realistically require?",[11,426,427],{},"The largest investment is upfront — building the workflow and role assignments the\nfirst time. Once the framework exists, the incremental time per event is roughly\ntwo to three hours: one for structured content capture during the event, one for\nthe immediate package the following day, and one for coordinating the follow-up\nassets. Much of that can be parallelised across team members.",[421,429,431],{"id":430},"what-if-the-town-hall-doesnt-contain-major-announcements","What if the town hall doesn't contain major announcements?",[11,433,434],{},"Not every all-hands is a landmark event. But every event contains something\nemployees are still thinking about afterward — a question from the Q&A, a\nleadership comment that needs context, a metric that raises more questions than\nit answers. The starting point isn't \"what was spectacular?\" It's \"what will\nemployees still be wondering about tomorrow?\" That's your post-event content.",[421,436,438],{"id":437},"how-do-you-serve-employees-who-missed-the-live-event","How do you serve employees who missed the live event?",[11,440,441],{},"The immediate package — summary, Q&A in writing, recording with chapter markers —\nis designed specifically for this group. The critical design principle is that\neach asset should stand alone, without requiring the full event as context. No\nreferences to \"what we discussed earlier.\" Self-contained, navigable, accessible\nwhenever is relevant to each person.",[421,443,445],{"id":444},"should-every-manager-do-their-own-follow-up-communication","Should every manager do their own follow-up communication?",[11,447,448],{},"Yes — but as a local translation, not a repetition. \"What does this mean for our\nteam specifically?\" is the question employees actually want answered, and it's the\none only their direct manager can credibly provide. A brief briefing document (three\nto five bullet points) from the IC team gives managers the foundation without\nasking them to reconstruct the whole event themselves.",[421,450,452],{"id":451},"how-do-you-build-this-structure-when-theres-no-dedicated-ic-team","How do you build this structure when there's no dedicated IC team?",[11,454,455],{},"Start with the immediate package only — it has the highest leverage for the\nleast effort. Then add one element per event: a pre-event survey the next time,\na leadership clip the time after that. The approach works incrementally. What\nit doesn't work as is improvisation — the decision to do it at all needs to\nhappen before the event, not after.",{"title":457,"searchDepth":458,"depth":458,"links":459},"",2,[460,461,462,463,464,465,466,467,468],{"id":23,"depth":458,"text":24},{"id":50,"depth":458,"text":51},{"id":63,"depth":458,"text":64},{"id":103,"depth":458,"text":104},{"id":141,"depth":458,"text":142},{"id":221,"depth":458,"text":222},{"id":373,"depth":458,"text":374},{"id":405,"depth":458,"text":406},{"id":418,"depth":458,"text":419,"children":469},[470,472,473,474,475],{"id":423,"depth":471,"text":424},3,{"id":430,"depth":471,"text":431},{"id":437,"depth":471,"text":438},{"id":444,"depth":471,"text":445},{"id":451,"depth":471,"text":452},"Insights & Learnings",[478,482],{"type":479,"label":480,"buttonLabel":481},"request-demo-cta","See how MEETYOO turns your next town hall into a four-week communication campaign","Book a demo",{"type":483,"label":484,"referencedArticles":485},"referenced-articles","Keep reading: strengthen your internal communications strategy",[486,493,499],{"title":487,"subtitle":488,"category":489,"readingTime":490,"slug":491,"image":492},"The passive audience problem: why your all-hands meeting isn't reaching the people in it","Why employees mentally check out during company-wide meetings — and what you can actually do about it","Use Cases & Industries",12,"all-hands-meeting-passive-audience-engagement","/uploads/medium_Editorial_photography_natural_light_office_enviro_2026_04_11_98302bbe5e.png",{"title":494,"subtitle":495,"category":476,"readingTime":496,"slug":497,"image":498},"Change communication that actually lands: how to get employees to hear the message, not just receive it","Why a single town hall isn't enough—and how to build a content cascade that drives real behavior change",16,"change-communication-strategy-internal-comms","/uploads/medium_2c15b44c_1665_4d50_80ca_04bd12397b22_d5f7c15485.jpeg",{"title":500,"subtitle":501,"category":489,"readingTime":471,"slug":502,"image":503},"From Meeting to Momentum: How to Transform Your All-Hands Events into Measurable Success","Attendance numbers alone mean nothing. Discover the four crucial metrics that finally prove the true success of your internal communication.","all-hands-events-in-messbare-erfolge-verwandeln","/uploads/medium_all_hands_meeting_erfolg_messen_1947891f1f.jpg","Most town halls vanish within 48 hours of ending. Learn how to turn a single company event into a four-week internal communication campaign — with a practical framework.","sk4wgnjoj7knc6g5od0gdw7l","md",false,"/uploads/medium_Editorial_photography_natural_office_light_late_2026_04_11_c2d7260f46.png",null,{"de":511,"en":512},"town-hall-kommunikationskampagne-content-strategie","town-hall-internal-communication-campaign",{},"One event, four weeks of impact: your town hall as a content campaign",true,"/town-hall-internal-communication-campaign","2026-04-11","---\ndocumentId: sk4wgnjoj7knc6g5od0gdw7l\nlocales:\n  de: town-hall-kommunikationskampagne-content-strategie\n  en: town-hall-internal-communication-campaign\ntitle: \"One event, four weeks of impact: how to turn your town hall into a\n  content campaign\"\nmetaTitle: \"One event, four weeks of impact: your town hall as a content campaign\"\nsubtitle: Why the stream going offline is the beginning of your communication\n  strategy, not the end of it\ndescription: Most town halls vanish within 48 hours of ending. Learn how to turn\n  a single company event into a four-week internal communication campaign — with\n  a practical framework.\nauthor: Tim Adelmann\npublishedAt: 2026-04-11\nupdatedAt: 2026-04-11\ncategory: Insights & Learnings\nreadingTime: 12\npublished: true\ncta:\n  - type: request-demo-cta\n    label: See how MEETYOO turns your next town hall into a four-week communication\n      campaign\n    buttonLabel: Book a demo\n  - type: referenced-articles\n    label: \"Keep reading: strengthen your internal communications strategy\"\n    referencedArticles:\n      - title: \"The passive audience problem: why your all-hands meeting isn't reaching\n          the people in it\"\n        subtitle: Why employees mentally check out during company-wide meetings — and\n          what you can actually do about it\n        category: Use Cases & Industries\n        readingTime: 12\n        slug: all-hands-meeting-passive-audience-engagement\n        image: /uploads/medium_Editorial_photography_natural_light_office_enviro_2026_04_11_98302bbe5e.png\n      - title: \"Change communication that actually lands: how to get employees to hear\n          the message, not just receive it\"\n        subtitle: Why a single town hall isn't enough—and how to build a content cascade\n          that drives real behavior change\n        category: Insights & Learnings\n        readingTime: 16\n        slug: change-communication-strategy-internal-comms\n        image: /uploads/medium_2c15b44c_1665_4d50_80ca_04bd12397b22_d5f7c15485.jpeg\n      - title: \"From Meeting to Momentum: How to Transform Your All-Hands Events into\n          Measurable Success\"\n        subtitle: Attendance numbers alone mean nothing. Discover the four crucial\n          metrics that finally prove the true success of your internal\n          communication.\n        category: Use Cases & Industries\n        readingTime: 3\n        slug: all-hands-events-in-messbare-erfolge-verwandeln\n        image: /uploads/medium_all_hands_meeting_erfolg_messen_1947891f1f.jpg\nimage: /uploads/medium_Editorial_photography_natural_office_light_late_2026_04_11_c2d7260f46.png\n---\nThe all-hands ends. You send the recording to everyone who missed it. The slides go\ninto the intranet. You close your laptop and move on.\n\nThree weeks later, a manager asks you what was actually decided at that meeting.\n\nThis isn't a story about one forgetful colleague. It's a description of how most\ninternal events end — not with a bang, but with a quiet disappearance. And it\npoints to where most internal communications investment silently goes to waste:\nnot in the planning of the event, but in everything that doesn't happen afterward.\n\n## The effort-to-impact gap\n\nThink about the last major all-hands your team ran. The prep time alone — speaker\nbriefings, leadership alignment, technical rehearsals, design iterations — likely\nspanned two to three weeks. The event itself: sixty minutes. The post-event\ncommunication: one email, one recording link, maybe a summary document written\nunder pressure the following morning.\n\nThe ratio is striking. Weeks of input for one hour of output, followed by a\nfollow-up strategy that's largely improvised.\n\nThis isn't a resourcing problem. It's a framing problem. Most internal teams think\nof an all-hands as an event with a beginning and an end. The more useful frame\nis to think of it as the **centrepiece of a communication cycle** — with a\nbefore, a during, and an after that each deserve deliberate attention.\n\n:::callout\n**The question worth asking:** One week after your last town hall, how many\nemployees could name the three core messages? If the answer is uncertain, the\nproblem is rarely lack of interest. It's almost always that the message was\nsent once, through one channel, at one moment in time.\n:::\n\n## Why messages don't stick after a single broadcast\n\nMemory research offers a useful frame here. Ebbinghaus's forgetting curve —\none of the most replicated findings in cognitive psychology — shows that under\npassive conditions, people forget roughly 70% of new information within 24\nhours and up to 90% within a week. Without active reinforcement, a message\ndelivered once is a message largely lost.\n\nInternal communications adds a layer of complexity on top of this. Employees\naren't sitting in a quiet room absorbing your town hall. They're half-watching\non a laptop, fielding messages in another window, managing the reality of their\nactual workday at the same time. The live event is already competing for\nattention. The single follow-up email is competing with everything else in an\ninbox that's already full.\n\nThe solution isn't to shout louder or send more messages. It's to design a\ncommunication architecture that distributes the message across time and formats —\nso it finds employees where they are, not just when the calendar says the event happened.\n\n## Phase 1 — Before the event: building anticipation, not just logistics (week −2 to 0)\n\nMost pre-event communication treats the town hall as a scheduling problem:\nget it on calendars, send a reminder, done. From a logistics perspective, that's\nsufficient. From a communication perspective, it's a significant missed opportunity.\n\nThe two weeks before an event are the only window you have to shape the mindset\nemployees bring with them. And that mindset has a direct effect on how much they\nretain. Cognitive research on the **pre-exposure effect** shows that people\nprocess and remember information more deeply when they've encountered the topic\nbeforehand — even briefly, even casually.\n\nThree pre-event formats that actually move the needle:\n\n**A teaser with real substance:** Not \"we look forward to seeing you\" — but a\nshort clip from a senior leader that raises a genuine question without answering\nit. *\"We've made a decision this quarter that changes how we think about X.\nWe'll walk through the reasoning live on Thursday.\"* This creates genuine\ncuriosity rather than a compliance-driven obligation to attend.\n\n**A pre-event survey with a visible payoff:** Two or three questions that show\nthe agenda was shaped around what employees are actually thinking about — not\nonly what leadership wants to communicate. Opening the event by showing the\nsurvey results is one of the simplest trust signals in internal communications:\nwe listened before we spoke.\n\n**Advance question submissions:** Employees who've already submitted a question\narrive invested. They have a personal stake in the event before it begins.\nAnd they're far less likely to drift if their question is still unanswered.\n\n## Phase 2 — During the event: producing content, not just delivering it\n\nThe live event is your communication moment. It's also your **content\nproduction window** for everything that comes after.\n\nThe difference between teams that extract three assets from a town hall and\nthose that extract ten rarely comes down to budget or team size. It comes\ndown to whether someone decided beforehand which content would be repurposed —\nand planned for it.\n\nIn practice, that means three things decided before the event goes live:\n\n- Identify two or three segments that will work as standalone short clips —\na CEO statement, a key announcement, a moment of unusual clarity on a\ncomplex topic\n- Structure the Q&A documentation in real time as categorisable units\n(topic, question, answer, any open items) rather than freeform notes\n- Designate one person whose only job during the event is structured\ncontent capture — not moderation, not technical support, just\nsystematic documentation\n\n:::callout\n**One role change, significant return:** The content capture role sounds\nminor. In practice, it's the difference between a post-event summary that\ntakes 30 minutes to write and one that takes three hours of reconstructive\nwork the day after.\n:::\n\n## Phase 3 — After the event: this is where the campaign begins (weeks 1–4)\n\nThis is where most teams stop thinking strategically — and where the\nhighest-leverage communication work actually happens.\n\nThe challenge isn't motivation. Most IC professionals know they should do\nmore after an event. The challenge is structure: what gets created, for whom,\nthrough which channel, by when. Without a clear framework, post-event\ncommunication either gets skipped or becomes reactive, rushed, and under-resourced.\n\nHere's a concrete four-week model — scalable to your team size and cadence.\n\n**Days 1–2: the immediate package**\n\nThis window is the most critical. Employees who attended are still in context.\nEmployees who missed it are wondering what they need to know. Both represent\na communication opportunity — but only if you move quickly.\n\n- Three headline takeaways from the event (not a full summary — half a\nscreen at most, written for someone who wasn't there)\n- The top five Q&A questions with written answers — in plain language,\nnot meeting-speak\n- Recording link with chapter markers, so no one needs to scrub through\n60 minutes to find what's relevant to them\n\n**Week 1–2: the depth layer**\n\nNot every message needs immediate depth. But the topics that generated the\nmost questions in the room deserve a second communication wave — one that goes\nbeyond \"here's the recording.\"\n\n- A 60–90 second clip of the event's strongest content moment, packaged\nas a standalone asset that works without the surrounding context\n- A short intranet post or follow-up article on the topic that raised the\nmost questions — with an explicit invitation to continue the conversation\n- A manager briefing document: not the full event replay, but a one-page\ntranslation of the key messages into team-level language. \"What does this\nmean for us, specifically?\" is the only question employees ultimately care\nabout — and only their direct manager can credibly answer it\n\n**Weeks 3–4: the long tail**\n\nMost internal teams have mentally moved on by this point. That's precisely\nwhy content in this window is disproportionately effective.\n\n- A concrete progress update on whatever was announced or committed to in\nthe event. \"We said we'd do X. Here's where we are.\" This is one of\nthe most powerful trust signals in internal communications — and one\nof the most consistently underused\n- Targeted surface of on-demand content for employees who've since hit\na relevant moment in their own work — a new team member who just joined,\nsomeone now working on a project that was announced at the event\n- Early teaser for the next event, with an explicit callback to the last one:\n\"At the last all-hands, many of you asked about Y. Here's what's happened\nsince — and what we'll be covering next.\"\n\n→ [How MEETYOO automatically generates chapters, summaries and a searchable\narchive from a single live event](https://contenthub.meetyoo.com/ai-features)\n\n## What one well-documented town hall actually produces\n\nTo make this concrete:\n\n| Asset | Format | Channel | Timing |\n|---|---|---|---|\n| Three-point summary | Text | Email / intranet | Day 1 |\n| Top 5 Q&A in writing | Text | Intranet / FAQ | Day 2 |\n| Recording with chapter markers | Video | On-demand | Day 1–2 |\n| CEO / leadership clip | Short video (60–90s) | Intranet / team chat | Week 1 |\n| Deep-dive post on key topic | Text | Intranet | Week 1–2 |\n| Manager briefing doc | One-pager | Internal | Week 1 |\n| Progress update on commitments | Short update | Email / intranet | Week 3–4 |\n| Teaser for next event | Text / clip | Email | Week 4 |\n\nNone of this is hypothetical. Every asset in this list is extractable from a single\n60-minute event — if you decide in advance to extract it.\n\n:::callout\n**The key shift:** you're not creating new content. You're curating and\ndistributing content that was produced during the event anyway. The\ninvestment is in structure, not in additional production.\n:::\n\n## Why this works for everyone, not just the communications team\n\nIt's easy to read this framework as more work for an already stretched\nIC function. In practice, when it's built into the workflow rather than\nadded on top of it, it reduces reactive work significantly.\n\n**For employees:** the message reaches them when and where it's relevant to\ntheir actual work — not only when the calendar said the event was happening.\nCommunication finds them, rather than requiring them to find it.\n\n**For senior leaders:** their statements work harder. A clear position from\nthe CEO, pulled as a standalone clip and shared a week after the town hall,\nlands with more focus and attention than the same words delivered mid-event\nto a partially distracted audience.\n\n**For the IC function itself:** a structured content strategy is far easier to\ndefend than a collection of reactive one-offs. When leadership asks why the\nmessage didn't land, \"we communicated it across eight touchpoints over four\nweeks\" is a credible answer. \"We sent it at the all-hands\" is not.\n\n→ [How to make your internal event engagement and reach measurable](https://contenthub.meetyoo.com/engagement)\n\n## Conclusion: the event is the beginning, not the destination\n\nA town hall that ends when the stream goes offline was always going to\nunderperform. Not because the content was poor or the production was inadequate —\nbut because a single broadcast moment was never designed to do the work of\na sustained communication strategy.\n\nThe teams that treat internal events as the centrepiece of a deliberate campaign —\nwith structured phases before, during, and after the live moment — don't just\nreach more employees. They build something harder to manufacture and more\nvaluable than any single event: the expectation that internal communication means\nsomething. That announcements have follow-through. That the next event is worth\nshowing up for, because the last one was.\n\nOne event. Four weeks. A campaign worth running.\n\n## FAQ\n\n### How much additional time does this approach realistically require?\nThe largest investment is upfront — building the workflow and role assignments the\nfirst time. Once the framework exists, the incremental time per event is roughly\ntwo to three hours: one for structured content capture during the event, one for\nthe immediate package the following day, and one for coordinating the follow-up\nassets. Much of that can be parallelised across team members.\n\n### What if the town hall doesn't contain major announcements?\nNot every all-hands is a landmark event. But every event contains something\nemployees are still thinking about afterward — a question from the Q&A, a\nleadership comment that needs context, a metric that raises more questions than\nit answers. The starting point isn't \"what was spectacular?\" It's \"what will\nemployees still be wondering about tomorrow?\" That's your post-event content.\n\n### How do you serve employees who missed the live event?\nThe immediate package — summary, Q&A in writing, recording with chapter markers —\nis designed specifically for this group. The critical design principle is that\neach asset should stand alone, without requiring the full event as context. No\nreferences to \"what we discussed earlier.\" Self-contained, navigable, accessible\nwhenever is relevant to each person.\n\n### Should every manager do their own follow-up communication?\nYes — but as a local translation, not a repetition. \"What does this mean for our\nteam specifically?\" is the question employees actually want answered, and it's the\none only their direct manager can credibly provide. A brief briefing document (three\nto five bullet points) from the IC team gives managers the foundation without\nasking them to reconstruct the whole event themselves.\n\n### How do you build this structure when there's no dedicated IC team?\nStart with the immediate package only — it has the highest leverage for the\nleast effort. Then add one element per event: a pre-event survey the next time,\na leadership clip the time after that. The approach works incrementally. What\nit doesn't work as is improvisation — the decision to do it at all needs to\nhappen before the event, not after.\n",{"title":5,"description":504},"Why the stream going offline is the beginning of your communication strategy, not the end of it","hIrB2wCU33BPvo3xTLZT6iQdd-mwi_tlKIUsAnkROGc",1776535698883]