💛 Top of Mind
| ||||||||||
Hey all, Today's one of my favorite days of the year. One of the best nap days of the year. One of the best sporting events of the year. Happy Sunday of the Masters. Today and for the next few weeks we will have some guest contributors to share their thoughts on AI, how they feel about it, what they're seeing, and more. Any one can contribute. If you want to write a piece, let me know! I also end the email talking about tomorrow' All Hands. It's a different one! With that, let’s dive into it. WHAT'S TOP OF MIND1) Be the ConductorBy Blake Madden Many writers and creators seem to be afraid of using AI in their writing claiming it's a tainted product or out of pride - "don't worry, I'll never use AI to write." I sympathize with this attitude out of pride for my craft, but also acknowledge it's a pretty shortsighted viewpoint. 2) Scope with AmbiguityBy Triet Le One thing I keep coming back to as we deepen AI adoption at Workweek is that the biggest differentiator between people who are succeeding with AI and those who aren't isn't technical skill, it's a state of mind. Specifically, the ability to scope with ambiguity. The AI playbook is evolving faster than any of us can keep up with. New tools, new capabilities, new failure modes and every week brings something that shifts what's possible. And here's the thing: every company is different. Every team within the same company is different. There is no single playbook that maps cleanly onto our workflows, our culture, our specific problems. Anyone trying to copy-paste a framework from somewhere else is going to hit a wall quickly. What I've observed is that the people who are thriving are the ones who can hold a clear goal while staying fluid about the path to get there. They're willing to experiment, willing to be wrong, willing to learn in motion, without needing all the answers up front. Patrick is a good example. He took on the challenge of incorporating our design system into Claude Code. The goal being to enable more teammates to work on bigger features safely, without breaking things. When he started, there was no existing pattern to follow. Nobody had a template for this. What Patrick did was embrace the uncertainty, experiment openly, and ground everything in a simple principle: treat this like a platform with real users. That framing gave him a north star when everything else felt unclear. The AI path was ambiguous. The goal was not. That combination — tolerance for ambiguity paired with clarity of purpose — is what I'm starting to think of as the core competency for anyone doing serious AI work right now. It's not a skill you can install. It's a posture you have to practice. 3) OKRs tomorrowTomorrow we go over Q2 OKRs. For some of you, this is your first time in one of these meetings. You'll see a continuation of what we laid out in January. More tooling so more creators can join our communities. More organic growth. More connection between members. Better ways to show our advertisers what working with us actually means. But none of that is what I want you to remember walking in. What I want you to remember is what Blake talked about. Storytelling. Insights. Perspective. That's not a Q2 initiative. That's the whole thing. It's what we were built on and it's what every platform feature, every analytics dashboard, every ad product exists to protect and amplify. We exist to help people with real experience share that experience consistently and proudly. The rest is infrastructure. The heart is still the story. Q2 is going to be a big one. A lot of the foundational work we've been grinding on is about to start compounding. You're going to see it. It's going to feel different. See you tomorrow. QUESTION OF THE WEEKWhat's a stretch goal you have in Q2? Thanks for giving it a read. Make it a great one. Adam | ||||||||||
|
If you believe this has been sent to you in error, please safely unsubscribe.
