NOWScale
Multi-Brand TeamsScenario 7 of 7

Nine people, six brands, and one tab that looked like every other tab.

The shared team could produce for any brand. Remembering which brand they were currently logged in as was the part that kept failing.

Ostrand Group·Composite: consumer group, six brands, one shared 9-person content teamIllustrative scenario

Snapshot

4 min read7 of 7
Segment
Multi-brandSix consumer brands, one group
Team size
159 shared content + 6 brand leads
Channels
246 brands × 4 platforms
Time to value
3 weeksAll six brands migrated
Placeholder

Six brand workspaces, one shared team

Scoped brands with per-brand voice presets and routingArt pending — 1600×1000

01 — The situation

Before

A shared content team is an efficient idea that gets harder to run with every brand you add to it.

Nine people produce for six brands. The brands are genuinely different: one sells to trade buyers and writes like it, one is aimed at eighteen-year-olds, one has a house style document that forbids exclamation marks and another opens most posts with one. A writer might touch four of the six in a single day.

Monday morning is the planning meeting. All fifteen people, ninety minutes, working through six calendars in six spreadsheets to establish what is going out where. The meeting exists because there is no other surface on which all six brands' plans can be seen at once.

Publishing runs through a shared password manager holding twenty-four sets of credentials, with the two-factor codes arriving on one team phone kept in a drawer. Assets live in a shared drive organised by shoot date, which means finding the right image for the right brand is a matter of remembering when it was photographed.

02 — The friction

What it was costing

Everything worked until someone was tired, and then it failed in the one way that is hard to take back.

Three times in twelve months, a post written for one brand went out on a sister brand's channel. Every instance was the same mechanism: several near-identical browser tabs, a writer moving between brands, the wrong one focused. Each took a deletion, an internal escalation, and — twice — a customer noticing first. A post is deleted in seconds and screenshotted faster.

Voice drift was the slower version of the same problem. With six style guides in six documents, applied from memory by nine people, brands blurred toward a house average. The brand leads spent a growing share of their review time correcting tone rather than judging ideas, which is an expensive use of the person who owns the brand.

Reporting was six exports assembled by hand into one deck, so the group-level question — which brand is growing, where should next quarter's production hours go — was answered monthly at best and never with confidence. And because assets were filed by shoot date rather than by brand or usage, a photo shot for one brand and perfectly reusable by another was found only by accident.

What this was costing

  • Cross-brand publishing mistakes3 in 12 months
  • Monday planning meeting90 min × 15 people
  • Credential sets in one shared vault24
  • Group-level reportingManual, monthly

03 — What changed

The reworked workflow

Each brand got a boundary, and the shared team started moving between brands deliberately instead of by tab.

  1. Multi-brand workspaces

    Six workspaces, each with its own assets and queue

    Every brand has its own space: its own channels, its own asset library, its own calendar. Switching brand is an explicit act with the brand's name and identity on screen, rather than clicking a tab that looks like the last one. The mistake that had happened three times in a year stopped having a mechanism.

  2. Caption and title presets per brand

    Voice rules live where the writing happens

    Each brand's tone rules, banned constructions and format conventions are attached to its workspace rather than sitting in a document nobody opens at 4pm. Generated caption and title variants come back already shaped by the brand being written for, so the brand lead's review is about the idea instead of about punctuation.

  3. Approval workflows

    Review routes to the right brand lead automatically

    A post in a brand's workspace routes to that brand's lead. No one forwards anything, and no lead has to work out which of the day's forty posts are theirs. The six leads stopped being a bottleneck by being addressed individually rather than collectively.

  4. Cross-platform analytics, rolled up

    Per-brand detail and a group view from the same data

    Each brand lead sees their own channels; the group sees all six side by side on consistent definitions. The Monday meeting's original purpose — establishing what is happening — was already answered before anyone sat down.

The team did not get bigger and the brands did not get simpler. The work just stopped depending on nine people holding six sets of rules in their heads at once.

04 — Results

What moved, and by when

  • Channels consolidated into scoped workspaces

    24 loose6 workspaces

    3 weeks

  • Cross-brand publishing mistakes

    3 in 12 months0

    11 months to date

  • Monday planning meeting

    90 min25 min

    from week 4

  • Brand-lead review time spent on tone corrections

    ≈45%≈15%

    by month 2

Honest note on what drove this

The meeting figure deserves an asterisk. Twenty-five minutes is the meeting; the coordination did not vanish, it moved into the workspaces where it happens asynchronously and is arguably easier to ignore. Two brand leads pushed back in month one that they now saw less of what other brands were doing — the group added a fortnightly cross-brand review to replace what the long Monday meeting had provided incidentally. The zero-mistake figure is the durable one, because it comes from a boundary rather than from anyone being more careful.

Six brands, six voices, nine people, and the only thing telling you which one you were in was a favicon.

Group content lead — composite of multi-brand consumer groupsIllustrative scenario

05 — What to take from this

Transferable lessons

Useful whether or not you ever open NOWScale — these are the parts that generalise.

  • Identical interfaces cause identical mistakes

    If switching between two contexts looks the same as staying in one, people will cross the boundary without noticing. Make the switch visually unmistakable, or make it impossible.

  • Style guides fail at the point of writing

    A voice document in a shared drive is consulted when someone is new and ignored when someone is busy. Rules only hold if they are present in the tool at the moment the sentence is written.

  • Route review to a person, not to a group

    Six approvers in one queue means six people scanning for their own items. Address each item to its owner and the same six people become six parallel paths instead of one contended one.

  • Watch what a long meeting was quietly providing

    Meetings that look wasteful often carry a second function nobody wrote down — here it was cross-brand awareness. When you shorten one, check what disappeared alongside the waste.

All 7 case studies