What's happening The teammate finished a task and the answer is wrong — a number is off, a fact is dated, a recommendation doesn't fit the situation, or a generated piece of work doesn't match what the chairman actually asked for.
Why it happens
- The brief left the most important detail implied instead of explicit, and the teammate filled the gap with a reasonable-but-wrong default.
- The teammate worked from general knowledge when the chairman expected them to use a specific source (a doc, a connector, recent data).
- The chairman and the teammate were using the same word for two different things.
What to do
- Reply in the same task thread and tell the teammate exactly what's wrong, in the chairman's own words: "The number for Q3 should be X, not Y, because [reason]."
- Point at the source the teammate should have used: "Use the Stripe data, not what you remember from last quarter."
- Ask for a redo with the correction: "Redo with this in mind." The teammate retries inside the same thread, with the chairman's correction kept as context.
- If the same kind of error keeps happening across tasks, tell Astra — she can adjust how the team approaches that kind of work going forward.
- If none of this works, message Astra and she'll loop in support.