"A standalone platform team can work — but only when the customers (editors, journalists) are treated as embedded users in the product process, not downstream consumers"
Evidence from the Archive
CNN
Upasna Gautam runs CNN's CMS platform team with journalists physically embedded in the product process — research sessions get scrapped mid-flight when breaking news hits
Her counterexample: standalone platform teams aren't inherently bottlenecks; the failure mode is distance from users, not reporting lines
Gautam runs the platform team that builds the content management system powering CNN Digital — the software journalists and editors use to write and publish every story. Her team is a textbook 'core platform team': horizontal, shared, foundational, not customer-facing publicly. But her experience complicates the standalone-is-a-bottleneck story.
Her stakeholders aren't abstract internal engineers — they're editors and journalists with visceral needs, physically embedded in her product development process. The team is independent in reporting structure and owns a multi-year CMS replatforming project, but the direct, real-time, round-the-clock access to users means the team never drifts into the context vacuum. Her implicit argument: the bottleneck risk comes from distance to the user, not from reporting lines.
In Upasna's own words: "On my team, the core platform team, our stakeholders and our customers, like I mentioned, are journalists and are editors. Which presents a really unique dynamic, and it's one that I love. We have direct access to our customers at all times of day, for better or for worse, and they're embedded into our product development process." (Describing what it's like running a standalone core platform team whose 'internal' users are journalists on deadline.)