McKinsey Rewiring Still Routes Through Email

McKinsey’s State of AI reporting keeps repeating the same lesson: adoption climbs, but value concentrates where workflows and roles are rewired (McKinsey State of AI). Gartner’s 2025 commentary to CFOs is the other half of the sentence: productivity and headcount effects are not automatic (Gartner CFO AI productivity). Harvard Business Review’s email guidance is still relevant for a boring reason: batching and boundaries change how much mail eats your week (HBR email control tip). MIT Sloan’s digital exhaustion article names the enemy as fragmentation, not laziness (MIT Sloan digital exhaustion).

The rewiring mistake

Transformation programs fail when every team adds another destination app, but handoffs stay fuzzy. The “operating model” slide gets updated; the routing of work does not.

Email is still the cross-functional router

Even sophisticated enterprises compress status, approvals, and exceptions into threads. That is not nostalgia. It is coordination physics: vendors, time zones, and legal all meet in mail.

Where via.email sits

via.email is email-native AI: specialist agents at unique addresses, replies in-thread, humans on the send line. It does not access your inbox or external accounts.

• Prep Meeting Brief — prep.meeting.brief@via.email
• Extract Action Items — extract.action.items@via.email
• Assess AI Risk Exposure — assess.ai.risk.exposure@via.email
• Screen Vendor Security — screen.vendor.security@via.email

Related reads

Connect this to Agent Managers Are the New Role. Your Inbox Already Has One., When AI Intensifies Work, One Inbox Pushes Back, and 14% of Workers Have AI Brain Fry. One Inbox Fixes It..

The takeaway

Rewiring is not a workshop. It is where decisions actually get made. If your AI strategy ignores mail-heavy roles, you are optimizing the greenfield while the business runs on forwards.