Email and office suites: taking control of a fragmented workspace

The useful hypothesis is not the imminent death of email or Office, but the possibility of reducing a channel stack that fragments attention, duplicates documents and makes supplier exit difficult.

• Observed facts concern shifts in use, pricing changes and governance requirements.
• Convergence on one surface remains an architecture scenario, rather than a market law or a 2030 deadline.
• An organisation can act now by clarifying each channel’s role and testing reversibility.

Email remains an exchange and has also become an archive

Email combines two durable functions — asynchronous coordination and organisational memory — which newer tools are more likely to complement than replace completely.

• The British Library holds about 40,000 emails in Wendy Cope’s hybrid archive [1].
• The Harry Ransom Center acquired Ian McEwan’s electronic correspondence dating from 1997 [2].
• The University of Manchester studied about 215,000 emails and 65,000 attachments from Carcanet Press with archiving, visualisation and network-analysis tools [3].
• Salman Rushdie’s digital archive is held at Emory University, which emulated his old Macintosh to recreate his writing environment [4].

This archival value does not mean that all information belongs in an inbox, because an exchange, a reference version and an approved decision have different lifetimes and control requirements.

• Email suits interoperable, asynchronous exchange between organisations.
• A versioned document space is better for content that must remain current.
• A business register is better for a decision, quotation or invoice that must be found and audited.

Atos “Zero Email”: reduction was possible, elimination was not demonstrated

The initiative announced by Atos in 2011 shows that a company can move some internal exchanges to an enterprise social network, without establishing that email can disappear from external relationships or digital identity [5][6].

• The public objective was to become a “zero email” company within three years.
• The blueKiwi environment organised internal exchanges into communities.
• Case publications report a sharp fall in internal volume while describing change-management difficulties, rather than general eradication [6].
• The evidence remains specific to one organisation and programme.

Need	Email (SMTP/IMAP)	Team messaging	Collaborative canvas
External exchange	Broad interoperability	Often limited to a tenant	Invitation-based access
Timing	Asynchronous	Near-synchronous	Synchronous or asynchronous
Source of truth	Weak without filing	Channel history	Visual board version
Reversibility	Established protocols and formats	Supplier-dependent	Export and API-dependent

The operational lesson is to assign each channel a purpose and measure shifts in use, without turning a change-management target into a technology prophecy.

• Retain email for external exchange and notifications requiring a universal address.
• Move tasks, versions and approvals to their systems of record.
• Remove duplication once the new channel has taken over the function reliably.

Reduce the attention burden before changing tools

The effect an organisation can control most directly comes from interruption frequency, unnecessary copies and unclear choices between asynchronous and synchronous work.

• A Loughborough study measured about 64 seconds to resume work after an email interruption in its protocol [7]; that figure alone cannot support a universal estimate of hours lost.
• Batch processing can reduce voluntary context switches when a separate route exists for genuine emergencies.
• In France, Article L2242-17 of the Labour Code places arrangements for the right to disconnect within negotiations on quality of working life and conditions [8].

A communication rule is useful only when it fits the team’s context and its effect is tracked for several weeks.

• Measure the share of copied messages and remove obsolete distribution lists.
• Set a number of exchanges after which the team chooses a short call or shared document.
• Track response times, follow-ups and reported interruptions before extending the rule.

Office suites: weigh cost, dependency and jurisdiction

Integrated suites remain convenient, but their pricing and role in identity, documents and collaboration justify a comparison based on total cost and exit risk.

• Microsoft applied new list prices to several commercial Microsoft 365 products in July 2026, with changes varying by product and country [9].
• In September 2025, the European Commission made Microsoft commitments on suites without Teams, interoperability and data extraction legally binding [10].
• These facts show dependency and competition concerns; they do not prove that a modular suite will always be cheaper or better.

Digital sovereignty should be analysed through effective control, jurisdiction and continuity, rather than the supplier’s nationality alone.

• Map who administers identities, encrypts data, holds keys and may answer a legal demand.
• Classify data and uses before imposing the same protection level everywhere.
• Examine subcontractors, operating locations and the ability to continue during migration.

