|
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 the typing. A lot of investment firms assume that no recorder means no automation. I'd like to offer another way to see it. My suggestion was a small change to how the notes are stored: one page per meeting, titled with the date and client. Here's why that helps. A scheduled task needs something it can find and read. A page that grows for months holds many meetings with no clear edges. A page per meeting has edges, and "today's meetings" becomes the pages created today. From there, a scheduled task runs late each afternoon. It reads that day's meeting pages, pushes the action items into Asana, and drafts a follow-up email for each client with their action items and the team's. A person reviews every draft before anything goes out. One of the partners volunteered to build it once and share it with the whole team. Here's how to try it:
I am taking one new client in 2026. Apply to work with me here. When the spot fills, I'll be looking to 2027. Can't believe the new year is right around the corner!! Alex |
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.
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...
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...
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...