Delegate work that continues in the background
Give Edvin a bounded outcome, deadline, and definition of done so the assignment can continue after you leave Chat.
Updated Jul 13, 2026
What you will have
Outcome
A durable assignment with an accountable owner, clear completion criteria, background execution, and a verifiable deliverable.
Delegate an outcome, not an activity
Say what must be true when the work is finished. Include the intended deliverable, deadline, and people who should collaborate or review whenever you know them.
Confirm the boundary
Edvin saves the assignment with an objective, definition of done, next action, autonomy boundary, and approval requirements. The work cannot silently gain permissions beyond the workspace rules.
Let the same work continue
You can leave Chat while the work continues safely in the background. Progress, blockers, retries, deliverables, and completion checks remain attached to the same outcome.
Try it in chat
Use this as a starting point. Add your real goal, source material, and deadline.
“Edvin, own the competitor report before Friday. Compare our five closest competitors, cite the sources, and ask Lisa to review it.”
More ways to ask
“Own a launch-readiness review by Thursday and give me the evidence-backed risks.”
“Research these suppliers, create a comparison, and send the final version to Anna for review.”
“Turn these customer interviews into a decision memo before tomorrow afternoon.”
Things worth knowing
- Name the reviewer when review is part of done.
- Use one assignment for one bounded outcome.
- Open the related work when you need the full timeline or execution detail.
Still blocked?
Tell us where the guide stopped being useful.