Case Study 07 SaaS / AI / Digital Asset Management

ioMoVo — usability, unlocked.

A mixed-methods UX research study and usability audit of ioMoVo, an AI-powered Digital Asset Management platform. We paired a heuristic evaluation with user interviews and think-aloud testing to map the friction between powerful engineering and confused users — then designed a way out.

Role
UX Research
Usability Audit
Team
Adnaan Lalani
Saurabh Jogdeo
Shrey Patel
Context
Toronto Metropolitan
University
Year
2025
01 / Overview

Robust engineering, fragile experience.

Executive summary

ioMoVo is an AI-powered Digital Asset Management (DAM) platform built to help organizations consolidate, manage, and retrieve massive volumes of digital files across multiple connected cloud storage services. Its back end is genuinely powerful — but it was designed and engineered primarily by developers rather than UX designers, and it had grown into a case of severe feature creep: an abundance of complex features that compromised usability and intuitive navigation.

Acting as UX consultants, our team ran a rigorous mixed-methods study. We paired a baseline heuristic evaluation grounded in Jakob Nielsen's usability principles with qualitative user interviews and quantitative usability testing to map the critical friction points along the primary file-retrieval journey. This study unpacks our end-to-end process, empirical findings, and strategic recommendations.

02 / The Challenge

Capability versus usability.

The mismatch

The job of a DAM platform is to centralize files scattered across disparate machines and cloud drives, so teams can locate a specific asset quickly. ioMoVo's unique selling point leans on AI-powered natural language processing to search through petabytes of data.

Despite those back-end capabilities, users hit severe friction. The platform suffered a critical mismatch between its complex functionality and its users' mental models, which made basic operations feel unintuitive. To make sense of it, we framed the work around a single question:

"

How might we declutter, simplify, and make ioMoVo intuitive — shortening the learning curve between connecting drives, uploading data, and retrieving it quickly and easily?

Two journeys
01
The input data flow

Connecting external drives and uploading assets to create a single source of truth.

02
The retrieval flow

Leveraging traditional keyword algorithms, AI metadata tags, or hybrid search to locate files fast.

03 / Methodology

An evidence-based roadmap.

How we worked

To build a redesign roadmap on evidence rather than opinion, we ran a structured, multi-phase research plan — moving from an objective usability baseline into live testing with real creative professionals, then synthesis.

Phase 01
Discovery
Scoping the platform, its value proposition, and the two core journeys worth testing.
Phase 02
UX Audit
Three independent heuristic evaluations against Nielsen's 10 usability heuristics.
Phase 03
User Testing
In-depth interviews plus think-aloud usability sessions on the live platform.
Phase 04
Synthesis
Compiling findings into validated gaps, new discoveries, and design solutions.
The plan, in detail
01
Heuristic evaluation

Three UX researchers ran individual audits, then compiled overlapping issues to keep the baseline objective. The evaluation used Jakob Nielsen's 10 usability heuristics.

02
Screener & recruitment

A strict screener filtered for creative professionals — video editors, design managers — who manage large volumes of assets daily. Six qualified participants took part, enough to surface roughly 85% of core usability issues.

03
Mixed-methods testing

Each ~60-minute session combined open-ended, non-leading interviews to probe mental models with think-aloud usability testing across five critical tasks on the live platform.

What we measured

To keep the testing objective, we tracked five key performance indicators across every session:

Key performance indicatorDefinition
Task Success RatePercentage of participants who successfully completed each task.
Task Completion TimeTotal time taken to navigate and execute a given workflow.
System Steps TakenThe total number of clicks and page transitions required.
Error & Loophole RatesNon-standard pathways or mistakes made during task execution.
Emotional ResponseObservable frustration, confusion, or satisfaction.
04 / Findings

Where the platform broke down.

Validated gaps

Testing validated several of our initial hypotheses. The friction clustered around four areas: the home screen, the search architecture, file sharing, and a manual sync step nobody expected.

