What’s the biggest discovery habit that breaks when scaling dental product teams?
When I first scaled product teams at a dental software company, the biggest habit that cracked was regular customer interaction. Early on, the product manager—usually me—talked directly with the dental practice managers, hygienists, and front-office staff multiple times a week. These conversations shaped our roadmap and surfaced pain points like patient no-shows or billing errors.
But as the team grew from 3 to 12, and we expanded coverage to regional dental groups, that direct line to customers frayed. PMs got pulled into meetings, reports, and coordinating with dozens of moving parts. The result? Product decisions started relying more on analytics and less on actual discovery calls.
Here’s the catch: data can show what happened but rarely explains the why. For example, noticing a 15% drop in online appointment bookings (based on a 2023 Dental Economics report) tells you there’s a problem, but not if it’s due to UI friction, patient anxiety, or front-desk communication breakdowns.
The takeaway: you have to protect time for discovery interviews. At scale, this often means setting strict personal quotas—like 3 customer calls per week—and making it a core KPI for every PM. If you don’t, your team drifts into feature factories.
How do you maintain discovery habits when automation starts creeping in?
Automation feels like a natural fix. You think: “If we can automate surveys or use chatbots to gather feedback, we’ll stay close to users without sacrificing time.” The reality? It helps, but it’s never a full replacement.
For one dental appointment reminder system we built, we introduced Zigpoll to get quick patient feedback post-appointment. The response rate increased by 40%, and the data helped prioritize UI tweaks. But we still paired it with bi-weekly calls to practice managers and dental assistants.
Why? Automated tools often miss nuance. For example, a survey might flag dissatisfaction with appointment scheduling, but a live conversation reveals that many patients struggle because their preferred provider’s availability isn’t well displayed—something the data alone didn’t catch.
Also, beware of over-automation leading to data overload. Mid-level PMs often get stuck analyzing ping-after-ping from tools like Medallia or Qualtrics, while missing the bigger picture.
A solid approach is blending automation with scheduled qualitative check-ins. Use tools for scale and speed, interviews for depth and context.
What’s the most underrated habit for product managers working with dental practice teams?
Shadowing end-users. I know it sounds time-consuming, especially when managing multiple feature streams. But I’ve found that spending a half-day observing dental hygienists or front-desk staff use your product can yield insights no survey ever will.
One team I coached went from a 2% to 11% conversion improvement in patient recall messaging after a PM watched the front desk handle no-shows. The PM noticed staff juggling between their CRM and a paper calendar, leading to double data entry errors.
The fix wasn’t flashy: a small UI adjustment to sync patient info automatically. It took a few hours but boosted satisfaction and reduced manual workload.
Caveat: shadowing isn’t scalable for every PM, especially in big enterprises. But rotating this habit among team members every quarter can keep user empathy alive at scale.
How do you keep discovery fresh when expanding product teams across regions?
One tricky part of scaling in dental tech is that practices vary wildly by region. What works in a dense urban cluster differs from a suburban or rural practice. I saw this first-hand when my team launched a product in the Southeast US after focusing mostly on California and New England.
We assumed patient engagement tactics would translate directly. They didn’t. Urban practices leaned heavily on text and app reminders, while rural practices preferred phone calls and paper notes.
To maintain continuous discovery, we had to decentralize some habits. We empowered regional PMs and user researchers to run localized discovery cycles, then synced findings weekly to the central team.
If you keep discovery centralized, you risk missing critical regional nuances that can tank adoption.
What common scaling trap should mid-level PMs avoid when instilling discovery habits?
Thinking discovery is a one-off sprint.
Early in my career, I treated discovery as a phase—do it upfront before development, then move on. That mindset falls apart fast in scaling dental practices, where workflows, regulations, and patient demographics evolve rapidly.
For example, changes in dental insurance policies or tele-dentistry adoption can shift user priorities in months. A 2024 survey by the American Dental Association showed tele-dentistry use surged 35% post-pandemic, forcing quick pivots.
Discovery has to be continuous, embedded in weekly routines, not just quarterly or bi-annually. That means built-in rituals like weekly “customer pulse” meetings, rotating listening posts, or a dedicated Slack channel for real-time user feedback.
How to balance quantitative data and qualitative discovery when scaling?
Relying solely on dashboards is tempting. After all, KPIs like appointment booking rates or patient retention numbers are easy to track across hundreds of practices.
But in dental product management, those numbers often miss context. A drop in patient retention could be caused by external factors like a local competitor or seasonal shifts in patient behavior.
I recommend a two-layer approach:
| Layer | Focus | Tools/Examples | Caution |
|---|---|---|---|
| Quantitative | Track broad trends and spot issues | Google Analytics, Mixpanel, Tableau | Don’t assume causation from correlation |
| Qualitative | Understand “why” behind the data | Interviews, shadowing, Zigpoll | Time-intensive, but essential for prioritization |
Combining these layers helps teams avoid costly missteps, like building features no one wants or missing urgent pain points.
What’s a practical way to scale discovery without losing depth?
Use customer advisory panels or feature councils drawn from your best dental practice clients.
At one dental SaaS company, we formed a monthly advisory group of 8 clinic managers and dental office admins. Each session focused on upcoming features, usability challenges, and workflow pain points.
This panel became a force multiplier—helping the product team vet hypotheses before costly builds. It also deepened client relationships and boosted NPS by 7 points within eight months.
The downside? These panels skew toward more vocal or tech-savvy clients and can bias feedback. Rotate members regularly and supplement with anonymous surveys or one-off interviews.
How do you keep discovery habits alive when the product roadmap feels jam-packed?
Prioritization kills discovery time. It’s the eternal tension.
My advice: bake discovery back into your sprint cycles. For example, allocate every fourth sprint as a “discovery sprint” focused entirely on user research, prototyping, and testing new ideas. This cadence resets the team’s focus and reminds everyone why they build products in the first place.
We tried this at a dental tech firm juggling a dozen feature requests from hundreds of practices. Discovery sprints led to sharper prioritization and avoided building unnecessary features. One discovery sprint unearthed a simple fix that reduced patient no-show rates by 8%—worth more than several costly feature launches combined.
What role does cross-functional collaboration play in continuous discovery at scale?
It’s huge. Product teams that silo discovery with PMs alone lose valuable front-line insights from sales, support, and even marketing.
In the dental industry, support reps often hear the same patient frustrations daily—about appointment scheduling, billing confusion, or insurance claims. Sales reps can share real-time competitive intel.
Encouraging regular cross-team discovery syncs—maybe bi-weekly “discovery huddles”—helps surface these insights early.
For instance, one team I advised used shared Slack channels and weekly syncs with support and sales. They uncovered that many practices needed better training materials for new features, a problem that didn’t show up in metrics but caused churn.
How do you measure if continuous discovery is actually working as you scale?
Good question. It’s easy to preach discovery but hard to prove its ROI.
I look at a few proxies:
- Cycle time to validated learning: How long from hypothesis to tested insight? Shorter times mean discovery habits are accelerating.
- Feature success rate: Percentage of launched features hitting user satisfaction or adoption targets.
- Customer retention and NPS trends in target segments (e.g., solo practices vs. multi-location clinics).
- Team feedback: Are PMs and researchers reporting they have the bandwidth and tools to do discovery regularly?
At one dental practice software company, tracking these metrics showed a 25% increase in feature adoption in one year after embedding discovery rituals, alongside a 15% drop in support tickets.
What’s your final practical advice for mid-level PMs pushing continuous discovery at scale?
Don’t wait for perfect processes or dedicated research teams. Start where you are:
- Block calendar time weekly for real user conversations.
- Use lightweight tools like Zigpoll to supplement, not replace, qualitative insights.
- Rotate discovery duties among your team to build empathy and spread workload.
- Keep findings visible: share learnings openly with sales, support, and execs.
- Remember, discovery is messy and imperfect. Celebrate small wins and adapt as you grow.
Scaling continuous discovery in dental tech is a grind, but it’s what separates good products from the costly, under-used ones.
If you incorporate these habits consistently, you’ll avoid common scaling traps and keep your product team grounded in the real-world needs of dental practices—not just dashboards and deliverables.