One PM, One Designer, One Engineer: How AI-Native Teams Build Now
It is Tuesday morning and a product manager is running the company's checkout
page on their laptop. Not a mockup of it. The actual app, on localhost, on a
branch called proto/split-payments, with seed data loaded. They ask Claude
Code to let a customer split an order across two cards. Four minutes later
they are clicking through it. The confirmation screen looks wrong when one
card is a gift card with a low balance, so they call the designer over, and
the two of them fix the layout in the running product while the agent keeps
up.
By lunch they have found six edge cases nobody would have written into a requirements document, killed one idea (three-way splits), and written down why. No engineer has touched it yet. No Figma file exists. The engineer will be pulled in on Thursday, once the PM and designer are satisfied, and their job will not be "build this." It will be "make this safe to ship."