If you can visualize a solution and have seen the path to its creation in your mind, then you’ve already created it. Everything between now and then is simply acting on your project plan embedded in your memory. I imagined the WFPro system about eight years ago. Today it exists and it was created without a platform. Today I’m visualizing some new things, and now I have the systems to facilitate real creation amidst the digital work revolution. Check the program over here.
As a customer of Workfront, it’s important to know your Strategic Customer Success Manager as they should be a key resource when you need direction as you develop your strategy and execute your plans. They should know what you’re doing in your instance. My situation is somewhat unique, but it still requires the building of a relationship and an understanding of the use cases. With a new SCSM assigned, I look forward to sharing my plans for WFPro Home as indicated in this email I just drafted to my contact:
When you finally figure out that one of our most basic human needs is issue resolution, and that with the right tools and basic communication skills, you can solve any problem.
There is still significant emphasis being placed on communicating in platforms other than Workfront, such as Slack or in Microsoft Teams. I understand that communication will always occur outside of Workfront (phone calls, emails, instant messages, Slack, Microsoft Teams, drive-by cubings). However, when communication relates to work, it should immediately move into Workfront and proceed from there. If work hasn’t been defined for notes to be added to, that’s your cue to define the work work immediately.
The ability to easily transform communications into work is essential. If you choose to communicate about work outside of Workfront when you use Workfront to do your work, prepare to fail regularly. Unless there’s an integration pulling communications into the appropriate projects, tasks and issues from these other communication tools instantaneously, other methods of communication will be immediately out of context and disconnected from your operations. I believe that’s heading backwards. I can imagine automating this would be a nightmare, which is why integrations should be avoided until Workfront has been exhausted as the solution.
My goal is for 100% of my work-related communications to be handled within Workfront so that Outlook can be what it’s really good at, a cold email collector and a password reset tool. If you’re being forced to use these other communication tools, I encourage you to move your notes into Workfront as soon as you can and pull people into the conversation in context ASAP so you set the precedent and train them, even though they don’t know it’s happening.
Don’t underestimate what can be done in every Workfront instance with some elbow grease and #TheWFProWay. If you can keep other tools in their place, you’ll have a better shot at conquering the biggest challenge I think we face as humans, the ability to effectively communicate on our projects.
Arinze is a partner we’re working with to deploy an attestation solution in Workfront. Today he started our weekly meeting by saying “This is the meeting I look forward to the most because it’s one where we innovate, break boundaries, push the limits and create something magical.” I had to write it down because it’s perfect language for our job descriptions as Workfront professionals and because it makes me proud of what I do.
Learn how to control widths like a pro in your Workfront views and reports in this WFPro University text mode training session.
Believe it or not, Workfront’s native view/report editor writes most of the code for you. The only text mode lines you really need to know for advanced view/report development are as follows:
- displayname=What’s the label in the header of the column.
- description= When a user hovers over the column header, text that pops up.
- shortview= When the report is in a multi-column dashboard layout, show the column?
- sharecol= Used to share two columns in the view. Click for training on on shared columns.
- usewidths= Tells the view to use widths. Click for training on using widths.
- width= Sets the width of the column in the view. Click for training using widths.
- value= What’s the value to be rendered?
- valueformat= What format should we render the value in?
- valuefield= What field to retrieve data from.
- valueexpression= Render whatever you wish.
- querysort=What field to use in the sort.
- sortType=Ascending or Descending?
- sortOrder=1,2,3, etc. First, second, third, etc.
When code is written by the user interface, switch to “text mode” and master configuring each of these attributes. If you ignore the rest of the noise, you’ll be ahead in the game.
Check out this nine minute YouTube video where Narayan of WFPro explains how he deploys solutions quickly at Truist using #TheWFProWay and the WFPro Package Manifest.
Don’t back yourself into an unsustainable corner by deploying solutions to users that are architected incorrectly. Believe it or not, there is often only one “right” way of doing things in Workfront. Most of the variability comes when solutions are architected the “wrong” way. And when this happens, we as owners of the products we deliver, back ourselves into corners with “systems”‘ that become overwhelming, unsustainable, not configurable, garbage in reporting, and ultimately failed projects. Don’t work so hard just to fail. Get with WFPro for solutions to succeed with minimal effort.
Do we speak the same language? I don’t mean English. I mean WFPro. Do you communicate on issues or tasks within projects and almost always in context? But more importantly, are all of your communications true and from the heart? Who do you love the most? Would you be okay if they read your journal notes with context? Would they like what they see? Would it represent who you are? When you’re ready to communicate #TheWFProWay, then we’ll be speaking the same language.