France 2030 supported the development of collaborative cloud suites, while SecNumCloud provides a demanding reference whose precise scope matters [11][12].

• CollabNext appears among the supported projects described by Bpifrance [11].
• ANSSI qualifies a specific cloud service, rather than automatically qualifying the supplier, all its products or software merely hosted on that service [12].
• A product hosted on a qualified service therefore does not inherit the qualification without its own assessment.

Telephone, messaging and email: uses are shifting

Voice, SMS and messaging do not share one path to disappearance; their uses shift according to urgency, context, audience and the need for a record.

• A call remains effective for resolving complex ambiguity quickly.
• Chat suits brief coordination within an established group.
• Email remains appropriate for deferred, interoperable external exchange.
• A business object is preferable when a transaction must be structured, signed, paid or audited.

Multiple channels become costly when the same conversation is copied everywhere and no surface is authoritative.

• Give each channel a primary purpose.
• Define where the reference version lives after a call, chat and email.
• Close old flows once the new process is stable.

An internal analysis for selecting the first workflows to move

A reported internal analysis of 874 business conversations from a consulting micro-business suggests substitution candidates, but its method supports neither a general SME rate nor a market forecast [13].

• Period: April to June 2026.
• Preparation: 54 technical-noise threads and 472 automated-supervision threads removed from a raw flow of 1,400.
• Classification: seven rule-based categories, with 631 usable summaries.
• Limits: one context, estimated substitution rates, no controlled experiment and no independent audit of classifier precision.

The illustrative calculation assigns about 68% of volume to a potentially more structured channel, making it a pilot hypothesis rather than a measured gain.

Category	Threads	Share	Estimated substitution	Pilot candidate
Client and project coordination	285	32.6%	~60%	Client space + booking
Training and Qualiopi	147	16.8%	~70%	Shared repository + signature
Invoicing and accounting	141	16.1%	~75%	Register + portal
Notifications and logistics	107	12.2%	~85%	Filing + unsubscribe
Inbound prospects	69	7.9%	~45%	CRM form
Suppliers and catalogue	66	7.6%	~70%	Synchronised catalogue
Quotations, contracts and signatures	59	6.8%	~80%	Business object + signature

Two related observations mainly show why signal quality should be checked before an inbox is automated.

• After automated flows were removed, 14% of threads carried an urgency signal, compared with 26% in the flow that included them.
• At least 21% contained a document marker, although signature logos could create false positives.
• Quotations and contracts had the highest document density in this corpus, making them a stronger test candidate than a general migration.

Turning these estimates into a decision requires a pilot that measures the complete task before and after the change.

• Count handling time, follow-ups and errors on a stable sample.
• Check that the new tool actually reduces duplicate entry and copies.
• Document exceptions that should remain in email.

Living documents and canvases: choose the right collaboration spaces

Collaborative canvases can bring ideas, decisions and AI contributions together, but they need distinct spaces for private exploration, shared production and publication.

• Hinze-Hoare’s work distinguishes collaboration functions including communication, planning, production, reflection and confidentiality [14].
• An IBM study presented at CHIWORK 2024 explores LLM-supported ideation in a virtual canvas and reports needs for transparency and private spaces [15].
• These studies describe configurations and user needs; they do not establish that a canvas should replace every document.

Layer	Function	Control required
Scoping	Objectives and hypotheses	Sources, mandate, private space
Interaction	Co-editing and feedback	Roles, notifications, history
AI	Generation and classification	Provenance, validation, filtering
Governance	Publication and retention	Access, retention, export

AI at work: treat impacts as scenarios to monitor

Generative AI can accelerate drafting and synthesis while weakening critical review when users also delegate problem framing and verification.

• Retain a step where a person defines the objective, criteria and permitted sources.
• Separate generation from verification when the outcome matters materially.
• Train teams to detect plausible but unsupported answers.
• Measure quality and rework alongside time saved.

Employment research describes exposure and changes already visible, but its categories cannot mechanically predict the fate of a role or organisation by 2030.

• A structured, repetitive task is easier to automate than a whole responsibility.
• One role can combine substitution of some tasks, augmentation of expertise and rebalancing of duties.
• Training needs depend on actual work content, organisation and the autonomy granted to the system.

