Asana structure for my digital agency


I’m currently on an Asana trial and would like to know how to structure of digital agency’s workflow:

  • Client (system some clients have multiple systems which can be separated)
  • Project/Request under client
  • Definition
  • Development
  • Test/review (approve go to regression test- fail go back to Development)
  • CI/CD release to QA
  • Regression test QA (approve go to client approval- fail go back to Development)
  • Client Approval (approve go to production- fail go back to Development)
  • Production Release schedule
  • Production Release Implementation Track code changes for the Project/Request Time related to each item under the Project/Request



Answer: I’d split out your service types (web development, app development etc) as Teams and then add new projects for clients within those teams using reusable templates. You could choose to either allow clients to access the whole project or you could run two project spaces in Asana per project, one for staff only and one for staff + clients. The staff + clients could include some onboarding instructions for clients and include areas where progress demos are shown. For labeling, I’d look at using ABC Project (staff), ABC Project (client).

About the author

Rich Peterson

I've spent the last 10 years planning, mapping & reimagining the processes of hundreds of SMBs. Whether the goal is more money, more time, more clarity or more customer smiles, my insightful process is worth every minute for my successful clients.
Disclaimer: I use affiliate links on my website and only recommend what I use, have used or have vetted in the best interest of my readers. I may earn a commission if you click on an affiliate link, but it won’t cost you extra.