UX direction & product design

NOAH Cloud

Noah is a cloud media workspace for teams who live in video — one place to store, find, review, and share, with feedback stuck to the frame instead of lost in Slack.

UX Director Product Manager Multi-tenant SaaS MAM
NOAH Cloud marketing hero: headline A library worthy of your beautiful work, cloud mascot, and media library UI with search and asset cards.
Marketing hero — library-first positioning with the product UI underneath.

The gap I designed into

Creative teams were stuck between tools that are easy but fall apart under rights and versions, and enterprise MAM that feels like an IT project. I set Noah to win the middle: approachable on day one, governable as the company grows — with review attached to the media itself.

Too light

Drive and Dropbox are simple, but they break on permissions, versions, and frame-level notes.

Too heavy

Iconik-class platforms prove the ceiling — hybrid storage, AI search, automation — but mid-market teams stall on day-one complexity.

Noah’s bet

Win the daily loop first: find the cut, mark the frame, share safely. Deepen enterprise power after that habit sticks.

Who had to succeed

I started from the decisions each person makes — then only built what answers them.

Jobs Noah had to win for each role
Role They need to decide What I designed
Producer Is this the right cut — and can my note hit that frame? In-page viewer with canvas drawing and timeline markers
Editor Where does this version live, and who can change it? Projects, folders, and scoped company / project / personal tags
Studio ops Are seats, MFA, and share policy under control? Org settings for roles, security, workspaces, and share defaults
Guest / client Can I review without creating an account? Branded share pages with access controls — no full seat required

The loop the product is built around

Everything else supports this sequence. If a feature does not help someone find, mark, share, or govern — it waited.

  1. 01 Find One library across folders, projects, tags, and review status Editor / Producer
  2. 02 Mark Canvas annotation on the frame — not a comment lost in chat Producer
  3. 03 Share Governed guest links so clients review without seat sprawl Editor
  4. 04 Govern Org controls for customers; a separate plane for Noah operators Ops / Platform

Three calls that mattered

These are the trade-offs a hiring manager should understand — not a feature list.

Review

In-page, not a modal

Harder layout work. Worth it so scrubbing and annotation stay in one workspace — review stays primary, not a peek.

Structure

Scoped tags, not flat tags

Company, project, and personal scopes stay visible. Flat tags look simpler and create false hierarchy and cross-project leaks.

Admin

Two planes, not one settings app

Customer admins govern their org. Platform admins run Noah. Mixing them forces support to borrow customer logins.

Product surfaces

Four screens that prove the loop — library, canvas review, guest share, and platform admin.

Find One browse model for folders, projects, and tags
Mark Feedback on the frame, not in a side thread
Share Guest review without seat sprawl or file dumps

Media work is not files plus comments. It is find, mark, decide, and share — under real org constraints. Noah is designed to win that loop before chasing enterprise vanity features.