Applying the Junyr Method™ to the workspace

In the Junyr Method™, moving from isolated tools to a coordinated set corresponds to the Orchestre level when data, supervision and exit rules are explicit.

• Spectateur: uses are observed without a common framework.
• Artisan: tools are chosen locally for occasional needs.
• Orchestre: workflows are coordinated, responsibilities are written and measures are shared.
• Architecte: architecture, security and governance are designed at system level.
• Pionnier: advanced experimentation operates with risk controls and organised learning.

A governed surface depends on three guarantees that can be checked at purchase and during operation.

• Open standards for communication and exports in documented formats.
• Modularity so one component can be replaced without immobilising the workflow.
• Reversibility tested through export, restoration and a migration scenario.

Three objections to test in the real context

Objections to convergence are useful because they force the target scenario and the current stack to be compared against the same criteria.

• Email persists: retain its interoperability role and remove only tasks with a better system of record.
• Alternatives may be less integrated: measure functional gaps and change costs in a pilot.
• Unification may lock users in: require replaceable components, documented formats and a contractual exit process.

A leader can obtain a first picture this week without starting a migration.

• How many tools does one colleague consult to handle an ordinary case?
• Where is the reference version after a call, chat and email?
• Can identities, documents and histories be exported in a reusable format?

Review your position in 30 minutes

The free Junyr audit is a no-commitment, 30-minute video call that places the organisation on the maturity scale and identifies a sensible next step.

• Your current position on the scale.
• The principal blocker to address.
• The first sensible project to test.
• A one-page follow-up after the call.

Book the Junyr audit

Sources and data status

[1] British Library, Wendy Cope Archive. https://www.bl.uk/collection-guides/wendy-cope-archive

[2] Harry Ransom Center, Acclaimed Writer Ian McEwan’s Archive Acquired (2014). https://www.hrc.utexas.edu/press/releases/2014/ian-mcewan-archive.html

[3] University of Manchester, Palladium: providing access to large literary archives in a digital medium. https://www.manchester.ac.uk/about/news/palladium-providing-access-to-large-literary-archives-in-a-digital-medium/

[4] Emory University, Rushdie: Digital archive at Emory “allowed me to write” memoir (2012). https://news.emory.edu/stories/2012/03/er_rushdie_digital_archives_memoris/campus.html

[5] Atos, “Zero Email” announcement, 7 February 2011. https://atos.net/en/2011/press-release_2011_02_07/pr-2011_02_07_01

[6] N. Silic & M. Back, Atos, Towards Zero Email Company, ECIS 2015. https://aisel.aisnet.org/ecis2015_cr/168/

[7] T. Jackson, R. Dawson, D. Wilson, The Cost of Email Interruption, 2001. https://interruptions.net/literature/Jackson-JOSIT-01.pdf

[8] French Labour Code, Article L2242-17. https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000039070718

[9] Microsoft, Microsoft 365 Pricing and Packaging Updates, 16 February 2026. https://www.microsoft.com/en-us/licensing/news/2026-m365-packaging-pricing-updates

[10] European Commission, Commission accepts commitments offered by Microsoft to address competition concerns related to Teams, 12 September 2025. https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2048

[11] Bpifrance, France 2030 project collection, CollabNext entry. https://www.bpifrance.fr/sites/default/files/inline-files/Recueil%20AAP%20France%202030%20Bpifrance.pdf

[12] ANSSI, FAQ avant de se lancer dans la qualification SecNumCloud. https://cyber.gouv.fr/enjeux-technologiques/cloud/faq-qualification-secnumcloud/

[13] Croissance et Transitions / Junyr, internal analysis of 874 business conversations, April-June 2026; data not verifiable on the web, non-generalisable proportions and non-experimental estimates.

[14] V. Hinze-Hoare, CSCR: Computer Supported Collaborative Research, 2006. https://arxiv.org/abs/cs/0611042

[15] J. He et al., AI and the Future of Collaborative Work: Group Ideation with an LLM in a Virtual Canvas, CHIWORK 2024. https://dl.acm.org/doi/10.1145/3663384.3663398