← Back to all work Project · Adobe Acrobat Web

The dead end after every Acrobat task. And the 27.5% hiding there.

Users were compressing, converting, and organising files in Acrobat Web — then immediately dropping off. The cause was a default no one had questioned. Identifying and fixing it produced a 27.5% lift in document opens.

Product Adobe Acrobat Web
Role Product Designer
With Atal Pandey
Status 🔒 NDA · Selective details
The investigation

The data showed a cliff. The question was why.

Looking at user behaviour around task completion flows — compress, convert, organise — a consistent pattern emerged: users who successfully completed a processing task were not following through to their output. Task completion was not translating into continued engagement with the processed file.

This was counterintuitive. These users had done the work. The file existed. The product had done its job. Something was happening at the handoff.

The question worth asking

Was this a design problem? A discoverability problem? Or was it something further upstream — an assumption the product was making that users weren't aware of?

The diagnosis

A task completed. A dead end left behind.

The mechanism was simple once you saw it. When a user compresses a PDF, the progress bar fills, the modal closes — and they're left looking at the original document, not the compressed file they just created. The processed output exists, but it's not in front of them. They'd have to navigate away, find the file, and open it themselves.

The product had always assumed users would take that extra step. They weren't. Not because they didn't want the file — but because at the moment a task feels done, any additional step is a reason to stop. The job felt complete. There was no visible next thing.

What was happening
Task completes
→
Original doc stays open
→
User leaves
Why it was happening
Task completes
→
Product assumes user will seek output
→
User doesn't
The insight

This wasn't a bad UX feature. It was an unchallenged default — one that had always placed the burden of continuation on the user, at exactly the moment they felt least motivated to carry it. Identifying the assumption was the work.

The hypothesis

Remove the decision. Remove the drop-off.

Once the diagnosis was clear, the hypothesis followed directly. If the problem was users being required to take an extra step at the worst possible moment, the solution wasn't to make that step easier. It was to eliminate the step entirely.

Hypothesis

If the processed file opens automatically at the moment of task completion, users arrive at their output with zero extra effort — and the engagement that follows will be measurable.

01

The path of least resistance becomes the useful path

Users default to the easiest available action. If the processed file is already open, it becomes the next thing — not a conscious choice to pursue.

02

Context drives continued use

A user already inside their compressed or converted document is already in the right context to use additional Acrobat tools. The dead end was breaking that chain before it started.

03

Visibility shapes habit

Users who never see their processed file inside Acrobat never associate the outcome with Acrobat. The habit of returning for the next task requires the first task to feel complete — inside the product.

The intervention

One default changed. Three tools. Live for all users.

On task completion — compress, convert, or organise — the processed file now opens automatically in a new Acrobat tab. A notification confirms the action and gives users direct access to the setting if they want to change it.

  1. 1
    User runs a task Compress, convert, or organise — the user triggers processing.
  2. 2
    Processing completes Processed file opens automatically in a new Acrobat tab. Zero extra steps.
  3. 3
    User is informed + in control A notification explains what happened and links directly to the preference to change it.
Live on Acrobat Web
Auto-open notification toast — live on Acrobat Web

Notification on task completion · live on Acrobat Web

Settings
Auto open
Automatically open exported and compressed files in new tab
Cancel
Save

Settings › Auto open — user preference, on by default

Compress PDF
Convert
Organize pages
Designing for the no

The notification isn't just confirmation — it's a transparent explanation of what changed, and a one-tap path back to the old behaviour for users who want it. The default carries the lift. The setting earns the trust.

The result

The hypothesis held. The numbers confirmed it.

The change produced a measurable result — not because the design was clever, but because the diagnosis had been right. The friction was real. Removing it worked.

+27.5%
Users opening their processed documents

Users who would previously have left the task behind now arrived directly at their processed file — inside Acrobat, in the right context to continue.

↑
Same-session multi-tool usage

A measurable lift in users going on to use additional Acrobat tools in the same session — the compounding effect of removing the exit point.

Why the diagnosis mattered more than the fix

The fix was one line of behaviour logic. The work was in correctly identifying where the fracture was, understanding why it was costing engagement, and being precise enough about the mechanism that the hypothesis was almost predetermined to succeed. Fewer elements. More momentum. The 27.5% was a confirmation, not a surprise.

Reflection

The most valuable skill isn't fixing problems. It's finding the right ones.

Any designer can propose a solution once a problem is named. The harder part is looking at a metric and asking: what assumption is wrong here? This project started with a pattern in the data and ended with a confirmed thesis. The intervention was small. The thinking behind it wasn't.

← See more work Get in touch