The Lesser Played Chord: On the Borrowed Harmony of Adjacent Properties

There’s a moment in certain songs, often in jazz or more adventurous pop, where the harmony shifts in a way that feels both unexpected and perfectly right. The composer reaches into a nearby but distinct key, borrowing a chord that doesn’t ‘belong’ to the song’s home scale. This borrowed chord creates tension, color, and a depth that a straightforward progression lacks. It introduces a momentary complexity that, when resolved, makes the return to the tonic feel earned and more satisfying.

I’ve been thinking about this musical concept, called ‘borrowed chords’ or modal mixture, while wrestling with the architecture of a sprawling website. Specifically, the challenge of handling top-level sections that are thematically related but serve distinct purposes—adjacent properties, if you will. Think of a company’s main commercial site and its separate, dedicated support portal. Or an academic institution’s primary .edu domain and its distinct site for a major research institute.

Our instinct, much like a novice composer sticking to a simple C major scale, is often to force everything into a single, unified structure. We try to make the support portal a subdirectory of the main site, or we cram the institute’s content under the primary domain, creating awkward URL paths and bloating the main site’s architecture. We do this in the name of consolidation, of presenting a united front. But in doing so, we often create a different kind of dissonance—a user experience that is confusing and a content hierarchy that is illogical.

The Resolution of a Separate Domain

This is where the borrowed chord offers a lesson. The beauty of the borrowed chord is that it isn’t a permanent modulation; it’s a temporary visit. It acknowledges the existence of another space, draws strength from it, and then returns home. Applied to our websites, a separate domain for a distinct property can function in the same way.

A support.yourcompany.com isn’t an admission of failure in site structure. It’s a deliberate, harmonic choice. It says, “This is a different mode of engagement.” The user’s mental model shifts from ‘browsing a company’ to ‘solving a problem.’ The content, the navigation, the entire tone can be optimized for that single purpose without being forced into the mold of the main marketing site. The two domains are adjacent keys, and the user moving between them experiences a shift in context that is, when signaled correctly, perfectly logical.

The crucial element, as in music, is the resolution. You can’t just throw the user into a foreign key and leave them there. The links between these properties must be our cadence. A clear, prominent link from the main site’s global navigation to the support portal is the harmonic preparation. A persistent link back to the main site from the portal is the resolution back to the tonic. And the canonical tag? It’s the composer’s notation, ensuring that if someone tries to play the ‘support’ chord progression on the ‘main’ site’s instrument (i.e., via a search engine), they are correctly directed to the proper key.

This approach requires more finesse than a monolithic site. It demands thoughtful redirects, clear signal-passing, and an understanding that a unified brand doesn’t always mean a single URL structure. But the result is a richer, more nuanced web presence. Each property can achieve its purpose with clarity, and the journey between them becomes a deliberate, composed experience rather than a structural compromise. It’s the difference between a simple melody and a piece with depth—a harmony borrowed from an adjacent property, creating a more compelling whole.

Notes & further reading

A few pages I came back to while writing this: