|
There's a specific kind of anxiety that comes with being in AI right now. It's not the fear of being left behind. It's the accumulation of "I should really learn that"... the Substack you flagged, the YouTube video someone texted you, the X thread with 200 likes you saved and never opened. For a while, my "learning system" was a graveyard of browser tabs and starred emails. I knew things were there. I just couldn't find them. And the more they piled up, the less I actually learned because opening that pile felt like work before the work. So I built a queue. Here's what's in it right now: how to set up Claude correctly, Claude Cowork, a 20-minute YouTube video on Code and Paperclip, a 9-minute one on Claude and iMessage, Perplexity's new computer mode, two Substack pieces on delegators and agentic tools, and the Lenny newsletter on Openclaw. I'm familiar with all of these tools; I use several of them daily. But knowing how something works and knowing how to teach it are two different skills. I'm not learning these for me. I'm learning them so I can figure out the simplest, most compelling way to bring a room of skeptical executives along with me. I take insights from founders, engineers and practitioners. When I have 12 free minutes between calls, I'm not scrolling for something to read. I'm filtering my database by "Video" and picking the 9-minute one. When I'm at my desk with focus time, I go deeper. The queue shapes what I learn when, not just whether. The system has three rules:
That cap is the uncomfortable part. It's also the most useful. It forces prioritization at the moment of capture, when your interest is highest and your judgment is clearest. Inbox zero for learning isn't about reading everything. It's about never losing track of what you decided was worth reading and being honest when that decision has expired. My queue right now tells me something: I'm deep in Claude tools and agentic infrastructure. That's a reflection of where my client work is heading. The queue has become a mirror. What does yours look like? Alex P.S. I built this in Notion, but a simple spreadsheet works just as well. |
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.
I saw the future yesterday. In a blurry screenshot I pulled from my laptop while sitting across the room with my phone. Here's what happened. Claude Desktop (the app that launched in January with Code and Cowork) quietly added something new: Dispatch. It's a feature that lets your phone talk to your desktop. Not just send messages. Actually operate your computer. I paired my phone with my desktop through a QR code in the app's left-hand menu, tapped Dispatch, and typed: "Get the last...
I’ve been on a lot of calls lately with private equity firms trying to figure out AI. Not “should we use AI” calls. That ship has sailed. These are the harder conversations: where do we actually start, what’s worth paying for, and how do we get our teams to use this stuff consistently? Three calls in this week. Three very different firms. And yet the same five themes kept surfacing. I think they apply well beyond PE, to enterprise and to non-profits. Build vs. Buy is the wrong question (until...
Last week, a senior leader at a large investment firm opened our Zoom call with what usually sounds like a win: "We've got high usage across the firm." Everyone has access. People are familiar with the tools. A few internal workflows are already connected. Great. I love talking with people for whom AI is really embedded and working. I quickly determined this call was a "trading notes" kind of call. It wasn't a request for help from me. And then, about twenty minutes in, he said shared their...