Skip to main content
There is nothing to build. Email it, message it in Google Chat, mention it in Slack or invite it to a meeting, and tell it what you need in plain words. It replies where you asked, works in its own apps, and comes back when it’s done or needs a decision. Anyone at your company can ask it for help. The people it works for set its priorities.

​
What makes a good first job

Pick something real and small, where you’ll know at a glance whether it went well.
“Research Acme before my call on Thursday and put a brief in a Doc.” Or: “Build me a list of 15 companies like our best customers, in a Sheet, with where you found each one.”
“Draft the launch announcement for next week from this brief, and share it with me.”
“Here’s a question a customer asked. What should I tell them?” Or: “Write a help article on this, from our website.”
“Make me a Sheet of our vendors from this document, with a link to each one’s pricing.”
“Put together a job post and an interview plan for this role. Leave the salary as a question for me.”
Connect GitHub on its Apps tab, then: “Look into this issue and open a pull request.”
“Find 30 minutes with Dana next week and send the invite.”

​
What happens next

  1. It says it’s on it. For anything that takes more than a moment, you get a short reply.
  2. It does the work. Documents go in its Drive and are shared with you. Every step goes in its activity log.
  3. It asks if it must. It checks with you before spending money, contacting someone new outside your company, or doing anything that can’t be undone.
  4. It tells you it’s done, with links to what it made and what it couldn’t confirm.
Correct it in the thread, as you would a new hire. It remembers how you like things done.
It can make mistakes, so check what matters before relying on it. A good teammate will tell you what it could not confirm: read that part.