John Friedman, Microsoft\u2019s Microsoft 365 Chief Design Officer, described<\/a> the effort as \u201can AI-forward design system we\u2019re crafting to feel intentional and humane.\u201d Microsoft still wants Copilot visible across work apps, but it is trying to make that presence feel built in rather than bolted on.<\/p>\n How Microsoft Wants Copilot to Work <\/p>\n Microsoft centers the redesign on the Dynamic Action Button, a floating in-app Copilot shortcut that changes with the task on screen instead of acting like one static icon. Users would see chat, suggestions, or in-document actions from a control that stays near the document, worksheet, or presentation already in front of them.<\/p>\n \u00a0<\/p>\n Another piece is Throw & Catch, which Microsoft uses for a handoff model that moves Copilot between chat, on-canvas actions, contextual prompts, and side panels. Friedman frames the feature as a way to pass context and focus between surfaces instead of leaving each one to act like a separate tool. Microsoft also wants Copilot to read user intent more closely so the assistant can respond to the current job without a full manual prompt every time.<\/p>\n Microsoft has already pushed fewer entry points and updated shortcuts<\/a> across Office, so the new design extends an existing cleanup instead of reversing course. Copilot remains central to the product strategy. Microsoft is changing how often the assistant steps forward and how easily users can tell where it is active.<\/p>\n Why the Redesign Follows Earlier Copilot Friction <\/p>\n Recent feedback helps explain why Microsoft is reworking the interface now. Microsoft rolled back floating Copilot button changes in Word, Excel, and PowerPoint after complaints that the controls felt too intrusive. It also let Office users remove the floating Copilot button, turning a layout choice into a visible usability issue.<\/p>\n Microsoft had already tried to reduce earlier interface fragmentation in March 2026 by removing confusing Copilot app skills<\/a> in Excel. In March, that fix cut overlapping entry points in one app. Current design work broadens the same correction into a cross-app interaction model for Microsoft 365.<\/p>\n Microsoft\u2019s unified Copilot ambition from 2023<\/a> also remains part of the backdrop. Microsoft still wants one assistant to span Windows, Microsoft 365, Edge, and Bing. Now the harder question is how that assistant can stretch across many surfaces without making those surfaces feel crowded.<\/p>\n Microsoft 365 Stakes and Market Pressure <\/p>\n Microsoft has already acknowledged that early Copilot integration across products created fragmentation<\/a>. Earlier rollout history raises the stakes for the redesign because layout, timing, and continuity affect whether Copilot feels coordinated or scattered. Design choices now carry product weight, not just visual polish.<\/p>\n Enterprise rollout pressure sits underneath that design work. Microsoft says organizational factors accounted for 67% versus 32%<\/a> of reported AI impact compared with individual factors. Manager support, internal trust, and rollout discipline may matter as much as feature depth if Copilot becomes more deeply embedded in Word, Excel, and PowerPoint.<\/p>\n<\/a><\/p>\n
<\/a><\/p>\n