This article examines how Pfizer operationalized lessons from its COVID-19 vaccine development into a permanent cross-functional operating model. The central problem addressed is how to sustain the speed and decisiveness of crisis-mode operations within a large, historically bureaucratic organization. Sherry Cassano, Pfizer's chief talent officer, describes a framework called 'project-based ways of working,' anchored by three principles: a single accountable decision-maker per team (the 'pilot in command'), a maximum of one governance layer above the team ('air traffic control'), and fit-for-purpose team composition. Key evidence includes the model's scaling trajectory from 9 to 700 teams, and its embedding into Workday's performance management system, where the pilot in command — not the functional manager — assesses project-related performance. Two implementation challenges are identified: functional managers required more transition support than anticipated, and teams systematically underestimated the scope of their own authority. The article concludes that structural change requires both system-level reinforcement and deliberate psychological safety work to become culturally embedded. Key insights: Pfizer's 'pilot in command' model assigns single-person accountability to cross-functional teams, explicitly displacing committee-based and co-lead structures. Performance management system integration — specifically graying out functional manager fields for project goals in Workday — was identified as a critical mechanism for making authority structures visible and enforceable. Functional managers experienced significant role disruption as their responsibilities shifted from decision-making to coaching, a transition the organization underestimated and had to address through dedicated support forums. Practical takeaways: Embedding authority structures directly into performance management software (e.g., restricting field access by role) can operationalize organizational design decisions in ways that slide decks and policy documents cannot. Scaling a new operating model requires parallel workstreams: one for team-level capability building and one for the managers whose roles are substantively changed by the new structure.