Tell me about a time you disagreed with your manager, what happened?

The agency founder wanted me to build a feature for Tiny Steps that would let agency admins manually override the credential lockout system. Her reasoning was practical: sometimes a therapist's paperwork is stuck in processing, the credential is technically valid, but the system shows it as expired. Locking them out means they can't see their patients.

I disagreed. The lockout exists because when a therapist's medical license or background check expires, it's a compliance violation for them to access patient records. That's not a UX decision. That's a legal boundary. An admin override would let anyone bypass it, and if that override was used incorrectly, the agency could be in regulatory trouble.

I didn't just say no. I built what she actually needed: a credential waiver system. An admin can request a temporary waiver for a specific credential, with a documented reason, an expiration date, and a full audit trail. The therapist gets access. The compliance record shows exactly who approved it, why, and when it expires. 48 waivers have been processed through the system.

What I learned is that disagreement in engineering is almost never about who's right. It's about finding the solution that satisfies both the human need and the constraint. The agency founder's need was real. The compliance requirement was real. The answer wasn't either/or. It was a third option that honored both.