Our small organization (under 20 employees) consists of three separate brands (Doctor-facing Membership, Consumer-facing Platform, and a Brick+Mortar Practice),
Most employees support 2 of the 3 brands OR all 3. (Example: Head of Ops at the Brick+Mortar also creates content for the Doc-Facing Membership Brand…but does nothing on the Consumer -facing platform)
I’m trying to find the best way to organize all of our projects crossing between each company to create better clarity as well as ensuring members who work across multiple brands are not getting overbooked.
The general consensus I’m finding on these forums is to organize our Asana like so:
Teams = Marketing, Sales, Support, Content, Events, Operations
Portfolios = Brand 1 Projects, Brand 2 Projects, Brand 3 Projects
But I’m thinking it would be best to do:
Teams = Brand 1, Brand 2, Brand 3
Portfolios = Marketing Projects, Sales Projects, Support Projects, Content Projects, Events Projects, Operations Projects
Will I miss out on some sort of advantage / function by going this route??