The Tool Carousel: A Survival Guide to Forgetting Where You Saved That Document

Somewhere in your organization, right now, someone is asking in a chat: “Is this the right place to post this?” They will not receive an answer. Or they will receive three answers, each pointing to a different platform. This is normal. This is fine. This is the modern Digital Workplace. Let us speak of the tool carousel – that magnificent enterprise ritual where organizations adopt, abandon, and re-adopt collaboration software with the romantic intensity of a European royal dynasty managing succession. Slack begat Teams begat Slack-for-some-teams-but-Teams-for-others. Confluence was born, briefly flourished, and now exists in that peculiar purgatory of “we still have it but please use SharePoint.” Somewhere, a Notion workspace holds the dreams of a departed project manager. Nobody has the admin rights to delete it. Nobody dares to ask.

The Archeology of Abandoned Platforms

Every organization of sufficient age develops sedimentary layers of collaboration tools. Like geological strata, they tell a story – not of prehistoric climates, but of prehistoric management consultants. The bottommost layer: a Lotus Notes installation that technically still runs, maintained by someone in IT whose job title contains the word “legacy” and whose retirement party is perpetually six months away. Above that: the SharePoint 2013 site that was “temporary” during a migration that never finished. It contains, according to legend, the only working version of a contract template that Legal insists upon. Nobody knows the URL. People email the file to each other like samizdat literature. Then the modern era: the bold pivot to Slack in 2019, followed by the bolder pivot to Teams in 2021 because “Microsoft licensing,” followed by the quiet return of Slack for the development team because “integrations,” followed by the official policy that “we are a Teams organization” which everyone interprets as “use whatever, just don’t ask IT.”

The Pilot That Never Lands

No tool arrives without a pilot. The pilot is a beautiful concept: a small group tests the tool, identifies issues, and provides feedback before the organization commits. In theory. In practice, the pilot group consists of enthusiasts who would adopt anything, skeptics who were voluntold to participate, and one person from IT who is actually evaluating security while everyone else discusses emoji reactions. The pilot concludes. The feedback is “mixed.” The tool is rolled out anyway because the contract was already signed in January. The pilot group disbands, their insights preserved in a SharePoint site that – well, you see where this is going. Eighteen months later, someone suggests a new tool. It is, functionally, identical to the one abandoned two tools ago. But it has a different logo and a sales rep who promises “seamless integration.” The cycle begins anew. The carousel turns. The music plays on, slightly distorted, like hold music for a support line that will never pick up.

The Search for the Single Source of Truth

“We need a single source of truth,” says someone in every meeting about information architecture. Everyone nods. The single source of truth is a noble quest, the Holy Grail of knowledge management. And like the Holy Grail, it is sought by many, found by none, and occasionally faked for political purposes. The problem is not the concept. The problem is that every tool wants to be the single source of truth. SharePoint is the single source of truth for documents. Except the documents that live in Teams. Which sync to SharePoint. Except when they don’t. Confluence is the single source of truth for documentation. Except the documentation that’s in the wiki. Which wiki? Exactly. Meanwhile, the actual single source of truth is a senior employee named Margret who has been here since 2007 and knows where everything is because she remembers where everything was before the last four migrations. When Margret retires, the organization will discover that her brain was the integration layer they never bought. There will be a brief moment of institutional panic. Then someone will propose a new tool.

The License Graveyard

Somewhere in Finance, if you know where to look, there exists a spreadsheet. This spreadsheet contains a list of software licenses the organization currently pays for. It is out of date. It is always out of date. It contains line items for tools that were “sunset” three years ago but never actually canceled because the cancellation process requires approval from a manager who has since left, and their approval authority was never formally reassigned. The spreadsheet reveals that the organization spends more on collaboration tools per employee than some countries spend on healthcare per citizen. This is not a joke. This is enterprise software economics. Each tool promised efficiency gains that would “pay for themselves.” Collectively, they have created an efficiency loss that nobody measures because the people who would measure it are too busy figuring out which tool to use for measurement. There is a special poetry in paying simultaneously for Slack, Teams, Zoom, Webex, and Google Meet. It speaks to a profound organizational truth: we have commitment issues, and we are willing to pay monthly for all of them.

The Desktop: Last Refuge of the Desperate

In the end, all tools fail, and knowledge flows to its natural resting place: the Windows desktop. Arranged with the care of a teenager’s bedroom floor, the desktop becomes the true collaboration layer. Files named “final_v2_FINAL_use-this-one.docx” sit alongside “Copy of Copy of Q3 Report.” There is a folder called “Old” that is eight gigabytes. There is a shortcut to a network drive that no longer exists. There is a screenshot from 2019 that was important once. The desktop is honest. It does not promise seamless integration. It does not require a subscription. It will not be replaced by a newer desktop in eighteen months, pending pilot results. It simply exists, patient and eternal, waiting to receive whatever document has nowhere else to go. And when the laptop is eventually returned – upon retirement, resignation, or the next relaunch of the device fleet – IT will discover these files and face an ancient question: migrate or delete? They will choose delete. The knowledge will vanish. In another department, someone will ask: “Does anyone have that template from the old project?” The silence will be deafening.

Acceptance: The Final Stage

The mature Digital Workplace professional eventually reaches acceptance. The tools will change. The logins will multiply. The single source of truth will remain plural. This is not a problem to be solved. It is a condition to be managed, like weather, or middle management. The wise employee develops coping mechanisms. They bookmark everything. They use browser profiles to manage their seventeen active sessions. They maintain a personal note (in a tool of their choosing, synchronized to nothing) that lists which thing is where. They answer “Is this the right place to post this?” with gentle honesty: “It’s one of the right places. There are several.” And when a new tool is announced – with enthusiasm, with a launch event, with a training video that nobody will watch – they will smile, sign up for the pilot, and quietly continue saving important files to their desktop. Because the carousel turns. The music plays. And somewhere, Margret is updating her retirement date again.