Satya Nadella Rebukes Scout VP Over ‘Make People Addicted’ Memo

On June 2, Microsoft unveiled Scout, its first “Autopilot” AI agent, at Build 2026 in San Francisco, pitching it as a way to help workers take back their time from inbox and coordination drag. Hours later, 404 Media published an internal Microsoft strategy document describing Scout’s launch roadmap in three phases. Phase one’s heading read: “Make people addicted.”

The document was co-authored by Omar Shahine, the corporate vice president leading the Scout project, and by a second executive, Jakob Werner. CEO Satya Nadella has since rebuked it publicly, calling the document “nonsense,” but the authorship question he raised is easier to resolve than his message implied, and the publication he rebuked has pushed back firmly on his framing.

The Three-Phase Plan

The Agent at Launch

Microsoft had been developing the agent under the codename ClawPilot, as part of a project called Project Lobster, long before the June 2 announcement. The product runs on OpenClaw, the open-source agentic framework created by developer Peter Steinberger, which accumulated 180,000 GitHub stars in the three months after its November 2025 launch. Scout connects to Teams, Outlook, OneDrive, and SharePoint, carries its own Entra identity, and acts continuously on a user’s behalf without waiting for a prompt; unlike a standard chat assistant, which responds only when asked.

The internal pilot showed the concept working before any public launch:

• 1,000+ Microsoft employees, including the CEO, used the agent internally before the public announcement
• 20 million paid Microsoft 365 Copilot subscribers as of May 2026, the installed base the agent is designed to expand into
• Microsoft targets October 2026 for the agent’s general availability
• 3 phases in the strategy document, describing a journey “from addictive app to agentic platform”

Phase One’s Stated Goal

The strategy document, titled “ClawPilot: Overview and Plan with Project Lobster,” described that journey in three phases. Phase one’s heading stated: “Make people addicted.” The instructions beneath told the team to “continue shipping the standalone ClawPilot experience, pilot the UX, grow the user base, and build the skill and tool ecosystem that makes people depend on it daily,” per 404 Media’s reporting. The document added that the process was “already happening organically.”

Internal pilot data backed that claim. Employee testers showed what the document described as “Daily Usage with High Retention and intensity of usage (chats, queries, workflows, skills),” and the agent had spread widely inside Microsoft without a formal announcement, no marketing push, and no org-wide directive. The document cited that organic spread as evidence the approach would translate externally.

Phase two covers linking the platform to broader AI networks; phase three positions the agent as a full agentic ecosystem open to third-party developers. Microsoft announced an SDK at the conference enabling external developers to build custom skills into the agent, which maps directly to the “agentic platform” endpoint in the strategy document.

One anonymous Microsoft employee told the publication the language was “very troubling,” saying addiction “is something no product should be making a part of its build strategy.”

The VP Who Wrote Both

As corporate vice president for the Scout project, Shahine wrote the official launch blog post introducing the agent publicly and was quoted in coverage describing Autopilots as systems that act autonomously “without needing to be prompted each time.” His role as the project’s lead is documented on his personal blog, his LinkedIn page, and in Microsoft’s own press materials for the event.

His name also appears as a co-author on the leaked strategy document, alongside Werner. Together they produced two documents in the same week describing the same product in notably different terms.

At the conference, Microsoft demonstrated the agent preparing an entire quarterly business review without the user switching between a single app, per Bloomberg’s coverage of the event. His public blog post described the same product in terms of autonomous task completion, risk surfacing, and coordination, with no mention of dependency or retention as goals.

Consumer tech companies routinely target daily engagement and habit formation in product strategy. “Addicted” is a step further than the industry’s standard language of stickiness or daily active users. The document also carried a note that it was “co-created turn-by-turn with AI. Human verified every sentence.” That attribution doesn’t change the two authors’ formal ownership; both are named in the document, and their identities as the project’s leads are publicly documented.

A Rebuke With a Fuzzy Target

What Nadella Wrote

Nadella’s response, sent to roughly 50 of Microsoft’s top engineers working on AI products and reported by The Information, came after the document’s public exposure. He attached a copy of the report and posted the following to an internal board:

