04 · Selected work
PubAdmin
Give a rights-management platform a system it can grow in, and workflows people can finish without getting lost in the ledger.
- Year
- 2024
- Type
- B2B SaaS · complex workflows
- Role
- Product design · design systems
- Focus
- Ops + visualisation
The tension
Music rights software is a dense object: catalogues, splits, territories, statements. The work is inherently tabular. The failure mode is that every new feature invents its own language, and operators spend their day translating the product back into their job.
What I designed
I architected a scalable design system and designed the complex rights-management workflows, data visualisation, and operational experiences around it. The system was the product, not a sticker sheet delivered after the screens.
- Component and token foundations so new workflow surfaces could inherit behaviour, not reinvent it.
- Operational patterns for dense tasks (review, exception, confirm), with visualisation where a table wasn’t enough.
- A shared language with product and engineering so the system could keep evolving after I left the file.
How I worked
I sat with the people who run the product daily. Rights work is expert work. The interface has to respect that expertise instead of hiding it behind a “simple” metaphor that doesn’t hold.