ready, it won't happen. Start small Go top-down Inspect everything A pilot group showed us what works, and what doesn't, before we scaled. Once we were ready, it was a leadership decision. We wanted everyone on it. We measure every team's usage and provide necessary supports.
Make adoption visible Learn from the signal Measure the outcomes A Slack bot shares every team's usage, so everyone knows where they stand. High-usage teams show what works. Low-usage teams get the help they need. Go beyond active users: Merge Request throughput and the AI share of committed code.
everyone Freedom to pick Always re-evaluated Premium seats for every engineer. A tool is cheaper than an engineer’s time. Engineers use what fits their workflow, and share what works. We keep one company default and re-test it. When something better ships, the default moves.
Engineers Manage a team of agents: review AI pull requests, verify correctness, set strict constraints. PMs Let AI analyze customer conversations, cluster feedback and surface trends. Designers Direct agents to polish UX directly in the codebase, blurring the line with front-end.
Engineers Write the specs and tests. Agents iterate on the code until the tests pass. PMs Swap static PRDs for raw problem transcripts and clear success criteria. Designers Define constraints, visual intent and success criteria instead of rigid wireframes.
is building the wrong thing. Engineers Explore several implementations in parallel and keep what works in reality. PMs Bring working prototypes to alignment meetings, not pitch decks. Designers Make rapid AI mockups, and let customers iterate on the interface themselves.
code. Engineers Capture architecture decisions and incident learnings so agents don't repeat past mistakes. PMs Bring working prototypes to alignment meetings, not pitch decks. Designers Codify taste and user review feedback into principles agents can follow.
Producer → Manager Implementation → Intent Less typing, more reviewing and steering. Describe the goal, let AI build. Delivery → Discovery Content → Knowledge Test more ideas, faster. Expertise becomes the edge, not just code. Source: Patrick Debois, “The 4 Patterns of AI-Native Dev”
matters. 1 2 3 AI that collaborates AI that knows AI that ships So humans stay in their workflow, with no copy-paste. So humans don't have to provide context every time. So humans step in only where judgment matters. AI bots Queryable company · Closed loops AI Software factories
legible to AI. 01 Every important action leaves an artifact, so the company’s AI keeps learning and improving. 02 Meetings get AI notes, and communication moves out of DMs and emails into channels where agents can join. 03 Anyone can talk to the data to get metrics and insights, with access control matched to risk.
agents build. Automate the manual tasks and enable agent-to-agent handoffs, limiting human intervention to specific review gates. HU M A N A I AG E N TS Specs and tests Build and iterate Define what success looks like Generate code until the tests pass SHIPS
Trust. AI will do things you don't expect. Verification Observability Review gates Specs and tests define success before agents write any code. See what agents did, and why, on every run. Humans step in at the decisions that carry real risk.