Audience architecture

One of the two developed fundamentals delivered under the Audience pillar in BRD-Strategy.

What it is

Audience architecture is the structured read of who the presence is for, how those audiences differ, what each one needs, and how the digital ecosystem serves each of them. It sits one layer below "target audience": the actual mapping of the people, their context, their questions, and the order they arrive in.

What's included

• Audience segmentation. Categorized by function: current customers, potential customers, peers and partners, internal stakeholders, press and other amplifiers. Each segment scoped to what they need from the presence.
• Personas. Detailed profiles for the key segments, grounded in research (interviews, voice-of-customer data, behavioural data) rather than in assumption. Each persona names the questions they bring, the friction they expect, and the trust signals that move them.
• User journeys. Mapped per persona. Where they start, what they touch, where they decide, where they drop off. Annotated with the questions the journey is answering and the proof the journey is supplying.
• UX flows. The on-site flows that follow from the journeys: landing pages, conversion paths, navigation patterns, secondary actions. Documented as flows rather than as wireframes, so the Build phase has the logic and can produce the visuals.

When you'd want this

• You speak about your audience in singular ("our customer") and you suspect that's hiding real differences in needs and journeys.
• Your conversion paths perform unevenly and you don't know why.
• A previous audience exercise produced personas that no one used because they didn't connect to actual journeys.
• You're entering a new market or segment and need the architecture before the build.