Logo

Command Palette

Search for a command to run...

Case Study

Asset Scout

Unified asset search dashboard that brings reliable, permission-aware discovery to post-production teams.

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Python
  • Flask
  • Elasticsearch
  • Bun
  • GitHub
  • Jest
  • Figma
Screenshot of the Asset Scout file sync dashboard

Timeline

3 weeks

Focus

Product Strategy • UX & UI Design • Front-end Development • System Architecture

Status

Internal launch

Purpose

Asset Scout gives editors and producers a single, trustworthy place to search every asset on the company server. By consolidating fragmented folders, shadow knowledge, and inconsistent naming into one synced catalogue, the dashboard removes the time waste and uncertainty that slowed production teams.

  • Eliminated folder spelunking and repeated transfers.
  • Made institutional memory discoverable through search.
  • Embedded permission-aware access into existing workflows.

Problem

Prior to Asset Scout, nothing reliably surfaced what lived on the shared drives. Assets sprawled across nested folders with ad-hoc naming, and high-value files often depended on whoever remembered the path last. Production timelines slipped while team members DM’d each other, re-transferred footage, or altogether missed critical assets.

  • Inconsistent folder structures and zero naming discipline.
  • Manual browsing or asking teammates became the default workflow.
  • Duplicate transfers and lost assets disrupted delivery dates.
  • Lacked a single source of truth for “what exists and where.”

Goals

  • Deliver a unified, fast query interface across all server assets.
  • Support faceted filtering for type, project, client, tags, date, and location.
  • Present decision-ready results with inline metadata and previews.
  • Respect existing folder permissions without requiring reconfiguration.
  • Keep the index continually fresh with transparent sync status.

Users & Context

Asset Scout serves time-pressed creative teams who work across a mix of desktop environments and network conditions.

  • Editors & producers: need the fastest path from brief to asset delivery.
  • Assistants: handle requests, prep cuts, and support live sessions.
  • Archiving & operations: curate metadata and ensure folder hygiene.

The dashboard runs on the internal network with adaptive layouts so power users can work from the suite or on-set tablets without losing context.

Design Principles

A set of shared principles guided decision-making across discovery, design, and implementation.

  • Make search the heart of the experience with an obvious, global entry point.
  • Use chip-based filters that are easy to scan, add, and remove.
  • Show value immediately with metadata, counts, and previews inline.
  • Build forgiving interactions that handle typos, synonyms, and partial matches.
  • Favour clarity and accessibility over clever patterns.

UX Approach

The experience was co-designed with editors and producers. Shadowing sessions surfaced real-world searches, while rapid prototyping tested the balance between density and scanability.

  • Shadowed daily workflows to document recurring search intents.
  • Built mid-fidelity prototypes validated with focused user sessions.
  • Iterated on layout density to serve both browsing and power usage.
  • Instrumented feedback states that reinforce trust during sync or lag.

Information Architecture

The IA balances a persistent search paradigm with fast drill-downs into asset detail.

  • Global search: anchored across every view.
  • Results list: surfaces filename, project, client, tags, path, and timestamps.
  • Filters panel: exposes facets that collapse to the top on mobile.
  • Asset detail: deep metadata, related items, and quick path actions.
  • Saved searches: optional pins for frequent requests.

Key UI Decisions

Visual and interaction decisions focused on speed, legibility, and confidence.

  • Type-ahead assisted search with relevant projects, clients, and tags.
  • Filter chips live directly beneath the search bar for quick toggles.
  • Keyboard-first navigation gives power users rapid control.
  • Comfortable and compact density modes accommodate browsing styles.
  • Clear empty, loading, and error states guide users back to productive paths.

Search Interaction Model

Search needed to support both quick lookups and precise filtering.

  • Type-ahead suggestions for projects, clients, and tags accelerate discovery.
  • Query helpers like type:video project:“Client A” speed up complex filters.
  • Fuzzy matching handles plurals, synonyms, and common typos.
  • Highlights the matching terms and offers multiple sort orders.
  • Pagination vs. infinite scroll chosen per collection size and performance tests.

Metadata & Previews

Results have to deliver confidence before anyone leaves the keyboard.

  • Always surface filename, type, project, client, date, and canonical path.
  • Inline tags stay visible with tooltip overflow for longer metadata.
  • Thumbnails and previews enable visual confirmation for high-value footage.
  • Copy path and open-in-finder actions remove context switching.

Performance & Reliability

  • Debounced input prevents over-fetching and keeps interactions snappy.
  • Progressive results and caching reduce perceived latency.
  • Index health and sync telemetry stay visible from the results view.
  • Offline-resilient index keeps searchable data available during share outages.

Permissions & Trust

  • Search results mirror folder-level permissions exactly.
  • Sensitive assets display masked metadata or explanatory messaging.
  • Audit-friendly logging captures major search activity for review.

These safeguards turned Asset Scout into a system teams trust rather than another tool to second-guess.

Implementation Overview

  • Crawler: scans directories and normalizes metadata.
  • Indexer: structures data for fast, faceted querying.
  • API: exposes search endpoints with permission filters.
  • Web app: ships the dashboard UI with responsive layouts.
  • Sync jobs: schedule refreshes, health checks, and error alerts.

Outcomes

  • Markedly faster asset discovery for editorial teams.
  • Fewer redundant transfers and “can you find…” interruptions.
  • Shared visibility into project libraries across clients.
  • Smoother onboarding with a reliable system of record.

What's Next

  • Lightweight in-app tagging and curation tools for producers.
  • Expanded synonym dictionaries and domain-specific vocabulary.
  • Proxy previews to handle large video assets gracefully.
  • Collaborative saved searches, alerts, and CSV exports.

Lessons Learned

  • Metadata quality is the backbone of any search experience.
  • Simple, forgiving filters outperform complex query builders.
  • Fast, accurate feedback loops build long-term user trust.
  • Visible system health prevents confusion about content freshness.
  • Accessibility work benefits every team member, not just edge cases.

For the next iteration, I plan to expand the case study with flow diagrams and UI motion studies to communicate system interactions at a glance.