Use Workfront Blueprints to Optimize Your Work Management Environment!

Blueprint Name: Post-implementation: New use case rollout
Blueprint Type: Project Template
Preview Release Date: September 29, 2022
Target Production Release Date: Week of October 3, 2022

The purpose of this blueprint is to assist customers to expand their implementation of Adobe Workfront beyond the initial implementation scope. The project template contained in this blueprint assumes it is an expansion of use cases within an implemented user group. If growing use cases outside of a previously implemented group, we suggest engaging Workfront professional services or a partner consultant instead of relying solely on this template.

While this template was designed for newer customers that just completed their first implementation, it is expected this blueprint will also be useful to more established implementations as well.

Blueprint Name: System Administrator Maintenance Dashboard
Blueprint Type: Dashboard
Target Preview Release Date: September 29, 2022
Target Production Release Date: Week of October 3, 2022

The purpose of this blueprint is to help system administrators stay on top of their Workfront maintenance activities. Using this dashboard provides a digest of all the items a typical administrator will need to review to keep Workfront tidy and clean. End users appreciate this because unnecessary configuration causes confusion and loss of data integrity; not to mention gums up your processes.

Blueprint Name: Workfront Usage Dashboard
Blueprint Type: Dashboard
Target Preview Release Date: September 29, 2022
Target Production Release Date: Week of October 3, 2022

The purpose of this blueprint is to help system administrators identify healthy usage patterns of key Workfront objects. By reviewing this dashboard regularly, you will be able to detect spikes or troughs in usage of Workfront. Additionally, you will be able to assess whether users are leveraging the functionality you intend them to use and measure the adoption of your processes as represented in the key activities you identify. You may find you need to modify the reports on this dashboard to fit the specific key activities for your organization.

How can I go about suggesting a new Blueprint template?

Hey @j_hobbs Thanks for your question. If you visit the Blueprints landing page, you should see a "Feedback" button on the top left. You can use the feedback page to submit content requests, which will place your suggestion into a Blueprints backlog for an internal team to further investigate. Please see the attached image for details and let me know if you run into any issues with blueprint content submissions. 

Would there ever be a blueprint for process integration - not the process creation itself, but that would align with the process visual that is shown in the Adobe Workfront PPM?

@megsvt we are always looking for additional ideas of processes to include as a blueprint. I am not familiar with the visual you are referring to in your post. Can you send a link to the visual for this process?

@mattmi3 

The link is https://experienceleague.adobe.com/docs/workfront/using/manage-work/portfolio-management/portfolio-overview-in-adobe-workfront/portfolio-managament-overview.html 

@mattmi3 -- 

I should be more specific with this idea... I am envisioning that each of these six steps would be a blueprint of their own that could easily be customized by System Admin to fit the need of the organization.

We are currently trying to revamp our marketing process within our organization and this is basically the process that we are working from. As the System

Admin and also the Traffic Manager, it is incredibly challenging for me to try and manage projects along with build the new process in Workfront. 

@megsvt Thank you for sharing this image. I really like this idea. It is consistent with what the long term vision of blueprints has been from the beginning.

Earlier this month we release the first Dashboard blueprints. With this blueprint type coming online, it starts to fill in the Project Review, Execution, and Postmortem nodes in the diagram. We definitely need to provide you with more reporting and dashboard related content to consider those nodes covered.

In the coming months, we are planning to also release blueprints content for custom forms and request queues. This will start to cover off on the Project Request node of the diagram.

I'm curious about your comment "I am envisioning that each of these six steps would be a blueprint of their own." I agree with you that we could package up blueprints that way. Would it also be useful to have a blueprint that addresses all steps for a single request type? For example, we start with a digital asset creation as a work process, and we create a blueprint that contains the form and queue, the routing rules and teams needed, the template and roles, and the supporting reports to usher the work through the full process. Would this be more or less helpful than separate blueprints; one with all the creative request queues and forms, one with all of the creative templates and roles, one with all of the supporting reports for a creative workflow, etc.?
Or maybe we provide blueprints that contain both approaches? What are your thoughts?