Briefings, not newsletters: the right output for a consulting knowledge base
Most teams confuse curation with publication. A weekly briefing is what you actually need — and it's not the same thing as a newsletter.
The team behind Pith Lab
The wrong default
Most consulting teams default to newsletters. The Information for tech, Bain Insights for strategy, FT Alphaville for markets. The promise is curation; the reality is a fire-hose of opinions you didn't ask for.
The deeper problem isn't volume. It's that newsletters reflect the editor's worldview, not the reader's. A consultant working a healthcare-AI engagement doesn't need AI news in general. They need the three pieces from this week's reading that change how the engagement runs.
What a briefing actually is
A briefing is a one-page summary of what your team read this week, structured around the engagements you're working on. Not "AI news" — the AI news that matters for the Acme deal. Not "regulation update" — the regulation update that affects this client's deadline.
The format matters. Not 20 bullet points. Five short paragraphs, each tied to a saved passage with a citation. Read in three minutes. Acted on in ten.
The output of a knowledge base should look like a memo, not an inbox.
Why this changes the input loop
When the output is a briefing, the input changes. People stop forwarding "interesting" articles and start saving useful ones. Highlights get tagged by client, not by topic. The team starts reading for the briefing rather than reading and hoping something sticks.
This is the part most tools miss. The output shape determines the input behaviour. A newsletter says: consume. A briefing says: capture for next Friday.
Cost of running it
The cost is mostly attention discipline, not technology. Three minutes of saving per article, a tag per client, and a Friday-morning summary. The technology is cheap; the change is in habits.
A team of five with disciplined capture produces a briefing nobody else can buy. It's not a feed. It's not a newsletter. It's the team's reading, distilled. That's the output worth optimising for.
FAQ
How is this different from a newsletter subscription?
A newsletter is one editor's worldview. A briefing is your team's reading, summarised. Different inputs, different outputs.
What if my team doesn't read enough?
If your team isn't reading, no automation fixes that. The briefing is a forcing function — it's empty when the input is empty.