We've struggled with part 2 as well. One place we landed: Technically a deliverable is one asset of a specific localization (that is language and/or geographic-specific content).Because we often try to generate localizations of an asset simultaneously, there is a lot of pre- and post-work that is lu...

You're tapped one of the perennial philosophical debates. The short but complex answer is that it depends on your needs, preferences, and project owner capabilities. I'm a fan of one project per deliverable. In this approach, my PMs have pushed back because there are sometimes activities done in bul...

I echo @skyehansen. For us, we don't have Fusion, but we do use SSO. When we were migrated to the Admin Console, it actually helped me in that terminated users in Azure are automatically deactived in Workfront. I didn't have to do anything in Workfront; IT controls it. Prior to this, I would run rep...

@MoniqueEvans Leslie said you were interested in hearing more about the T-shirt sizing and scope creep. I suspect you know how I built it, but if anyone needs to see, it's on pages 13-14 in my attachment on [Event follow-up] November 2024 Skill Exchange: Wo... - Adobe Experience League Community - 7...

I had a blast! Thanks to everyone for entertaining my wild idea. At one point I glossed over how I proactively added calculations to my custom form in case I needed them. As a look behind the curtain, I created three calculations (shown in the screenshot below): LanguageRegionCountry (see screenshot...

Here's an older thread where I share a couple templates I created from my own governance documentation. My knowledge base comes in a couple different forms:   Governance documentation (a.k.a. The Nerdy Details) I have many documents beyond the two linked in the above thread; basically one for each o...

I concur with everything @Daniel_Clarke said and will add: We have customized access levels in conjuction with layout templates to optimize user experience. If people aren't using the functions and have not been trained to safely tinker, they're liable to break things—for themself or others. Also, i...

In our instance almost everyone belongs to a single company. We use portfolios that are assigned to certain groups to isolate work. The group that is assigned to the portfolio manages the programs within, however other groups and teams may own projects in those programs to support reporting on cross...

I'm also a big fan of testing in sandbox, as @AbiBeggs suggests. That said, it's not super difficult to: Create a new group.Add users to the new group.Deactivate the old groups.Wait a bit and delete old groups. This might give a good cushion for discovering hidden reasons for those groups that don't...

I see: it's about statuses. I've heard others recommend keeping statuses relatively simple because, as you've discovered, managing them is sometimes not easy. Defining clear governance around statuses can help reduce how often someone asks for a new status. For example, in our organization we use: N...