Most work that goes wrong was asked for badly. ORIGIN has one way to ask for something, and it works equally well on a colleague and on Claude.

The thinking behind a good ask
An ask is our word for a request. Before you write one, answer five questions. If you cannot answer one, you are not ready to ask.
Lead with the ask. Your reasoning, your evidence and your references are real and useful: they go in a separate note, linked at the bottom.
You are about to ask a colleague to review a competitor. You know what you need, but not by when. What do you do?
If you cannot answer one of the five, you are not ready to ask.
Title, brief, steps, due, done when.
A working example
One ask, in full
One trap
A step must be something that can be finished. "Keep the client updated from now on" can never be ticked. It is a way of working, so it belongs in the brief.
Rewrite the last request you sent to a colleague in this shape. Notice which of the five questions you had not answered. That gap is usually why the work came back wrong.
You are writing the steps of an ask. Which of these is a step?
It starts with a verb, and it can be finished.
If you cannot fill one in, you are not ready to ask.
Before you move on
Three questions before you move on. Type your answer, send it, then check it.
Your answers stay on this device.1What are the five parts of a good ask?
The answerTitle, brief, steps, due, done when.
2How long is the brief, and how many steps are there?
The answerThree sentences at most, and three to seven steps, each starting with a verb.
3Where do your reasoning and your references go?
The answerIn a separate note, linked at the bottom.
A clear ask gets done.
Know what finished looks like before you start. That is owning the outcome. Next: cybersecurity, the last section of this act.