Skip to content
KR.

CreativeOPS · Internovus · 2026

A creative library connected to the team's project board

I designed and built an internal application for finding creative assets and managing requests and approvals.

It connects a searchable catalogue with the project board the team already uses.

Users
Marketing team, with approval workflows
Role
Interface design, application development and workflow automation
Scope
Catalogue, search, saved views, requests and approvals
Stack
HTML, CSS and JavaScript, with a shared data-access layer
Status
Internal application

The task

Tracking a request and finding its finished asset are different tasks.

CreativeOPS adds a browsing and retrieval interface around the existing project workflow. The board remains responsible for the requests; the catalogue provides a way to find, preview and download the resulting work.

The workflow

  1. Search or filter
  2. Preview
  3. Download

For new work, requests and approvals connect back to the project board through automation.

webhooksProject boardsource of truthAutomationtwo-way syncCataloguesearchableThe teambrowse · approveCompany sign-on
The project board keeps owning what was commissioned; the catalogue owns finding it again. Automation keeps the two in step in both directions, so using one never means abandoning the other.
CreativeOPS
SearchMarketProductQuarterSaved view
Browsing is built around what people actually remember — roughly what it looked like, roughly when, which market — rather than around how the company files things.
InterfaceOne access layerevery callDemo datain memoryLive backend
Every read and write goes through one layer with two interchangeable implementations. The application cannot tell which is attached — which is why it can be demonstrated in a meeting without showing a single real record.
Workflow diagram

Design decisions

  1. 01

    Keep the existing board in the workflow

    The catalogue synchronises with the project board rather than asking the team to manage unrelated records in two places.

    This gives asset retrieval its own interface while preserving the request workflow already used elsewhere in the company.

  2. 02

    Give assets more than one way to be found

    Search, filters and saved views let users browse by attributes such as market, product and period.

    Previews and direct downloads sit within that browsing flow. A saved view preserves a useful combination of filters for the next visit.

  3. 03

    Use the same interface for demo data

    The application routes data operations through a shared access layer with separate production and demo implementations.

    The demo mode can present the application's workflow without connecting to real company records. It is a useful way to show interaction detail while keeping the underlying material private.

  4. 04

    Control which features are visible

    Feature flags keep incomplete features out of the normal interface until they are ready.

    This is a delivery decision as well as an implementation detail: the visible workflow stays limited to the features available to use.

What I delivered

A searchable creative catalogue, preview and download workflows, saved views, request and approval integration, and a demo mode.

Project note

This application is internal. The diagrams describe its workflow. Any demonstration uses the approved scope and sample data.

Ask me about this project← All builds