For my digital training workshop project, I optimized my four-week schedule using Notion as my main planning and tracking tool.

I am working with a fictional team of three members, with six working hours available per day, Monday through Friday. I distributed responsibilities among project coordination, content preparation, and logistics and communication.

1. Planning and task organization

I organized the activities in Notion using a Kanban board with three statuses: To Do, In Progress and Completed. I adapted the Monday.com task structure by including task owners, priorities, deadlines, estimated durations and dependencies.

I divided complex activities into manageable subtasks and paid special attention to high-risk tasks.

2. Objectives and milestones

I divided the project into four weeks, establishing an objective and a milestone for each week:

• Week 1: Project planning and objective definition.

• Week 2: Training materials preparation and approval.

• Week 3: Technical testing and participant confirmation.

• Week 4: Workshop delivery and final evaluation.

3. Schedule tracking and critical path

I established daily 10-minute check-ins and weekly 30-minute meetings. I also introduced four weekly sprints to keep the team aligned.

I identified the project's critical path, from defining the content to delivering the workshop, and communicated the dependent tasks and their owners to all team members.

To avoid unnecessary complexity, I focused on progress that affects project objectives and deadlines rather than spending too much time on minor details.

4. Communication and risk management

I used WhatsApp as a direct communication channel for blockers, risks and urgent changes; Zoom for coordination meetings; and Notion to centralize project information.

I prepared a risk mitigation plan covering the main potential problems: content delays, technical issues, low participant confirmation and incomplete materials.

5. Change tracking

I added a Project Change Log in Notion to document any schedule modifications, including the date, affected task, reason for the change and agreed action.

This allows me to maintain a record of decisions and understand how changes affect the overall project schedule.

6. Collaboration and Agile methodologies

I applied the Kanban Swarming approach to encourage team collaboration. If a priority task is delayed, team members can work together to resolve the blocker instead of focusing exclusively on their individual assignments.

I also introduced weekly sprints with shared objectives while maintaining the four-week overall project schedule as a reference.

Final reflection

This optimization allows me to distinguish between the overall project schedule and daily tracking, identify risks in advance and improve team coordination.

I believe that combining structured planning with Agile methodologies makes it easier to adapt to changes while keeping the project objectives and deadlines in focus.