What are some Workfront Planning training topics I should consider for my end users? | Community
Skip to main content
Level 3
February 26, 2026
Solved

What are some Workfront Planning training topics I should consider for my end users?

  • February 26, 2026
  • 2 replies
  • 49 views

We are about to embark on our Workfront Planning journey and just wanted to think about topics I would need to cover in training for the end user?  They will not be the ones creating workspaces and stuff like that so just wondering what all the training could entail on their end.

Currently, I have the following topics:

  1. What is Workfront Planning?
  2. Create and managing view tables
  3. Importing information from a spreadsheet

 

 

 

Best answer by MelanieM1

 

Found some helpful information via AI, so posting here in case it helps someone else come up with their training plan!

Training Topic

Notes

What is Workfront Planning?

What Workfront Planning is (vs. Projects/Tasks)

How it connects to intake, forecasting, and visibility

What problem this solves for the organization

What changes for them (and what doesn't)

TIP: Emphasize "This helps us plan smarter, not create more work

10 minutes

Workfront Planning Terminology

 

Where to Submit a Plan

How to access the correct workspace
How to find the correct record type
When to click "New Plan"
Required vs. optional field

Common confusion to prevent:
Submitting in the wrong workspace
Saving drafters vs. submitting
Not completing required fields

How to Fill Out a Plan the Right Way

What level of detail is expected
What makes a "good" description
How to define scope clearly
Selecting correct timelines
Attaching supporting documents

Include:
Bad Plan Example
Strong Plan Example
Planning Submission Checklist
Planning Do's and Don'ts

Understanding Statuses & What Happens Next

What each status means (Draft, Submitted, Approved, etc.)
What happens after submission
Who reviews it
How they'll be notified of changes

Editing or Updating a Submitted Plan

Can they edit after submission?
How to revise scope?
How to cancel or withdraw?
What to do if dates change?

Basic Searching & Viewing Their Plans

Filter by "My Submitted Plans"
Use basic filters
Sort by status or timeline
Avoid duplicates

Common Mistakes to Avoid

Submitting vague descriptions
Choosing unrealistic deadlines
Forgetting attachments
Creating duplicates
Selecting wrong initiative/category

Create and manage table views

 

Importing information from a spreadsheet

 

Governance & Expectations

Timeline submission expectations (quarterly planning deadlines)
Who approves
How prioritization works
SLAs (if applicable)

 

2 replies

KellieGardner
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 26, 2026

The scale team just did an event on this. ​@CynthiaBoon  - did you guys cover any use cases in your event? I wasn’t able to attend and I haven’t seen the post event follow up yet. 

MelanieM1Author
Level 3
February 26, 2026

Hi Kellie!  I was on the last Planning call around the trial. I’ll need to re-watch it to make sure I didn’t miss anything.  I believe it was mostly around infrastructure setup, which the end user won’t need to know that information.  So, I’m looking for key topics a user should know who will be inputting their plans.  I see some more Planning sessions were just announced.  I’ll add my question there too.  Thanks!    

MelanieM1AuthorAccepted solution
Level 3
February 26, 2026

 

Found some helpful information via AI, so posting here in case it helps someone else come up with their training plan!

Training Topic

Notes

What is Workfront Planning?

What Workfront Planning is (vs. Projects/Tasks)

How it connects to intake, forecasting, and visibility

What problem this solves for the organization

What changes for them (and what doesn't)

TIP: Emphasize "This helps us plan smarter, not create more work

10 minutes

Workfront Planning Terminology

 

Where to Submit a Plan

How to access the correct workspace
How to find the correct record type
When to click "New Plan"
Required vs. optional field

Common confusion to prevent:
Submitting in the wrong workspace
Saving drafters vs. submitting
Not completing required fields

How to Fill Out a Plan the Right Way

What level of detail is expected
What makes a "good" description
How to define scope clearly
Selecting correct timelines
Attaching supporting documents

Include:
Bad Plan Example
Strong Plan Example
Planning Submission Checklist
Planning Do's and Don'ts

Understanding Statuses & What Happens Next

What each status means (Draft, Submitted, Approved, etc.)
What happens after submission
Who reviews it
How they'll be notified of changes

Editing or Updating a Submitted Plan

Can they edit after submission?
How to revise scope?
How to cancel or withdraw?
What to do if dates change?

Basic Searching & Viewing Their Plans

Filter by "My Submitted Plans"
Use basic filters
Sort by status or timeline
Avoid duplicates

Common Mistakes to Avoid

Submitting vague descriptions
Choosing unrealistic deadlines
Forgetting attachments
Creating duplicates
Selecting wrong initiative/category

Create and manage table views

 

Importing information from a spreadsheet

 

Governance & Expectations

Timeline submission expectations (quarterly planning deadlines)
Who approves
How prioritization works
SLAs (if applicable)

 

CynthiaBoon
Adobe Employee
Adobe Employee
February 27, 2026

This is amazing!  I’m not able to share the event recording from the trial globally, so I’m glad you were on that session.  I figured I would create summary of the advice shared on “how to prep your users for Workfront Planning” which I’ve included below.  Your list is way better, and I will definitely be borrowing it.
 

1. Set the right expectation upfront
Position Planning as the space for early-stage ideas and campaign visibility, not a replacement for Workfront Workflow. Workflow remains the system for task execution and project management. Planning supports the “before execution” phase.

2. Clarify when to use Planning vs. Workflow
A helpful rule of thumb:

  • If it’s not ready to be a project yet → it belongs in Planning.

  • If tasks need assignments and timelines → it belongs in Workflow.

This reduces hesitation around using the request queue too early and gives teams a structured place for ideation.

3. Start with one clear use case
Rather than introducing it as a new tool to explore, anchor it to something tangible (e.g., Q3 campaign planning, rebrand coordination, editorial calendar management). Clear purpose drives adoption.

4. Emphasize what’s in it for them
Planning helps eliminate scattered spreadsheets, reduces duplicate work, and gives teams better visibility into what others are planning, without impacting existing projects.

5. Reinforce that it’s safe and flexible
Planning is separate from Workflow, so users can collaborate and shape ideas without disrupting active execution work.

One of your notes on the first post gave me something to think about in terms of end-user training, and that was around the spreadsheet to import.  That might be the place to start, having them think about what records they would want to track, so that they can prep their spreadsheets.  Just in case, I wanted to share the link to the post from Vazgen’s session last year.  He shared a sample spreadsheet that we attached to the post, so that might be something for the end-user?  

Thanks again for sharing your list.  That might be a great idea for a Scale event this year - “How to train your users on Workfront Planning.” 😀