Menu

Posts tagged “ai”

How I work with AI

I recently read Rich Holmes’s post Personal Agent Systems Explained - How 5 Leaders Run their work through AI Agents (well, the part before the paywall) and found it really interesting. I decided to ask Claude to make a diagram of my own system as well, and then I wrote some content around it, and now I’m sharing it with you in case it’s helpful (or you want to yell at me about how I’m doing it wrong).

How I Work is a mini site that goes through the whole thing, but here’s the overview diagram:

Diagram of my AI agent system

The main elements:

  • Me: nothing is fully autonomous. I don’t think that should ever change.
  • Context: what the agent knows about me and my work, loaded only when a task needs it.
  • Workflows: saved commands for repeated work.
  • Live data: agents check the real systems instead of guessing.
  • Review: a second model checks anything before it even gets to me for editing.
  • Lessons: corrections go back into the context, so agents don’t make the same mistake twice.

I’m sure lots of people have more sophisticated workflows and one of my reasons for posting this is that I want to hear about them!

The one thing that I don’t see a lot of out there, and that I want to point to specifically here, is how important it is for the system to be able to learn. The most important command I have is /session-end (generic version available here), which writes a handoff note and updates context and skill files. That way the system keeps learning and the agent never (well, rarely…) makes the same mistake twice.

An update from Amazon engineering leadership on the role of the developer in the age of AI

There’s not an awful lot new or surprising in this memo from Amazon leadership about the role of AI in software engineering, but it’s still interesting to see companies starting to codify the things that remain incredibly important for engineers (and product people!) to focus on. From real and continued first hand experience:

As a technical or organizational leader, part of your job is making sure that your team or organization is using AI to the best effect to improve delivery for customers and your business. That requires deeply understanding these technologies yourself, working with them hands-on rather than relying on what you hear, and understanding how others are using them. Sufficient understanding means you have used these tools on your production work, can describe a task where they helped and a task where they did not, and can explain that judgement to your team.

To the importance of staying close to customer needs:

We have also found that [Software Development Engineers] and [Software Development Managers] who are closer to their products and businesses are able to take the most advantage of AI and agentic software development. As Amazon has grown, we’ve seen some of our ICs and SDMs become less connected to their customers and business. We want to reverse this trend. We recommend that ICs of all levels find ways to become deeply connected to your customers, and your team or org’s product direction. As always, the scope and depth of this ownership will increase as you become more senior.

How To Write With An LLM

Don’t let an LLM pick your words. Be careful not to let it trick you into thinking your first draft is better than it is. Then outsource all the most tedious work to the model. Your voice stays intact, but your work is faster, better, and less painful.

—Thomas & Erin Ptacek, How To Write With An LLM

Slack Content Design in the Age of AI

I’m a words person from a UX background so I am deeply invested in how products communicate with users. This is a great article about how we should use AI to help with our content and not make it worse…

As AI takes on more of the work of generating language, the question is no longer whether machines can sound human enough. It’s whether those conversations earn trust, accurately set expectations, and reflect our human values. That gap is exactly where content design lives. With our deep expertise in applied linguistics, humanities, language systems, and behavioral economics, we are equipped to be the connective tissue between technical capability and the human experience.

I think the reduction of strong content people in organizations because “AI can just do the writing” is something we’ll regret even sooner than reducing software developers. Words, (I’m so sorry for the cliché), matter.

Why AI hasn’t replaced software engineers, and won’t

The research in this post is interesting, especially as it relates to where the software development bottlenecks are in the age of AI:

If writing code isn’t the bottleneck, what is? The task-breakdown surveys point at things like meetings or debugging. This just leads to more questions: what are developers doing in those meetings and why can’t it be done by AI? Won’t debugging get automated as capabilities improve? To understand the real bottlenecks, we have to get qualitative, and dig into software engineers’ own understanding of what it is they do that resists automation. When we did this analysis, it revealed three things as the real bottlenecks (1) deciding and specifying what to build, (2) verifying and being accountable for what is delivered, and (3) the deep human understanding — of the codebase, the business, and the environment — required to carry out both of these.

How PM Work Is Changing in the AI Era

This article is a very good representation of how I see the PM landscape right now as well:

After a brief period where PMs were expected to become engineers themselves, the engineering team is moving back to owning most implementation mechanics. PM increasingly owns what should happen, why, the principles governing a product’s behavior, and how success should be evaluated. There are debates around communicating that vision between PRD’s vs. prototypes, but that debate hides the fact that the eval is becoming the core product artifact. The initial strategy doc or PRD is re-emerging as an artifact for agents as well as humans to understand what we intended to build. The eval defines whether we did or not.

Why Is Everyone In Tech So Sad?

Aaron Horwath implements AI for a living, and in a good essay for Noema he asks why so many knowledge workers are losing faith in their careers:

In coffee shops and in the low-lit corners of bars, professionals are sharing dreams of “disappearing” or “living on a farm somewhere” or “going off the grid.” These aren’t fantastical daydreams; they are visions of escape shared in a tone that betrays an underlying existential angst, a fundamental doubt about work and careerism inspired by a seemingly increasingly common experience: waking up one morning at an existential precipice, struck with a sudden sense that knowledge work is, and perhaps always has been, pointless.

