Everyday AI · Module 6

Separate actions from decisions and suggestions

Suggested time: 6 minutes.

An action is a specific piece of work that has been agreed or explicitly required in the notes. It should describe something someone can do. Its owner or deadline may still be missing.

A decision records a choice, such as which room layout to use. A decision can explain an action, but it does not automatically create an extra task.

A suggestion is a possible idea that has not been accepted as work. Preserve it separately if useful. Do not silently promote it into a commitment.

Worked snapshot W6

Use these notes for the lesson examples:

• W6.1: Agreed task W01: Draft the welcome script. Owner: Mira. Due: 3 October 2030. Dependency: none recorded. Status: Done.
• W6.2: Agreed task W02: Review the handout. Owner: Lee. Due: 4 October 2030. Dependency: handout draft received. Status: In progress.
• W6.3: Required task W03: Check the room access information. Owner field left blank. Due: 5 October 2030. Dependency: venue reply. Status field left blank.
• W6.4: Copy of W6.1: Agreed task W01: Draft the welcome script. Owner: Mira. Due: 3 October 2030. Dependency: none recorded. Status: Done.
• W6.5: Decision: Use one sign-in desk.
• W6.6: Suggestion: We could invite a second speaker. No action was agreed.

W6.1, W6.2 and W6.3 describe work to record. W6.3 remains an action even though the owner and status are missing. W6.5 records a choice. W6.6 is an idea without approval.

Weak extraction:

“Lee will invite a second speaker by 5 October.”

This invents an assignment, a deadline and agreement to act. Neither Lee’s presence elsewhere nor another task’s due date supplies that authority.

Better extraction:

“Suggestion: invite a second speaker; no action agreed. [W6.6]”

Quick pause: Does the lack of an owner make W6.3 a suggestion? What wording establishes whether it is a task?