How to delegate well
Ta treść nie jest jeszcze dostępna w Twoim języku.
John works better with outcomes than with click-by-click scripts. A strong ask tells him what done looks like, where to look, what he may send, and how to report back.
You still talk on Slack or Telegram. Connections and skills expand what he can reach; they do not replace a clear brief.
A reusable pattern
Section titled “A reusable pattern”Include these four pieces:
- Outcome - the result you want, not the menu path. “List deals that went quiet this week” beats “open the CRM, click Pipeline, export.”
- Sources - which apps, threads, files, or mailboxes to use. Name the connection (“our HubSpot”, “unread Gmail”) when you have more than one.
- Approval boundary - draft only, or send/update after you OK. Default: John asks before risky writes.
- Format and deadline - bullets, a table, a message ready to paste, “by 10:00 in my timezone.”
Optional fifth: who it is for (you, a client, the exec team) so tone matches.
Example asks
Section titled “Example asks”Bounded triage
Summarize unread mail from the last day. List anything that needs a reply today. Draft replies for the top three and wait for my OK before sending.
Research with a stop line
Check the CRM and last week’s Slack thread on Acme. Give me a one-page status: what moved, what is blocked, and one recommended next step. Do not email the client.
Recurring shape (when you already have a thread)
Every Friday in this thread: pipeline snapshot, quiet deals, and meetings I owe notes on. Draft only unless I say send.
More full recipes: Recipes.
What to say about risk
Section titled “What to say about risk”- “Wait for my OK before sending” is the default for anything that leaves your company.
- “Always allow” in Slack is for routine writes you already trust. You can still deny a specific card. Approvals.
- Do not ask John to use your personal bank card. An optional wallet is on the roadmap and is not live.
What slows John down
Section titled “What slows John down”- Vague goals (“look at my week”) with no source and no output shape.
- Mixing several unrelated jobs in one message.
- Assuming he can see a tool you have not connected. Check Connections.
- Assuming a vertical playbook exists because a marketing page named an industry. Check Skills.
Languages
Section titled “Languages”You can write to John in any language on Slack or Telegram. He follows the conversation language. Product UI language is a separate setting. Settings.
When work is long
Section titled “When work is long”Ordinary work pauses after 25 AI steps and returns the best result so far. Ask John to continue to start another bounded turn. This is a spend guardrail, not a failure. See Work Credits and Usage.
In Slack, tell him to stop in any language to halt a running task. Progress updates replace themselves in the thread.