It’s definitely worth reading the whole thing if you find yourself in the same situation. He mentions two concepts that feel super relevant right now:

  • Workism is Derek Thompson’s term for the way work has become the place we look for the meaning that earlier generations got from religion.
  • The spectacle comes from the French theorist Guy Debord’s 1967 book The Society of the Spectacle. It’s his word for modern life lived secondhand, like watching other people travel on YouTube.

Horwath sees workism as a small version of the spectacle, where work only has to look important. He argues that as AI agents do more and more of the work, it gets even harder to keep pretending it matters.

His conclusion:

But perhaps the most powerful action of all is simply to maintain an awareness (and remind others) that Workism is a spectacle. For most employees, we owe it to each other to remind one another that this work is not, in the grand scheme of things, all that important. It is illusory. No one has ever died over a spreadsheet. The world does not wait with bated breath for product launches. A marketing campaign will not change the world. Almost no one will remember all the work we do. But they might remember the types of people we were, the relationships we had and how we treated the people we worked with.

I really need that last sentence to be true, because I’ve pretty much banked my whole career on it.

How AI is changing product management (and what to ask your team about it)

Next week I’m running a session with our product and engineering leadership on how AI is changing the product management role. To prepare, I read the people who’ve shaped how product managers think about the job (Marty Cagan, Melissa Perri, Teresa Torres, Rich Mironov, John Cutler, the Reforge team), alongside product leaders doing the job right now at Anthropic, OpenAI, Netflix, Instagram, and Whatnot. Then I went through the 2025-2026 survey and study data I could find.

Most of what I found applies well beyond our team, so I’m sharing the condensed version here, along with the questions we’ll be discussing in case they’re useful for yours.

Where the sources agree

  1. Building got cheap. Deciding what to build got expensive. Mike Krieger, Anthropic’s chief product officer, says 90-95% of the Claude Code product’s own code is now written by Claude Code, and that their bottleneck moved to deciding what to build. (Self-reported, but the rest of the sources point the same direction.) Writing documents by hand is losing its value, because AI now produces a serviceable draft of any of them on demand: product requirements documents (PRDs), backlogs, research summaries, status updates. So the hard parts of being a PM are becoming more important: choosing which problems to work on, understanding customers, and defining what “good” means.

  2. Speed alone is not converting to outcomes. In an April-May 2026 survey of 309 senior product leaders, nearly nine in ten had adopted AI coding assistants. But just over a third said AI strengthened how their org operates. DORA, Google’s long-running research program on software delivery, found in 2025 that teams using AI ship faster but their releases get less stable. GitClear, which analyzes code quality across millions of code changes, found duplicated code up 81% since 2023. Refactoring, the cleanup work that keeps a codebase maintainable, dropped sharply over the same period. Marty Cagan calls this the AI productivity paradox: shipping faster without better discovery (the work of figuring out what’s worth building) gets you to the wrong place sooner.

  3. Teams are getting smaller and more senior, with wider scope per person. Netflix, Instagram, and Whatnot all describe versions of this. Instagram is moving toward pods of 4-6 engineers plus one “product staff” generalist covering product management, design, data, and research. Nobody agrees on what the smaller team should look like, though. Across the sources I counted multiple different proposed structures, and none of them match. The one that maps best to enterprise infrastructure, where I spend my days, is Drew Breunig’s. He splits the role into application PMs, who move fast and sit with customers, and foundation PMs, who own the platform, compliance, and quality underneath the application teams.

Where they disagree

The biggest disagreement is over validation: do you still need to test whether an idea works before shipping it, or is shipping the test? Cat Wu at Anthropic is on the “shipping is the test” side. Her argument is that models improve so fast that a plan made at the start of a project can be wrong by the end of it, so her team ships quickly and revisits what they’ve built at every model release. In her version of the job, the PM names the few non-negotiables and lets go of the rest.

Leah Tharin argues the opposite. The slow part of building something valuable is finding out whether people want it, and that depends on how many users you can learn from, no matter how quickly the code gets written. Even at Smallpdf, the document-tools company where she used to work, experiments across 50 million users took weeks to produce a real answer.

Marty Cagan’s build-to-learn versus build-to-earn distinction is the middle position, and roughly where I currently land. Prototype and learn as fast as you like, but a prototype exists to answer questions, and a product has to work at scale for people who pay for it, which hasn’t gotten any cheaper.

They also split on the PM-to-engineer ratio. Oji and Ezinne Udezue, both longtime product leaders, argue PMs are the constraint now, so the ratio should go up. The strongest counterpoint is Microsoft’s 2025 cuts: of 1,985 roles cut in Washington state, 817 were engineers and 373 were product managers, roughly one PM for every two engineers, a far bigger share of PMs than any org I’ve worked in. The sources do agree on one thing here: scope per PM keeps growing.

