Thanks for sharing the prompt below. I was looking through your other videos earlier today because our team is in the process of building out our folder hierarchy in Google Drive and matching our process to Clickup. Do you have any resources about how you have set up agency file structures? And how this connects with your Clickup Process?
Here is the prompt! Act as if you are a marketing professional and designing workflows + processes for your marketing agency. The first workflow you need to build is for writing a blog post for a customer. Can you please write out 20 different subtasks for a blog post process? These should only include the tasks needed and not the descriptions. The first subtask should focus on the strategy and the last subtask should be about publishing the blog. Please also include multiple rounds of revisions for the client to review the blog post. Here is an example of a workflow I created for a basic deliverable. Please use this as a guide. Deliverable Workflow Scope Create draft Internal review of draft Revisions of internal review Send draft to client Receive & share client revisions / follow up with client Round 1: Apply revisions from client Round 1: Internal review of revisions from client Round 1: Apply revisions from internal review Round 1: Send to client Round 1: Receive & share client revisions / follow up with client Round 2: Apply revisions from client Round 2: Internal review of revisions from client Round 2: Apply revisions from internal review Round 2: Send to client Round 2: Receive & share client revisions / follow up with client Final Round: Apply revisions from client Final Round: Internal review of revisions from client Final Round: Apply revisions from internal review Final Round: Send to client for Approval Final Round: Confirm client approval Publish
That is fine to do! The only downside would be when you need to update those instructions (especially if they live in a variety of locations from already deployed templates). Linking to a knowledge base document just makes it easier to update documentation.
🚀Let us help you double your agency's productivity + profits: www.zenpilot.com/working-with-zenpilot
🔥
Thanks for sharing the prompt below. I was looking through your other videos earlier today because our team is in the process of building out our folder hierarchy in Google Drive and matching our process to Clickup. Do you have any resources about how you have set up agency file structures? And how this connects with your Clickup Process?
This is an old video (th-cam.com/video/_yYA0RgVVWw/w-d-xo.html), but still relevant to how we recommend setting up google drive for agencies.
Hi there, can you share the link on how to link and assignee view? :)
Here's how to create an assignee view in ClickUp th-cam.com/video/IaApZZJU2N8/w-d-xo.htmlsi=MWa-kqVTLK1KvzNZ
Hello, I would like the prompt for creating tasks 🙏🏻
Here is the prompt!
Act as if you are a marketing professional and designing workflows + processes for your marketing agency.
The first workflow you need to build is for writing a blog post for a customer.
Can you please write out 20 different subtasks for a blog post process? These should only include the tasks needed and not the descriptions.
The first subtask should focus on the strategy and the last subtask should be about publishing the blog.
Please also include multiple rounds of revisions for the client to review the blog post.
Here is an example of a workflow I created for a basic deliverable. Please use this as a guide.
Deliverable Workflow
Scope
Create draft
Internal review of draft
Revisions of internal review
Send draft to client
Receive & share client revisions / follow up with client
Round 1: Apply revisions from client
Round 1: Internal review of revisions from client
Round 1: Apply revisions from internal review
Round 1: Send to client
Round 1: Receive & share client revisions / follow up with client
Round 2: Apply revisions from client
Round 2: Internal review of revisions from client
Round 2: Apply revisions from internal review
Round 2: Send to client
Round 2: Receive & share client revisions / follow up with client
Final Round: Apply revisions from client
Final Round: Internal review of revisions from client
Final Round: Apply revisions from internal review
Final Round: Send to client for Approval
Final Round: Confirm client approval
Publish
What do you think about adding the process's instructions/description/steps to the actual task instead of linking it to a knowledge base document?
That is fine to do! The only downside would be when you need to update those instructions (especially if they live in a variety of locations from already deployed templates). Linking to a knowledge base document just makes it easier to update documentation.
Client SOPs & Processes vs in-house ones. Where would you build the client processes, templates and SOPs?
You could build a separate Client knowledgebase at the everything level (or delivery) and share it publicly with clients.