Begin with an experience worth expressing
Brief a sonic identity by identifying an experience the product genuinely owns, then decide what sound should communicate about it. A prompt for something futuristic, premium or friendly is too broad to establish a distinctive direction on its own.
In her 29 October Design Week opinion, Pearlfisher's Natalie Prout argues for identity grounded in product experience, using Apple Music as an example. My proposed exercise applies that idea to a small AI-assisted brief. It does not claim a search-ranking effect from adding sound.
Observe before turning everything into an effect
List sounds, gestures and moments that belong to the product or service. A physical workshop might have a distinctive closing action. A software product may have a meaningful completion moment rather than an obvious natural sound. Observe the experience before deciding that it needs an audio signature.
Record why a moment matters to the user. Is it reassurance, anticipation, progress or recognition? Many products should remain quiet during ordinary use. Sonic identity can belong in a film or introduction without becoming a repeated interface interruption. The brief should name the application and the option to use no sound.
Translate the observation into constraints
Describe intended associations in plain language, alongside associations to avoid. Specify where the sound will play, approximate duration, interaction with speech and whether a silent alternative is needed. Distinguish a brand signature from background music or a spoken brand voice.
For a fictional document tool, the brief might connect completion with a light, orderly resolution. It might reject dramatic alerts that imply urgency. That is a design scenario, not an acoustic recipe or a completed experiment. A composer or assistant needs room to interpret the idea while respecting the product's actual behaviour.
Explore routes without copying the reference
Human composition, sound design and generated exploration can each contribute. Give every route the same application brief so the comparison is about fit rather than spectacle. Confirm usage rights for source recordings and generated outputs before including them in a deliverable.
Keep the source of the idea separate from the finished sound. Apple Music's example is a reason to study your own product, not to reproduce its signature or visual treatment. Record what a selected option expresses and why alternatives were rejected. That gives later production a usable design decision instead of a mysterious preference.
Test in context and document restraint
Review a candidate beside narration, on ordinary speakers and in the shortest actual application. Ask whether it supports recognition without competing with the message. Avoid a test that merely asks which option sounds most expensive.
Write the approved uses, volume relationship, silent fallback and conditions for revisiting the work. JQ's product-film service offers a natural place to test a sonic direction before applying it more widely. Begin with one meaningful moment. A coherent identity can extend across senses without requiring an audible flourish on every interaction.
Link Map
Sources and editorial review
Assigned to the 27 October–2 November 2026 editorial series. This edition was prepared and source-checked on 2 November 2026; assigned dates do not imply prior public deployment. Proposed workflows and illustrative examples are JQ AI SYSTEMS editorial analysis, not completed client experiments.
- Natalie Prout, Design Week: The sound of things to come in branding (29 October 2026; practitioner opinion).