I Don't Know Where to Start: Prioritization with Workfront

We have talked about the top ten pain points creative teams face and took a deep dive into the creative brief and request process. But what happens once a request becomes a project? Another major pain point creative teams let us know about is prioritization. Only 10% of respondents said they have no idea what their own priorities are daily. This was good news. However, within organizations, there is a lack of clarity at a project level, resulting in issues with expectations and deadlines. With 24% of teams working with external agencies and clients, prioritization becomes difficult.

 Other complaints that were mentioned along these lines are:

• Inconsistent direction from various stakeholders
• Too many stakeholders in unclear roles
• Lack of a clear point of contact at a partner which also leads to duplication of work
• Delays due to missed deadlines or other issues
• Conflicting creative direction based on look and feel from different teams

 One respondent commented that:
“when multiple agencies are involved, it can cause issues with who own which part of the process. It needs to be clear is who responsible for what when this is the case.”

With a quick internet search, you can find many articles sharing prioritization methods and many software solutions seek to help with prioritization. But, when teams are not all in the same tool or the same company, competing internal priorities or changing stakeholders can have an impact.

 Workfront can help with both project and team prioritization. If your request intake process is happening in Workfront and projects are being created via Workfront, the next logical step is to manage the tasks of resources through Workfront. Prioritizing tasks so that team members know what to work on and in what order can lead to greater efficiency and will reduce frustration. How does Workfront do this? Below, see the demo from 3|SHARE's CTO Paul Legan.

3|SHARE is here to help you with your creative process workflow. Learn more about Workfront or how you can add other Adobe Experience Cloud products into your ecosystem. Contact us.

Video Transcript

Paul Legan: [00:00:35] My name is Paul Legan, Chief Technology Officer at 3|SHARE, and I'd like to talk a little bit about work prioritization within Adobe Workfront. So typically when a user logs into Workfront, they will see a list of tasks. These can be related to projects. These can be related to steps within an approval process.

And they can ultimately be work that they need to get delivered for a particular assigned group of functionality. So I'll talk about tasks for a second. So each task itself, when you click in, you see things like the plan completion, date, the status prioritization, all of the history. And most importantly, perhaps the project.

So if I click on this project, I'm given a little bit more context about what this task is about. And once I get to this project area, I see all of the tasks, how they're related all of their statuses. And I also see things like the project details itself so I can talk through or to the stakeholders if I have questions and [00:01:35] ultimately understand more about why I am actually being asked to do this particular task.

So those are tasks. Now another part of the Workfront work list is approvals. So when a particular project is, has a status of a particular type. So in this case, I have set a trigger that a new project that has been requested as its status requires approval. And this approval process can be one of many different steps in this case.

It's just one, but it can include as many different people and people can be named people or they can be project related people like the project owner or the portfolio owner. So that's really helpful so that you don't have to assign individual people to each project. So if I were to come over here and approve this particular project, I will see how upon refresh this task has now gone away.

So that [00:02:35] project workflow has now been assigned to the next person, if that step exists. And if not, It will automatically trigger a series events, uh, not withstanding things like project status completion, new tasks created, et cetera, all in, in the name of getting more work done.