Skip to content

Review and improve results

A useful answer fits your goal and can be checked against the information it uses. Take a moment to review it before putting it to use.

Four questions for every result

  1. Does it match the task? Check the audience, scope, language and requested format.
  2. Are the claims correct? Compare names, numbers, dates and decisions with your materials.
  3. What is missing? Look for open points, missing sources and unclear ownership.
  4. What actually happened? Distinguish a proposal from a completed action.

Work with sources

Open cited passages when they matter for an important claim. Check that the source actually supports the claim and is recent enough.

If no source is given, ask what the answer is based on. A source provided afterwards still needs checking.

Which claims in your answer come directly from my notes?
Mark assumptions and information for which you have no supporting basis.

Request specific improvements

Describe what should change. You can build on the existing conversation.

You notice… Possible feedback
The answer is too long “Shorten it to five bullet points. Keep all decisions.”
A date has been added “That date isn't in the notes. Mark it as open.”
The audience is wrong “Write for new team members and explain abbreviations.”
Tasks are hard to compare “Show tasks, owners and deadlines in a table.”
Uncertainty isn't visible “Separate supported details, assumptions and open questions.”

Understand proposals, approvals and execution

What you see What it tells you
A text draft A proposal is available. Review it before use.
An approval request A decision from you is needed. Read the scope and effects.
A message reporting a completed step Check which step the message refers to.
A confirmation from a connected service Use it to check the result in that service.
An unclear or interrupted workflow First establish which steps have already taken place.

Check first when the outcome is unclear

If an action may already have been performed in another system, check its state there before requesting it again. This helps avoid duplicate entries, for example.

Something missing or looking different in your workspace? Here's how to get support.