Our Solution For Internal Tasks Shared In External Projects (While Hiding Our Process)

For forever we’ve been trying to solve for internal tasks that can be shared with external clients for approval (without them seeing how the sausage is made.)

With no real solution, we’ve operated with 2 separate asynchronous projects where task updates have to be made on both ends; internally and externally.

Use case: for us as an agency we want clients to see the final product for review rather than the behind the scenes. Whether it be contractors, internal edits, etc.

The answer for is Multihomed Subtasks.

Without going into the entire workflow, the basics of our approval process goes like this.

1: Internal Design Approval

  • One our internal product is approved, the final subtask is completed.

  1. A rule fires once all subtasks are complete. This moves the section AND adds a new subtask.

  1. This new subtask is already set to me multi-homed in the external project.

What this does:

  • Appears as parent task in external project (Without access to the actual parent task if you’re not in internal project)
  • Date, feedback, comments, etc added to subtask are visible and updated in the parent task on our internal board.
  • Everything can be done from the comfort of our own internal board :slight_smile:.

The final step is to manually upload the design into that new subtask (if anyone knows how to automate that, hit me up!)

I may be late to the multihomed subtask game but after searching for a solution like this for months, I figure this may help another team dealing with a similar problem.

4 Likes

Thanks for sharing, @Samuel_Maier .
This is a great method to use, indeed!

1 Like