Hi everyone! My organisation is optimising the way we use Asana across our global marketing team. We have regional marketing leads across the world, as well as our HQ department with marketing areas for social/PR, content and creative to name a new. I’m looking for advice from other enterprise (or large organisations) on how they best use Asana.
Currently, our team has separate projects for their departments, for regional marketing teams, and then individual boards for things like events, webinars and campaigns - though these are getting unweildy. We’re also trying to utilise a marketing intake board (and form) for work requests related to our HQ team.
We also have a very large number of custom fields floating between projects without any consistency, and automated rules that are sometimes interfering with each other.
I’d appreciate any insights or advice! Also, happy to connect and discuss!
1 Like
Hi @Caitlin_Ahne-Hawley1
If you need any help with your setup and best practices, I’d recommend reaching out to your Asana Account Manager to discuss the options.
You can see some information on how other companies use Asana here: Customers who use Asana • Asana
You can also browse through different use cases here: Asana Workflow Solutions and Team Uses • Asana
1 Like
hi @Caitlin_Ahne-Hawley1 I’d be happy to walk you through how I set up Asana for a creative team within a company of about 800 people. The larger marketing team also uses it, albeit in a less structured way. If you’re interested, feel free to message me directly.
2 Likes
Hi Caitlin
I am late to this one, but the intake part of your post stood out because it’s the thing we see big marketing teams wrestle with most.
Asana’s native forms will take you a fair way, and they can even be shared by public link so people outside your org can submit. Where it gets messy is after the submission.
The requester doesn’t get a thread, so every follow-up question drifts into email. Requests that arrive as email in the first place can be forwarded in as tasks, but replying
to that person still means leaving Asana for your inbox — and now the request history lives in two places.
That after-the-form part is what our product, Hipporello Service Desk for Asana, is built for — disclosure, I’m the founder. It’s in the Asana apps directory:
Service Desk for Asana + Asana • Asana . Requests from a portal, form or shared email address land as Asana tasks and your team replies from inside the task. The
back-and-forth stays synced, requesters don’t need Asana accounts, and several projects can feed one intake. And it’s more than a form front-end: the portal can carry
self-service articles so people find answers before submitting, routing and assignment can be automated, requesters can rate how their request was handled, and there’s
reporting to see volumes and how the team is keeping up.
If the one-way form flow isn’t actually hurting you yet, native forms are honestly probably enough. But if email intake or scattered follow-ups are part of the mess, feel
free to DM me and I can walk you through how other teams have set this up.