Everyone wants to know what’s the tea. Almost nobody stops to ask if it’s actually true. Gossip spreads quickly because it feels like information. It feels like that information holds power. Oftentimes, gossip has the shape of a fact. It can be specific, urgent, worth repeating. But really, it’s more a guess wearing a fact’s clothing. A masked wolf, amongst sheep.

SIGNAL, the third stage in THE READ Collective^TM framework, is about telling the two apart before you act on either one.

What signal actually means here

A cup of tea is calm. It’s something you sit with. You savor the smell and enjoy it;s warmth against your cheeks. Spilling the tea has the exact opposite effect. It is fast-paced, dramatic and built to be repeated. Most organizations run on spilled tea. A metric moves, someone reacts quickly and a decision gets made before anyone checks whether the movement meant anything at all.

Signal is what’s left after you’ve sat with the cup, instead of spilling it. It’s the customer behavior that shows up consistently, building a pattern over time. Not the one loud complaint in a sea of quiet satisfaction. It’s the trend that holds after a second, third and fourth look.

Why this stage gets skipped

Noise is louder than signal, almost by definition. A single angry customer is more emotionally available than a thousand quietly satisfied ones who said nothing. A dashboard alert feels more actionable than a slow trend line. Teams chase whatever demands attention, while the real signal sits underneath, easy to miss.

That’s where “data-driven” decisions go wrong. The data is real. The interpretation mistakes volume for importance. Loud isn’t the same as true.

What good signal-finding looks like

Ask what’s the tea, but don’t stop there. Ask who’s saying it, how often, and whether it holds up outside the one conversation where you heard it. One customer’s complaint is an anecdote. Ten customers saying the same thing in different words is a pattern, it’s the signal.

Good signal work looks unglamorous from the outside. It’s tedious and rarely feels like insight in the moment. A good signal is about checking a pattern against three data sources, not just one. It’s waiting a week to see if the spike was a trend or just a blip before reallocating a roadmap around it.

The takeaway

SIGNAL depends on a good READ and a disciplined REFINE. You can’t find real signal in a product you haven’t understood. And you can’t tell signal from noise in a message that’s still cluttered with everything you haven’t cut. This stage rewards patience in an environment built to punish it.

Before you act on what’s the tea, ask if it’s actually the tea, or just something loud enough to sound like it.

This is the third in a four-part series breaking down the READ › REFINE › SIGNAL › SCALE framework. Next up: SCALE.

Subscribe now

Leave a comment

Share THE READ COLLECTIVE's Substack

Every team has something rough around the edges. The mistake? Many teams decide whether to fix it or scrap it before they've actually looked at what's underneath.

REFINE is the second stage in THE READ Collective^TM framework, and it’s the one most teams rush. They come out of a good read with real insight, then immediately start adding new features, new messaging, new segments. Refinement gets treated like expansion when it’s actually the opposite.

What refining actually means here

A diamond in the rough isn’t rough because it’s incomplete. It’s rough because it hasn’t been cut yet. The material is already there. Refining means removing what’s covering it, not adding more material on top.

The instinct is to protect what’s already there. Every feature has a name attached to it. Every slide has a reason someone added it once. Cutting feels like erasing someone’s judgment.

But refining isn’t about judgment. It’s about weight.

Not everything that was right when it was added is still earning its place now. That’s the four-step onboarding flow built when the product had three features. That’s the deck that grew a slide every time someone new joined the room. The material wasn’t wrong. It’s covering something that could be sharper without it.

Why this stage gets skipped

Adding feels safer than cutting. A new feature is a visible, definable decision. Removing a feature can look like admitting the original decision was wrong. So teams pile on instead, and the product gets rough around the edges in a different way: bloated instead of unfinished.

Back to the drawing board sounds like failure, BUT it’s usually the fastest path forward. Teams that resist end up refining a product that should have been rebuilt, polishing something that needed to be cut down first.

What good refining looks like

Polish it up only works after you’ve already refined and decided what’s staying. Polishing something you haven’t finished cutting just makes the wrong thing shinier. The order matters.

Cut the fat, then refine what’s left.

The takeaway

REFINE only works on top of a good READ. You can’t cut the fat if you don’t know what the muscle is. Skip the read, and refinement becomes guesswork about what matters.