This is absolutely a non goal! If anything we are doing the exact opposite. We want to make sure AI empowers and adds real value to human endeavor and broad economic growth! We should make sure that our teams are clear about this. Not sure what this document is or who is writing and leaking this nonsense! They may want to go work elsewhere.

The rebuke went to The Information. So did Microsoft’s prepared statement on the subject. Frank Shaw, a Microsoft spokesman, told the outlet that the agent is designed to help people complete tasks more effectively, with the company’s goal being to give time back to users. Users will have “clear choice and control,” Shaw said.

Neither the rebuke nor the statement was shared with the publication that obtained and published the strategy document.

The Publisher’s Rebuttal

404 Media responded publicly, rejecting the framing that the document’s authorship was unclear. “The document we reported on was not some random document,” the outlet wrote. “As we wrote at the time, the strategy document was written by Microsoft executives Omar Shahine, Jakob Werner, and some sort of AI writing tool.” The outlet noted that the project lead’s identity is documented on his own blog, his LinkedIn profile, and in Microsoft’s own announcement materials, and that he had written publicly about his role on the project numerous times.

The outlet also described what happened before publication. It had specifically told Microsoft it was writing about the addiction language in the document and had asked for comment, context, and more information. Microsoft sent back a link to the project lead’s public blog post. The company then, per the outlet, “attacked our report internally and externally to another media outlet.”

The project lead who authored both documents remained the corporate vice president overseeing the agent through the week of reporting. Nadella’s internal message questioned the document’s origin while the document was publicly attributed to the executive who wrote the conference’s official announcement the same day.

When “Addicted” Became a Liability

On March 25, 2026, ten weeks before the strategy document became public, a Los Angeles County Superior Court jury found Meta and YouTube liable for addictive platform design, awarding $6 million in the first bellwether trial of consolidated litigation now involving more than 2,400 cases against social media companies. Meta was found 70 percent responsible. A second user trial is scheduled for July 27; a school district case begins June 15.

The litigation has drawn direct comparisons to the 1990s tobacco lawsuits, which forced the industry to restructure its marketing practices and settle for hundreds of billions of dollars. In those cases, the central question became what companies knew about addiction and when they knew it. A strategy document with a labeled phase headed “Make people addicted” sits close to that question, even if the agent’s users are enterprise workers operating inside organizational policy controls rather than teenagers on a social feed.

European law adds a separate dimension. Article 5 of the EU AI Act prohibits AI systems that deploy “subliminal, manipulative, or deceptive techniques” to materially distort behavior in ways causing or likely to cause significant harm. The prohibition has been enforceable since February 2025, with fines reaching €35 million or 7 percent of global annual turnover. The leaked document does not automatically place the agent under that prohibition; the EU Act targets behavioral manipulation causing harm, and the agent operates within organizational tenant-level governance. But the phrase is now visible to regulators in a way it wouldn’t have been without the leak.

What Enterprise Buyers Are Now Asking

The agent’s immediate market is enterprise organizations running Microsoft 365 E3 or E5. Getting access requires:

• A Microsoft 365 Copilot license
• A GitHub Copilot license
• Enrollment in Microsoft’s Frontier program, with Intune policy configuration and an opt-in attestation completed

That procurement gate means every adoption decision goes through a buying cycle that includes legal, compliance, and security reviews. Enterprise buyers don’t just read press releases; they assess what product teams appear to be optimizing for.

Microsoft 365 Copilot’s own adoption curve gives context. Around 3 percent of Microsoft 365 customers were paying for the Copilot add-on at the start of 2026, a figure that climbed to 20 million paid subscribers by May after more than a year of sustained selling. The agent enters that same enterprise base as a further add-on, with broader preview access opening in late June before the general availability push. At the same event, Microsoft unveiled seven new in-house MAI models, the first output from its own AI superintelligence lab, in a week meant to show enterprise customers a coherent AI roadmap. The strategy document became the story from that week that required the most explanation.

By October 2026, when the agent reaches general availability, its behavior inside enterprise tenants will have replaced the leaked document as the primary evidence of its design intent.