The media workflow tax: The unexpected cost of tool switching

TL;DR

• Tool sprawl builds up one disconnected tool at a time, and the gaps between them are where approvals, versions, and context get lost.
• The average employee now touches 40 apps just to do their job, and media teams building their own patchwork of tools follow the same pattern at a smaller scale.
• When tools don't talk to each other, people end up carrying the context between them instead of the systems doing it automatically.
• Bringing storage, review, and the final handoff into one connected layer is what actually closes the gap.

Every time an editor leaves the timeline to check a Slack thread, hunt through a shared drive, or confirm which version is actually approved, they pay a small, invisible tax. It doesn't land on an invoice. It shows up later, in slower deliveries, lost approvals, and editors who end up holding a fragmented stack together by memory.

Tool sprawl: What it is and how it happens

A colorist working through a single grade stays inside one continuous piece of work. The real cost sits in the gap between the tool where the edit lives, the tool where feedback lives, and the tool where the final file needs to land.

That gap has a name — tool sprawl — and media workflows tend to accumulate it fast because a single deliverable can touch a nonlinear editor, a review tool, a digital asset management (DAM) tool holding the brand asset library, and whatever your team uses to stay in sync.

This holds up at scale, too. According to Torii's SaaS Benchmark Annual Report 2026, the average employee now interacts with 40 apps just to do their job. Across the average organization, that adds up to more than 831 applications, 61 percent of which operate as shadow IT outside of formal oversight. 

Creative teams building their own patchwork of storage, review, and scheduling tools are part of the same pattern, just at a smaller scale.

The impact of tool switching in a real workflow

Nobody notices the cost of tool sprawl line by line. It typically happens like this:

None of this happens on purpose. An editor picks the review tool that works for them, the social team picks a scheduler, and nobody is ever sitting down to look at the whole chain those choices add up to. That is exactly where the friction collects.

What gets lost when tools don't talk to each other

Liz Dellheim, product marketing lead at Backlight, has watched this pattern play out across accounts of every size. "People become the integration layer instead of there being a tool that is acting as your connective tissue,” she explains.

That absence shows up in small, compounding ways. Information gets stuck in the tool where it was created, so someone ends up rebuilding context that already existed somewhere else because they couldn't find it, and a task sits waiting simply because no one is sure whose move it is next. None of that shows up on a budget line. All of it shows up in a delivery timeline.

Iconik's 2026 Media Stats report frames the next era of media asset management (MAM) around the ability to find, reuse, and retire content without friction.

Bringing the media workflow back together

Editors need one place to work from, where the cost of tool switching disappears.

Iconik is a MAM platform that brings storage, review, and the handoff into a single hybrid cloud layer. An editor pulling from on-prem storage and one pulling from the cloud work inside the same system, with feedback attached directly to the asset and version history that never gets separated from the file.

The ultimate payoff? Less time spent locating the work means more of it spent on the work itself.

Frequently asked questions about tool sprawl

What is the difference between tool sprawl and a normal tech stack?

Every team uses multiple tools. Sprawl starts once those tools stop connecting to each other, forcing people to manually carry context between them.

How do I know if my media workflow has this problem?

Watch for filenames stacked with "final," "v2," and "v3" that nobody ever cleans up, metadata that is missing or inconsistent from one asset to the next, and one person who has become the unofficial search engine everyone messages first.

Do cloud-based collaboration tools solve this on their own?

A cloud tool disconnected from your review and storage layer just becomes another isolated step, and a DAM alone only covers your brand asset library, not what is still in production. Consolidating the workflow layer is what closes the gap.

Does moving to a centralized platform mean migrating everything at once?

No. Iconik sits on top of the storage you already have, and it connects to the tools your team already relies on. Consolidating the workflow layer doesn't mean giving any of them up, just connecting them.

Put your own media workflow to the test

Your team already knows where the friction sits. Our latest guide, The accidental architecture of modern media teams, walks through how to audit your own workflow and start closing the gaps. Download it for free to get started.

‍