Microsoft's EngThrive framework reframes developer productivity around outcome metrics rather than activity metrics. Key insights include: engineers spend only 10-15% of their time actively coding; AI is shifting the SDLC so that 'create' time approaches zero while 'plan' and 'validate' grow; and productivity should be measured at the system level, not the individual level. The framework uses three core metrics — speed (idea-to-customer time), ease (innovation time ratio), and quality (defect escape rate, MTTR). Two case studies are shared: an 8-week focus-time initiative that recovered 2.1 hours/engineer/week and 55,000 total engineering hours, and a time-to-first-PR initiative using an onboarding agent ('First Mate') that compressed new-hire ramp time below one week. The central principle is that targeting outcome metrics creates real value, while targeting activity metrics (tokens used, PR counts, lines of code) produces gaming and noise.