A product manager asks you to build a visually complex feature and insists on a one-week delivery, but your estimate is two weeks. How would you handle the conversation and what options would you propose to meet business goals while managing technical risk?

I’d start by sharing a clear, itemized breakdown of my two-week estimate so the PM understands where time is spent: design polish and animations (3 days), integration with our language-model API and edge cases (4 days), accessibility and QA (3 days), and buffer for unforeseen bugs (4 days). Then I’d propose pragmatic options: deliver a focused MVP in one week by removing nonessential animations and visual extras, behind a feature flag so we can iterate; or split into two milestones — core functionality in 1 week and visual enhancements in week two. I’d also offer to prototype the most complex visuals first (1–2 days) to validate feasibility. I’d quantify trade-offs (e.g., 30–50% less polish, 0% cut to accessibility/testing) and agree acceptance criteria so business goals advance without taking unnecessary technical risk.