Product design · Web app

Details generalized for confidentiality

Child health metrics app

Nasdaq-listed start-up developing medicines for rare diseases · 2025

A hand-annotated flow diagram of five tracker screens. Screen 4, the medication question, and Screen 5, the combined confirmation, are circled in red.(view full size)
I drew the client’s requested flow to show two problems they hadn’t seen.

Outcome

A new version of a pediatric health metrics tracker was about to go into build with a confusing, data-corrupting question. It instead shipped with two simple, fit-for-purpose flows. Unnecessary steps were eliminated so caregivers of ill children could complete their routine logging with less effort. The client got cleaner data and confidence for a $amount withheldK expansion.

Problem

The client’s app had replaced paper for caregivers logging their children’s bowel movements, a key measure for the client’s investigational medicine. We had finished designing an updated version and were set to build when the client added a medication-use question. The new request carried two risks. The first was user confusion, because the medication question was to be answered once a night, but caregivers were expected to complete the stool tracker multiple times each day. The second was imprecise data, because a single confirmation asked about medication and stools together, preventing a statistician from telling the responses apart. A fix was needed before user acceptance testing, or the $amount withheldM project faced expensive rework and delay. The client hadn’t yet seen the conflict with their own end goal.

My role

I bridged the client and the build by aligning the design with how caregivers would actually use the app, optimizing the flow for efficiency, and co-creating with the client and our internal teams. A solutions architect wrote requirements, product delivery engineers built, and clinical advisors addressed compliance and medical data use.

Constraints

Five factors bounded what a fix could look like.

Five constraints on the fix and what each one meant
ConstraintWhat it meant
The client needed a medication question,
but not in the way they requested
Keep the medication-use question, change how it’s asked
Engineers confirmed the user issue and flagged data inconsistenciesThe design couldn’t be built as specified
The clinical team advised on what data the client requiredThe client’s needs, not the current design, set the scope
The direction came from the client, and it would have caused errorsThe solution had to be one the client arrived at
Everything had to be resolved before UATFix it now or face rework, delay, and costs

Guiding principle

Ask what the data is for before designing how to collect it.

My first attempt to resolve the issue was to prompt self-discovery by the client. I asked them open-ended questions about how their request would work in practice, such as “How would data be reconciled if a caregiver answers YES and then NO, referring to the same day?” Their answers showed they didn’t yet recognize the incompatibility.

My second attempt was to use flow diagrams. I diagrammed the flow the way a solutions architect had once walked me through a specification. Now the client could picture a user moving through their instructions. The problem I’d described became real, and the client became invested in solving it.

Then we hit a new problem. Every attempt to fix the design made the flow more complicated. After much back-and-forth, the flow was snarled even though the obstacle was visible to everyone: the medication question now sat first, asking about yesterday.

A later version of the flow with six screens. Screen 1, the medication question asked about yesterday, is circled in red.(view full size)
Iterating on the client’s single flow resolved the logic at the cost of usability. Caregivers had to wait until the following day to log whether their child took medication.

I went back to basics. What did the client need to collect, what didn’t they need, and why? I confirmed there were no technical or clinical limitations on splitting the task in two. The client needed one yes-or-no answer about medication per day regardless of the stool count, with details only when the answer is yes. As the client put it, “We would like to know in a given day if the child was given medicine to pass stool irrespective of the number passed.” The client agreed that two simplified flows, one for medication use and one for stools, would be less of a burden on caregivers.

How the medication question was added to the tracker The project started with a single-flow stool diary. A medication question was inserted, which produced one confirmation question covering two data items. Clarifying the client’s needs was the decision point. The shipped path is two fit-for-purpose flows: a stool flow logged as often as needed, and a medication flow with one daily yes-or-no, then name and dose. Branching off the same decision is the rejected alternative: a single-flow stool and medication diary, where the answers can’t be told apart. PROJECT DECISION Single-flow stool diary Medication question inserted One confirmation for two data items Client needs clarified Two fit-for-purpose flows Stool as needed Medication 1x daily Single-flow stool & medication diary Answers mixed Rejected alternative How the medication question was added to the tracker The project started with a single-flow stool diary. A medication question was inserted, which produced one confirmation question covering two data items. Clarifying the client’s needs was the decision point. The shipped path is two fit-for-purpose flows: a stool flow logged as often as needed, and a medication flow with one daily yes-or-no, then name and dose. Branching off the same decision is the rejected alternative: a single-flow stool and medication diary, where the answers can’t be told apart. PROJECT DECISION Single-flow stool diary Medication question inserted One confirmation for two data items Client needs clarified Two fit-for-purpose flows Single-flow stool & medication diary One confirmation, answers mixed Rejected alternative
The decision. Two fit-for-purpose flows shipped. Forcing a single flow was the rejected alternative.

Uncoupling the flows made the task easier for caregivers and improved data integrity at the same time. Learning what data the client needed, and why, is what made a good solution possible.

Cleaner data gave the client confidence in a $amount withheldK expansion, and the diagrams gave them confidence in the decisions they made with us.

The shipped medication flowThe shipped medication flow. Start. Did the child take stool medication today? If yes, enter the medication name and dose, then: any other stool medication? Yes loops back to enter another; no goes to a review screen. If the first answer is no, go straight to the review screen. Then done.MEDICATION DIARY FLOWStartStool medicationtaken today?Enter name & doseAny other stoolmedication?ReviewDoneYesNoNoYes The shipped medication flowThe shipped medication flow. Start. Did the child take stool medication today? If yes, enter the medication name and dose, then: any other stool medication? Yes loops back to enter another; no goes to a review screen. If the first answer is no, go straight to the review screen. Then done.MEDICATION DIARY FLOWStartStool medicationtaken today?Enter name & doseAny other stoolmedication?ReviewDoneYesNoNoYes
The shipped medication flow. One yes-or-no question, with details only when the answer is yes.
The shipped stool flowThe shipped stool flow. Start. Did you enter all the stools your child had yesterday? If no, select the stool type for yesterday, then review. If yes, go to review. Then: did you enter all the stools your child had today? If no, select the stool type for today and return to review. If yes, done.STOOL DIARY FLOWStartAll of yesterday’sstools entered?ReviewAll of today’sstools entered?DoneSelect type, yesterdaySelect type, todayYesNoYesNo The shipped stool flowThe shipped stool flow. Start. Did you enter all the stools your child had yesterday? If no, select the stool type for yesterday, then review. If yes, go to review. Then: did you enter all the stools your child had today? If no, select the stool type for today and return to review. If yes, done.STOOL DIARY FLOWStartAll of yesterday’sstools entered?Select type, yesterdayReviewAll of today’sstools entered?Select type, todayDoneNoYesNoYes
The shipped stool flow. Yesterday first, so the count is complete.

Learning

Next time, I’d start with the diagram. My initial attempt at a fix was unproductive, with open-ended questions that failed to help the client discover the issue themselves. The diagram did in one discussion what abstract clarification questions couldn’t in several.