Three AI-native builders. Three different customer audiences. One team shipping all of them. The AI had to behave differently depending on who was using it while staying consistent enough to hold quality across all three.
Designers pushed PRs alongside engineering and PM from concept through release. Review cycles gave way to embedded guardrails and MCP-driven standards.
That operating model spread to other product teams across GoDaddy because the work got better, not because the process was mandated.
This site is a working example. Built entirely in code, directed by a single human in the loop. See how it was made.
He expanded his scope meaningfully by shifting from execution-heavy ownership into experience strategy across agentic builder products, enabling his team to operate more autonomously while he focused on higher-leverage, cross-product problems. This included establishing new connections between UX, Research, and AI through initiatives like Common Language, and embedding UX more deeply into teams that had historically resisted design partnership.