From Sound Systems to Digital Systems

From sound systems to digital systems

Before becoming a Product Designer, I spent several years working in music, sound engineering, live performance and independent creative production.

At first, these worlds may seem far from product design. One belongs to studios, stages, microphones, consoles and performances. The other belongs to interfaces, user flows, prototypes and digital products.

But the more I progressed in Product Design, the more I realized that the core process was deeply familiar.

The medium changed.
The way of thinking did not.

Designing an experience before designing an interface

As an artist, I was never only “making songs”.

I was designing an experience.

A song is not just a melody. It is an intention, a structure, a rhythm, a mood, a story and an emotional journey. A live show is not just a performance. It is a sequence of moments, transitions, tensions, releases and interactions with an audience.

As a sound engineer, the same logic applied in a more technical way.

The goal was not to make everything louder. It was to listen carefully, identify what mattered, reduce noise, balance signals and create clarity.

That is exactly what I now recognize in Product Design.

A good product is not just a set of screens. It is an experience shaped around a user’s needs, constraints, expectations and emotions.

Listening is the starting point

In music and sound engineering, listening is not passive.

It is an active skill.

You listen to what is present, but also to what is missing. You notice imbalance, friction, tension, noise, hesitation. You learn to detect weak signals.

Product Design starts in the same place.

User research is not about asking questions mechanically. It is about listening carefully, understanding context, identifying patterns and separating symptoms from real problems.

My background as a musician and songwriter trained me to pay attention to what people express directly, but also to what sits underneath: emotion, intention, frustration, expectation.

That sensitivity is now one of the strongest links between my past work and the way I approach user research.

Structure turns intuition into something usable

In music, intuition matters. But intuition alone is not enough.

A song needs structure.
A live set needs a flow.
A recording session needs a setup.
A technical production needs routing, constraints, preparation and coordination.

As a sound engineer, I learned to work with systems: inputs, outputs, channels, routing, monitoring, levels, EQ, signal paths.

That technical mindset translates naturally into Product Design.

Wireframing, for example, feels very close to audio routing. In sound, routing defines how a signal moves through a system. In design, wireframing defines how a user moves through an experience.

Both are about structuring flows before execution.

Before the final sound, there is a routing diagram.
Before the final interface, there is a wireframe.

In both cases, the goal is to make a system understandable, coherent and usable.

Testing is part of the work, not the end of it

Music production is built on iteration.

You record, listen back, adjust, try again.
You test an arrangement.
You rehearse before a live show.
You change a level during soundcheck.
You adapt when something does not work.

Nothing is final too early.

Product Design works the same way.

A prototype is not a finished product. It is a way to test an idea, reveal friction and learn before investing too much in the wrong direction.

Usability testing reminded me of something I already knew from music and live performance: feedback is not a personal attack. It is material. It helps make the experience better.

The goal is not to defend an idea because it is yours.
The goal is to build the best possible experience.

Working under constraints

Music also taught me how to work under pressure.

Live performance does not wait.
A concert has a start time.
A recording session has limited hours.
A production has a budget.
A video shoot has a team, a schedule and unexpected problems.

These constraints shaped the way I work: prepare seriously, stay adaptable, communicate clearly and make decisions when needed.

Product Design is also full of constraints: user needs, business goals, technical feasibility, deadlines, accessibility, product priorities.

I do not see constraints as blockers. I see them as part of the design material.

A solution is only strong if it works within reality.

From both sides of the glass

One of the most valuable parts of my background is that I have been on both sides of the glass.

I have been the artist expressing an intention.
I have also been the sound engineer translating that intention into a technical setup.

That double perspective taught me how important it is to understand both the creative goal and the technical constraints.

This is also how I want to grow as a Product Designer.

I am learning the fundamentals of code not to become a developer, but to better understand feasibility, communicate with engineering teams and design solutions that are both user-centered and technically realistic.

For me, good design lives in that space: between intention and execution.

Why Product Design felt like a natural progression

Product Design did not feel like starting from zero.

It gave a name, a structure and a method to a process I had already been practicing in another medium.

Listen.
Understand.
Structure.
Create.
Test.
Adjust.
Iterate.

In music, I applied this process to sound, emotion and live experiences.
In Product Design, I now apply it to digital products, interfaces and user journeys.

The medium changed.
The process stayed familiar.

That is why becoming a Product Designer feels less like a break from my previous path, and more like a natural progression of it.