In a studio, every sound can be technically correct and the record can still be wrong. Software is similar. A team can close every ticket and still fail to make the product better. Execution matters, but taste determines what deserves to exist.
I learned this through years of writing, producing, DJing, running creative businesses, and building music projects including Pete Fox and Aycan. Later, when I moved deeper into software and technology leadership, the environment changed but the underlying work felt familiar. Both disciplines require a clear intent, a shared language, and the judgment to turn many specialized contributions into one experience.
Begin with the experience, not the equipment
A studio full of expensive equipment does not create a good record. Neither does a large technology stack create a good product. Tools expand what a team can do, but they cannot decide what the work should mean to the person receiving it.
Before choosing sounds, I want to understand the emotional center of a track. Before choosing product architecture, I want to understand the human problem and the experience we are trying to create. Without that anchor, teams start optimizing parts in isolation. The drums become impressive but fight the vocal. A feature becomes sophisticated but adds friction to the central workflow.
A clear intent is not a rigid specification. It is the standard against which options can be judged. It allows specialists to improvise without pulling the work in unrelated directions.
Signal flow comes before polish
When a recording is noisy, you trace the signal. You do not keep adding processing and hope the problem disappears. Where did the signal originate? What touched it? At what point did it change? Strong engineering teams do the same: understand how data, responsibility, and decisions move through the system before adding another abstraction.
This is also an organizational lesson. When work repeatedly stalls, I look at the path rather than blaming the person nearest the delay. Does the team know who can decide? Is important context lost during handoff? Are people solving the same problem in separate rooms? A broken workflow cannot be repaired with more urgency.
In both music and software, the cleanest result often comes from fixing an early decision. A better source recording needs less processing. A better product model needs fewer interface explanations. Quality compounds from the beginning of the chain.
Build the rough mix early
A rough mix lets you hear whether the song works as a whole before every detail is finished. Product teams need the same thing: the smallest end-to-end experience that exposes whether the central promise is real.
This is different from building a collection of disconnected prototypes. A rough mix includes enough of the full journey to reveal relationships. Can the user begin, make the important decision, receive a useful outcome, understand the result, and recover if something goes wrong? Until those pieces connect, local progress can hide a weak overall experience.
Working end to end also changes team conversations. Instead of debating imagined behavior, people can react to something concrete. The product becomes the shared object in the room, just as a playback gives musicians and engineers a common reference.
Iteration needs a point of view
Creative work improves through iteration, but endless options are not progress. Someone has to decide what the work is trying to say. Product leaders serve a role similar to producers: protect the intent, create space for specialists, and make the call when additional exploration stops helping.
That responsibility is not the same as having every answer. Some of the best production decisions come from recognizing an idea that another person introduced and understanding how it strengthens the whole. Leadership requires enough confidence to make decisions and enough humility to let the work become better than the original plan.
The productive question is rarely “Which person won the argument?” It is “Which choice best serves the result?” Strong teams can disagree directly because the shared objective is more important than ownership of an idea.
Taste is disciplined subtraction
People sometimes treat taste as mysterious instinct. I think much of it is the ability to notice what the work does not need. A mix can have excellent individual parts and still lack focus because too many of them demand attention at once.
Organizations do this too. Too many priorities, meetings, dashboards, and parallel initiatives make every contribution less audible. A team can be busy while the product becomes less coherent. Removing work is often the highest-leverage form of leadership.
Subtraction also creates perceived value. Space communicates confidence. A restrained interface, a focused message, and a product with a clear purpose often feel more capable than something that displays every feature at once. My background in graphic design and branding reinforced the same lesson: hierarchy is created as much by what you quiet as by what you emphasize.
Specialists need a shared language
A producer does not need to play every instrument better than the musicians. The job is to understand what each specialist contributes, communicate the intent in language they can use, and recognize when a technical choice changes the emotional result.
Product leadership works the same way across engineering, design, operations, sales, and support. Each function sees a different part of the truth. The leader’s job is not to flatten those perspectives but to translate between them. A customer complaint may reveal a product-model problem. An infrastructure concern may change what the interface should promise. A brand decision may affect onboarding and support expectations.
The most effective teams develop language that connects those layers. They can discuss technical constraints without losing the customer outcome and discuss creative ambition without pretending constraints do not exist.
Deadlines create decisions
A track eventually has to be printed. A show goes live at a specific time. Those moments force decisions that can otherwise remain theoretical forever.
Software is never truly finished, but useful releases still need a definition of complete. The point is not to ship carelessly. It is to decide which uncertainty must be resolved now and which can be learned from responsibly after release. A deadline is valuable when it concentrates judgment, not when it merely compresses labor.
Live production adds another lesson: recovery is part of quality. Equipment fails, networks change, and people miss cues. A professional system is designed not only for the ideal performance but for graceful degradation, clear monitoring, and fast recovery. Product teams should judge reliability the same way.
The audience only experiences the whole
The listener does not grade the separate departments that made a record. The customer does not experience an org chart. They experience one product, one brand, and one relationship.
That is why coherence matters so much to me. The marketing cannot promise simplicity while the interface creates confusion. The design cannot signal premium care while support feels indifferent. The product cannot claim intelligence while hiding uncertainty. Every layer contributes to the perceived value of the whole.
When the pieces support each other, the result feels inevitable—even though getting there required hundreds of deliberate choices. That is true of a strong record, a strong brand, and a strong product. The craft is making all that complexity arrive as one clear experience.