Reviews via Workflow, Task or Something Else?

Hello all,

Looking to see if Wrike has a best practice, or if anyone else has a recommendation, for accounting for various rounds of review for tasks when planning project timelines. We can only think of two ways to do it - either workflow steps or sub-tasks - but hoping there might be a third way. Here are the pros and cons we're debating.

Workflows: We currently have reviews listed as steps in our workflow, e.g. Content Review, SME Review, Requester Review, Customer Review, etc.

  • Pros: Reduces the amount of sub-tasks that need to be created and managed. On the final deliverable task, we just change the workflow step. When Content Review is complete, we move it to SME Review, and so on.
  • Cons: Confusion around the definition of "Finish Date." For instance, if a task has a finish date of Friday, is that when the primary assignee is supposed to upload it for review, or are they supposed to do that on Wednesday so there's time for review? Do we create an arbitrary standard - e.g. "always move to review five days before the due date to allow for review time" - to avoid tasks going overdue?

Sub-Tasks: We've seen other companies create separate tasks for each review. So, for us, we'd potentially have 2-4 additional sub-tasks for every single deliverable requiring review.

  • Pros: Avoids confusion and missed steps by getting even more granular with actions required. Helps take some thinking out of work for assignees because they don't need to mentally account for how much time reviews will require. Helps plan waterfall-type projects more realistically by accounting for all necessary review time when planning tasks start and end dates.
  • Cons: That's a ton more tasks we have to create with every single project!

Has anyone tried both, or a third way, and found a method they prefer? Or are we thinking about anything the wrong way?


2 comentarios
Spot On Innovative Approach Stellar Advice

Lee Procida We've used both methods you mention above, but have settled on workflow steps with Approvals.  You may already be using workflow approvals, and if so you can ignore the rest of this 😄.  For example, when artwork review is needed, the status is set to "Submitted for Approval" which automatically launches the approval process to the assigned approver.  If the approver approves or rejects the artwork, it automatically transitions to the appropriate workflow status based on their decision.  This covers the responsibility (task owner) and accountability (approver) aspects for a given task.  

We also use automation steps to notify the correct team members once a task has reached a particular status.  This give a seamless transition from, for example, approval of artwork to integration of that artwork into our product specification which is managed in a separate task by a separate team member.

Hope this information is helpful!

Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice

Thanks Trevor Tollefsbol! I'm not familiar with that functionality - is that an add-on or a feature only available with a certain plan tier?

That's definitely a helpful automation. The trouble we're having is just trying to schedule work appropriately to account for review times while also making use of task start/end dates for our widgets and dependencies. Do you plan out your projects in a Gantt chart, or just generally based on meeting a certain deadline? If so, how do you account for review time needed for each task?

Acciones de comentarios Permalink

Folllowing List for Post: Reviews via Workflow, Task or Something Else?
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post