DAILY EXECUTION
Turn the project plan into work people can do today
Connect preparation, delivery and follow-up through explicit tasks, assignees and dates. Use the day’s work views without losing the customer project behind the action.
A meeting is not the whole customer workflow
A customer appointment may need preparation beforehand and a follow-up afterward. Those actions deserve their own owners and dates rather than remaining implied by a calendar entry. Tsumira project tasks provide that practical structure. The project retains the wider delivery context while personal work views help each colleague identify what they are responsible for now.
Describe the work around the appointment
Create separate tasks for the preparation, the deliverable and any follow-up that needs a clear outcome. Give each task a relevant project, description, assignee and date. A customer booking or calendar event provides useful context; the necessary tasks are created explicitly for the engagement. The team deliberately captures the actions required for this engagement and checks the resulting plan.
- Preparation and follow-up as explicit tasks
- Assignees and dates for actual actions
- Customer project context retained
Give each colleague a practical daily view
Personal work distinguishes tasks due today, overdue, already in progress and due in the coming days. The upcoming lane covers tomorrow through the following six days, keeping it distinct from today. These lanes are based on open assigned work and the relevant project visibility, not a global dump of every employee’s tasks. Counts and bounded previews make the view useful as an entrance to the wider work collection.
- Today, overdue, in-progress and upcoming lanes
- Open work assigned to the current colleague
- Counts with bounded previews of the work
Keep the handover explicit
When work is ready for someone else, update the task state and the description or related conversation. Completing a preparation task does not mean an appointment happened; a finished customer session does not prove the follow-up was done. Separate tasks make those transitions visible. If effort or billing is required, use the connected Time and finance workflows instead of treating a daily checkmark as an issued invoice.
- Clear outcome at each handover
- Task status separate from appointment occurrence
- Time and billing keep their own review steps
A concrete workflow
Identify the customer outcome
Start with the project and decide what preparation and follow-up the customer engagement actually needs.
Capture the necessary actions
Create dated tasks with clear assignees instead of leaving the work implicit in the appointment title.
Work from the personal day
Use the assigned-work lanes to start with today’s responsibilities and inspect overdue items.
Close the next handover
Update the result and create or clarify the next required action while the context is still fresh.
An illustrative working example
Example: a customer consultation and its follow-up
A consultant creates a preparation task for reading the customer’s documents and a follow-up task for sending a reviewed recommendation. Both belong to the customer project, with dates around the appointment. On the day, the preparation appears among the consultant’s assigned work. After the conversation, the recommendation remains its own open responsibility until it is actually prepared and reviewed. Booking the consultation did not silently complete either task.
Questions about this topic
Does every booking automatically create a project plan?
No such universal automation should be assumed. Use bookings as context and explicitly create or instantiate the required project tasks.
Is the upcoming lane the same as today?
No. Personal work separates today from the next six days beginning tomorrow, as well as from overdue work.
Does a completed appointment close its follow-up task?
No. An appointment and a task describe different outcomes. Keep the follow-up open until its own intended result is complete.
Can I capture a follow-up before choosing its project?
Supported quick task creation can use the inbox project. Assign the correct project context when the delivery relationship is clear.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Calendar
Workflow concept: Plan preparation and follow-up tasks around a checked customer appointment.
Outlook
Workflow concept: Clarify the actual deadline before putting follow-up work into the day.
Asana
Workflow concept: Review personal task responsibility separately from the project’s overall schedule.