Chat course 03 — Turn discussion into accountable work

A conversation is complete when its result and remaining responsibility are clear, not when an unread badge disappears. Some requests end with a simple answer. Others need a work record with an owner, date and completion condition. This chapter explains that handoff and shows how to close a review without pretending that a message automatically created a task.

In this chapter

• Separate review from revision and delivery
• Decide whether a Board task is needed
• Set fields according to the agreement
• Reopen and compare the saved work
• Close the loop with an observable result
• Practise an end-to-end review

Separate review from revision and delivery

Consider the welcome-checklist plan. A colleague agrees to review whether preparation steps are missing. They identify that nobody owns arranging the materials. The review produced a useful finding. It did not assign the colleague to arrange materials or make the event ready.

Write the next action as an output: “Revise the plan with an agreed materials owner and return the same version for review.” Identify the author, reviewer and operational owner separately. One person can hold several roles, but each responsibility still needs to be clear.

A date is not agreement. If the reviewer can respond only at 17:00 UTC, do not preserve a 16:00 deadline as accepted. Keep a timed promise explicit in the description or accompanying record when the task's date field does not carry time and timezone.

Decide whether a Board task is needed

Use a task when the work needs accountable follow-through beyond the discussion: a named output, responsible person, completion condition and date. A quick factual answer may not need a new task. Search for existing relevant work first so the conversation does not produce duplicates.

Open Board in the correct workroom and select the approved Board. The manual route is separate from Chat; do not claim an automatic conversation-to-task conversion or native message link unless the actual supported feature has been verified.

If a genuinely new task is authorised, use the available Create action to open New Task and confirm the Board field. Enter a specific Task Title such as “Resolve preparation ownership in welcome plan version 2.” In Description, include the exact request, material version, review finding, required output and acceptance condition. Preserve enough conversation context for the person to continue without copying unnecessary private discussion.

Set fields according to the agreement

Use Assign Members for the verified eligible person who has the responsibility under your team's process. A fictional role name is not a selectable account. A saved assignment is also not proof that the person accepted the work or can open its supporting file.

Set Due Date from the agreed plan. Where the control selects a calendar day and confirms with OK, it does not by itself establish a time-of-day reminder. Preserve a relevant time and timezone explicitly in the description and use the team's supported scheduling process if needed.

Keep Status aligned with actual work. Backlog fits a planned action not yet started. Done requires the task's actual completion condition, not merely that a Chat request was sent. Priority expresses urgency, not acceptance or progress.

Review the Board, title, full description, assignee, date and state, then use Create Task once. For an existing task, use its supported update action rather than creating another item with the same name.

Reopen and compare the saved work

Find the task independently through Board. A generic blank New Task form after reload does not prove the saved item vanished. Use the Board's normal list or search, confirm the full title and read the retained values.

Compare the assignee and due date in the task and the appropriate Table row. If an empty picker conflicts with a saved list value, establish the same record identity and re-read before changing anything. Do not repeatedly assign or save until two views happen to look alike.

Check the full description and material reference. A task titled “Review plan” is not useful if it points to version 1 after the discussion moved to version 2. A filename or link still needs the right body and audience. Receiving readability is separate from your own successful preview.

Close the loop with an observable result

Before reporting completion, compare the result directly with the request. If the task is to revise the plan, inspect the revised plan. If it is to obtain review, read the meaningful response about that same version. If it is to check a room or deliver a file, obtain that separate result; a Done badge is not the evidence itself.

A useful closure says what changed, which version was checked, what the reviewer concluded and what remains. For example: “Version 2 now names the materials owner. The reviewer checked that version and found the preparation responsibilities clear. Physical room readiness is still a separate check.” Use such wording only when the stated results exist.

Do not delete conversation history or alter attention state to make the discussion appear finished. Preserve the source and agreed result so another authorised person can understand the decision later. If the outcome remains blocked, say exactly which action, access or response is missing.

Practise an end-to-end review

Use this complete fictional plan: objective, practise welcoming visitors; agenda, four-minute briefing, twelve-minute role play and four-minute debrief; materials, a room map and eight blank registration sheets. The room-open check has no owner. A reviewer offers only to review the plan and cannot finish before 17:00 UTC.

Prepare a request that includes the full plan and asks for a readiness finding. Then write two distinct next actions: obtain review of the correct version, and establish an owner for the room-open check. Do not assign both to the reviewer merely because they replied.

Suppose a saved task is marked Done, names the reviewer for both actions and has only a calendar date, but neither review nor room check exists. The correct decision is to preserve the record, obtain authority for the necessary correction and reconcile its scope, ownership, timing and state. Do not create a duplicate task or report the room ready.

Your expected course result is a clear chain from intended audience to complete request, retained outgoing message, meaningful response, accountable work and checked outcome. Each stage can be useful while a later stage remains open. Report those boundaries plainly rather than treating conversation activity as completed work.