Expand my Community achievements bar.

The Community Ideas review for H1 2025 is out now, see which ideas our Product team prioritized and let us know your thoughts.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

Naming conventions in Workfront for Programs and Projects

Avatar

Level 1
Hi All- Wondering if anyone has any tips or tricks for naming conventions of Porfolios, Programs and Projects. Currently we are using this naming structure: Portfolios: 2016 GWC External Program: AVAIL 2016 Marketing Campaign Project: AVAIL 2016 PDM Video Due 6/1 If you don't have the Workfront icons memorized you don't know if you are looking at a Program, Project or Task. The 'AVAIL' is a client code. Our Portfolios are set up each year by Client type (we only have 5). The Programs are a drop down in the Custom Form. I guess the real struggle is when you use the search field it is hard to distinguish what you are really looking at i.e Program, Project &/or task the way we are currently naming things because it is so similiar. Is anyone else struggling with this and do you have any suggestions?
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Level 10
Stacy, We use project's all the time. Every now and then, if we need to group projects - then we will group them in a portfolio. Now with that said, I do have a suggestion for naming convention for you to consider - going forward - this is a new year - why couldn't you just incorporate the type name in the actual name? What was the draw back to doing that? 2016 GWC External Portfolio AVAIL 2016 Marketing Campaign Program AVAIL 2016 Project - PDM Video Due 6/1 Benetta Perry APS