From Signals to Strategy: Insights from Gradual's New York Executive Dinner

# Format: Event Recaps

# GTM Strategy

Leaders across Product, Marketing, Sales, and Customer Success discuss how organizations turn customer engagement signals into shared strategic decisions.

March 25, 2026

Joshua Zerkel

We recently hosted an exclusive dinner in New York City for leaders across Product, Marketing, Sales, Customer Success, Growth, and Community. The group included people responsible for product direction, go-to-market strategy, customer relationships, and community engagement. In other words, people who spend their days close to the signals organizations receive from customers.

The goal of the evening was simple. We wanted to create space for a candid conversation about how those signals actually shape decisions. Every team collects feedback, engagement data, and insight from customers. Yet very few organizations consistently translate those signals into shared strategic decisions across teams.

The dinner was part of our Context First series, which focuses on the idea that strategy increasingly depends on how teams interpret signals together. Signals alone rarely move decisions forward. Context does.

Early in the conversation, one guest captured the tension many organizations are feeling. They said, “We’re not short on signals. We’re short on alignment around what they mean.” That observation stayed with the group for the rest of the evening.

Signals are easy to collect

We began with a straightforward question. Which customer signals actually influence executive decisions in your organization?

Around the table, people quickly listed the signals their teams gather every week. Product analytics, customer interviews, sales conversations, support tickets, community discussions, surveys, and event feedback all surfaced within the first few minutes. Modern organizations have more visibility into customer behavior than ever before.

The challenge, however, is not collecting signals. The challenge is determining which ones travel far enough across the organization to influence planning.

Several leaders described a similar pattern. Teams capture valuable signals constantly, but most of them remain inside the function that collected them. Product teams see patterns in usage. Customer success hears recurring friction during onboarding. Marketing notices shifts in how prospects describe their problems.

Each of those signals offers insight into the customer experience. Yet those insights rarely move across teams in a way that shapes strategic decisions.

One participant described it this way: “We’re very good at collecting signals. We’re less good at translating them.” The group immediately recognized the dynamic.

Signals on their own rarely influence decisions. Someone has to interpret the signal, connect it to a broader customer story, and help other teams understand why it matters.

Signals become strategy when someone carries them forward

As the conversation continued, we asked participants to share examples where engagement or customer feedback actually changed a strategic decision.

Those stories revealed a common pattern. Signals gain influence when someone inside the organization recognizes their significance and carries them into broader conversations.

Sometimes that person is a product manager who notices a pattern in customer feedback and brings it into roadmap planning. In other cases, a marketing leader connects engagement data to a shift in positioning or messaging. Customer success leaders often surface signals that appear repeatedly across accounts.

What matters is not only the signal itself, but the interpretation around it.

Several participants noted that signals become far more credible when they appear across multiple channels. A single piece of feedback might not move a conversation forward. But when the same signal appears in customer calls, product usage patterns, and deal feedback, it becomes much harder to dismiss.

One leader described how their team pays close attention when signals converge across different parts of the customer journey. Behavioral data, qualitative feedback, and sales insight together create a stronger picture than any one signal alone.

“It’s rarely the loudest signal that matters,” someone observed during the discussion. “It’s the one that keeps showing up everywhere.”

Cross-functional context changes how signals are understood

As dinner continued, the conversation naturally shifted toward cross-functional alignment.

Different teams see different pieces of the customer story. Product teams observe how customers interact with features. Marketing teams see engagement patterns across content and campaigns. Sales hears objections and buying signals. Customer success experiences the challenges customers encounter after the deal closes.

Each of those perspectives captures part of the picture. The difficulty is that those perspectives often live in separate systems and separate conversations.

One participant put it plainly. “We all have pieces of the puzzle, but we rarely sit down to assemble it together.”

Several leaders described the value of creating deliberate opportunities for teams to compare what they are seeing. Not formal reporting meetings or dashboard reviews, but real conversations where product, marketing, sales, and customer teams interpret signals together.

Those discussions often reveal patterns that no single team could identify alone. A behavior observed in product analytics might suddenly make sense when paired with something sales is hearing during late-stage conversations. A support pattern might align with something the marketing team has seen in community discussions.

Signals become far more meaningful when they are interpreted through multiple lenses.

That dynamic is one reason cross-functional conversations are becoming increasingly important. As organizations collect more signals from more channels, the ability to interpret those signals together becomes a leadership capability.

When signals become noise

Toward the end of the evening, the discussion turned to another challenge that many teams are encountering.

Signal overload.

Most organizations no longer struggle with a lack of customer feedback. Instead, they are navigating an environment where signals arrive constantly from dozens of channels. Community discussions, support interactions, product analytics, surveys, and customer conversations all generate valuable insight.

The question becomes how leaders determine which signals deserve attention.

Several participants described relying on pattern recognition rather than isolated feedback. Signals that appear repeatedly across multiple customers or channels tend to receive more attention. Other organizations described creating internal rituals where teams review signals together and discuss what they might mean.

In both cases, the goal is not to gather more signals. The goal is to create shared understanding around the signals that already exist.

One guest captured the challenge well when they said that decision velocity often depends less on the number of signals available and more on whether teams agree on how to interpret them.

Without shared interpretation, signals can easily become noise.

Why shared context matters

As the evening wrapped up, Jerry reflected on something that had surfaced throughout the discussion.

Turning signals into strategy is not primarily a data problem. Most organizations already have more signals than they can process. The real challenge is connecting those signals across teams in a way that creates shared understanding.

When leaders from different functions compare what they are seeing, signals begin to form a clearer picture of the customer experience. Decisions become easier because teams are operating from the same context.

That idea sits at the center of how we think about engagement at Gradual. Community conversations, events, learning programs, and customer feedback all generate signals. When those signals live in isolation, they rarely influence strategy. When they come together, they create the shared context organizations need to make better decisions.

Evenings like this one are a reminder that many teams are working through the same challenges. The signals may be different, but the underlying questions are remarkably similar.

How do we interpret what customers are telling us?

How do we connect those signals across teams?

And how do we turn those signals into decisions that shape the future of the business?

Those are the conversations that matter.

Key takeaways

The dinner surfaced several themes about how customer signals influence strategy inside organizations.

Teams collect far more signals than they consistently use in decision making.

Signals gain credibility when they appear across multiple channels or functions.

Cross-functional conversations often reveal patterns that individual teams miss.

Signal overload is becoming a growing challenge as feedback channels expand.

Shared context helps leaders interpret signals and make decisions faster.

FAQ

What are customer signals? Customer signals are behaviors, feedback, and engagement patterns that reveal how customers experience a product or service. They can come from product usage, community discussions, support interactions, sales conversations, or surveys.

Why don’t customer signals always influence strategy? Many signals remain within the teams that collect them. Without cross-functional interpretation and discussion, signals rarely travel far enough to influence executive planning.

What creates shared context across teams? Shared context emerges when teams interpret signals together and compare what they are seeing across product, marketing, sales, and customer success.

Why is signal overload becoming more common? Organizations now collect feedback from many sources simultaneously. Without clear prioritization or shared interpretation, the volume of signals can slow decision making.

Comments (0)

Popular