Embedding Customer Voice into Strategy

Across different companies I have worked with, the same issue has come up: product decisions were made without a reliable or structured way to bring in customer input. Feedback was scattered through support tickets, one-off conversations, or occasional surveys, but it was rarely organized into something teams could act on. Without a consistent pipeline, roadmap priorities often missed the mark. The result was frustrated customers, launches that fell short of expectations, and strained relationships with customer-facing teams who needed a way to show users their voices were being heard.

There are a number of tools that can be used to understand potential customers, active users, and the patterns that lead to churn, and many of them offer quick, quantitative data that helps make fast decisions. When solving complex, data-heavy problems entrenched in regulatory obstacles for unpredictable personas, a more qualitative approach is often necessary. Addressing the gap between product and customer ensures the roadmap is aligned to innovation and value, not just band-aids.

To achieve this, I launched customer feedback programs that created multiple customer voice touch points during the product design and development lifecycle, often starting with a roster of customers who volunteer to participate in regular discovery and product evaluation outreach. This user pool provided a flexible channel for insights, including email surveys, concept testing, and discovery discussions to better understand the problem to be solved and what delivery success looks like. These groups met two to four times per month depending on need, and often included annual in-person sessions at the customer conference.

Contributions at unique companies solving a similar problem:

• Datacor. Faced with combining two very different systems that had grown into an overlapping product space, we ran a hands-on workshop where customers could build out their ideal workflows and information architecture. Using printed modules, assets, actions, and common app elements, participants designed the dashboards and processes that best fit their team sizes and environments, revealing not just feature requests, but the deeper logic customers applied when structuring their work.
• Plex Systems. The same approach helped address the tension between a legacy product and its new cloud successor, easing customer conversions. Giving users a structured space to share feedback surfaced what they valued in the old system and gave product managers clear priorities for the new one. This established group later had a massive impact on a new product launch that was nearing failure, but with the processes already baked into our PDDLC, we turned it around and launched with great success. Less than a year later, Plex Systems was acquired by Rockwell Automation.
• SafetyChain. This foundation of ongoing discovery set the stage for deeper data-driven practices. Once the cadence was established, we introduced Pendo to track performance and adoption, turning qualitative insights into measurable product outcomes. I also held workshops on design-thinking research methods, teaching product managers how to generate new ideas through conversations rather than simply validating their own expectations.

The consistent thread was that customer voice was no longer treated as an "extra." It became a normal part of how product and design planned, prioritized, and measured success. Roadmap priorities were better aligned with actual customer needs, which improved adoption and reduced churn risk at launch. Customer-facing teams had a reliable way to bring user perspectives into planning, which strengthened relationships and reduced the feeling of disconnect.

• Steady cadence. 2–4 structured customer research sessions per month.
• Hands-on workshops. Annual sessions at customer conferences with 50+ participants shaping workflows and dashboards.
• Better adoption. Fewer escalations tied to "missed expectations" on new feature launches.
• Stronger alignment. Closer ties between Product and Customer Success, reducing churn risk and enabling expansions.
• Evidence-based planning. Product managers began tracking success metrics for features in advance, shifting toward measurable, outcome-driven planning.
• Analytics integration. Onboarding to Pendo enabled performance tracking, linking customer voice with usage analytics.