Expand my Community achievements bar.

Scale project design for multi-market setups - thoughts?

Avatar

Level 3

Hi everyone,

 

I’m working on a project setup that needs to accommodate multiple markets for an org.

 

At the moment, our project template includes one task per market, each with its own market-specific actions. We structured it this way to keep accountability clear: every task has a single assignee, rather than bundling multiple assignees into one task where ownership becomes unclear. We also use project-level custom fields to capture market-specific data, but because fields can’t be reused within the same form, the number of fields multiplies as we add more markets. For example, if 1 market needs 2 fields, 2 markets require 4, and so on.

 

This quickly becomes difficult to scale. Whenever a new market is added, the project template needs to be updated to include a new task, and the custom form needs additional fields. As we onboard more markets, this approach becomes increasingly unsustainable and creates downstream complications, especially for Fusion...

 

For those who have faced similar challenges: how do you design your Workfront project architecture so it can adapt dynamically as new markets are added? How do you avoid having to constantly update templates and custom forms while still capturing all the necessary market-specific information?

 

Thanks

0 Replies