The feedback loop

The team will find errors before you do. Make it easy to tell you. A single line in the assistant's instructions: "If an answer looks wrong, tell [name] or post in [channel]." A pinned message in the team channel saying the same. And a visible response when someone does: fix it, tell them it is fixed, thank them.

Feedback is also how the assistant grows. New questions arrive that are not in version one. Add them to a list. Once a quarter, run the Module 01 sort on the new list and build the next version. The assistant becomes the team's memory, and the team maintains it because they can see it responding to them.

In practice. A team channel got a pinned message: "Ask the assistant first; if it is wrong, reply here and I will fix it within a day." In the first month there were nine replies. Six were fixes. Three were new questions that became documents. By month three there was one reply, and it was a thank you.

At your desk. Add the feedback line to the instructions and pin the message in your team channel. Start the new-questions list. Set a quarterly reminder to sort and build the next version.

Write it down.

• Where people report errors:
• First error reported:
• Quarterly review date: