MedTech is exciting because healthcare contains so many visible problems: delays, duplication, fragmented information, inaccessible services and staff spending time on tasks that feel unnecessarily difficult. That visibility can also make it tempting to move too quickly from noticing a problem to proposing a product.
A polished demonstration can create the impression that the hard work is finished. In reality, a prototype is often the beginning. The most important questions concern the clinical need, the people affected, the evidence required and the conditions under which the technology will actually be used.
1. Is the problem important enough?
Not every irritation requires a new platform. The first task is to define the problem precisely: who experiences it, how often it occurs, what consequence it creates and how it is currently managed. A broad statement such as “communication is inefficient” is not yet a useful product problem.
It is also worth asking whether technology is the right intervention. Sometimes the better answer is a clearer process, a redesigned form, a change in staffing or the removal of an unnecessary step.
2. Does the solution fit the workflow?
Healthcare technology often fails at the point where a good idea meets a busy clinical environment. A tool may work perfectly in isolation while requiring users to duplicate information, switch between systems or remember an additional task during an already complex process.
A solution that saves time in the demonstration but adds friction in the real workflow has not yet solved the problem.
Workflow mapping should happen early. Who enters the information? When? What happens during the night shift? What if the data are incomplete? What happens when the tool is unavailable? Who has authority to act on what it shows? These questions are not minor implementation details; they are part of the product itself.
3. What evidence would justify trust?
Different technologies require different forms of evidence. A low-risk administrative tool does not need the same evaluation as software influencing diagnosis or treatment. However, every product should be able to explain what success means and how it will be measured.
Useful evaluation might include accuracy, time saved, completion rates, patient outcomes, user burden, unintended consequences or equity of access. The choice should reflect the claim being made. If a product claims to improve patient safety, a satisfaction survey alone is not enough.
4. Who carries the risk and the workload?
Benefits and burdens are not always distributed equally. A system may make reporting easier for managers while increasing documentation for clinicians. A patient-facing tool may work well for confident digital users while excluding those with language, disability or access barriers.
Technology should be assessed from the perspective of everyone who interacts with it, including the people expected to maintain data quality, respond to alerts, support users and manage failures. The hidden operational cost matters as much as the visible feature set.
5. Can it be adopted, maintained and improved?
Implementation is not the final stage after product development. It should shape development from the start. Adoption depends on trust, training, integration, leadership, procurement, governance and a credible plan for support.
The question is not simply whether users can operate the technology. It is whether the organisation can sustain it, learn from it and change it safely over time. A tool that depends on one enthusiastic champion may struggle once that person moves on.
A more useful definition of innovation
Innovation is often associated with novelty. In healthcare, usefulness is more important. A modest intervention that removes ambiguity, saves staff time or makes follow-up more reliable may create more value than a technically impressive system that remains outside the daily workflow.
My interest in MedTech is therefore less about predicting which technology will be most fashionable and more about understanding how a clinical need becomes a trusted, usable and sustainable part of care. The best healthcare technology should not merely look intelligent. It should make the system behave more intelligently.
Part of My Side of the Stethoscope.