Client communication · Mobile app

Details generalized for confidentiality

Seizure & medication app

Nasdaq-listed start-up developing treatments for neurological disorders · 2022

Seizure diary screen in Portuguese for October 17, with a link to the calendar, columns for seizure type and count, report buttons, and a confirmation that no seizure occurred that day.
The seizure diary, in Portuguese: no seizures reported for today.

Outcome

A showstopper bug just before user acceptance testing (UAT) ended up strengthening the client relationship. The app launched successfully, equipping caregivers to log seizures and medication on their phones instead of paper. Months later, as the client grew their business, they came back with a new bid request. Internal teams changed their specification checks so this class of problem wouldn’t recur.

Problem

The app wouldn’t load and we didn’t know why. The bug was discovered before UAT. Not delivering on time would jeopardize the client’s company, including their financial backing. A failed launch could shutter them. The stakes were high for everyone, and I had to keep the client’s confidence while our engineers searched for a cause.

My role

I was the client’s advocate inside our team and our team’s voice to the client. I managed the relationship, problem-solved with internal and external stakeholders, and made sure deliverables matched needs. R&D and delivery engineers identified the issue, checked specifications against technical limitations, and reviewed code. The localization team handled translations.

Constraints

Four constraints limited what I could do for the client.

Four constraints and what each one meant
ConstraintWhat it meant
We could not offer a cause, a fix, or a timelineReassurance had to come from how we communicated, not from certainty
The client’s frustration was legitimateTheir concerns had to be heard and acknowledged, not dismissed
Short-term financingA delay could threaten the client’s survival
Our team was distributed across Europe and the USSlower when the situation was ambiguous

Guiding principle

Actions under fire show you’re on the same team.

I knew my communication with the client could either sustain or break our collaboration when under pressure. I told the client the moment the problem was confirmed, with nothing yet to offer but a commitment to fixing it. That decision is what strengthened the relationship.

I listened to and acknowledged their frustration. I anticipated their questions so they weren’t left waiting for responses. I shared what we knew and what we didn’t yet know. My message was clear: “I recognize this is not a satisfactory answer. Resolving the problem is our highest priority.”

I braced for the client to explode. Fortunately, their reply was a relief: “We do find your response satisfactory and appreciate your transparency. These things happen.” Because the reaction was reasonable, everyone could concentrate on the solution.

Timeline of the incident The bug is found and the app won’t load. Then comes the decision of when to tell the client. The chosen path: the client is told at once, before the cause is known, then several days of investigation, then the cause is found, an OS incompatibility, then user acceptance testing. Branching off the same decision is the rejected alternative: waiting to tell the client until there is a fix, risking trust. PROJECT DECISION Bug found App won’t load When to tell the client? Told at once No cause yet Build trust Investigation Several days Cause found OS incompatibility UAT Wait to tell Until there is a fix Risk trust Rejected alternative Timeline of the incident The bug is found and the app won’t load. Then comes the decision of when to tell the client. The chosen path: the client is told at once, before the cause is known, then several days of investigation, then the cause is found, an OS incompatibility, then user acceptance testing. Branching off the same decision is the rejected alternative: waiting to tell the client until there is a fix, risking trust. PROJECT DECISION Bug found App won’t load When to tell the client? Told at once No cause yet Build trust Investigation Several days Cause found OS incompatibility UAT Wait to tell Until there’s a fix Risk trust Rejected alternative
Communication style. We told the client as soon as the problem was confirmed, before the cause was known. The alternative was to wait until we had a fix, and risk trust.

After several days of investigation, R&D flagged an OS incompatibility. The cause was embarrassing, but the client was still with us.

Learning

I would facilitate internal communication more intentionally. With the team spread across time zones, meeting in the same room wasn’t an option. Messaging back-and-forth works well for quick answers but can slow investigation when the situation is more ambiguous. I’ve since found that brief daily calls help to align the team and sustain momentum when solving a time-sensitive problem.