Hi everyone,
this question is pretty simple yet pretty vague. I have noticed there is already a question (https://experienceleaguecommunities.adobe.com/t5/workfront-discussions/workfront-planning-what-are-y... ) connected to the topic but would like to ask it and have it in a single place.
Question is: what are some recommendations, and what are limitations that you have noticed while implementing Workfront Planning?
Any input is appreciated.
Best regards,
Ivan
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @IvanBebek-iX ,
Glad to see the discussion on planning is helping others. Here are some recommendations and limitations that I can think of having used planning for a while now -
Recommendations -
1. Get to a drawing board first. Planning is well suited to formulate a structured approach to the strategic planning phase of your marketing workflow. Listing down the elements of your strategic marketing initiatives is the first step.
2. Analyze the path to least resistance and introduce planning to strategic teams who plan your marketing activities before execution.
3. Write down what are you trying to get out of WF Planning - timeline views, many to many mapping, intake briefs, resource planning. Once you have that figured out its easier to implement
4. Differentiate between what is a deliverable and what is a taxonomy. This helps you track dates and other metadata on the deliverables and then pull all that information into taxonomies and see a connected view
Limitations -
1. Unless you have AEM assets integrated with WF, its not possible to attach documents to WF planning records.
2. WF planning request forms are not as evolved as the native custom forms in Workfront.
3. WF Planning is not at all connected to the reporting side in WF core. This is a huge limitation but can be solved by using fusion to carry over data from WF Planning to WF Core.
Hope this helps. I can think of many more smaller ones but this is what comes to mind when it comes to major recommendations and limitations.
Hi @IvanBebek-iX ,
Glad to see the discussion on planning is helping others. Here are some recommendations and limitations that I can think of having used planning for a while now -
Recommendations -
1. Get to a drawing board first. Planning is well suited to formulate a structured approach to the strategic planning phase of your marketing workflow. Listing down the elements of your strategic marketing initiatives is the first step.
2. Analyze the path to least resistance and introduce planning to strategic teams who plan your marketing activities before execution.
3. Write down what are you trying to get out of WF Planning - timeline views, many to many mapping, intake briefs, resource planning. Once you have that figured out its easier to implement
4. Differentiate between what is a deliverable and what is a taxonomy. This helps you track dates and other metadata on the deliverables and then pull all that information into taxonomies and see a connected view
Limitations -
1. Unless you have AEM assets integrated with WF, its not possible to attach documents to WF planning records.
2. WF planning request forms are not as evolved as the native custom forms in Workfront.
3. WF Planning is not at all connected to the reporting side in WF core. This is a huge limitation but can be solved by using fusion to carry over data from WF Planning to WF Core.
Hope this helps. I can think of many more smaller ones but this is what comes to mind when it comes to major recommendations and limitations.
Great points, @RowvillBh1, just a clarifying comment for you @IvanBebek-iX . You can use Canvas Dashboards to report on Planning data (or a mix of Planning & Workflow data in cases where they are connected). You do not need Fusion for this. Learn more about opting into the Canvas beta here if you're not already.
Thank you for clarifying. I agree, although WF planning data is not available in the native reporting functionality it is available in canvas dashboards. Haven't tested it out yet so maybe you don't have to use fusion after all @IvanBebek-iX
Views
Replies
Total Likes
Views
Likes
Replies
Views
Like
Replies
Views
Likes
Replies