Adobe Employee

Webinar | System Admin Essentials: What IS Workfront Governance? (Mar 30, 2022)

Forum|Forum|3 years ago
March 14, 2022
13 replies
15147 views

Governance might sound like a "leadership problem," but it’s a key concept every Workfront System Administrator must address. The good news is, you can start small, maybe with just a glossary of terms or a small working group, and evolve your practices over time.

In this on-demand webinar, originally broadcast on March 30, 2022, Tyler Holt (@tylerholt-adobe), a Consultant in Workfront’s Success Services organization, and Luke Ramlow (@lukera), Application Analyst at Mayo Clinic College of Medicine, covered:

What governance in Workfront actually means
Examples of different types of governance
Ways governance can evolve and mature over time
Mayo Clinic College of Medicine’s multi-year journey to full scale governance (spoiler alert, it didn’t happen overnight!)

You can view the recording here and a copy of the slides is attached. Have questions for our speakers? Tag them in a comment below!

Webinar---Admin-Essentials---Governance---Mar-30,-2022.pdf

Workfront

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Show previous replies

L

LukeRa

4) What is the best way to do a clean up?

Answer: I really like the kick-starter provided by Workfront for doing a clean up. found here:

https://one.workfront.com/s/article/Workfront-Cleanup-Dashboard

At Mayo, I review this once per quarter.

Heather_Kulbacki

Community Advisor

I also really like the dashboard this kick-start creates for a quarterly review. I've also added some extra reports to that dashboard that are specific to our use.

L

LukeRa

5) As part of your governance did you establish a best practice on naming conventions for projects, issues, etc?

Answer: We did not establish a naming convention for projects, tasks, or issues. We did however, establish naming conventions for things like custom fields, custom forms, templates, Portfolios/Programs. This was around/after the intermediate governance step I noted in my presentation. So we've actually been working recently to make sure we have a consistent identifier for the objects I mentioned. What we've done to this point is use a prefix or suffix of the work unit acronym. (Ex. if the work unit is "Education Technology Center" the acronym is ETC and a custom form name might be "ETC - Request Form")

Heather_Kulbacki

Community Advisor

We recently implemented another group into our instance where we were very conscious of adding an acronym to all those objects as well - learning as we go with governance :)

But for the custom fields, I put the acronym in the field name and left it off the field label. It felt like this would leave the field more "readable" for end-users.

L

LukeRa

You bring up a great point, Heather. When we use an acronym for group identification of an object we try as best we can to not make it customer facing (not always possible though). Your example of putting the acronym in the custom field name, but not the custom field label is the same practice we follow so it doesn't have an impact on the end user.

Heather_Kulbacki

Community Advisor

@Luke Ramlow‚ are you able to share your implementation onboarding task list - or the highlights of it? Or does the screenshot in the slide deck show the majority of the tasks?

L

LukeRa

Here is an export of the template with the full list of tasks.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded