AI and Customer Support
I used to think senior engineers earned trust by always having an answer. Then I watched a launch slip because nobody wanted to say “I do not know.”
At a multi-site outpatient clinic group, we rebuilt the patient app around a new sign-in flow and shared-family access. Tight timeline, small team, a vendor SDK in the middle.
The staff engineer stayed crisp in every meeting. No uncertainty, no pauses. Everyone else stopped asking basic questions because it felt like we were the only ones behind.
What broke us was not the hard problem. It was the unspoken assumption that someone had already validated the edge cases.
When the first round of app review feedback hit, we found two different interpretations of “guardian consent” buried in the requirements. Fixing it meant rewiring screens, logs, and support playbooks in one week, plus a second security review.
This month, mobile teams are also juggling shifting app store compliance expectations and court-driven policy timelines in the US, so “I skimmed it” quietly becomes a release risk.
The turning point was simple: the same senior person started saying “I do not know yet” in front of everyone.
Within two sprints, the quiet questions showed up early and our QA bounce-back dropped roughly 30%.
It makes me wonder whether confidence is sometimes just a way to hide responsibility.