Digital health products fail on behaviour, not on technology

A digital health product can measure a great deal, organise data and present results in clear charts. But if the user does not know what to do with that information, the dashboard may never translate into daily life.

This is where the product development question begins: Which behaviour of the user do we want to support, under what conditions, and how?

Measurement must connect to a next step.

Seeing a value change does not, on its own, make a decision easier. Users need to understand what the change means, how far it can be interpreted and what step it calls for.

The product does not have to generate a recommendation from every data point. Sometimes it is right to explain that there is not enough information, sometimes to keep tracking, sometimes to point towards professional support. What matters is a clear link between the information shown and the behaviour expected.

Without that link, the burden of interpretation falls on the user.

The scientific basis should be visible in the experience's decisions.

Citing research is a starting point. The real design work is deciding how that knowledge is used in the product.

Which data do we collect? Why do we ask for measurements at this frequency? When do we give feedback? What is the basis for the step we suggest, and where is it limited?

The answers should shape the timing of notifications, the language of feedback and the effort asked of the user. The scientific basis then shows up in how the product behaves.

A reason to return must carry value for the user.

A notification can get an app opened. For users to find returning meaningful, each visit needs to meet a need.

That value might be seeing progress, reducing uncertainty, easing a difficult step or clarifying the next decision. Entering new data or looking at the same chart each time does not create it by itself.

So alongside 'How do we bring users back?' we must also ask 'What do they gain when they return?'

Behaviour design must account for the realities of everyday life.

Users are sometimes busy, sometimes low on motivation, sometimes unable to carry out the suggested step. The product's flow has to adapt to these conditions.

Small, achievable steps, a clear purpose and the ability to pick up easily after a break are therefore design decisions. The effort asked of users should be weighed against the value they receive.

Success metrics must align with the product's health purpose.

How often the app is opened says something about the experience. Understanding whether the user's need is being met requires other measures: Can they understand the information? Can they choose the right step? Can they sustain the routine they are aiming for?

In some products, users may need less support over time. That possibility should be built into the definition of success from the start.

Strategy in digital health means bringing the scientific basis, the step the user can take and the need that makes that step worthwhile together in one experience. The dashboard gains meaning to the extent that it fulfils its role within that experience.