← Articles
Daily columnWritten fresh this morning

A Feed Is an Incentive System, Not Just an Interface

A Feed Is an Incentive System, Not Just an Interface

18 August 2026

Today's argument

Distribution mechanics should be managed as product strategy because they change user and supplier behaviour long before a roadmap can correct the consequences.

A feed looks like an interface choice. In practice, it is an incentive system.

That distinction matters as more products adopt short-form video, algorithmic ranking and agent-led experiences. Reddit is testing a video experience that resembles formats already popular elsewhere. YouTube is changing when a video view is counted. Spotify is adding notes that let people explain why a song belongs in a playlist. At the same time, product teams are discussing what remains distinctive when AI agents take over more of the middle of an experience.

These developments may look unrelated. I think they point to the same product problem: the mechanism that distributes attention eventually shapes the product being supplied.

If a platform rewards an immediate start, creators will optimise for the first seconds. If a feed rewards frequent posting, suppliers will produce more often. If ranking favours familiar interaction patterns, teams will gradually design content and features that fit those patterns. None of this requires an explicit instruction. People learn what the system rewards.

That is why I do not see a feed, ranking model or view definition as an implementation detail. It is part of product strategy. It decides which behaviour becomes economically and socially sensible inside the product.

Product teams often evaluate these changes too narrowly. They run an experiment, see whether consumption rises and decide whether to ship. The dashboard might show more starts, longer sessions or more items viewed. But that only captures the immediate user response. It says little about how contributors, creators, sellers or internal teams will adapt over the next six months.

A local improvement can create a structural problem. A video feed may increase browsing while making thoughtful contributions harder to discover. A looser view definition may increase the reported number while weakening its usefulness for comparing performance over time. An automated middle may make a journey faster while turning every product using the same underlying model into a similar experience.

Spotify’s playlist notes are interesting in this context because they add something ranking systems tend to remove: stated intent. A recommendation can tell me what was selected. A note can tell me why it matters. That explanation is not decoration. It creates room for taste, judgment and context that cannot be reduced to position in a feed.

In product leadership, I would therefore ask more than whether a new distribution pattern improves engagement. I would ask what it teaches every participant to do.

Before changing a feed or ranking mechanism, the team should be clear about the behaviour it wants to make more valuable, the behaviour that may be displaced and the suppliers who will need to adapt. The experiment should observe both sides of the system. Did users consume more? Did contributors change what they produced? Did variety narrow? Did low-frequency but high-value activity lose visibility? Could we reverse the change without leaving participants with a broken expectation?

This also changes roadmap discussions. A request for a short-form feed is not merely a request for a new screen. It implies decisions about ranking, moderation, creation tools, notifications, measurement and supplier incentives. The visible interface may be one quarter of the work. The rest is the operating system that decides what succeeds inside it.

I have seen roadmaps become crowded because teams treat each visible feature as an isolated opportunity. The better question is whether those features reinforce the product’s intended behaviour. If the feed rewards one thing, the metrics reward another and the commercial model rewards a third, teams spend their time resolving contradictions they created themselves.

Product strategy is often described through target customers, problems and differentiation. I would add one more element: the behaviour your distribution system rewards repeatedly.

Users may listen to what a product says it is for. They will respond to what it consistently makes visible, measurable and valuable.

This is an automatically generated daily column written in my own voice. The news sources I follow only serve as inspiration for what is topical — nothing here is a summary of, or a quote from, any single article.

Inspired by what was in the air at: lennysnewsletter.com, techcrunch.com, tpgblog.com, mindtheproduct.com, romanpichler.com

  • product-strategy
  • platform-design
  • incentive-design
  • content-discovery