On a schedule · Operations lead
Go into Monday knowing what moved.
Delivery tasks are in Asana, while blockers appear in Slack. The lead needs a Monday agenda with owners.
Asana
Slack
Google DocsRole: Operations lead at a 20-person consultancyTrigger: Sunday evening before the team meeting
Discuss this workflowDelivery commitments · Example review
Completed
Client discovery notes are ready for review.
Blocked
Delivery dates depend on the client’s response.
Decision
Choose who owns the revised project plan.
THE WORK
How the workflow works
- 01Asana
Read selected Asana projects and tasks completed since the previous review.
- 02Slack
Check the permitted team channel for recorded blockers and mark stale status updates.
- 03Google Docs
Prepare a Docs-ready progress, blocker and decision brief in the Mainframe workspace.
THE RESULT
What you get
Time backReduces the pre-meeting chase for updates already recorded in project tools.
GETTING STARTED
What you need to set up
Connect the sources used in this example, then confirm the scope and schedule.
- Asana
- Slack
- Google Docs
Connections and available actions depend on your account permissions and setup.
HUMAN CHECK
Before anything goes out
The operations lead confirms status with owners and assigns next actions.
Illustrative workflow and fictional output, not a customer testimonial or measured result. Actual results depend on source quality and setup.
Explore another use case
On a schedule
Start the day with the context that matters.
Start the day with selected meetings, messages and follow-ups.
Explore this workflow
When needed
Bring the numbers back to the customer story.
Compare sales and payment records with customer activity.
Explore this workflow
When needed
Find the messages that need your attention.
Find urgent threads and prepare replies for a person to check.
Explore this workflow