A Shared Reading Feed for a Small Team That People Open
A team of eight people who each read 30 articles a week sees about 240 pieces between them. Maybe a dozen of those would change how someone else on the team works, and almost none of them get passed along, because sharing a link in chat...

A team of eight people who each read 30 articles a week sees about 240 pieces between them. Maybe a dozen of those would change how someone else on the team works, and almost none of them get passed along, because sharing a link in chat means it scrolls away within the hour. A shared reading feed for a small team fixes that by giving good finds one calm, permanent place to land.
I have set up shared feeds for a design studio, a four person newsroom and a nonprofit research group. The tools differed each time. The things that made the feed survive past the first month did not, and they are what this guide is about.
What a Shared Reading Feed for a Small Team Actually Is
It is a single stream of hand picked links that anyone on the team can add to and everyone can subscribe to. Think of it as an RSS feed written by people instead of publications. Each item carries a title, a link and, crucially, one or two sentences explaining why it matters to this team.
That last part is the whole point. A raw link is a request for someone's time. A link with a reason is a recommendation. On every team I have worked with, items with a note got opened roughly three times as often as bare links.
Picking a Format Your Team Will Open
The best format is the one that lives where people already read. There are three common setups:
| Setup | How it works | Best for |
|---|---|---|
| Shared bookmarking feed | Members save links with a team tag; the tag outputs an RSS feed | Teams that already use RSS readers |
| Shared folder in a reader | One account stars items into a public folder with its own feed URL | One editor, many readers |
| Weekly digest email | Collected links are sent once a week as a short newsletter | Teams that live in their inbox |
If half the team has never used a feed reader, start with the email digest and offer the RSS address as an option. Forcing a new app on people is the fastest way to end a curation project in week two.
At the research group, we ran both for a month and compared. The digest went to all twelve people and about nine opened it each Friday. The RSS version had four subscribers, all of whom read every item. Both numbers were useful, and keeping both formats cost the editor about five extra minutes a week.
Setting Rules Before the First Link Goes In
A shared feed with no rules turns into a dumping ground. Write three or four rules on one page and keep them short.
- Every item gets a reason. One or two sentences, written for a colleague, not a summary of the article.
- Read it before you share it. Skimming a headline is not enough.
- Cap contributions. Three items per person per week is plenty for a team of under ten.
- Tag by use, not topic. Tags like "try this", "background" and "client question" are more useful than "design" or "AI".
Why More Contributors Can Make the Feed Worse
The common advice is to get everyone posting, because more contributors mean more variety. In practice, open contribution usually produces a burst of 40 links in week one and silence by week six. People feel obligated, post weak finds to meet an imagined quota, and readers learn to skip the feed.
What has worked better for me is a rotating editor. One person owns the feed for a fortnight. Anyone can send them suggestions, but the editor decides what goes in and writes the notes. The feed stays focused, nobody burns out, and each new editor brings a slightly different eye. On the newsroom team this kept the feed alive for more than two years.
Building the Collection Habit
Curation lives or dies on the moment of capture. If saving a link takes more than two taps, people will mean to do it later and never do. Set up a browser button or a share sheet shortcut for every contributor on day one.
For the editor, a short weekly routine works:
- Monday: clear the suggestion inbox and drop anything older than a month.
- Wednesday: write notes for the three to five strongest items.
- Friday: publish, or send the digest.
If you already star items in your own reader, the same flow I describe in turning RSS stars into a weekly link roundup adapts easily to a team version. The only change is that the starred folder becomes shared.
Keeping the Feed Useful Over Months
A feed that is useful in March can be noise by September. Three habits keep it healthy.
Prune the archive
Every quarter, scan old items and remove dead links or advice that has gone stale. A clean archive turns the feed into a searchable reference new hires can read on their first day.
Watch what people open
Many bookmarking tools and newsletter services show click counts. If a tag never gets clicks, retire it. If one kind of item gets opened every time, ask for more of it.
Keep it small
Five strong items a week beat twenty average ones. When the volume creeps up, readers start treating the team feed like every other source in their reader and stop opening it. Keeping your own subscriptions organized, as in organizing RSS folders so you stop missing posts, also helps the team feed stand out.
Mistakes That Quietly Kill a Team Feed
- Making it mandatory reading. The moment it is homework, people resent it.
- Mixing announcements in. Office news belongs elsewhere. Once a feed carries one "reminder: timesheets due", it loses its tone.
- Letting one person dominate. If 70 percent of items come from one contributor, the feed reflects one taste, and the rest of the team tunes out.
- No owner. Shared responsibility means nobody's responsibility. Name someone.
Frequently Asked Questions
Do we need a paid tool for a shared reading feed?
No. Several bookmarking services and RSS readers offer free plans that output a public feed from a tag or folder. Paid plans mainly add private feeds, search and analytics, which matter more once the team grows past ten or so.
How many items should a small team feed carry each week?
Between three and eight is a good range for a team under ten people. Fewer than three and people forget it exists. More than ten and it starts competing with everything else in their reader.
Should the feed be public or private?
Start private so people feel free to share half formed reasons. Once the feed has a steady voice, a public version can double as a light marketing channel, but keep a private one for internal notes.
The Practical Takeaway
Pick a format your team already opens, require a one line reason for every link, cap contributions, and give the feed a rotating editor. Do that and a shared reading feed becomes the place your team learns from each other, not another stream to ignore. For more ways to filter the web well, see our curation guides.
More in Curation
Curation
A Tagging System for Saved Articles That Survives a Year
I exported my read-later library last spring to check something unrelated and found 1,847 saved articles carrying 240 distinct...
Curation
How to Handle Paywalled Links in a Curated Reading List
The complaint that finally changed how I do this arrived in March, from a reader who had followed my weekly links for about two...
Curation
How to Share an OPML Bundle People Will Actually Import
Someone asked me in September for my feeds on soil science and small presses.