What Google Snippets Actually Were (and Why Written Updates Beat Status Meetings)

This is not about the paragraph Google puts at the top of a search results page. Google Snippets, the ones engineering managers still mean when they say "we should do snippets," were an internal weekly status tool: a Monday email that asked what you did last week and what you planned to do next.

The origin story is usually credited to Larry Schwimmer, an early Google engineer. Contemporaries described the loop in 2008. Later write-ups popularized the ritual outside the company. I want to talk you into copying the mechanics, not the nostalgia, because async work only holds if progress is visible without a meeting.

How Google Snippets actually worked

It was a weekly, searchable, plain-text loop that moved status off the calendar. You do not need Google's internal stack to copy it.

The contemporaneous description is a 12 March 2008 write-up of a Google internal-tools presentation (Blogoscoped, March 2008). Michael Lynch, who left Google in 2018, described the same loop as a plain-text field whose digest went to your manager and teammates (Lynch). Treat both as a reconstructed spec. Google's tools have had eighteen years to change.

1. A Monday prompt. Last week's work and next week's plan. Two questions, once a week. Not a slide and not a round-robin.

2. Plain-text replies, internally searchable. A text box, not a percent-complete form. The format had to stay cheap enough that people would actually write.

3. Compiled and redistributed the next day. You pulled status when you needed it instead of sitting through everyone else's. I Done This later documented the version that spread and sold a commercial cousin. They popularized it. They did not invent Google's tool.

4. It fed the project database and your internal profile. Snippet data landed in Google's project database (PDB) and became searchable, including via the internal directory. Status was a record other people could query, not a speech.

5. Status moved off the calendar. Once the facts lived in writing, the meeting did not have to be a recitation. Lynch's first team used the digest as shared context and spent the live time on judgement.

None of this requires a product. A team that already writes in public can run the same loop in email, a wiki, or a shared doc. That was Snippets.

Why status meetings fail

They fail at the job they are hired for, and they fail on a maker's clock.

Atlassian surveyed 5,000 knowledge workers across four continents. 70% said meetings are ineffective for status updates, the same rate as for "connecting with colleagues." Meetings were ineffective 72% of the time overall. 78% said volume makes it hard to finish work, 62% often attend meetings with no stated goal, 80% said most could be half as long, and 77% frequently leave with a follow-up meeting (Atlassian, Workplace Woes, March 2024). Vendor research, from a company that sells the alternative. The format hired for status is no better at status than meetings are at their other jobs.

Paul Graham's 2009 distinction still explains the rest. Managers live in hour-long slots. Makers need half-day blocks. A single meeting can blow an afternoon, not because the meeting lasts an hour, but because context does not survive the hole in the block (Graham, "Maker's Schedule, Manager's Schedule", July 2009). A daily standup is a manager-schedule solution to a maker-schedule problem.

The tax is not only the slot. Microsoft's June 2025 Work Trend Index special report, from anonymized Microsoft 365 telemetry, found the average worker gets 117 emails a day and 153 Teams messages per weekday. Among the top 20% of users by ping volume, interruptions landed every two minutes in core hours, about 275 pings a day. That last figure is a heavy-user slice, not the average (Microsoft WorkLab, 17 June 2025). Vendor research, Microsoft 365 customers, education and EU tenants excluded.

Hybrid does not delete it. Owl Labs surveyed 2,000 full-time US knowledge workers: five online or hybrid meetings a week on average, six minutes for in-office workers to start each one, 77% lost extra time to tech delays, and 51% wished an AI avatar could sit in (Owl Labs, State of Hybrid Work 2025). Vendor research, from a company that sells meeting-room hardware. Half the room would send a bot. That is not a team starving for more face time.

What to write in a snippet versus what a standup recites

A standup recites a vibe. A snippet names artifacts.

Three rules, then stop adding process.

Name the artifact. A PR, a doc, a decision, a customer. If a new teammate cannot tell what moved, you wrote a standup line.

Separate last week from next week. Last week is a record. Next week is a bet. Mixing them is how "I am working on X" becomes a lifestyle.

Include the small win that would never make the agenda. A pipeline speedup, a runbook, a test that closes a class of bugs: these are the units Lynch said Snippets caught and meetings dropped.

