The purpose of this thread is to continue the conversation from the Virtual User Group on the topic of Reporting to Executives on December 8, 2020.
Many thanks to everyone who came to our virtual meetup! Special thanks to @Christopher Jewell‚ from Nordstrom for sharing dashboards he created for his leadership team, as well as the delivery process he uses to share the reports with the executives directly.
As promised, attached is a PDF of the presentation, and you can watch the recording here.
Do you have any outstanding questions or ideas to share? Leave a comment below and we’ll keep the conversation going!
Thanks again to those who joined us. You can find the schedule for all upcoming User Groups on the Events page on Workfront One (one.workfront.com/events).
Topics help categorize Community content and increase your ability to discover relevant content.
Hi - here is thee info for the Document Report we talked about for reporting on "assets". Just to clarify, we tend to only proof assets so that is why this works for us.
Prompt: Project >> Portfolio ID
Hi - I also mentioned in my group a User Activity report I use for new deployments. Just so they can see who is doing stuff in the system. It is a Note report where the grouping is by Owner Name and then by Audit Type.
Thanks Kristin -- great session!
As discussed, for those interested in leveraging the Done Right At Workfront team's goodies to clean up their own environments...
Ah: and along the same lines as Anthony’s suggestion, I invite you to deploy The Scoop while you are at it, too.
I hope these are of use, and am interested to hear how you make out!
@Kristin Farwell‚ I really like the use of change orders for campaigns and this isn't something that we use yet at my company but would love to track! How exactly do you track it? Is it a request at the programme level that requires an approval?
Great question! I thought that was clever as well. Tagging @Christopher Jewell‚, @Anthony Imgrund‚ and @Doug Den Hoed‚ to get their thoughts for how they would recommend doing something like this.
Hi Ashley - I believe Christopher said they have one request queue for input, but then they move the issue to the project afterwards so that it is tied to the project.
I'm thinking of potentially using this idea as well. Although for me, the issue would be on the project to begin with, but that is because we are already using Workfront in a way that every project is a mini-request queue so my people are used to that.
Hi - that's correct.
We have a request queue that is for Change Requests. Second and Third drop down in request queue is Portfolio and Program - which allows us to report for these areas.
The Change Request form has options for reason including things like Strategy Shift, Scope Change, Missing Information, Inventory Update, etc. As well as if content is live or not.
It's made a big impact to report on this all up and by portfolio!
Hope that helped
Thanks for the tag, Kristin, and nice timing Ashley,
After the User Group call yesterday, this was one of the topics I then discussed in more detail with @Eileen Womelsdorf‚ and @Mark Hahn‚ during a queue setup best practices session we'd previously scheduled, and suggest:
I'm sure there are others with great suggestions, and encourage folks to submit them here, too.