Thank you, @CynthiaBoon, for trying to address this.Two things:I've only heard reasons why resource pools can be helpful; not why they're required. If we don't use Resource Pools, does Planner not fully function?What if we don't yet know what the resource pools should be for projects? In my organiza...

I think it's in a decent shape to share. Template overviewThere are four categories of work: Prepare, Translate, Localization and review, Close out. The flow of work assumes that:There is a base file (in our case, the US version) that gets localized first, then translated.The localized files are sen...

Eventually I hope to get to the nirvana of build-your-own based on add-on templates. For now it's Everything Bagel (a nickname I'm now going to hide as an Easter egg in the template).Because we're transitioning from Everyone Is Master to Admin is Master, we also have "blank" templates that have basi...

Duuuude, thank you for connecting the dots between the task name and template task name.

While we default to Schedule From Start Date, we have a few that use Completion Date. And we have a few that are a hybrid (technically based on a Start Date, but there is at least one tasks somewhere in the middle with a Fixed Date task constraint).I think the key is awareness with your project owne...

Indeed. What I forgot to say is thank you for the idea of auditing task names. While I don't want to be auditing task naming all the time, it will be a great way for me to get a sense of the diversity of naming.

There are two possibilities that come to my mind:Create a custom filter and train those users to apply it when viewing projects.(I think I'd advocate for this one as it requires less training for your audience.) Build a report or even a dashboard to pull in only the relevant tasks for your less savv...

Great idea! I've been using the Task Description field for general process reminders and scheduling guidance.I also use the Task URL field if there is an external resource to help complete the work (for example, an SOP, request form, governance documentation, or data source).

I have a couple thoughts here:Lately I started exploring shell projects. The templates include high level tasks so, when I convert it to a project I have consistent tasks. Then, in the project, I can add issues to tasks, which I then convert to projects based on the scope of work needed. This allows...

Consistent task naming is something our Creatives have been begging for. That said, the second someone says to me, "I want a report on all tasks named x," I slow their roll and start talking about milestone paths. A milestone that is associated with a task can allow project owners to name tasks as t...