Event Follow-up | Reflections on the "Journey to Adoption" at the SF Skills Exchange

[BeckyBarus]

A heartfelt thank you to everyone who joined me for my Wild West session, "The Journey to Adoption," at the San Francisco Skills Exchange last week! It was an incredible experience, and I'm thrilled to continue the conversation here.

I invite everyone in our community to share your own experiences and insights on getting your organization to adopt Workfront. Did your pre-Workfront days feel like the Wild West, with multiple project management tools and scattered processes? Have you faced resistance from teams when transitioning from their old tools to Workfront? I'd love to hear your stories and learn from your experiences.

For those who missed the session, I've attached my presentation. Here are the key takeaways:

1. Executive Support is Essential: Having the backing of your leadership team is crucial for a successful adoption.
2. The Tool is Just the Start: While Workfront is powerful, the real change comes from the users' willingness to adapt and embrace new processes.
3. Adopt a Learn, Iterate, and Adapt Mentality: Teams may not get it perfect the first time, and that's okay. Start with one process and build from there.

Please use the comments section below to share your thoughts, ask questions, or offer insights. Let's continue this journey together and make the most of Workfront in our organizations!

Looking forward to hearing from you all.

Becky Barus 

[NicholeVargas]

If you weren't able to attend Becky's session at the in-person Skill Exchange last week - you're in luck! She delivered a similar presentation in late October with the Customer Success team, so HERE is a link to the on-demand recording. Some highlights from the session are:

• A Center of Excellence is crucial for housing documentation and boosting credibility. 
  • Can serve as a dedicated space for additional training materials (ex: simple steps for requestors) vs. large trainings
  • Link comms/newsletter content back to a centralized hub. Want example of end-user comms, check out the Customer Comms Cookbook
• Focus on simplicity and standardization
  • How many layout templates are actually needed? 
  • Consider renaming fields (ex: Planned Completion Date) in views and lists to align with different team terminology vs creating new fields 
• Align on metrics for consistency – are all teams reporting on the same data? 
  • Capture usage data to understand what features users are/aren’t taking advantage of. No need to start from scratch, download the Usage Dashboard in the Blueprints library!  
• Limit access whenever possible! Governance guardrails are key.
  • Becky is the sole System Admin, but relies on members of the Tiger Team for understanding processes from start to finish
  • Set standards around naming conventions, project templates, universal custom forms, and more