How would you approach implementing a PM system for an agency with small, generalist teams where roles aren't clearly defined? What strategies would you recommend to create a simple, non-overwhelming system that still provides the necessary visibility for leadership and operational efficiency?
I'd still follow this framework: ruclips.net/video/Sdf4xeDxUKU/видео.html Even if roles aren't defined, you still always have general roles. For example, you'll always have a copywriter, proofer, designer, account manager, etc. These can be used to assign work out to the team.
Great video! I have a Q: Where would you draw the line for automations? There is so much possible with make for example. But all the assign stuff, seetting up a new costum field option for every client to have the views, to assign specific people etc. still needs to be done.
Focus on the basics first. The automations can come second. Don't start working on automations and getting overly complex until you're comfortable with what you've got built. Most teams try to get overly complex first and don't focus on the basics.
@@ZenPilot Thanks you for the answer! But once the basics are set, what would be the thinks to automate? Would appreciate a short list of the stuff you automate. Thank you very much for your effort! Love your videos!
I'm grouping by a custom field called client at that part (so not by folder). This custom field can be set by automation at each folder. Every time a task get's added to a folder, it'll automatically get the client custom field applied to it.
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
🚀Let us help you double your agency's productivity + profits: www.zenpilot.com/working-with-zenpilot
Crazy amount of value here
Thank you!
How would you approach implementing a PM system for an agency with small, generalist teams where roles aren't clearly defined? What strategies would you recommend to create a simple, non-overwhelming system that still provides the necessary visibility for leadership and operational efficiency?
I'd still follow this framework: ruclips.net/video/Sdf4xeDxUKU/видео.html
Even if roles aren't defined, you still always have general roles. For example, you'll always have a copywriter, proofer, designer, account manager, etc. These can be used to assign work out to the team.
Great video! I have a Q: Where would you draw the line for automations? There is so much possible with make for example. But all the assign stuff, seetting up a new costum field option for every client to have the views, to assign specific people etc. still needs to be done.
Focus on the basics first. The automations can come second. Don't start working on automations and getting overly complex until you're comfortable with what you've got built.
Most teams try to get overly complex first and don't focus on the basics.
@@ZenPilot Thanks you for the answer! But once the basics are set, what would be the thinks to automate? Would appreciate a short list of the stuff you automate. Thank you very much for your effort! Love your videos!
Thanks for the great content! In the minute 08:23, how did manage to include the Group view by folder? I only have the option to group by list.
I'm grouping by a custom field called client at that part (so not by folder). This custom field can be set by automation at each folder. Every time a task get's added to a folder, it'll automatically get the client custom field applied to it.
13:00 how can we build this screen?
This training will have more detail on how to build out that workload view: ruclips.net/video/x0hiGo3CvaU/видео.html