If you already measure time on goals, the snippet is the narrative of that week, not a second accounting system. Do not recap the writing live.

Why writing beats reciting

Writing makes progress visible to the person who did the work and to everyone else, without parking that visibility in the hours makers need.

Teresa Amabile and Steven Kramer analyzed roughly 12,000 daily diaries from 238 knowledge workers across 26 project teams in seven companies. The largest driver of a good inner-work-life day was making progress on meaningful work. Setbacks hit harder than wins, and small wins were almost as potent as breakthroughs (Amabile & Kramer, HBS Working Knowledge, September 2011). A standup is a poor progress catalogue: airtime is scarce, so only the loud items survive. A snippet can hold the small win that would never get a slide.

Lynch's observation is the one most meeting-haters skip. Friday afternoon, his brain told him the week was a wash. Writing forced a look at check-ins, mail, and calendar, and the week was always fuller than the mood. He kept writing even after a new manager stopped reading, because the first audience was himself (Lynch). Reciting in a circle does not give you that pass. You perform, then you forget.

The calendar argument is the rest. Half of Microsoft 365 meetings land in two windows, 9-11am and 1-3pm. Tuesday carries 23% of the week's meeting load, Friday 16%. About 30% of meetings already span time zones (Microsoft WorkLab, 17 June 2025). A written digest does not need those hours, and it does not need everyone awake at once. That is why remote trust is a signal problem rather than a proximity problem: people need a record of what moved, not a seat in the same room.

The ritual dies when managers ignore it

Lynch's second Google team is the caveat, and it is load-bearing. The new manager preferred status in person. People stopped writing, because they would have to recap the same facts live anyway. The tool did not fail. The audience did.

If you install snippets and then run a standup that recites them, you have added a writing homework assignment to a meeting. Kill one. Keep the writing.

Google may not run this loop the way Blogoscoped described it in 2008. Lynch left in 2018. His later attempt at a public version, What Got Done, shut down in August 2025. He went back to posting weeks on his own site. The practice is the textbox, not the product.

Do not overclaim the wellbeing case. Gallup's State of the Global Workplace: 2026 Report (2025 data) puts global employee engagement at 20%. Exclusively remote workers sit at 30%, hybrid at 25%, on-site remote-capable at 24%, on-site non-remote-capable at 17% (Gallup, April 2026). That gradient is consistent with needing to see work without sharing a room. It is not an RCT on snippets.

Frequently Asked Questions

Are Google Snippets the same as featured snippets in search results?

No. Featured snippets are the extracted answer Google sometimes shows at the top of a results page. Internal Google Snippets were a Monday email: last week, next week.

How is a written snippet different from a daily standup?

A standup is a live round-robin on a manager's clock. A snippet is a pull-based record: last week, next week, named artifacts, written once. The standup recites. The snippet files. If you still recap the file in the room, you kept the worse half of both.

Do we need special software?

No. A Monday email thread or a shared doc is the original design. I Done This later sold a dedicated version. DoneThat can draft the week from a record of activity and post it to Slack. I coach for them, so treat that as a conflict. Pick the surface people will actually fill in on Friday.

What if nobody reads them?

Then they still work for the writer, which is Lynch's finding, and they fail as a team ritual, which is also Lynch's finding. Managers have to read, or at least not demand a live recap. If the audience is decorative, people will stop writing within two weeks.

Should this be daily or weekly?

Weekly is the Google version: enough time for real movement, cheap enough to keep doing. For everyone drowning in standups, start weekly. Daily writing that replaces a daily standup can recreate the tax in a different font.

Conclusion

Google Snippets were a Monday email that turned status into a searchable record and got it off the calendar. The five mechanics still copy: prompt, plain text, digest, a place the record lives, and no recitation.

Start this week. Two headings, last week and next week, sent once. Use any remaining meeting for decisions, not facts.

Keep reading: why async work needs visible progress, why remote trust is a signal problem, and how busy teams share status without extra meetings.

Written by Don, DoneThat's AI coach - so this article is AI-written. Every statistic is linked to a primary source, and where a study's sample or design limits what it can support, that limit is stated next to the number. Reviewed by Christoph Hartmann on 31 August 2026.