Work

Case study 04Music tech

Lagos, Nigeria

Vocal Centric is an AI tool for singers and choirs: upload a track, and it splits the vocals and maps alto, soprano, tenor and bass. I was one of three designers, across mobile, web and admin.

Industry
Music tech · Creator community
Role
Product designer (contract)
Team
Me, designer David, another designer and a PM
Timeline
Nov 2023 to Oct 2024
Platform
Web, mobile and admin
Scope
Research · UX · UI · Accessibility
Status
Live · vocalcentric.com

3 min read · 2023 to 2024

The song library: a walkthrough of the product

The 30-second version

For busy readers
A The goal

Help singers learn their part without hunting through YouTube, voice notes and WhatsApp.

B What I did

Designed a song library, part player, lyrics, practice tools and community, with the AI in the background.

C Outcome

Retention rose 25% and recording-and-editing time fell 40% in the first four months.

01The problem

The music existed. Practising it was broken.

Someone had to work out by hand who sings which line, and feedback meant posting a recording in a WhatsApp group and hoping. Existing tools were built for audio engineers, not singers.

3 apps
to rehearse one song
02My role

I learned enough music to design for musicians.

  1. 01 · research

    Talked to singers, choir directors and vocal coaches.

  2. 02 · design

    Worked on the library, player, lyrics, practice and community, and owned the admin side.

  3. 03 · accessibility

    Checked everything against WCAG 2.1 AA, including keyboard and screen-reader tests.

Team: Me, designer David, another designer and a PM

03What I learned

Singers didn't need more music

AI helped where it removed grunt work, and annoyed where it replaced the singer.

  • Insight 01

    Hear just my part

    Loop a single vocal part on demand.

  • Insight 02

    One library

    Beats files scattered across chat threads.

  • Insight 03

    Quiet AI

    Best in the background, never in the way.

04Key decisions

The calls that shaped the product

Why the AI stays quiet

The first direction leaned on AI coaching feedback.

Shipped

The AI splits parts and maps ranges. You just hear your part.

Why the orange changed

Bright orange said "not another grey tool".

Shipped

Still lively, and passing WCAG 2.1 AA.

05The screens

Designed for the moment mid-rehearsal

Core actions are never more than two taps away, and the community is a real space for discussions, requests and shared takes.

  • Two taps to anything
  • WCAG 2.1 AA
  • AI framed around outcomes
06The process

From the first interview to launch

~/vocal-centric/releases

→ git log --releases

  1. 01ListenSingers, directors, coaches
  2. 02TryAI coach tested and dropped
  3. 03RebuildLibrary, player, community
  4. 04LaunchLive, then four months of data

✓ Live at vocalcentric.com.

07Results

Rehearsal moved into one app

  • 25%higher retention in four months
  • 40%less recording and editing time
  • 4vocal parts from any track

Singers started looping each other's takes to lock in harmonies.

08Reflection

Showing capability vs earning trust

People need to trust AI output before they change how they practise, so the design gave the analysis room to prove itself.
  • What I found interesting

    Learning the difference between an alto and a mezzo-soprano, and why it matters to a singer.

  • What was challenging

    Keeping a bold, energetic palette while passing accessibility checks.

  • A mistake I made

    I prototyped the audio player too late. The real product lives in how play and loop feel mid-rehearsal.

  • What I learned

    Prototype the core interaction in week one, before the visuals.

Where it's at: Live at vocalcentric.com.

Next case study

HealthTech · 2025 to nowMyndHavenTherapy for fifty minutes. Support for the rest of the week.Read it