Using the API was a big win for us in this type of scenario (any workflow really). If you have a developer that can code the API here are the steps we do to accomplish similar workflows that you've described: Create a Request (Issue) custom form to capture any fields you need for your process. Create Request Project to display the Request form (and expose it to whomever you wish – by person, team, group, or company) and do your routing etc. Create a Landing Project for the Request to go. This is done so your permissions etc. aren't done in the Request Project. Once the request is submitted the API has a job that is trigger by the looking for the custom form itself (we can use other criteria as well to trigger it). The API converts the Request to a Project using a Template that has tasks to all the different teams/groups/companies We also have code in the Template that interacts with the API to delete certain Tasks that aren't required for this request. So the resulting project will only have the tasks that are needed. People work their tasks, when all are complete, WF marks the project complete and marks the original Request (Issue) Closed. All done. We also put these processes in specific "Programs" to easily find and report on, etc. For example, we use this for New Hires. A new hire may require a new computer, phone, access to certain applications, a cell phone, a badge, etc. And these are all done by different people in different teams. If the person filling out the New Hire Request doesn't check the box for a cell phone, the API removes the Cell Phone Task for us. We have several workflows that work similarly. And what everyone has said is true. If your process is ill-defined, it will take time to get it right. The aforementioned New Hire process was a bear to work with because so many teams had to do something and no one knew the whole process. So it took me a long time to get it perfect. And it still evolves. I do recommend getting a resource so you can use the API. It has saved a ton of time and really helped with our adoption. It can be impressive which makes people want to jump on board and request more workflows (which is good news/bad news right �� ) And I don't know if anyone said this already, but if you want adoption, REQUIRE EVERYONE that will use Workfront to take the Workfront Training (and you can track who actually took it). You can tell them which classes are required and which are optional, but I highly recommend this. We did the following: Learned and configured with the WF Tech for 5 weeks Required all our staff that would use Workfront to take the WF training (gives them basic WF skills and knowledge) Provided our own classroom training to train people on the new processes themselves (gives them process skills and specific knowledge on how it should be used for your instance) Then walked the floor for 2 weeks after deployment helping answer questions and solving issues. This was a big win because people weren't asking questions until we stopped by (they just suffered in silence). Hope this helps. I know it's a lot. Feel free to reach out if I can help. Vic Alejandro, PMP, CSM | IT | Sr. IT Project Manager Denver Water | t: (303-628-7262) | c: (303-319-6473) "http://www.denverwater.org/">
http://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT ------Original Message------ Thanks everyone for the quick reply!!!!  All helpful insight!!!  One follow up question.  Obviously our overall objective is to streamline process, gain efficiencies, and provide visibility into the work of various departments.  We all work very silo'd, and I'm sure we're reinventing the wheel alot, and not working cross departmentally very efficiently.  As we start to talk to other departments- I'm really interested in identifying the points of intersection between departments. Can any of you site an example where workfront helped streamline a task/function between departments and how did you accomplish that? For example: My department- creative services, works on all the event collateral.  For a print invitation that we are designing- we need a data list of names to send to the mail house to mail the invites.  The data list comes from the operations team. Right now- that is a separate ask to operations from the event team.  But I'm imagining there will be a smarter, more efficient way to tie this all together in workfront.  I know alot of this will be on us to rethink workflows- but I'm just looking for examples to help me get outside of my silo a little bit.   tks Karen Karen Rutz Harvard Alumni Affairs and Development
