đď¸ How I AI: Quests, token leaderboards, and the elite AI adoption playbook & Notionâs spec-driven development
Listen now on YouTube ⢠Spotify ⢠Apple Podcasts Brought to you by: WorkOSâMake your app enterprise-ready today ThoughtSpotâBuild AI-powered analytics into your product John Kim is the co-founder and CEO of Sendbird. In this episode, John shares how his marketing team built a live swag store with Stripe integration without engineering support, why he tracks every token spent across the org, how he identifies âAI Godsâ inside the company, and why the future of work belongs to people with curiosity, agency, and energy, not just years of experience. The most successful AI transformations treat internal tooling as a product, not a program. John built the âAutomatorsâ platformâa gamified internal marketplace where anyone can create a âquestâ (a request for automation or tooling), and engineers or AI agents can pick it up and build it. Each quest shows the risk level, weeks saved, and who benefits. People earn experience points for completing quests, which they can exchange for gift cards, tea with executives, or the chance to present their work to the entire company at Wednesday standups. This isnât a top-down mandate but a product that makes AI adoption fun, measurable, and rewarding. When you give creative teams builder capabilities, theyâll create things that would never make it onto a traditional product roadmap. Johnâs marketing team built a fully functional e-commerce swag store with Stripe integration, custom designs, and even a Konami Code Easter egg that unlocks secret conference details. In the old world, this would have required two sprints of engineering time and probably would have been deprioritized. Now it shipped in days, delights customers, and generates actual revenue. The biggest unlock for non-technical builders is creating secure, compliant templates they can build on top of. Johnâs team created app templates where authentication, environment setup, databases, and security are pre-configured and vetted by InfoSec. Marketers, salespeople, and CSMs just extract the template and build their idea on top. This removes the biggest barrier to non-engineers shipping to production: the fear of doing something wrong or insecure. Measure token usage without shame, and create tiers that make it aspirational. John created five tiers: Beginner (under 1M tokens/day), Intermediate, Expert, Architect, Catalyst, and AI God (over 100M tokens/day). Every manager can see where their team members are and tailor enablement accordingly. This isnât about performance reviews; itâs about bringing people along the journey and making AI fluency visible and celebrated. The goal isnât just to use AI during work hours but, rather, to smooth the curve so AI works around the clock. John monitors token usage over time and looks for smoothness in the curve. Dips mean people are on weekends or vacation and AI isnât working. When the curve smooths out, it means AI partners are working 24/7. This is a fundamentally different vision: not just augmenting human work, but having AI fill the gaps when humans arenât available. Build a cross-functional AI task force that meets weekly to unblock challenges. John created a role called AI Engineer for Internal Operations that reports directly to him and the chief of staff. This person works cross-functionally with the CTO, engineering, and InfoSec to vet tools, set up compliant tech stacks, and remove barriers. They meet weekly as a task force to discuss whatâs blocking people and how to enable faster iteration. The most important hiring criteria for AI-first companies are curiosity, agency, and energyânot tenure or experience. John rewrote job descriptions to optimize for people who are curious, willing to go deep, and figure things out on their own. He lowered the bar on years of experience and raised the bar on learning ability. In a world where you can build a custom learning center for any topic in 20 minutes, the constraint isnât access to knowledge; itâs the drive to learn. Start with your champions, not your skeptics. Johnâs advice to CEOs struggling with AI adoption: find the people in your organization who are already curious and have agency. Make them the champions. Give them the spotlight. Let them share their work at all-hands meetings. Build energy around their stories. Innovation doesnât start from theoretical structuresâit starts with people who have energy and a story to tell. Once others see whatâs possible, adoption spreads organically. Leadership has to model the behavior, not just mandate it. The top token consumers at Delight.ai are the executives. When leaders show up with new capabilities and ship things faster, it signals to the team that this is real and important. John also does one-on-ones with people who arenât using tokens: âWe noticed you havenât been spending any tokens. Can we help you? Whatâs stopping you?â This combination of top-down modeling and bottom-up support is what drives transformation. How I AI: John Kimâs Playbook for AI Transformation with Quests, Skills, and âAI Godsâ: https://www.chatprd.ai/how-i-ai/john-kims-playbook-for-ai-transformation âł How to Create an Internal AI Marketplace to Crowdsource Automations: https://www.chatprd.ai/how-i-ai/workflows/how-to-create-an-internal-ai-marketplace-to-crowdsource-automations âł How to Build a Personal AI-Generated Learning Center on Any Topic: https://www.chatprd.ai/how-i-ai/workflows/how-to-build-a-personal-ai-generated-learning-center-on-any-topic âł How to Automate Personal Knowledge Management with an AI âGardenerâ: https://www.chatprd.ai/how-i-ai/workflows/how-to-automate-personal-knowledge-management-with-an-ai-gardener Listen now on YouTube ⢠Spotify ⢠Apple Podcasts Brought to you by: Ryan Nystrom is a software engineer and engineering manager at Notion, where he works on Notion AI, Custom Agents, and internal systems that help engineers move faster with less busywork. He joined Notion after the company acquired Campsite, the team communication platform he co-founded. In this episode, Ryan shares how his team automates standup prep, ships PRs from a single Notion comment, uses specs as the new source of truth, and why fast CI is becoming essential for AI coding agents. He explains why engineering managers should still write code, how AI is changing meetings, and why great developer experience matters more than ever. Never prep for standups again by auto-generating meeting notes from all your workstreams. Ryanâs Notion AI agent pulls from Slack conversations, closed tasks, merged PRs, telemetry metrics, and yesterdayâs meeting transcript to create a comprehensive pre-read every morning at 9 a.m. This transforms standups from rote status updates into high-bandwidth problem-solving sessions where the team spends 100% of their time on decisions, blockers, and next steps instead of âI did this thing yesterday.â Fast CI is the mathematical limit on your AI coding velocity. If your CI takes an hour to run, your agents sit idle for an hour waiting for test results. If it takes three minutes, you can run 20x more iterations in the same time frame. Ryanâs team is aggressively cutting Notionâs CI to 25% of current time specifically to unlock agent productivityâbecause agents donât get tired, donât sleep, and can work in parallel across VMs if your infrastructure supports it. Background agents that ship PRs from Slack mentions eliminate context switching. Ryanâs âBoxyâ system lets him @mention Codex from a Notion task, and 20 minutes later he gets back a PR with implementation, screenshots of UI verification, and a preview URL. This morning a friend texted him a feature request; Ryan wrote four sentences and dropped a screenshot in a Notion task, mentioned Codex, and had a shipped PR before lunch. No IDE, no local environment, no context switch. Specs as source of truth beats code as source of truth for AI-powered development. Notion engineers now maintain Markdown spec files in their repo that describe features in plain English with code pointerâŚ
Send this story to anyone â or drop the embed into a blog post, Substack, Notion page. Every play sends rev-share back to Lenny's Newsletter.