Interesting topic about when to split or share tasks: In a previous system we had the concept of "Work Orders" (which are now Tasks). One benefit of our Work Orders was we could create a chain reaction of events. So a single work order could say "Design will hand off artwork to Production to prep art and provide it to Comps so they can produce mock-ups." This work order could have separate deadlines for each group, and caused a seamless and fast handoff between the two groups. We initially launched with separate tasks as suggested by this thread, but handoffs became more confused and slower. We've tried everyone on the same task, but allocation of time is confusing, handoff less clear, and reports became cluttered (if a particular user is "done with my part" it still stays on their Active Tasks report...). Managing deadlines and handoffs became alot of task micromanagement. So in short, both methods are slower than our old system; it's foisted alot onto the Project Managers rather than spreading-around the responsibility a bit. Granted, we're new to Workfront, which has turned our Project Manager's lives inside-out, buried them in notifications, and forced them to micro-manage when they didn't have to before. Some of the pain is just getting used to a new system and method; but as a SysAdmin it's also my job to mitigate their pain when possible. ;-) Any suggestions? Kevin Quosig
