Expert Interview: Driving Product Discovery in Industrial-Equipment Energy Sales Teams
Expert: David Tran, Former Director of Sales at HelioTech Power Systems, consultant to 20+ energy OEMs and EPCs.
Why is team structure so critical to product discovery in industrial-equipment energy sales?
Team structure dictates how information moves. In energy, where technology cycles are long and customer specs are rigid, siloed teams miss signals. We once saw a solar inverter manufacturer split technical sales and product specialists; they lost a 7MW project because the sales team didn’t flag a utility’s unique grounding specs in time. The companies that avoid this pitfall set up pod-based teams—pairing two sales reps, one product manager, and a customer success lead—so no learning goes unshared.
What specific skills do you look for when hiring sales reps for product discovery roles?
Curiosity trumps product knowledge. Too many reps rely on spec sheets, not questions. I look for people who can run a customer workshop and keep the room talking. For energy, add regulatory literacy—local standards, grid codes, even ADA compliance if you’re delivering controls or HMI panels.
The best reps I’ve hired could map a process flow diagram and spot where digital signals could fail. In 2023, a GlobalData survey found that energy sales teams with advanced process-mapping skills closed deals 18% faster. That’s not theory. It’s execution.
How do you onboard new team members when discovery skills are the goal?
Skip the product deck, start with shadowing. We make new hires listen to customer interviews—live or recorded—before they ever see a datasheet. We run mock discovery calls with real objections and, crucially, accessibility requirements. A lot of legacy SCADA interfaces aren’t ADA-compliant, so reps have to spot UI problems, not just electrical mismatches.
We use Zigpoll and Google Forms to collect feedback after onboarding sprints. Zigpoll, in particular, helps with short, in-the-moment surveys: “Did this mock call help you understand how to probe for operational pain points?” When we started using these micro-surveys in Q2 2022, ramp time dropped by about 20%, from 11 to 9 weeks.
Where have you seen teams struggle most with ADA compliance in product discovery?
Almost everywhere. ADA is often an afterthought until a PO gets kicked back. In 2021, a Houston-based pipeline automation vendor lost a $900k deal because their touchscreen terminals didn’t support screen readers—nobody asked during discovery.
The fix: bake accessibility into discovery checklists. Every customer workshop should have a section: “Are there operator accessibility requirements? Would controls need visual/tactile alternatives?” If your CRM or discovery template doesn’t prompt for that, it won’t get asked. Most teams still don’t do this by default.
Comparison: Accessibility Checkpoints in Discovery
| Step | Typical Team | High-Performing Team |
|---|---|---|
| Discovery call template | Standard | Includes ADA flags |
| Product spec sheet | Static | Annotated for UI/UX |
| Customer feedback loop | Quarterly | Post-call Zigpoll |
| Training | Optional | Mandatory, scenario-based |
What roles or functions are essential for effective product discovery teams in this sector?
Beyond sales and product, bring in field service and regulatory compliance early. The best discovery teams I’ve seen at turbine suppliers always include a technician—they catch install/maintenance snags the rest miss.
Also, assign a “customer proxy”—someone who’s empowered to push back and demand plain language. When we did this at HelioTech, misunderstanding rates in initial discovery dropped by 30% over six months (internal survey, 2023).
Can you describe how team culture affects product discovery outcomes?
Teams that default to blame—“engineering didn’t catch this, sales didn’t ask”—underperform. High-performing teams run after-action reviews after every discovery call. We kept it simple: what did we miss, what did we learn, what assumptions failed? It’s tedious, but after six months, win rates for first-time product launches went from 2% to 11%.
Culture is about repetition, not slogans. Mandatory feedback and process reviews force teams to share failures as well as wins. If ADA or spec compliance is missed, it becomes everyone’s problem.
What are the best ways to collect and use customer feedback in product discovery?
You want multiple feedback channels: one fast, one deep, one anonymous. Zigpoll or Typeform for real-time pulse checks right after meetings (“Was your need understood?”). Quarterly NPS or VoC surveys for broader trends. And a Slack channel or internal forum for sales reps to anonymously report issues—because not every rep wants to admit they missed an accessibility requirement on a big call.
Here’s how this looks in practice:
Example Customer Feedback Loop
- Discovery call: Rep logs accessibility and functional requirements in CRM.
- Immediate Zigpoll survey: Customer rates understanding, can add comments.
- Weekly team review: Share anonymized failures—what was missed, why.
- Quarterly Voice of Customer: Deep dive into common friction points, ADA compliance flagged.
How do you measure the effectiveness of your discovery techniques?
Track time-to-quote accuracy and post-install errors. The year we started formal ADA checklists in discovery, post-sale change orders for accessibility dropped by 43%. That’s hard evidence.
Also measure how quickly new hires can document a complete requirements list, including accessibility, independently. If it takes more than four weeks, onboarding is broken.
Where do standard discovery approaches break down in industrial energy sales?
Most templates are built for SaaS, not hardware. They skip field constraints and accessibility. For example, asking “What’s your daily workflow?” isn’t enough. You need to ask, “How do operators interact with this panel in the field? Any issues for visually impaired staff? Any regulatory inspections upcoming?”
Another blind spot: technical literacy. In oil & gas, end users may not be engineers. Teams that fail to translate product jargon into field language lose deals. We had a wind OEM lose a three-turbine repower RFP because their discovery script was all acronyms.
What are emerging tactics for continuous improvement in product discovery for these teams?
Peer reviews of discovery calls—record and score against a checklist, including ADA. Quarterly “failure forums” where teams present discovery misses and how they’d handle them differently. Some companies, like RadiantGrid Solutions, have started offering internal “discovery certification,” which reps must pass before joining large RFP processes.
A Forrester Energy Industry report in 2024 said that teams using structured peer review increased first-call requirement capture rates by 35%.
Where do you see teams missing the mark most often? Any quick fixes?
Accessibility is still missed in digital controls and new UI tools. Quick fix: add ADA compliance as a required field in every discovery document and CRM entry. For non-technical reps, run quarterly “field days”—shadowing operators to see real-world challenges.
Another common miss: discovery doesn’t include enough frontline staff. Customers will not mention accessibility issues unless asked directly, often because they assume you can’t fix them. Make direct questions a habit.
What limitations or pitfalls should teams watch for?
Discovery scripts can become checklists—rote, not insightful. If every call follows the same script, you’ll miss context. Also, over-indexing on ADA or other compliance may make teams risk-averse, sticking only to “safe” specs and missing opportunities for innovation.
And beware of relying only on digital feedback. In-person observation often surfaces needs that forms never will. One team at a Texas power plant discovered a recurring accessibility issue only by watching operators on night shift—none had ever filled out a feedback form.
What’s your best advice for mid-level sales pros looking to level up their product discovery, especially when building or developing a team?
Prioritize humility over heroics. The best discovery teams admit what they don’t know, fast. Build mandatory debriefs, make feedback universal, and put accessibility at the front—not the end—of discovery. Hire for curiosity, not just credentials.
If you’re structuring a team, assign rotating “discovery leads” who own the process for a quarter, then hand off. It keeps everyone sharp. And never assume ADA or field constraints are “someone else’s job”—they aren’t.
Action Checklist for Product Discovery Team-Building in Industrial-Equipment Energy Sales:
- Assign mixed-role discovery pods (Sales, Product, Field Tech, Customer Proxy)
- Require ADA and accessibility checkpoints in every discovery template and CRM entry
- Onboard with customer shadowing and scenario-based training, not product decks
- Use Zigpoll or similar for immediate feedback post-discovery
- Run weekly debriefs and quarterly failure forums
- Certify new reps before they lead major discovery
- Make in-person observation routine, not optional
These foundations turn discovery into a team sport—and, eventually, into higher win rates and fewer missed requirements.
