Chapter 9: A Safer Answer
I logged into the review ten minutes early and arranged my notes beside the laptop. The word draft sat in bold at the top of the test plan. I had left it there on purpose.
A neat document could make an uncertain idea look finished. I didn’t want anyone to mistake one for the other.
Before the meeting, I had run the interrupted-sync sequence again using synthetic data. I repeated it at two different points in the transfer. Each time, the system marked the overall record available before every section had arrived. Each time, the allergy field appeared blank without explaining whether the information was absent, still loading, or unavailable.
The result was reproducible. The proposed fix was not yet a fix at all.
Priya joined the call first. Then the project coordinator, two reviewers I had not met, and David Mercer appeared in separate squares on my screen. One reviewer introduced herself as the safety lead for the proposed evaluation. The other handled testing requirements. I wrote down their names and roles as they spoke.
Mercer nodded to me.
“Claire, walk us through what you observed. Start with what you can prove.”
I shared my screen.
“I can reproduce the failure with synthetic records. I can show where the record-level status changes before all sections finish syncing. And I can show that an unavailable allergy section displays as an empty field.”
I took a breath.
“I can’t yet show that the section-level status approach prevents every version of that failure. It’s a proposal. I haven’t implemented or validated it.”
The testing reviewer leaned toward her camera.
“What would a user think that empty field means?”
“That depends on the user and the interface,” I said. “That’s part of the problem. They might read it as no allergy information, when the system actually doesn’t know yet.”
“Can you guarantee the proposed change would make that distinction clear?”
“No. Not until we build it and test it.”
The silence after my answer was brief, but I felt my shoulders tighten anyway. I had spent so long wanting to prove I belonged in rooms like this that admitting what I didn’t know still felt like walking in with a flaw exposed.
The safety lead asked me to show the reproduction.
I ran the sequence while everyone watched. Priya called out the stages as the synthetic record moved through the system. When the transfer paused, I pointed to the overall status, then to the blank allergy field.
“Same result as yesterday,” Priya said. “And the second interruption point?”
I ran that one too. The display failed in the same general way, though the timing differed.
The testing reviewer asked about delayed sections arriving out of order. I showed her the case in my draft plan.
“I haven’t run it yet,” I said. “It’s on the list.”
“What about a connection that drops repeatedly?”
“Also not tested.”
“Then what do you recommend we do now?”
I looked at the screen share, at my test notes, at the red outline I had drawn around the empty field.
“Don’t put this version in front of clinic staff as something they can rely on. Don’t use clinic records. The system needs to communicate when information is incomplete, and we haven’t proved it can do that reliably.”
The coordinator shifted in her chair.
“That would rule out the evaluation as it was first described.”
“It would rule out that scope right now,” I said. “It doesn’t mean the idea has no value. It means we should learn in an environment where a missing section can’t be mistaken for a complete answer.”
Priya added that a section-level availability indicator might help, but that the team still needed to test how it behaved when information was late, interrupted, or out of order. She didn’t present it as a solution. That mattered to me. I was grateful she understood the difference between a promising direction and evidence.
Mercer listened without interrupting. Then he asked the reviewers what a safer first phase could look like.
They discussed a narrower plan: implement the proposed status changes in a test environment, use synthetic records, and run the interruption and recovery cases before considering anything beyond that. The system would need to show incomplete or unavailable information plainly. If any case produced an ambiguous display, the test would stop until the behavior was understood.
The safety lead wanted written acceptance criteria before testing began. The testing reviewer wanted a record of which cases had passed, failed, or remained unrun. Priya suggested adding delayed and out-of-order arrivals to the first set of tests, not saving them for a later milestone.
I added each point to my notes.
“Would this still be a pilot?” the coordinator asked.
“Not a clinic-facing one,” the safety lead said. “A limited, paid evaluation in the test environment. No patient records, and no staff relying on it for decisions. Anything beyond that would require another review and the necessary approvals.”
The distinction was small in the wording and large in what it allowed us to claim.
Mercer turned back to me.
“Would that scope address your concern?”
“It addresses the immediate risk,” I said. “If the written plan keeps those limits clear, and the next steps depend on evidence rather than a calendar date.”
He nodded.
“Then we’ll revise the milestones. The first one is not deployment. It’s proving we can represent incomplete information honestly.”
The team agreed to authorize the limited, paid pilot in that test-only scope, with oversight and revised milestones. Nothing about it promised immediate expansion. The additional project would remain separate from my signed job, and no one suggested it had created the position I had already accepted.
The coordinator would send updated documents. I would review the scope and terms before confirming my participation.
Mercer paused before ending the meeting.
“Claire, you could have made that failure sound smaller than it was. You didn’t.”
I felt heat rise in my face.
“I didn’t want the test plan to promise more than the system can do.”
“That’s what responsible engineering looks like,” he said. “Not pretending you’re finished. Knowing what you still need to find out.”
The words weren’t a victory speech. They were better than one. They described a standard I could keep meeting after the screen went dark.
When the call ended, Priya stayed on for a minute to compare notes. We agreed that the draft status labels needed review before anyone treated them as interface decisions. I thanked her for backing up the reproduction and making clear what we had—and hadn’t—established.
Then I closed the test plan and read the revised milestones the coordinator had sent. The first page said test environment only. The next said synthetic data. A section near the end stated that further evaluation required a separate review.
I read those lines twice. This time, it wasn’t because my mind was trying to turn two separate opportunities into one bargain. It was because the words mattered.
I replied that I was willing to proceed under the revised scope, pending my review of the written terms. Then I saved the email with my employment confirmation, in its own folder.
My job was secure. The project was a careful next step, not a rescue.
For a while, I let that be enough.
Later, I picked up my phone. Mother’s invitation to meet over the weekend was still there. So was Vanessa’s message, saying she meant what she had told Dad. I had not answered either. I wasn’t ready to claim I knew how the family meeting would go. But I was ready to decide what I needed in order to attend.
I wrote to Mother and Father first.
I’ll come this weekend. I want us to talk honestly about what happened, but I’m not agreeing to pretend it’s resolved. Please don’t ask me to reassure anyone or apologize for being upset. If I need a break, I’ll take one.
Mother replied a few minutes later.
We understand. Thank you for telling us what you need.
I didn’t know whether understanding would last once we were in the same room. I appreciated the answer without treating it as proof.
Then I opened Vanessa’s message. My thumb hovered above the keyboard. I could have asked her what she wanted from me. I could have said I wasn’t ready to forgive her. Both were true, but neither was the whole thing I wanted to say.
So I kept it simple.
I’m coming to the meeting. I need you to be honest, and I need you not to expect me to make this easier for you.
I set the phone down and went back to the updated pilot documents. The work still needed tests. My family still needed a conversation. I could take one careful step in each direction without pretending either one fixed everything.
May you like
That evening, Vanessa’s reply appeared.
I understand. I have something to show everyone at the meeting.