Home screen
Visual cognitive overload.
A rotating, high-contrast galaxy video background distracted users and significantly reduced text legibility. Redundant buttons and irrelevant modules — company blogs, announcements — buried the primary call to action.
4 of 6 users affected
Search architecture
The core feature was hidden.
ioMoVo's value is natural-language "Relevance" search — but the platform defaulted to keyword search, and the toggle to switch was separated from the search bar entirely. Natural-language queries returned poor, inconsistent results.
6 of 6 missed the setting
File sharing
Confusing, and unsafe.
All participants were unsure what "CDN" meant, and five of six couldn't distinguish between the two sharing links. Clicking "Delete CDN" left the shared file accessible, and the system accepted invalid emails without warning.
5 of 6 confused by links
Accessibility
Synced vs. unsynced was invisible.
The only cue distinguishing a synced file from an unsynced one was a subtle color change — a small green "AI" tag versus a gray one — which failed basic accessibility standards.
Fails contrast standards
The manual sync hurdle

The most damaging issue broke users' mental models entirely. Most assumed uploaded files would automatically sync and index. Instead, ioMoVo required users to manually select and sync files before they could be searched — so a fresh upload returned zero results.

User uploads file Assumes auto-sync Runs search query Zero results found
Cause: the platform requires a manual synchronization step after upload before a file becomes searchable.
05 / Discovery

And two we didn't expect.

Newly discovered

Testing on the live platform surfaced two usability gaps our heuristic audit hadn't caught — both born of inconsistency between screens.

Invisible upload CTAs
Users left a screen just to upload.
While the home page had a prominent upload area, the ioCloud storage interface lacked a clear, persistent Upload button. Users navigated all the way back to Home to upload, missing a tiny icon clustered among eight other tools.
5 of 6 backtracked to Home
Defective filters
A single mis-click cost the whole modal.
An accidentally selected file-format filter couldn't be deselected — users had to reset the entire modal. Worse, "Clear Filter" was styled as a prominent blue button, so users tapped it expecting "Apply" and erased their configuration.
No individual deselect
06 / Solutions

Fixing it with familiar patterns.

Design strategy

Rather than reinvent the wheel, we anchored the redesign in standard patterns popularized by industry leaders like Google Drive and Dropbox — patterns users already understand. We reorganized the dashboard architecture around a high-fidelity homepage prototype built for immediate cognitive clarity.

01
Persistent primary actions

A bold, clearly defined "Upload" button in the left sidebar, mirroring the highly recognizable Google Drive layout — available everywhere, not just on Home.

02
Quick action cards

The main dashboard was simplified to four essential tasks: connect a drive, create a folder, record video, and capture screens.

03
Search integration

The global search bar now carries explicit placeholder text — "Search through KEYWORD or RELEVANCE" — with a clear toggle switch built directly into the input to prevent errors.

04
Better system feedback

We replaced the subtle notification-bell ring with a floating bottom toast that confirms a successful upload and offers an immediate "Locate File" shortcut.

05
A single, clear share modal

The confusing double-link model became one modal with explicit permissions — Viewer, Commenter, or Editor — and a single copyable link, aligning with modern sharing flows.

Fig. 01 — Proposed dashboard / persistent upload, quick actions & integrated search toggle
07 / Conclusion

Capability was never the problem.

What we learned

Our research showed that ioMoVo's primary challenge was not a lack of technological capability, but a severe lack of design usability. Feature-rich products will still fail to retain users when those features are hidden behind complex, confusing workflows.

"

A powerful back end means nothing if users can't find the front door.

Recommended next steps
01
Interactive usability testing

Run task-based tests on the new high-fidelity prototypes to confirm the proposed layouts actually reduce task times.

02
Card sorting studies

Conduct open card sorting with target users to rebuild the information architecture and rename ambiguous modules like ioFlow and ioHub.

03
Automated synchronization

Move the platform from manual syncing to a default background auto-sync model, aligning with modern cloud storage standards.

Back to all work

More case studies.

Browse all projects