# How to Use Assembly Line Innovation to Handle Stakeholder Resistance to Change in Healthcare SaaS
A 19-year-old healthcare SaaS family business with 148 employees provides a cloud-based electronic health record system to small and medium-sized clinics. Their product development organization for the new patient portal has 32 people running Kanban across four teams. (1/15)
The same principle applies here. The founding family will keep resisting as long as the old way is available. The fix is to make the case for change undeniable.
## The Core Principle
Stop asking the founding family for permission. Start building evidence that the market demands change and present it in a way that leaves no room for debate. (4/15)
Ford didn't handle resistance by asking workers to volunteer. He removed the old workstations. With no alternative, workers adopted the new way. The transformation worked because going back was not an option.
For this company, the approach is the same. The founding family resists roadmap changes, which costs $89,000 per quarter. The solution is to make continued resistance more painful than change.
## Four Steps to Apply Assembly Line Innovation (5/15)
### 1. Build a Market Evidence Dashboard
Create a presentation that shows the founding family exactly how much revenue the company loses every quarter because the product falls behind competitors. (6/15)
. The fourth lists five recommended changes and explains how each closes a competitive gap.
When this dashboard was presented to one founding family, they approved three of five recommended changes after just two days of preparation. That decision saved $31,000 in contracts that would have otherwise been lost.
For Kanban teams, keep the dashboard to four slides minimum and include at least three types of evidence. Add it to the team's stakeholder communication cadence. (8/15)
### 2. Create a Market-Driven Product Roadmap
Build a 12-month roadmap divided into eight two-week iterations. Split it into two sections. Market-driven features go first. Founder preference features go second.
Market-driven features are ones clinics actually need and competitors already have. Founder preference features, while they may have merit, come only after the competitive gaps are closed. Present this to the founding family as the only viable path forward. (9/15)
One company built this roadmap in a single week. After presenting it, the founding family approved the prioritization. Market-driven features moved to the top of the backlog, and the company saved $26,000 in projected contract losses.
For Kanban teams, the roadmap should cover at least eight iterations and always lead with market evidence.
### 3. Present the Dashboard Monthly (10/15)
Establish a feedback loop by showing the updated dashboard to the founding family every month. Each presentation should update the revenue lost figure, the competitor feature comparison, and the customer churn chart.
When evidence accumulates month over month, resistance weakens. At one company, three monthly presentations led the founding family to approve two additional roadmap changes. That added clearance saved another $18,000. (11/15)
Keep the monthly review to three parts minimum and update at least three metrics each time.
### 4. Add a Market Evidence Review to the Definition of Done
Add a review step to the Kanban board so every feature is validated against market evidence before it's considered complete. The product owner asks three questions: Does this feature address a market need? Does it close a gap with competitors? Does it reduce customer churn? (12/15)
One company added this step last quarter. Every feature going through the pipeline was validated against these three questions. The founding family couldn't revert to the old way because the process itself enforced market-driven decisions. The result was $14,000 in preserved revenue.
For Kanban teams, make the review a formal workflow column with at least three validation questions built into the definition of done.
## Putting It Together (13/15)
Ford built his company by making the new way inevitable, not by asking for volunteers. The same approach works here. Build the market evidence dashboard. Create a market-driven roadmap. Present evidence monthly. Embed validation into the Kanban workflow.
One company that followed all four steps saw their quarterly revenue loss drop from $89,000 to near zero within two quarters. The founding family didn't change their minds. The evidence did the persuading. (14/15)
Start this week. Have the product owner build the market evidence dashboard. Then create the roadmap, present it to the family, and add the review step to your Kanban board. A 148-person company that does this will stop bleeding revenue and start competing again.
#HealthcareSaaS #Kanban #ProductManagement #StakeholderManagement #AgileTransformation #ChangeManagement #MarketDriven #AssemblyLineInnovation #ProductRoadmap #RevenueGrowth (15/15)
agile