A newsroom lunch and learn is a voluntary 60-minute session held during the lunch break in which one person on staff teaches everyone else one specific reporting skill, such as verification, records requests, data work or on-air preparation. That is the whole trick to how to run a lunch and learn for reporters: one real problem, one demonstrable skill, one hour, and something archived afterwards.
Other names for the same format: brown bag session, lunchtime workshop, newsroom brown bag, midday learning session, skills session. All of them are optional, none of them are a meeting, and none of them belong in a performance review.
The format has been running in real newsrooms for decades. At Mother Jones, Tasneem Raja described Skillz Thursdays in a Knight Lab interview: a one-hour brown bag where one staffer teaches everyone else one thing. Topics ranged from making a map to reading the revenue streams to not panicking when you get interviewed on air. The sessions that worked best were the low-stakes ones where people who never cross paths just talk. The topic request list got so long it became its own problem.
Most newsrooms have no training department, so somebody has to own it. That is usually an editor with a calendar and a list of names. Here is how to run a lunch and learn for reporters, start to finish.
Table of Contents
- What You Need
- Step-by-Step: How to Run a Lunch and Learn for Reporters
- 1. Define the learning outcome
- 2. Choose a topic reporters can use
- 3. Pick the format and time limit
- 4. Find the right presenter
- 5. Set the room or online logistics
- 6. Promote the session and manage RSVPs
- 7. Run the session with a clear structure
- 8. Capture useful resources and feedback
- 9. Follow up and turn interest into action
- Common Mistakes
- Frequently Asked Questions
- How long should a lunch-and-learn session for reporters be?
- How do you choose a topic that will interest reporters?
- Can a lunch and learn for reporters be run online?
- How often should a newsroom run lunch-and-learn sessions?
- What should the organizer do after the session?
- How do you measure whether the lunch and learn was useful?
- Conclusion
What You Need
You need nine things, and most of them take ten minutes to arrange. Only two of them are hard.
- A learning objective. One sentence naming what a reporter can do afterwards that they could not do this morning.
- A topic tied to reporting work. Not “technology”, not “innovation” — a thing someone needed this week.
- A presenter. Ideally someone inside the newsroom who does the work daily, plus a facilitator who runs the clock.
- A calendar slot. 60 minutes, ideally starting at 12:30, with a hard finish.
- A room or a video platform. Booked with screen sharing, and tested the day before.
- Food and accessibility arrangements. One-handed food, dietary needs collected in advance, captions turned on for the video link.
- Promotional material. A calendar hold and a short invitation blurb, written so it reads as opt-in.
- A sign-up method. A shared doc, an RSVP list or a poll. Cap the number if the room cannot hold more.
- A feedback form. Four questions, sent within an hour of the session ending.
If you are missing the topic or the presenter, stop there and fix those two before anything else. Everything downstream gets easier once someone credible has agreed to teach.
Step-by-Step: How to Run a Lunch and Learn for Reporters
1. Define the learning outcome
Write one sentence describing what a reporter will be able to do at 1:30pm that they could not do at 12:30pm. “Understand how to request newsroom data” works. “Evaluate a new mapping tool” works. “Technology” does not, and neither does “our new strategy”.
A useful test: ask the presenter to finish their sentence “after this session, you’ll know how to” and write that sentence down verbatim. You will learn within ten minutes whether the session has a spine or just an interesting speaker. Signal: the sentence is under fifteen words and contains a verb.
2. Choose a topic reporters can use
Pick the topic from a real newsroom problem, not from a list of interesting subjects. The best source is a question that came up on the desk twice this month.
Do not guess what people want. The advice that comes up most often on staff forums is to ask first: put two or three options in a poll and give people a week to vote. If nobody votes, treat the top result as the topic for next time rather than as a failure this time. How you know it is working: you can name the reporter who asked for it.
3. Pick the format and time limit
Use 60 minutes as a hard cap, split into 40 minutes of content and 20 minutes of discussion. Longer sessions do not produce more learning; they produce more absences next month.
| Length | Works for | Discussion budget | Risk |
|---|---|---|---|
| 30 minutes | A single tool, a new policy change, a short demo | 10 minutes | Too shallow for anything with a process |
| 45 minutes | A skill with a few steps, such as source documentation | 15 minutes | Rushes the hands-on part |
| 60 minutes | Anything with a live demo, a teardown or an exercise | 20 minutes | Overruns if the facilitator is absent |
The newsroom is the wrong place to try the 90-minute version. People eat at different times, phones ring on the desk, and half the room will already have been pulled into a story. Signal: the agenda you send out ends at a specific clock time, not a duration.
4. Find the right presenter
Look for someone who can explain the subject plainly, demonstrate it credibly and stay inside the timebox. A working reporter beats a polished executive every time, because the room can tell the difference.
There is a fairness question buried here. One desk should not end up running everyone else’s training, and unpaid preparation time is unpaid preparation time. A rotation or a small honorarium for prep avoids the resentment that kills series number four. Proof it is working: other people volunteer to teach after they attend one.
5. Set the room or online logistics
For an in-person session, book a room that seats more than the sign-up list, check the projector or TV with the presenter’s own laptop, and put the food where it can be reached without crossing the front of the room.
| Format | What works | What breaks | Bureau staff |
|---|---|---|---|
| In person | Conversation afterwards, easy food, people ask questions out loud | The room is too small or the session runs past the hour | Left out entirely unless someone drives it |
| Hybrid | One screen, one microphone, remote people named at the start | Two audio sources fighting, remote attendees talk over nobody | Bureaus join the same link |
| Remote only | A screen-share demo, a shared doc for questions, a recorded version | People mute out and the session becomes a monologue | Easiest way to include a bureau |
Whichever you choose, turn on captions for the video link, share materials in advance so nobody needs to take notes, and name a backup for the presenter. Check: someone on the desk joins a minute before the start and confirms the audio works from the back row.
6. Promote the session and manage RSVPs
Write the invitation in five lines: what attendees will be able to do afterwards, the date and clock times, the room and link, the presenter’s name, and whether food is provided. Say plainly that attendance is optional.
Here is a blurb you can copy. “12:30 to 1:30, Room 4 and video. Mara Ortiz shows how to build a records request that actually comes back answered. Bring a story you’ve been stuck on. Food provided, no prep needed, drop in for the first ten minutes if that’s all you’ve got. Optional.”
If sign-ups exceed capacity, open a second session rather than crowding the room. You will know it is working when the invitation is forwarded without your asking.
7. Run the session with a clear structure
Hand the run of show to the facilitator, not the presenter. The facilitator opens, watches the clock, collects questions in a shared doc and closes on time.
| Minutes | What happens | Why |
|---|---|---|
| 0–5 | Facilitator opens, states the outcome, names who is on the video | People arrive late; give them the frame anyway |
| 5–10 | Presenter sets up the problem, no theory | Skip the history of the tool |
| 10–35 | Live demo or teardown of a real published story | A demo teaches more than a slide deck |
| 35–45 | Hands-on or worked example, including the part that goes wrong | People trust the failure more than the success |
| 45–60 | Discussion from the shared doc, then a one-line recap | Questions are the session; protect the time |
Keep it inclusive in the room as well as on the screen: ask two people to speak by name rather than waiting for volunteers, and never let the session become a pitch for the presenter’s own project. Signal: the room is still talking as people pack up, and the facilitator stops at 1:30.
8. Capture useful resources and feedback
Send one page the same afternoon: the slide deck or the notebook, the demo link, the documentation, the code example and where questions can be asked. A session with no takeaway is the fastest way to lose the room next month.
Ask four questions and nothing more: was this relevant to your work, was the pace right, what was unclear, and what should the next session cover. A four-question form gets answers; a ten-question survey gets silence. The feedback you act on is a request list for future topics.
Archive it too. Recording the session and storing it with the onboarding material means the next new reporter gets the lesson without anyone repeating it.
9. Follow up and turn interest into action
Within 30 days, check whether anything changed. Ask two reporters who attended whether they used the skill, and look for the ordinary signals: a shared request template appearing, a records letter being written the new way, the demo tool showing up in someone’s workflow.
Keep a running list of what people asked for, publish it, and let people add names to it. If a session lands, book the next one before the interest fades, and if one flops, write down why in a sentence so the next organiser inherits the lesson. Check: you have a date in the calendar for the next session.
If someone has just come back from a conference or an external course, that return is the best possible topic. Knight Foundation newsroom training guidance argues the same thing: external training only pays off if it is transferred on return, and a brown-bag session is the cheapest transfer step available.
Common Mistakes
Nearly every failed newsroom session fails in a way someone could have predicted. The fixes are short.
- The topic is too broad. “Data journalism” teaches nothing in an hour. Fix: name the one task, such as cleaning a messy CSV or checking a spreadsheet before it goes in a graphic.
- It runs over the lunch hour. People eat at their desks and go back to stories. Fix: timebox to 60 minutes and let the facilitator cut the demo at 1:25 regardless of where it is.
- Only senior staff attend. Fix: put the invitation in the desk channel rather than only in management mail, and schedule around the evening package deadline rather than against it.
- The presenter pitches their own project. Fix: agree the outcome sentence in advance and ask the facilitator to interrupt if it turns into a sales pitch.
- No demonstration. Slides describing a tool teach less than ninety seconds of watching it used. Fix: make the live demo the middle of the session, not an appendix.
- Remote staff are an afterthought. Fix: name bureau attendees at the start, use one microphone, and put questions in a shared doc so the video participants can see them.
- Nothing is shared afterwards. Fix: send one page the same afternoon with the deck, the demo and the documentation.
- Feedback is collected and ignored. Fix: publish the answers, and let the top request become the next session.
The thing that makes a series repeatable is boring: a standing slot in the calendar, a named facilitator role, a published request list and an archive that grows every month. Mother Jones had a topic request list that grew past anything they could serve, which is the clearest possible signal that the format works once the queue exists.
Frequently Asked Questions
How long should a lunch-and-learn session for reporters be?
Sixty minutes with a hard finish is the working standard for a newsroom lunch and learn. Split it into about 40 minutes of content and 20 minutes of discussion, with the demo in the middle. Shorter formats work for a single tool or a policy change, but anything with a real workflow needs the full hour. Ending on time is what makes people come back.
How do you choose a topic that will interest reporters?
Ask instead of guessing. Put two or three options in a poll a week ahead and let the desk vote, or draw the topic from a question that came up twice this month. Frame every option around a task rather than a subject. If a poll gets no votes, keep the options for the next session instead of treating it as a failure.
Can a lunch and learn for reporters be run online?
Yes, and for a distributed newsroom it is usually the better option. Screen-share the demo, keep questions in a shared doc so remote people can follow them, turn on captions and record it. The thing that breaks is audio: use one microphone, name who is on the link at the start, and let the facilitator carry the discussion rather than the presenter.
How often should a newsroom run lunch-and-learn sessions?
Once a month is a sustainable rhythm for most newsrooms, and once a quarter works if each session is longer or aimed at a whole department. Weekly sessions tend to collapse by the third month because they compete with deadlines. What matters more than frequency is a fixed slot people recognise, and finishing on time every single week.
What should the organizer do after the session?
Send one page the same afternoon with the deck, the demo link and the documentation, then ask four feedback questions: relevance, pace, what was unclear and what the next session should cover. Publish the answers and let the top request set the next topic. Thirty days later, ask two attendees whether they used the skill at all.
How do you measure whether the lunch and learn was useful?
Attendance tells you almost nothing. Watch for adoption instead: a shared template appearing in someone’s workflow, a records letter written the new way, a bureau reporter using the demo tool, or two people volunteering to teach the next session. A short check with attendees after 30 days is the cheapest version and catches most of it.
Conclusion
Start with one concrete reporting problem. Ask four people on the desk what got them stuck last week, pick the answer with the clearest demo, and build a single 60-minute session around a 25-minute live demonstration and a reserved discussion block.
Send the resources the same afternoon, ask four feedback questions, and book the next session before the interest fades. That is how to run a lunch and learn for reporters that people actually expect to attend, and the hour pays back every time it is archived.
