DIGITAL

02 · Digital · Digital transformation

Digitalizing
medicine
starts
with the doctor

Nearly ten years of hands-on practice inside a working clinic. I design and launch digital transformation as a product, and I build the teams that carry it through to results.

Discuss a project How I work

Lens

Product

Every decision is tested against its value to the doctor and the patient.

Lens

Data

Clinical and management decisions grow out of structured information.

Lens

Doctor

Technology fits into the doctor's usual workflow with as few new steps as possible.

Lens

How I look
at the problem

Three principles behind every project

A product mindset

Every decision is tested against its value to the doctor and the patient. What ships is what helps a specific moment in the appointment.

Grounded in data

Clinical and management decisions grow out of structured information. Data becomes the basis for daily work, not a report once a quarter.

Gentle adoption

Technology fits into the doctor's usual workflow and asks for as few new steps as possible. It's learned almost invisibly, within the normal flow of the appointment.

Practice

What practice
shows

Observations tested over years of work inside a clinic

Data appears on its own, as a trace of the doctor's ordinary work

A well-built system gathers information from the usual actions of an appointment. The doctor cares for the patient while structured data accumulates alongside, as a natural by-product.

Lasting adoption happens one habit at a time

Each step settles in before the next one is added. That keeps the change manageable for the team and gets it into daily use.

The medical record is grown from the real flow of the appointment

The living process shapes the digital document. The system mirrors how the doctor works, so it takes hold within the first few weeks.

Technology sticks when it saves the doctor time from day one

Quick, tangible benefit keeps the team using a new tool. Value at the start matters more than a rich set of features.

Method

How the work
is done

Value is tested on the live process before a line of code

Step 01

Discovery

Immersion in the clinic's real flow, conversations with doctors and administrators, and finding the point where digitalization pays off.

Step 02

Value hypothesis

We frame a narrow scenario and the benefit we expect for the doctor and the patient. One clear hypothesis instead of a long technical spec.

Step 03

Quick manual test

We test the value on the live process by hand, with no app development yet. The doctor already gets a result at this stage.

Step 04

Decision

Based on the test, we make a clear call on the scenario's future. Only what's proven goes into the product.

Each cycle ends in one of three decisions: GO ITERATE STOP

Team

How I build
teams

Around a specific task, and by the ability to deliver

A team is assembled around a specific task. At the core is a trio of doctor, product and engineering, each fluent in the others' language. Selection is by the ability to see things through and to work in a medical context.

Core

Doctor

Holds the clinical reality and the common sense of the appointment. Makes sure the solution helps the real work.

Core

Product

Turns a clinical scenario into clear value and priorities. Carries hypotheses from Discovery to a decision.

Core

Engineering

Builds a reliable solution for the medical context. Works in short, testable steps.

Where it applies

Where it
works

The levels this approach applies to