PATTERN NOTE
The parent palette as creative resource, not constraint.
Most community brands in property treat the parent palette as a constraint. Treating it as a creative resource turns the community brand into a deliberate operational test of how far the parent system can flex without losing its identity.
Vinay Raja
6 min
A community brand in a developer's portfolio has a relationship with the developer's parent palette. The relationship is almost always defensive. The parent palette is treated as a constraint to design around – the community brand pulls a small subset of the parent's colours, defers where the parent system insists, and saves the creative latitude for everything else.
This is a missed move. The parent palette in most developer brands is richer than its community brands ever use. The community brand that only takes a subset of it leaves the rest of the parent system unused.
Why it matters
Three things go wrong when the parent palette stays underused.
The parent system never gets stress-tested. A brand system that has only ever been used inside its safe range will not surface its boundary conditions until something forces it to. The community brand that pushes the palette is the safest place to surface those boundary conditions.
The community brand has to do all of its work with whatever isn't colour. When the community brand defers entirely on palette, every other lever has to compensate. The result is often a community brand that's overworked in some dimensions and underworked in colour.
The portfolio's brand expression converges on sameness. When every community brand in the portfolio uses a similar restricted palette, the portfolio starts to feel monochromatic across its communities.
The parent palette is richer than its community brands ever use.
How Tydal sees it
Treating the parent palette as a creative resource is a strategic decision, not a styling one.
Audit the full parent palette. Most teams have no living document of the parent palette in its full extent. The audit gives the community brand a real menu to choose from, rather than the small habitual subset the team has been working with.
Anchor the brand on a constant. When the colour is allowed to flex, something else has to be the constant. A graphic device – a pattern, a motif, a recurring shape – has to do the work of keeping the brand recognisable across colourways.
Treat colourways as a system, not as one-offs. When a community brand carries multiple colourways, the colourways have to operate as a coherent set – assigned to release stages, to seasonal moments, to product types.
Where this shows up in our work
Rosella Rise. A coastal community on the NSW Central Coast, in Warnervale. For the first time in the AVJennings community brand work, the brief was also to use the AVJennings masterbrand colour palette to its fullest extent. The output was a brand identity built around two complementary mechanics: a constant graphic device (the Pattern), and a flexible colourway system. Five colourways – blue, green, light blue, red, yellow – give the brand five distinct moods to work with, each one drawn from the AVJennings masterbrand palette with discipline. The experiment held. The masterbrand-flex thinking from Rosella Rise then set a precedent for subsequent community brand engagements.
What to do about it
If you're a developer with a portfolio of community brands and a parent palette that you suspect is being underused, three places to start:
Lay out your full parent palette and your community brands side by side. What proportion of the parent palette is in active use across your portfolio? For most developers the honest answer is somewhere between 40% and 60%.
Pick the next community brand for the experiment. The best candidates are ones with a strong place identity that can carry the constant device.
Anchor the experiment on a single graphic device. Before you start choosing colourways, decide what the constant is going to be. Get that right first; then the colour can flex around it without losing brand definition.