Give it the task you gave up on


This week I went to a lunch at Stanford Law with Ethan Mollick and Kevin Roose.

If you haven't read them: Ethan Mollick is the Wharton professor behind Co-Intelligence, the book that showed readers how to use AI productively. His latest, Co-Existence: The Next Phase of AI, is about working well in the uneven zone where AI's abilities and ours overlap, the jagged frontier. Kevin Roose wrote Futureproof, and his new book, The AGI Chronicles, draws on more than 150 interviews to tell the story of the race among AI companies to build artificial general intelligence.

They didn't agree on everything but they did agree on this: we are not pushing AI far enough.

First, Kevin Roose's advice: give AI harder tasks. Most people, he said, are "using a Ferrari to go to the grocery store."

Second, Ethan Mollick's advice for the moment you hit a wall: escalate one level further. He said the gap between what AI can do and what people use it for is enormous.

It reminds me of decades ago when I was a new manager and went through new manager training. I learned about the Pygmalion Effect where people rise to high expectations.

The same (to an extent) is true with AI.

In the discussion, Kevin talked about how he used AI to help him file paperwork for a new company he was starting. He had AI write and check over his work.

Ethan challenged him. He said: AI can do a lot more than that.

Raise your expectations.

So do this:

  1. For a task you're using AI right now, make a note of where you're still doing *anything* as part of the task: whether it's the prep (uploading a file) or the next steps (copying it into an email).
  2. Instead of accepting it and going through the manual work, offload it to AI. Tell your LLM: I'm still doing XXXX. I need you to do this for me. What would it take? Walk me through the steps, simply.
  3. You might not be able to take all off your list, but you might edge out some of the manual work.
  4. Keep a note of that task. Revisit it in 6 months with a new LLM model release. Try again. You may be surprised by the results.

Apply to work with me here. I'm closing the doors on this option at the end of October. In November, I'll be looking to book 2027 clients.

Alex

AZAI Advisory

As an AI Coach, Advisor, and Agent Builder, I help organizations and business leaders harness the power of artificial intelligence to boost productivity and streamline operations. I enable organizations to navigate the transformative landscape of AI, educating teams, identifying operational and strategic opportunities with AI and creating a framework for safe and transparent use of data in the organization.

Read more from AZAI Advisory

Last week I was in a session with the operations lead at an investment fund. Her quarterly investor capacity calculation was due that day. She had saved a skill for it a while back. She had her doubts, and said so out loud. She fully expected it to fail. She ran it anyway. Midway through, the skill paused and asked her a question. Was a new investor exempt from the limit? It also picked up transfers that hadn't been booked into the capital activity tab yet. Something she would likely have...

This week I spent a session with a consulting firm. Their clients care a great deal about confidentiality, so the firm doesn't record or transcribe client meetings. Someone types notes live in Notion instead, in one long running page for each client. Then the typing starts again. After the meeting, a person re-enters the takeaways into Asana as tasks. Then a person writes them out a third time in a follow-up email. Same information, three rounds of typing. I'm tired just thinking about all...

Last week I was on a governance call with the general counsel of a hedge fund. The call was part of a firm kick off for the AI program. One of our first topics was: do we give people access to Claude Cowork or Claude Code? Here's how I reframed it. Cowork is an "ask for permission" environment. You pick the folders it can touch. Code is "ask for forgiveness." It was built for developers, and it starts with broad access to your machine. It related to a conversation a few days later around...