How do you handle prototype development when you don't have time for prototypes, and how do you manage senior developers who insist on their own approach?

When time for prototypes is limited, I prioritize rapid, low‑fidelity prototypes that validate core assumptions. I start by defining the problem scope and the key user interactions, then use tools like Figma, Balsamiq, or even a simple whiteboard to sketch the flow. I keep the prototype lightweight—just enough to test the hypothesis—so that it can be built and iterated quickly. I also involve stakeholders early; if a senior developer has a preferred approach, I schedule a short sync to align on the architecture and constraints. I explain the benefits of a quick prototype: it surfaces hidden requirements, reduces risk, and saves engineering effort in the long run. By setting clear expectations and deadlines, I ensure that the prototype stays on track. After the prototype is validated, I hand it off to the senior developer for implementation, ensuring that the design decisions are documented and that the final solution aligns with the team's standards. This approach balances speed, quality, and collaboration, and it keeps senior developers engaged without forcing them to reinvent the wheel.