What scaling teams get wrong about automation.

A discussion on why small signals often drive the biggest product opportunities.

We sat down with Peter Reinhardt, co-founder of Segment. A discussion on why small signals often drive the biggest product opportunities.

The noise problem

When Peter and his co-founders started Segment, they weren't building an analytics company. They were building a classroom lecture tool that nobody wanted. What changed everything wasn't a big insight—it was a small one.

"We kept getting the same request from other startups: 'Can we just use your data pipeline?' We almost ignored it because it wasn't the product. Turns out it was the only thing people actually wanted."

That signal—repeated, specific, unsolicited—was easy to miss. It didn't show up in their metrics. It showed up in conversations.

Why small signals get ignored

Peter's take is that teams over-index on what's measurable and under-index on what's noticeable.

"You can build a whole company around something someone said once in a support ticket. But most teams aren't set up to catch that. The data team is looking at dashboards. The product team is looking at roadmaps. Nobody's looking at the weird one-off request that keeps coming back."

What to look for

We asked Peter what makes a signal worth paying attention to. His framework:

  • Repetition without prompting. If three unrelated people ask for the same thing without you suggesting it, that's signal.

  • Emotional charge. When someone's frustrated or excited, they're telling you something they actually care about.

  • Workarounds. If users are hacking around your product to get something done, they're showing you what's missing.

  • Specificity. Vague feedback is noise. Specific feedback—"I wish I could do X when Y happens"—is signal.

How decisions get lost

One thing Peter emphasized: catching the signal isn't enough. You have to act on it before it disappears.

"We'd have these conversations, someone would mention something interesting, and then two weeks later nobody could remember what it was or where it came from. The insight just evaporated."

This is exactly what Wayan is built to prevent. Decisions and the context behind them—logged, linked, and findable. No more "wait, didn't someone mention that?"

The long game

Peter's advice for product teams:

"The best opportunities don't announce themselves. They whisper. Your job is to build a system—whether it's a habit, a tool, or a culture—that catches the whispers before they fade."

Thanks to Peter for the conversation. More Wayan Conversations coming soon.

Ben Gable
Customer Success

Create a free website with Framer, the website builder loved by startups, designers and agencies.