A key lesson from building healthcare products:
While working on a mammography annotation tool, we delivered a technically correct 4-view layout (CC + MLO). However, initial adoption failed.
The gap wasn’t functionality—it was workflow alignment.
Radiologists bench marked the product against their existing imaging systems and expected:
- Specific image alignment conventions
- Familiar interaction patterns
- Precise control over features like windowing (brightness/contrast)
Even minor deviations led to repeated feedback cycles, rework, and delayed deployment.
Core insight
In mature domains, users don’t evaluate products from first principles—they evaluate them against ingrained workflows built over years.
What this changed in my approach:
- Requirements ≠ stated needs → They must be validated against real usage patterns
- Discovery must include workflow mapping, not just feature gathering
- Wire-frames/prototypes should be validated early with end users to DE-risk assumptions
- Adoption risk should be treated as a product metric**, not a post-release concern
Another important observation:
User adaptability varied significantly—senior practitioners preferred near-identical workflows, while newer users were more flexible. This directly impacts prioritization and roll out strategy.
Takeaway:
In specialized products, success depends less on feature completeness and more on workflow fidelity.
If you don’t anchor early on how users already operate, you’re not building a better product—you’re introducing friction.
Top comments (0)