DiscoverVenture Step
Venture Step

Venture Step

Author: Dalton Anderson

Subscribed: 1Played: 3
Share

Description

What's being built, why it matters. Venture Step is an independent podcast for curious builders. Host Dalton Anderson explores AI, startups, company strategy, research, and policy through candid interviews, original deep dives, and solo episodes. Each episode looks at how ideas work, what they change, and the personal realities of building something meaningful.
130 Episodes
Reverse
How can a company see the next market coming, invest in it, and still lose ground?In this solo episode of Venture Step Podcast, I pick up a thread from The Nvidia Way and apply Clayton Christensen’s The Innovator’s Dilemma to five companies. When you judge every opportunity by what your current customers want, what margins you need, and how big the market is today, you can talk yourself out of a market that’s still taking shape.Blockbuster offered rentals by mail while carrying the costs of a store network. Kodak sold digital cameras while film and processing drove its business. Yahoo saw the value of search, partnered with Google, and bought search and advertising technology of its own. Each saw what was changing. Each faced a different problem building a business around it.Then I look at NVIDIA’s investment in CUDA, which gave researchers a way to use GPUs beyond graphics. Apple raises the question I’m still thinking about. When can you afford to wait on a category like foldables or headsets, and when does waiting give another platform time to attract the developers you’ll need later?The next time an idea fails your investment test, ask yourself: Is the opportunity weak, or are you judging an emerging market by what your most profitable business needs today?CHAPTERS00:00 Why The Innovator’s Dilemma matters in the AI era04:04 How customers, margins, and forecasts shape what gets funded06:01 Sustaining innovation, low-end disruption, and new markets09:34 Why promising ideas struggle to get funded13:41 Blockbuster saw Netflix coming but faced different costs16:49 Kodak sold digital cameras while film paid the bills22:00 Yahoo saw the value of search and still lost ground25:18 NVIDIA’s bet on GPUs, CUDA, and AI29:47 When can Apple afford to be late?34:20 Could AI glasses become the next platform?34:52 Making bets with incomplete informationSOURCESClayton Christensen and disruptive innovationhttps://www.christenseninstitute.org/theory/disruptive-innovation/Tae Kim, The Nvidia Wayhttps://wwnorton.co.uk/books/9781324086710-the-nvidia-wayBlockbuster’s annual reporthttps://www.sec.gov/Archives/edgar/data/1085734/000119312511186981/d10k.htmKodak’s digital camera milestoneshttps://www.kodak.com/en/company/page/milestones/Yahoo’s search partnership with Googlehttps://googlepress.blogspot.com/2000/06/yahoo-selects-google-as-its-default.htmlNVIDIA’s corporate timelinehttps://www.nvidia.com/en-us/about-nvidia/corporate-timeline/
What happens when the assistant that helps run your day also becomes the way you discover what to read, buy, and believe?In this solo episode of Venture Step Podcast, I compare my early experiences with Meta's Muse and OpenAI's Dot. Both can take action and bring useful context into daily work, but they feel different to me. Muse feels more like a companion that wants to keep a conversation going. Dot feels more like a chief of staff coordinating work across projects. These are early impressions, shaped by how much context I have already shared with each product.I walk through Muse's setup, personalized feed, goals, and suggestions, including where the proactive prompts felt helpful and where they became distracting. I also explain why keeping twenty projects in one conversation can make even a capable assistant hard to manage. Price and access matter here too: the assistant people can try easily may have an advantage over one that is powerful but expensive or unfamiliar.That leads to the larger question. The phone became the default way to reach people, services, and information. AI assistants are competing to become the next front door. I use Meta's history with Instagram, Stories, Reels, and Threads to explain why distribution can matter as much as product quality. Then I ask what happens when one assistant starts choosing the news, recommendations, services, and next steps that reach you first.I'm optimistic about how much work these tools can remove. I'm also trying to keep my own judgment and room for discovery as they become more useful. If an assistant handles more of your life, who decides what it shows you?CHAPTERS00:00 Muse, Dot, and the shift beyond model benchmarks04:52 Venture Step update and where to watch the show06:51 My first experiences with Muse and Dot10:22 Muse's personalized feed, ideas, and goals13:49 Dot as chief of staff; Muse as companion18:10 Why one chat gets crowded across projects20:27 Price, access, and who each assistant serves21:27 The phone as the distribution point24:04 Meta's acquire, adapt, and build playbook30:10 Why ease of use can win the next AI habit32:13 The assistant as gatekeeper for choices and information34:40 Discovery, agency, and the risk of being managed36:35 Closing thoughtsSOURCESMeta, Introducing Muse:https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/OpenAI, Introducing dots:https://openai.com/index/introducing-dots/
What do you do when the technology you believe in prevents customers from using your product?In this solo episode of Venture Step Podcast, I review Tae Kim's [*The Nvidia Way: Jensen Huang and the Making of a Tech Giant*](https://wwnorton.co.uk/books/9781324086710-the-nvidia-way). NVIDIA's position today can make its rise look inevitable. The book takes us back to the years when Jensen Huang, Chris Malachowsky, and Curtis Priem still had to decide whether to leave secure jobs and when early product bets nearly exhausted the company.The NV1 and NV2 were technically ambitious, but compatibility problems made adoption difficult. I walk through the decision to invest in simulation, the pressure to redesign with little runway, and the RIVA 128 launch. For anyone building a product, the question is familiar: are you solving a problem the market can use now, or asking customers to follow you somewhere they are not ready to go?Surviving once was not enough. I explore how a faster release rhythm, backward compatibility, and close work with PC manufacturers helped NVIDIA stay in the conversation. More releases meant more chances to learn. I connect that lesson to slower insurance product cycles and the danger of waiting years to get real market feedback.The story also runs through relationships and people: "rough justice" in a long-term partnership with TSMC, the Xbox deal, years of persistent recruiting, Jensen's whiteboard reviews, and his "top five" updates. Then I turn to researcher feedback, CUDA, and the investment that made GPUs useful beyond graphics and central to AI work.Listen for the painfully slow simulator, the employees who taped icons to their desks to save time, and the practical choice to cut scope while protecting a release date. My takeaway from the book: technical excellence and business judgment have to develop together. The visible victory lap rarely shows the cost of getting there.CHAPTERS00:00 Introduction, NVIDIA's founding, and Jensen Huang's vision02:10 Product development and market missteps04:56 Innovative use of emulators in chip design07:36 Market feedback and product iteration10:18 Staying ahead with rapid release cycles13:39 Building long-term partnerships and distribution16:56 Talent acquisition and company culture20:23 The future of NVIDIA and AI innovation23:11 Key takeaways for entrepreneurs and tech leadersSOURCESTae Kim, *The Nvidia Way*:https://wwnorton.co.uk/books/9781324086710-the-nvidia-wayNVIDIA corporate timeline, including the 1997 RIVA 128 launch:https://www.nvidia.com/content/timeline/time_97.htmlNVIDIA's CUDA overview:https://developer.nvidia.com/hpc
What changes when you stop asking AI for answers and start handing it work?Dalton breaks down OpenAI's DevDay announcements through a live experiment: call Dot, assign a plain-English briefing, request a sourced fact check, and ask it to design a five-second Venture Step intro. Then keep recording while the work happens and return to inspect the results.The bigger idea is a personal chief of AI staff: one place to communicate with agents, delegate tasks, and review their output. Dalton explores why avatars could make that feel more approachable, how Space and Pages could support collaboration, and why ChatGPT's plugin ecosystem matters for founders trying to reach customers.Enthusiasm meets friction: computer crashes, changing usage allowances, and the difficulty of keeping multiple projects organized in one chat. The intro demo shows the promise of handing off a creative task, while the follow-up conversation sharpens what was actually announced.Two distinctions matter: OpenAI's audience claim is "our collective 1.2B weekly users," not an independently verified ChatGPT active-user count. Using a ChatGPT allowance in participating tools covers eligible AI work; it doesn't automatically pay for an entire third-party product.Listen for "I'm recording the episode plus I'm getting work done," the live intro reveal, and the question of whether reviewing a deliverable becomes more important than steering every prompt.CHAPTERS00:00 DevDay and the live experiment01:36 Calling Dot and assigning the tasks09:51 Why AI agents have avatars16:36 Specialized Dots and collaboration18:09 Space and Pages21:30 Usage allowances and developer tools30:17 ChatGPT as a business distribution channel34:41 Checking Dot's results41:11 Allowance and audience-count clarifications42:22 The intro reveal43:11 From idea to action and the organizational gapSOURCESOpenAI DevDay recap, including model/API releases, Space, plugins, Sign in with ChatGPT, and Pro 500:https://openai.com/index/devday-2026-recap/Dots:https://learn.chatgpt.com/docs/dotsPages:https://learn.chatgpt.com/docs/space/pagesPlugin review and discovery:https://developers.openai.com/plugins/deploy/app-review
A real town square is noisy, awkward, and alive. What happens when a social feed recreates the bustle, but the people and reactions may be synthetic?Dalton revisits his “Synthetic Rubicon” idea and asks what AI slop does to trust. He traces the term’s rise, then explains three traits that let synthetic filler spread: superficial competence, asymmetric effort, and mass producibility. Shrimp Jesus and Jean Phil show how odd content can attract attention. Michael Smith’s bot-streaming fraud and the fictional influencer Emily Hart show how attention can become money.The episode also takes the objection seriously: people have always made mediocre content, and AI can help people learn and create. The real question is who bears the cost of checking a claim, and whether human time and in-person connection become more valuable as feeds fill up.Moments to listen for:• “What if that town center was social media?”• The “whack-a-mole” gap between generating a convincing video and checking it.• “Why am I even here?” when a feed stops showing you your friends.Sources and examples:• Term history: https://www.nytimes.com/2024/06/11/style/ai-search-slop.html• Simon Willison on slop: https://simonwillison.net/2024/May/8/slop/• Three traits of slop: https://arxiv.org/abs/2601.06060• Shrimp Jesus research: https://cyber.fsi.stanford.edu/news/ai-spam-accounts-build-followers• Jean Phil clip: https://www.instagram.com/reel/DdZ1-maCf_V/• Jean Phil reporting and the token’s reported market cap: https://www.dexerto.com/tiktok/who-is-jean-phil-ai-character-behind-multimillion-dollar-meme-coin-sparks-fake-persona-trend-3412528/• Michael Smith guilty plea: https://www.justice.gov/usao-sdny/pr/north-carolina-man-pleads-guilty-music-streaming-fraud-aided-artificial-intelligence-0• Emily Hart investigation: https://www.wired.com/story/ai-generated-maga-girls/• Automated web traffic (not a count of social posts): https://www.imperva.com/resources/resource-library/reports/2025-bad-bot-report/• LinkedIn’s “AI slop” feedback option: https://www.linkedin.com/help/linkedin/answer/a15410007• YouTube CEO’s AI-slop priorities: https://blog.youtube/inside-youtube/the-future-of-youtube-2026/Previously on Venture Step: Episode 93, “The Synthetic Rubicon”: https://venturestep.net/episodes/the-synthetic-rubicon-crossing-the-uncanny-valley
loading
Comments