Week 03 · lesson

Coordinate a Real Workflow

This week's assignment is a small coordination system. One message, one event, and one shared agenda must agree with each other.

Scenario — project planning meeting

Your fictional project team needs a 30-minute planning meeting for a student technology event. The team needs to decide roles, identify required files, and agree on the next deadline.

Build the workflow in the school-managed Google environment or a teacher-approved simulation.

Component A — the email draft

Write a concise professional invitation. It must include:

  • meaningful subject line;
  • meeting purpose;
  • requested action;
  • proposed date/time;
  • link to the agenda or clear note that it will be attached/linked;
  • closing.

Do not send the message to people outside the authorized classroom audience.

Component B — the agenda

Create a short Docs agenda containing:

  1. purpose;
  2. three discussion items;
  3. action-items section;
  4. owner/next-step space.

Give the intended team the minimum permission needed for the planned activity. If they need to propose changes but not rewrite directly, consider whether Commenter fits better than Editor.

Component C — the Calendar event

Create a 30-minute event with:

  • matching title/purpose;
  • matching date/time;
  • intended attendees or a safe simulated attendee record;
  • agenda link;
  • reasonable reminder if allowed.

Run the consistency test

Compare the three components side by side.

FieldEmailCalendarAgendaMatch?
purpose
date/time
intended audience
requested action
resource link

A mismatch is not a formatting problem. It can cause real coordination failure.

Run the access test

Verify the agenda from the intended role/context if the classroom environment permits it. Record the result. If the recipient cannot open it, fix the permission and retest.

Submit — Plan the Meeting

Your evidence packet includes:

  1. privacy-safe email draft;
  2. Calendar event evidence;
  3. agenda or agenda structure;
  4. consistency table;
  5. link-permission test;
  6. one revision after testing;
  7. one limitation.

Strong defense

Be prepared to answer:

  • Why did you choose this audience?
  • Why is the agenda permission appropriate?
  • Which component would fail if the date changed in only one place?
  • What does your access test prove, and what does it not prove?

The point is not “I used Gmail and Calendar.” The point is I coordinated a digital workflow and verified the connections.