Three questions for your team

  1. As engineering gets much faster over the next year, what breaks first in your org? The candidates across the sources are discovery, decision speed, validation, go-to-market (getting the thing sold and adopted), and your capacity to review and absorb everything that now gets built. Rejecting the premise is a legitimate answer. John Cutler calls “the bottleneck moved to product” a lazy metaphor, and points instead at the pace of knowledge turns, meaning how quickly the whole system learns.

  2. When a prototype can act as the spec, what is the PRD still doing for you? And who owns the evals that define “good” for your AI features? Uber’s experience suggests the PRD survives as the record of why, with prototypes carrying the what. Their line that “two hours of prototyping unblocked four weeks of discussion” matches what I’ve seen. As for evals: they’re the repeatable tests that grade an AI feature’s output, which you need because AI answers aren’t simply right or wrong. OpenAI’s Kevin Weil calls writing them a core skill for product managers. In most organizations I’d wager that job currently belongs to nobody.

  3. Where do the seniors come from, and what is their scope? Everyone wants smaller and more senior teams, but the junior work people used to build judgment on is the first thing AI absorbs. Stanford’s payroll data shows employment for early-career workers (ages 22-25) in the jobs most exposed to AI down 16% relative to other workers, while experienced people in the same jobs have held steady. Teresa Torres has the rule I find most convincing: an expert using AI beats AI on its own, but juniors who let AI do all the analysis never build the skills to become that expert. LinkedIn replaced its associate product manager program, the traditional way into the role, with a “Product Builder” program that trains generalists across product, design, and engineering. That’s one answer to the scope question; the sources’ proposed structures all differ, so it’s yours to decide.

The reading list

If you only read three of these:

Melissa Perri has the best take I’ve read on what matters most for PMs right now:

Measure your productivity by how often you changed a decision that mattered, how often you saw around a corner, how often a senior leader walked out of a room thinking differently because of something you said. How often your shipped features translate into real customer outcomes is what matters.

AI can speed up some of what’s on her list. The judgment behind it still comes from years of practice, and there are no shortcuts to that.

Should You Use AI for a Task? Here’s a Simple Way to Decide

Bruce Schneier has a great post about separating “work” tasks from “gym” tasks when it comes to AI usage:

At work, if your job is to move a bunch of heavy things from one side of the room to another, you should use whatever assistive tech you have on hand: a wagon, a forklift… even an AI-powered robot. But at the gym, it makes no sense for that robot to lift weights for you. The point of weightlifting isn’t to move heavy things across the room; it’s to actually lift those heavy things. The same analysis holds for any task an AI can do for you. If it’s work—if the task has to be done and no one cares how—then it’s fine to use AI assistance. But if the task is more like the gym, and how the task is done is at least as important, then it probably doesn’t make sense to use AI.

He goes on to point out that convincing people to go to the non-AI “gym” is very difficult because the payoff isn’t as immediate as just having AI do stuff for you. But it is very, very worth it in the end:

We do have a choice. We can look at the tasks of our lives and separate them into work or gym. Just as we might choose to use the stairs instead of the elevator, or walk instead of calling an Uber, we can wall off our cognitive gym tasks from AI and ensure that we don’t lose our skills to this technology.

Also see Bosses Horrified as “AI Native” College Graduates Hit the Workplace:

As one New York financier told Financial Times journalist Gillian Tett, new hires who were seen as “AI natives” are turning out to have alarmingly shallow ideas. So much so, the anonymous finance worker admitted, that his firm now actively avoids seeking out AI-literate STEM graduates, and opts to comb through humanities students instead. “We want critical thinking, not just AI,” the financier told the FT.

In the Age of AI, Esther Perel’s Relationship Counseling Is More Necessary Than Ever

I imagine that many of you will be Esther Perel fans, either via her book Mating in Captivity or her therapy podcast Where Should We Being?. In this excellent Vanity Fair profile she discusses, among other things, a recent podcast episode about a man and his relationship with an AI bot name Astrid:

Perel never questions the feelings between the man and Astrid. Yet she points out the inherent flaws in the relationship, using words such as “sycophantic” and “undemanding” in the podcast session to emphasize that Astrid has no life, no history to bring to the relationship. “We have had imaginary friends since we are little, and we have spoken to our ancestors forever,” Perel says in our interview, a few weeks after the episode ran. “The danger of AI is that it becomes so soothing and so flattering and so frictionless that real relationships start to feel way too difficult by comparison.”

And the point she eventually makes about AI relationships that I found really interesting:

“What stood out for me is that it’s not like people go from thriving social relations to suddenly talking to an AI. They go from being isolated, spending most of their time at home, maybe going out every once in a while in the evening for dinner or to get to a gym, and they are already so centered on a very small universe that from there, they themselves have become so flattened by technology, they live in their phone,” she says. It has made Perel zero in on the next great challenge. “This is a generation that actually doesn’t have a challenge of sustaining desire; they don’t even ignite it. You know, it’s not about keeping the flame going. It’s about getting the spark going. They don’t drink. They have not had much experience in their 20s, one or two relationships at most. They don’t have sex much. They don’t socialize much. They’re home a lot.” They are the children of people who first read Mating 20 years ago. Sounds like the topic for her next book.