Once you know what to cut, the work gets simpler, not harder. There is less to build. Less to explain. And more importantly, less standing between the consumer and what they actually came for.

This is the second in a four-part series breaking down the READ › REFINE › SIGNAL › SCALE framework. Next up: SIGNAL.

Subscribe now

Leave a comment

Share THE READ COLLECTIVE's Substack

The roadmap said Q3.
So the team shipped.

Nobody asked if the feature still made sense. It didn’t matter. It was already scheduled.

A founder used the same pitch on five different buyers this month. Same slides. Same words. Same story, no matter who walked in the room.

Marketing wrote another paragraph about what the product does.
Not what it means to the person who has to use it.

Nobody read the room first. That’s the whole thing.

This is where THE READ Collective™ starts. The stage almost everyone skips, because reading looks like doing nothing.

What “reading” actually means here

Reading the room means noticing what’s said and what’s underneath it. In a product context, that’s the difference between what a customer tells you in a survey and what they actually do when the trial ends. It’s the gap between the metric you’re tracking and the behavior it’s supposed to represent.

Read between the lines, and you stop taking data at face value. A drop in engagement isn’t just a number. It’s a customer telling you something they didn’t put into words. A support ticket isn’t a one-off complaint. Find 10 more like it and it’s a pattern.

Judge a book by its cover, and you’ll build for the customer you assumed you had instead of the one you actually have.

Why this stage gets skipped

Reading is slow. It doesn’t produce a deliverable. Nobody puts “read the customer interviews twice” on a roadmap, because it doesn’t look like progress. Refining, building, shipping — those feel like motion. Reading feels like standing still. It can feel tedious and unrelenting.

But every refinement built on a bad read just moves the problem faster. Teams don’t fail because they build the wrong thing slowly. They fail because they read the situation wrong and then executed on that misread with total confidence.

What good reading looks like

Take a page from how a good editor works. They don’t just check grammar. They ask what the writer was actually trying to say, then measure the draft against that intent. Product reading works the same way. You’re not just checking whether a feature works. You’re asking what the customer is actually trying to accomplish, then measuring what you built against that.

An open book doesn’t need translation. Most products aren’t open books yet. Part of the work is making them legible, both to the team building them and the customer using them, before you touch anything else.

The takeaway

Before you refine, before you find the signal, before you scale anything: read first. Read the data underneath the dashboard. Read the customer behind the persona. Read the gap between what was requested and what’s actually needed.

Everything downstream in this framework depends on getting this part right. REFINE without a good READ just polishes a wrong assumption. SIGNAL without a good READ finds noise and calls it insight. SCALE without a good READ multiplies the mistake.

Read the room before you decide what to build in it.

This is the first in a four-part series breaking down the READ › REFINE › SIGNAL › SCALE framework. Next up: REFINE.

Subscribe now

Leave a comment

Share THE READ COLLECTIVE's Substack

Twenty-five years ago, I thought growth was flawless execution.

Better campaigns.
Better messaging.
Better technology.
Better automation.

Execution matters. But it was never the first problem to solve.

Most organizations don’t lack ideas.
They lack understanding.

Subscribe now

THE WRONG QUESTION

I’ve worked inside media organizations, loyalty programs, subscription businesses, enterprise teams, and product marketing orgs.

The industries changed.
The products changed.
The technology changed.

The instinct stayed the same.

Something’s not working. So: run another campaign. Build another feature. Automate another workflow.

Optimization without understanding isn’t progress.
It’s speed in the wrong direction.

THE READ

That’s why I built The Read Collective.

Not another consultancy.
A way of paying attention.

A better read of the customer.
A better read of the product.
A better read of the experience.
A better read of the market.

Understanding first. Optimizing second. Never the other way around.

FOUR WAYS OF LOOKING

Everything published here will live inside one of four ideas.

READ
Understanding customers, behavior, and the friction no one names.

REFINE
Improving experiences, messaging, and product adoption.

SIGNAL
Recognizing the shifts that matter before they become obvious.

SCALE
Building systems that create sustainable growth.

THE INVITATION

I want this to be more than a newsletter.

A place where product marketers, founders, growth leaders, designers, and researchers start seeing products, and the people who use them, differently.

Because better growth starts with a better read.

Welcome to The Read Collective.

Share

Leave a comment