Give me an example of how you have changed the direction or view of a specific function/department and helped them embrace a new way of thinking.

On a recent project, our design team wanted engineering to wait until every edge case was specified before we started implementation. I understood why they worked that way, because they had seen rushed builds create rework before, but in this case it was slowing feedback a lot. I suggested that we split the work into a small first version with the highest-confidence flows, and I put together a simple list showing what was safe to build now versus what still needed design decisions. After we tried that on one feature, the team saw that they could get earlier feedback without losing quality, and they used the same approach on the next couple of features too. What I think changed was not just that one decision, but their view that engineering had to wait for full completeness before meaningful work could begin.

On a small product team where I worked, the product managers always pushed to pack sprints with visible new features and ignored maintenance work, which left engineers firefighting. I sketched a simple three-point rubric (user impact, frequency, and maintenance cost) and volunteered to score a subset of the backlog with one of the PMs for two sprints as a trial. After we presented the scored backlog, the PMs moved a few medium-priority maintenance items up, and we noticed fewer repeat incidents and quicker fixes for small regressions. Because the rubric made the trade-offs concrete, the product team started reserving a fixed portion of each sprint for upkeep and used the same scoring when planning future roadmaps.