Product1 publisher2 min readPublished
Ryan Roslansky's exit moves Office and Teams into Microsoft's Copilot organization
Ryan Roslansky, Microsoft's Office and Teams chief, is leaving after nearly 18 years, a week after the company announced its new Copilot. His teams now report to Charles Lamanna in the Copilot, Agents, and Platform organization, so Office is run from inside Microsoft's Copilot group.
The Product Desk · Product desk
What happened
- Roslansky, LinkedIn's CEO until recently, took over Office last year and added Microsoft Teams to his remit earlier this year.
- Microsoft's chief design officer, Jon Friedman, is moving to report to Copilot chief Jacob Andreou.
- This is the Office teams' second major reshuffle this year, following the retirement of Rajesh Jha, who headed the experiences and devices group.
- Dan Shapero, appointed LinkedIn CEO earlier this year, stays in the job and will report directly to Satya Nadella.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- decision Customers holding Office or Teams roadmap commitments made under Roslansky now need them reconfirmed with Lamanna's organization, the new owner of those teams.
- exposure The one Office executive on record calling fully AI-generated documents a doom loop is the one leaving, and the source records no similar view from Lamanna or Andreou.
- constraint With design reporting to the Copilot chief, any internal argument for keeping Office documents human-written now has to be won inside the Copilot reporting line.
About a month before his exit, Ryan Roslansky used a LinkedIn post to call fully AI-generated documents "a doom loop" for workers [4]. "If we're not careful, we'll end up with a very expensive way to avoid writing and reading in an ocean of sameness, genericness," he said in the post [5]. In the habit his words describe, a model drafts the update so the sender skips writing it, and another model summarizes it so the recipient skips reading it [5].
Microsoft is positioning the new Copilot as "the OS for work" [3]. Behind the label, the change is a set of new reporting lines [6][8]. Nadella's internal memo credits Roslansky's group with the groundwork. "Over the past year, Ryan's team has done critical work bringing together the product, engineering, and design foundations that have made this next phase possible," Nadella said [10]. Roslansky's own memo said the job meant "figuring out what Copilot, and the future of work, should look like as one ecosystem," and thanked staff who "set aside their own roadmaps to make that happen" [12][13].
The only link between the doom-loop post and the departure in the evidence is timing [4]. Roslansky gave geography as his reason. "I know what it would take for me to lead the next phase of this work well: being in Redmond full time, every day," he wrote to his teams. "But my life and my family's life are here in the Bay Area." [11]
The admin rolling out Copilot drafting next week can check Roslansky's worry against their own usage. The test is two questions about each document: who wrote it, and who read it. Human-written documents read by humans are last year's Office. Model drafts that a person edits before sending are drafting help, and the edits are the evidence it worked. Model summaries of long human documents save reading time on work someone still did. The fourth cell, a model draft read only through a model summary, is the loop Roslansky named [5].
Usage counts climb in all four cells. They cannot tell a team which cell it is in. Two shares can: generated drafts a person edits before sending, and recipients who open the full document instead of stopping at the summary. If both shares fall while Copilot usage rises, the team has moved into the fourth cell.
What to watch
- Whether Lamanna or Andreou takes a public position on fully AI-generated documents, either echoing or dropping Roslansky's doom-loop warning.
- Whether Microsoft names a dedicated Office or Teams leader under Lamanna or runs the apps directly from the Copilot, Agents, and Platform group.