Week three of the FoodNode alpha. I cut the social feed.

This was the module everyone — including me — was most excited about. An industry-specific timeline. Members post updates; the feed surfaces what's happening across the network. Twelve days in, the feed is gone, and the directory is twice as useful.

Here's how that happened.

What the feed was supposed to do#

The pitch: a verified, industry-only timeline. No spam, no growth-hacked carousels, no LinkedIn-style "I'm so excited to announce" posts. Members share real updates — a new line installed, a certification cleared, a pilot landed. The network gets a live read on what's happening in the industry.

I built it on day one. Built it well — a posting flow, image uploads, comments, reactions, a moderation queue, a daily digest email.

What actually happened#

Two things.

First: members posted, but not what I'd hoped. The first ten posts were product announcements — "introducing our new range of …". They weren't bad posts, exactly, but they were a different category of content from what I'd designed the feed for. The feed wanted operational updates; what it got was promotional posts.

Second: the feed quickly became the thing the platform was for. Members opened the app, scrolled the feed, closed the app. The directory, which was supposed to be the centre of the product, became a tab nobody clicked.

The signal was clear. The feed wasn't expanding the platform — it was eating it.

The cut#

I cut the feed in a single afternoon. Members got a notification: "the feed is paused; we'll bring it back later in a different shape." Twelve people emailed me back. Eleven of them said: thank god, the feed was distracting from why I joined.

The directory's daily-active-minutes went up the next day.

What's instead#

In place of the feed, I built innovations — a curated module where members can submit a single update about a thing they have just done. The lab vets it. Maximum one post per member per week. The whole module fits on one page, and the page is built so it can never become an infinite scroll.

It's not a feed. It's a magazine.

What I learned#

The lesson sits with three rules I now write down for every experiment:

  1. The most exciting feature is the most dangerous one.
  2. If a module is eating the rest of the product, that's data — not a sign to add more to the module.
  3. A pause notification, sent honestly, generates more trust than the feature it removes.

The directory is still the centre. Innovations is the magazine on the side. The feed will come back later — as a different thing, in a different shape, when I know what the shape should be.

Next week's log: the events module. Members' Mixer · Western Chapter is the target.