{"success":true,"count":9,"items":[{"videoId":"PplmzlgE0kg","chunkIndex":0,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 1 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["ai-product","product-management","startup","llm","enterprise-software","shipping","cross-functional","developer-tools","agile","tech-trends"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI 시대에 PM이 무엇에 집중해야 하는지 역할 재정의를 배울 수 있음"},{"who":"창업자","why":"빠른 실험과 출시 체계를 만드는 운영 원칙을 얻을 수 있음"},{"who":"엔지니어","why":"기능을 더 빨리 출시하게 만드는 협업·프로세스 설계를 볼 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"이 영상은 Anthropic의 Claude Code 팀이 AI 시대에 제품을 얼마나 빠르게 만들고 출시하는지, 그리고 그 속에서 PM 역할이 어떻게 바뀌는지를 다룬다. Kat Wu는 예전처럼 장기 로드맵 조율에 집중하기보다, 현재 모델에서 최대 역량을 끌어내고 아이디어를 일주일 단위로 사용자에게 전달하는 속도가 핵심이라고 말한다. 이를 위해 명확한 목표 설정, 연구 미리보기(research preview) 중심의 가벼운 출시 방식, 그리고 엔지니어·마케팅·문서화 팀이 바로 움직일 수 있는 운영 프레임을 강조한다.\n\n또한 좋은 AI PM의 역량으로는 코딩보다 \"무엇을 만들지\"를 정하는 제품 감각, 즉 product taste가 중요해진다고 본다. LLM의 범용성은 오히려 목표와 대상 사용자 정의를 어렵게 만들기 때문에, PM은 누구를 위해 무엇을 해결할지 좁혀야 한다. 이 영상은 AI native 제품 환경에서는 PM이 단순 조율자가 아니라, 속도와 선택을 가능하게 하는 설계자여야 한다는 메시지를 강하게 전달한다.","insights":["AI 시대 PM의 핵심은 조율보다 출시 속도다.","LLM이 범용적일수록 타깃과 목표를 더 좁혀야 한다.","좋은 PM은 무엇을 만들지 고르는 taste가 강하다.","연구 미리보기는 빠른 실험을 가능하게 하는 장치다.","PM은 팀이 스스로 결정하게 만드는 운영 프레임을 설계해야 한다."],"keyClips":[{"clipId":"PplmzlgE0kg:c0:1-10","startSegmentIndex":1,"endSegmentIndex":10,"startTime":1.95,"endTime":56.8,"durationSeconds":54.9,"preview":"AI PM의 변화","mustSee":false},{"clipId":"PplmzlgE0kg:c0:23-29","startSegmentIndex":23,"endSegmentIndex":29,"startTime":136.12,"endTime":200,"durationSeconds":63.9,"preview":"역할 분담의 원리","mustSee":false},{"clipId":"PplmzlgE0kg:c0:46-52","startSegmentIndex":46,"endSegmentIndex":52,"startTime":303.76,"endTime":397.64,"durationSeconds":93.9,"preview":"속도가 곧 전략","mustSee":true},{"clipId":"PplmzlgE0kg:c0:55-70","startSegmentIndex":55,"endSegmentIndex":70,"startTime":417.6,"endTime":536.76,"durationSeconds":119.2,"preview":"출시를 쉽게 만드는 법","mustSee":false},{"clipId":"PplmzlgE0kg:c0:74-78","startSegmentIndex":74,"endSegmentIndex":78,"startTime":549.52,"endTime":595.2,"durationSeconds":45.7,"preview":"데이터와 원칙","mustSee":false}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T11:55:51.126Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":1,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 2 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["product-management","engineering","ai","startup","saas","product-strategy","team-culture","enterprise-software","growth","developer-tools"],"normalizedKeywords":["프로덕트","엔지니어링","리더십·매니지먼트"],"targetAudience":[{"who":"프로덕트 매니저","why":"PM 역할이 엔지니어링과 어떻게 합쳐지는지 볼 수 있음"},{"who":"엔지니어","why":"제품 감각을 가진 엔지니어가 왜 더 빠르게 움직이는지 배울 수 있음"},{"who":"스타트업 창업자","why":"적은 프로세스로 빠르게 출시하는 팀 운영 방식을 참고할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자","창업자·스타트업"],"summary":"이 대화는 Anthropic 제품팀이 왜 그렇게 빠르게 움직일 수 있는지에 초점을 맞춘다. Cat Wu는 속도의 핵심이 특정 모델 하나가 아니라, 낮은 프로세스, 강한 실행 기대치, 그리고 엔지니어와 PM의 역할 경계가 흐려진 팀 구조에 있다고 설명한다. 특히 제품 감각이 좋은 엔지니어를 채용하고, 아이디어를 며칠 안에 실제 사용자에게 내놓는 문화를 강조한다.\n\n후반부에서는 Claude Code 소스코드 유출과 구독 정책 변경 같은 논란도 다룬다. 그는 이를 인간 실수와 수요 폭증에 따른 운영상 결정으로 설명하며, 중요한 것은 책임 추궁보다 학습과 안전장치 강화라고 말한다. 마지막으로 PM의 미래에 대해, 역할이 점점 융합되는 만큼 가장 중요한 역량은 직군명이 아니라 'product taste'라고 정리한다.","insights":["속도는 모델보다 팀의 기대치와 프로세스에서 나온다.","PM과 엔지니어의 경계는 점점 사라지고 있다.","제품 감각이 좋은 엔지니어가 가장 강한 실행 단위다.","코드가 싸질수록 무엇을 만들지 고르는 능력이 더 중요해진다.","실수 대응의 핵심은 비난이 아니라 재발 방지 장치다."],"keyClips":[{"clipId":"PplmzlgE0kg:c1:8-13","startSegmentIndex":8,"endSegmentIndex":13,"startTime":663.64,"endTime":706.68,"durationSeconds":43,"preview":"속도의 진짜 원천","mustSee":false},{"clipId":"PplmzlgE0kg:c1:20-27","startSegmentIndex":20,"endSegmentIndex":27,"startTime":732.92,"endTime":774.28,"durationSeconds":41.4,"preview":"실수 후의 대응법","mustSee":false},{"clipId":"PplmzlgE0kg:c1:32-38","startSegmentIndex":32,"endSegmentIndex":38,"startTime":798.44,"endTime":841.16,"durationSeconds":42.7,"preview":"수요 폭증의 현실","mustSee":false},{"clipId":"PplmzlgE0kg:c1:42-53","startSegmentIndex":42,"endSegmentIndex":53,"startTime":864,"endTime":943.36,"durationSeconds":79.4,"preview":"PM 조직의 구조","mustSee":false},{"clipId":"PplmzlgE0kg:c1:61-73","startSegmentIndex":61,"endSegmentIndex":73,"startTime":973.12,"endTime":1074.72,"durationSeconds":101.6,"preview":"역할 융합의 미래","mustSee":false},{"clipId":"PplmzlgE0kg:c1:77-89","startSegmentIndex":77,"endSegmentIndex":89,"startTime":1096,"endTime":1209.24,"durationSeconds":113.2,"preview":"가장 중요한 역량","mustSee":true}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:55:22.499Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":2,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 3 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["product-management","ai","enterprise-software","leadership","product-strategy","startup","team-culture","developer-tools"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI 시대에 PM이 어떤 문제를 우선 풀어야 하는지 감을 잡을 수 있음"},{"who":"창업자","why":"빠른 제품 실험과 조직 운영의 트레이드오프를 이해하는 데 도움됨"},{"who":"엔지니어","why":"역할 경계가 흐려지는 환경에서 필요한 사고방식을 배울 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"이 영상은 Anthropic의 프로덕트 팀이 AI 변화 속에서 왜 빠르게 움직일 수 있는지, 그리고 그 과정에서 무엇을 포기하고 무엇을 지키는지를 다룬다. 핵심 메시지는 AI 시대의 PM은 더 이상 고정된 직무가 아니라, 시장 변화에 맞춰 역할을 바꾸고 빈틈을 메우는 사람이어야 한다는 점이다. 동시에 모델이 아직 갖지 못한 인간의 공감, 맥락 이해, 이해관계자 조율 같은 '상식'이 여전히 중요하다고 강조한다.\n\n또한 Anthropic이 빠른 실험과 잦은 기능 출시를 택하면서 제품 일관성이나 신규 사용자 온보딩에서 비용을 치르고 있음을 솔직하게 말한다. 그럼에도 회사는 '안전한 AGI를 모두에게'라는 상위 미션을 기준으로 우선순위를 정하고, 혼란을 감수하더라도 신속한 학습과 개선을 택한다. 전반적으로 이 대화는 AI 제품 조직에서 필요한 태도는 완벽함보다 차분함, 유연함, 낮은 자아, 그리고 강한 미션의식이라는 것을 보여준다.","insights":["AI 시대의 PM은 고정 역할보다 빈칸 메우기가 핵심이다.","모델이 못하는 건 상식·EQ·이해관계자 조율이다.","빠른 출시의 대가로 제품 일관성과 온보딩이 약해진다.","혼란 속에서 오래 버티는 힘은 냉정한 우선순위다.","강한 미션이 있으면 기능보다 방향으로 결정할 수 있다."],"keyClips":[{"clipId":"PplmzlgE0kg:c2:2-3","startSegmentIndex":2,"endSegmentIndex":3,"startTime":1210.64,"endTime":1266.32,"durationSeconds":55.7,"preview":"PM의 새 역할","mustSee":false},{"clipId":"PplmzlgE0kg:c2:7-12","startSegmentIndex":7,"endSegmentIndex":12,"startTime":1303.72,"endTime":1342.48,"durationSeconds":38.8,"preview":"인간이 남는 이유","mustSee":false},{"clipId":"PplmzlgE0kg:c2:16-22","startSegmentIndex":16,"endSegmentIndex":22,"startTime":1359.44,"endTime":1471.8,"durationSeconds":112.4,"preview":"혼란을 버티는 법","mustSee":false},{"clipId":"PplmzlgE0kg:c2:32-43","startSegmentIndex":32,"endSegmentIndex":43,"startTime":1542.32,"endTime":1668.12,"durationSeconds":125.8,"preview":"빠른 실험의 비용","mustSee":false},{"clipId":"PplmzlgE0kg:c2:45-58","startSegmentIndex":45,"endSegmentIndex":58,"startTime":1676.2,"endTime":1804.92,"durationSeconds":128.7,"preview":"미션이 의사결정이다","mustSee":true}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:55:44.615Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":3,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 4 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["product-management","ai-tools","workflow","productivity","collaboration","saas","enterprise-software","agentic-ai","knowledge-work"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"제품별 사용 맥락과 우선순위 조정 방식이 PM 실무에 직접적이다"},{"who":"지식노동자","why":"코드가 아닌 문서·슬랙·덱 작업을 AI로 줄이는 방법을 배울 수 있다"},{"who":"초기 팀 리더","why":"미션 중심으로 팀을 정렬하고 빠르게 의사결정하는 원리를 얻을 수 있다"}],"normalizedAudience":["프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 구간은 Anthropic이 왜 빠르게 결정하고, 왜 특정 제품에 집중하는지에 대한 내부 논리를 설명한다. 핵심은 개별 제품의 성과보다 Anthropic의 미션과 사용자 확장을 우선시하는 문화이며, 그 덕분에 경쟁 우선순위가 생겨도 팀 전체가 같은 판단을 따를 수 있다는 점이다.\n\n이어지는 부분에서는 Claude Code, Desktop/Web, Cohere를 각각 어떤 상황에서 쓰는지 실전 기준을 정리한다. 코드 작업은 Claude Code/desktop, 이동 중 작업은 web/mobile, 비코드 산출물은 Cohere가 담당하며, 특히 Slack·Gmail·Drive·Calendar 같은 데이터 소스를 연결하면 회의 준비용 슬라이드 덱 같은 비정형 업무를 크게 자동화할 수 있다고 말한다.","insights":["미션이 선명할수록 조직 전체의 의사결정이 빨라진다.","개별 제품보다 회사 미션을 우선해야 장기 집중이 생긴다.","도구 선택은 '무슨 산출물인가'로 나누는 게 가장 실용적이다.","비코드 업무는 컨텍스트 연결이 성능의 절반을 결정한다.","AI는 초안을 빨리 만들고, 사람은 품질을 다듬는 데 집중해야 한다."],"keyClips":[{"clipId":"PplmzlgE0kg:c3:1-18","startSegmentIndex":1,"endSegmentIndex":18,"startTime":1801.87,"endTime":1930.88,"durationSeconds":129,"preview":"미션이 만드는 속도","mustSee":false},{"clipId":"PplmzlgE0kg:c3:19-22","startSegmentIndex":19,"endSegmentIndex":22,"startTime":1930.88,"endTime":1949,"durationSeconds":18.1,"preview":"첫째는 사용자 확장","mustSee":false},{"clipId":"PplmzlgE0kg:c3:23-40","startSegmentIndex":23,"endSegmentIndex":40,"startTime":1949,"endTime":2056.52,"durationSeconds":107.5,"preview":"제품별 사용 기준","mustSee":false},{"clipId":"PplmzlgE0kg:c3:41-52","startSegmentIndex":41,"endSegmentIndex":52,"startTime":2056.52,"endTime":2148.24,"durationSeconds":91.7,"preview":"이동 중 작업의 해법","mustSee":false},{"clipId":"PplmzlgE0kg:c3:57-88","startSegmentIndex":57,"endSegmentIndex":88,"startTime":2168.52,"endTime":2401.88,"durationSeconds":233.4,"preview":"컨텍스트가 덱을 만든다","mustSee":true}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:56:26.069Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":4,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 5 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["product-management","ai-tools","knowledge-work","slack","internal-tools","workflow-automation","sales","enterprise-software","technical-gotm","anthropic"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI를 PM 업무에 어떻게 붙이고, 최종 판단은 사람이 어떻게 가져가는지 볼 수 있음"},{"who":"지식노동자","why":"반복 업무를 자동화하고 개인용 내부 도구를 만드는 방식이 유용함"},{"who":"창업자","why":"조직 전체의 업무 흐름을 AI로 재설계하는 사례를 참고할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","지식노동자 일반"],"summary":"이 구간은 Anthropic 내부에서 Claude/Claude Code/Co-work가 실제 업무를 얼마나 바꾸고 있는지 보여준다. PM은 Claude를 브레인스토밍 파트너로 쓰되, 최종적으로 무엇을 제품이나 발표 자료에 넣을지는 사람이 결정해야 한다는 점을 강조한다. 그 뒤에는 표준 템플릿과 Figma 연동, Slack 기반 협업, 고객 컨텍스트를 끌어와 맞춤형 데크를 즉석에서 만드는 내부 도구 사례가 이어진다.\n\n핵심은 AI가 단순히 일을 '대체'하는 게 아니라, 반복적이고 맥락 의존적인 업무를 사람마다 맞는 워크플로로 재구성한다는 것이다. 특히 Anthropic에서는 Slack이 사실상 회사의 OS처럼 작동하고, 각 팀이 자신만의 작은 앱과 봇을 만들어 쓰며, Applied AI 같은 기술형 GTM 조직이 고객 대응과 프로토타이핑을 빠르게 처리한다. 모델이 좋아질수록 사람들은 더 많은 일을 위임하고 더 오래 도구 안에서 일하게 된다는 흐름도 드러난다.","insights":["AI는 초안 생산을 맡고, 최종 판단은 사람이 해야 한다.","좋은 PM은 모델이 아니라 '선택의 기준'을 설계한다.","반복 업무는 범용 툴보다 맞춤형 내부 도구가 더 효율적이다.","Slack 같은 허브형 도구는 조직의 실시간 운영체제가 된다.","모델이 좋아질수록 사람은 더 많은 일을 위임하게 된다."],"keyClips":[{"clipId":"PplmzlgE0kg:c4:1-8","startSegmentIndex":1,"endSegmentIndex":8,"startTime":2400,"endTime":2470.88,"durationSeconds":70.9,"preview":"AI는 초안, 사람은 결정","mustSee":false},{"clipId":"PplmzlgE0kg:c4:10-14","startSegmentIndex":10,"endSegmentIndex":14,"startTime":2475.36,"endTime":2515.36,"durationSeconds":40,"preview":"템플릿이 품질을 만든다","mustSee":false},{"clipId":"PplmzlgE0kg:c4:17-23","startSegmentIndex":17,"endSegmentIndex":23,"startTime":2522.36,"endTime":2586.84,"durationSeconds":64.5,"preview":"내부툴이 조직을 바꾼다","mustSee":false},{"clipId":"PplmzlgE0kg:c4:25-36","startSegmentIndex":25,"endSegmentIndex":36,"startTime":2592.68,"endTime":2682.2,"durationSeconds":89.5,"preview":"맞춤 덱 자동화","mustSee":false},{"clipId":"PplmzlgE0kg:c4:41-45","startSegmentIndex":41,"endSegmentIndex":45,"startTime":2704.68,"endTime":2735.68,"durationSeconds":31,"preview":"슬랙이 회사의 OS","mustSee":false},{"clipId":"PplmzlgE0kg:c4:61-83","startSegmentIndex":61,"endSegmentIndex":83,"startTime":2824.36,"endTime":3000.12,"durationSeconds":175.8,"preview":"기술형 GTM의 부상","mustSee":true}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:57:02.108Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":5,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 6 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["ai-product-management","llm","product-strategy","evaluation","model-harness","claude","anthropic","enterprise-ai","developer-tools"],"normalizedKeywords":["프로덕트","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"AI PM","why":"모델의 현재 한계와 강점을 제품화하는 PM 역량을 배울 수 있음"},{"who":"프로덕트 리더","why":"불확실한 모델 환경에서 빠르게 방향을 정하는 방법을 얻을 수 있음"},{"who":"LLM 실무자","why":"모델 사용, eval, 하네스 개선 같은 실전 운영 감각을 익힐 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자","지식노동자 일반"],"summary":"이 구간은 Anthropic/Claude Code 팀이 어떻게 모델 시대의 제품을 더 빠르게 만들고 개선하는지에 대한 실전 이야기다. 가장 먼저, 내부 팀이 막대한 토큰을 쓰며 모델을 적극 활용하지만 동시에 토큰 비용을 낭비하지 않도록 책임 있게 판단하는 문화가 강조된다. 이어서 Cat Wu는 AI 시대 PM에게 가장 중요한 능력으로 '한 달 뒤 제품이 어떻게 보여야 하는지 정의하는 힘'을 꼽고, 현재 모델의 한계를 바탕으로 사용자를 골든 패스로 유도하고 약점을 보완하는 감각이 핵심이라고 말한다.\n\n또한 이 감각을 키우는 방법으로 모델을 많이 써보고, 모델이 왜 그런 행동을 했는지 스스로 introspect하게 만들고, 믿을 수 있는 소수의 사용자 피드백을 빠르게 수집하며, 소수의 강력한 eval을 만들어 성공 기준을 명확히 하라고 조언한다. 마지막으로 Claude의 성격과 분위기, 즉 light-hearted하면서도 자신감 있는 캐릭터가 단순한 부가 기능이 아니라 제품 성공의 핵심이라는 점을 강조한다.","insights":["AI PM의 핵심은 한 달 뒤 제품 형태를 정의하는 능력이다.","현재 모델의 한계를 알아야 골든 패스를 설계할 수 있다.","좋은 제품 감각은 모델을 많이 쓰고 왜 그랬는지 묻는 데서 생긴다.","소수의 믿을 만한 사용자 피드백이 빠른 개선의 지름길이다.","eval은 많기보다 강해야 하며 성공 기준을 선명하게 만든다."],"keyClips":[{"clipId":"PplmzlgE0kg:c5:1-8","startSegmentIndex":1,"endSegmentIndex":8,"startTime":3000.79,"endTime":3075.36,"durationSeconds":74.6,"preview":"토큰 문화와 책임","mustSee":false},{"clipId":"PplmzlgE0kg:c5:9-24","startSegmentIndex":9,"endSegmentIndex":24,"startTime":3075.36,"endTime":3211.88,"durationSeconds":136.5,"preview":"한달뒤를 보는 PM","mustSee":false},{"clipId":"PplmzlgE0kg:c5:25-30","startSegmentIndex":25,"endSegmentIndex":30,"startTime":3211.88,"endTime":3271.56,"durationSeconds":59.7,"preview":"모델을 읽는 법","mustSee":false},{"clipId":"PplmzlgE0kg:c5:31-47","startSegmentIndex":31,"endSegmentIndex":47,"startTime":3271.56,"endTime":3406.4,"durationSeconds":134.8,"preview":"피드백과 eval","mustSee":true},{"clipId":"PplmzlgE0kg:c5:48-63","startSegmentIndex":48,"endSegmentIndex":63,"startTime":3406.4,"endTime":3525.68,"durationSeconds":119.3,"preview":"캐릭터가 제품이다","mustSee":false},{"clipId":"PplmzlgE0kg:c5:64-71","startSegmentIndex":64,"endSegmentIndex":71,"startTime":3525.68,"endTime":3605.96,"durationSeconds":80.3,"preview":"성격이 만드는 신뢰","mustSee":false}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:57:28.038Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":6,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 7 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["ai-product","llm","agentic-workflows","software-engineering","product-management","automation","code-review","model-capabilities","workflow-design","future-of-work"],"normalizedKeywords":["프로덕트","엔지니어링","커리어·성장"],"targetAudience":[{"who":"프로덕트 매니저","why":"모델 성능 변화에 맞춰 제품 기능을 빼고 더하는 판단 기준을 배울 수 있음"},{"who":"엔지니어","why":"에이전트 하네스, 툴링, 자동화 설계가 어떻게 단순화되는지 이해할 수 있음"},{"who":"지식노동자","why":"반복 업무를 AI로 넘겨 생산성을 높이는 실전 방향을 얻을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자","지식노동자 일반"],"summary":"이 영상은 Claude/Claude Code 같은 AI 제품이 어떻게 모델 성능의 향상에 맞춰 계속 단순해지고, 동시에 더 강력한 기능을 열어가는지를 설명한다. 초기에는 모델의 한계를 보완하기 위해 to-do 리스트 같은 하네스를 붙여야 했지만, 더 좋은 모델이 나오자 그런 장치들이 점점 불필요해지고 제품은 본질적인 작업 성공률에 집중하게 된다. 특히 코드 리뷰처럼 예전엔 어려웠던 기능이 최신 모델에서 실용 수준에 도달하면서, \"지금은 안 되지만 곧 가능해질 것\"을 먼저 프로토타입으로 만들어 두는 전략의 중요성을 강조한다.\n\n후반부에서는 이 흐름이 더 넓은 미래의 일하는 방식으로 확장된다. 앞으로는 여러 작업을 동시에, 더 많은 에이전트가 원격에서 처리하게 될 것이므로 인간은 무엇을 검토하고 어디에 피드백을 줄지 관리하는 역할로 이동해야 한다고 본다. 개인에게 주는 조언도 분명하다: 반복 업무를 찾아 AI에 넘기고, 성공률이 높아질 때까지 자동화를 다듬은 뒤, 그 여유를 더 창의적이고 가치 높은 일에 써야 한다는 것이다.","insights":["모델이 똑똑해질수록 제품은 오히려 단순해진다.","하네스는 영구 기능이 아니라 과도기적 보조장치다.","새 모델은 기존 기능을 지우게 만들고 새 기능을 열어준다.","가능해질 미래를 먼저 만들어야 학습 속도가 빨라진다.","AI 활용의 핵심은 반복 업무를 찾아 신뢰도 높게 자동화하는 것이다."],"keyClips":[{"clipId":"PplmzlgE0kg:c6:14-29","startSegmentIndex":14,"endSegmentIndex":29,"startTime":3663.6,"endTime":3764.48,"durationSeconds":100.9,"preview":"모델이 강해지면","mustSee":false},{"clipId":"PplmzlgE0kg:c6:33-40","startSegmentIndex":33,"endSegmentIndex":40,"startTime":3783.84,"endTime":3879.08,"durationSeconds":95.2,"preview":"새 모델이 여는 일","mustSee":true},{"clipId":"PplmzlgE0kg:c6:48-62","startSegmentIndex":48,"endSegmentIndex":62,"startTime":3932.72,"endTime":4039.16,"durationSeconds":106.4,"preview":"대량 에이전트의 미래","mustSee":false},{"clipId":"PplmzlgE0kg:c6:67-85","startSegmentIndex":67,"endSegmentIndex":85,"startTime":4069.64,"endTime":4206.08,"durationSeconds":136.4,"preview":"AI 활용의 실전법","mustSee":false}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:58:05.232Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":7,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 8 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["artificial-intelligence","productivity","automation","product-design","workflow","developer-tools","agentic-ai","leadership","books","technology"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI 제품을 실제 업무에 쓰게 만드는 설계 원칙을 배울 수 있음"},{"who":"창업자","why":"도구 최적화보다 핵심 과제에 집중해야 하는 기준이 유용함"},{"who":"지식노동자","why":"자동화와 AI를 일상 업무에 붙이는 현실적인 태도를 얻을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","지식노동자 일반"],"summary":"이 구간의 핵심은 AI 자동화를 '95%짜리 반쪽짜리 편의'로 끝내지 말고, 실제로 신뢰할 수 있는 100% 수준까지 다듬어야 한다는 점이다. 화자는 자신도 이메일 분류나 워크플로 자동화를 만들다 시간이 많이 들었지만, 결국 일상 업무에 제대로 붙는 자동화만이 진짜 가치가 있다고 말한다. 동시에 AI를 너무 많이 커스터마이즈하는 일 자체가 목표를 흐릴 수 있으니, 도구를 만지작거리는 즐거움과 핵심 업무 수행 사이의 균형이 중요하다고 강조한다.\n\n후반부에서는 AI를 '구경하는 기술'이 아니라 '매일 쓰는 실전 도구'로 써야 진짜 차이를 체감한다고 정리한다. 책 추천과 Waymo 이야기, 그리고 'Just do things'라는 삶의 모토까지 이어지며, 복잡한 분석보다 제약을 이해한 뒤 실행하는 태도가 일과 삶 모두에서 더 큰 레버리지를 만든다는 메시지로 마무리된다.","insights":["95% 자동화는 거의 자동화가 아니다.","진짜 가치는 매일 쓰는 업무에 붙을 때 생긴다.","도구 커스터마이즈가 목적을 삼키면 역효과다.","AI는 말해주는 것보다 대신 해줄 때 강해진다.","제약을 이해하면 답은 결국 실행으로 좁혀진다."],"keyClips":[{"clipId":"PplmzlgE0kg:c7:1-7","startSegmentIndex":1,"endSegmentIndex":7,"startTime":4200.35,"endTime":4244.72,"durationSeconds":44.4,"preview":"완성형 자동화 기준","mustSee":false},{"clipId":"PplmzlgE0kg:c7:8-15","startSegmentIndex":8,"endSegmentIndex":15,"startTime":4244.72,"endTime":4319,"durationSeconds":74.3,"preview":"개인 워크플로 개선","mustSee":false},{"clipId":"PplmzlgE0kg:c7:17-31","startSegmentIndex":17,"endSegmentIndex":31,"startTime":4322.68,"endTime":4439.64,"durationSeconds":117,"preview":"커스터마이즈의 함정","mustSee":false},{"clipId":"PplmzlgE0kg:c7:32-41","startSegmentIndex":32,"endSegmentIndex":41,"startTime":4439.64,"endTime":4519.96,"durationSeconds":80.3,"preview":"AI는 행동형 제품","mustSee":true},{"clipId":"PplmzlgE0kg:c7:44-79","startSegmentIndex":44,"endSegmentIndex":79,"startTime":4531.76,"endTime":4807.84,"durationSeconds":276.1,"preview":"실행력과 생활 설계","mustSee":true}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:58:38.675Z","keyClipsTotalSec":1331},{"videoId":"PplmzlgE0kg","chunkIndex":8,"totalChunks":9,"title":"How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code) — Part 9 of 9","thumbnail":"https://i.ytimg.com/vi/PplmzlgE0kg/maxresdefault.jpg","duration":5134,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=PplmzlgE0kg","keywords":["startup","product-management","leadership","agency","ai-product","claude","anthropic","career-growth","technology"],"normalizedKeywords":["리더십·매니지먼트","프로덕트","커리어·성장"],"targetAudience":[{"who":"프로덕트 매니저","why":"역할 경계를 넘어 문제를 푸는 제품 조직의 사고방식을 배울 수 있음"},{"who":"창업자","why":"초기 조직에서 프로세스보다 실행과 자율성이 중요한 이유를 확인할 수 있음"},{"who":"엔지니어","why":"팀 경계에 갇히지 않고 주도적으로 일하는 태도의 가치를 이해할 수 있음"}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","엔지니어·개발자"],"summary":"이 영상은 Anthropic의 제품팀이 왜 빠르게 움직이는지에 대한 핵심 태도로 'agency'와 'bias towards action'을 강조한다. 역할과 팀 경계가 엄격한 많은 회사와 달리, 문제를 해결하는 데 필요한 일을 스스로 찾아 실행하고, 잘못되면 사과하거나 고치는 문화가 속도를 만든다고 말한다. 학교식으로 정답만 따라가는 습관을 벗어나, \"허락을 기다리지 말고 필요한 일을 하라\"는 메시지가 반복된다.\n\n후반부에는 Claude의 'thinking words' 중 가장 좋아하는 단어로 'manifesting'을 고르고, AGI 이후의 삶에 대해선 암벽등반, 독서, 역사·물리·로봇공학 등 더 넓은 학습에 시간을 쓰고 싶다고 답한다. 마지막으로 청취자들에게는 Claude Code와 Co-work가 잘 안 되는 구체적 사례와 재현 가능한 오류를 보내 달라고 요청하며, 이런 피드백이 제품 개선에 가장 큰 도움이 된다고 밝힌다.","insights":["빠른 팀은 직무 정의보다 문제 해결을 우선한다.","agency는 허락을 기다리지 않고 필요한 일을 하는 능력이다.","학교식 정답 습관은 실제 협업 환경에서 오히려 속도를 늦춘다.","제품 개선은 칭찬보다 재현 가능한 실패 사례에서 더 빨리 나온다.","AGI 이후에도 인간의 가치는 학습과 취향의 확장에 있다."],"keyClips":[{"clipId":"PplmzlgE0kg:c8:1-14","startSegmentIndex":1,"endSegmentIndex":14,"startTime":4801.75,"endTime":4906.2,"durationSeconds":104.4,"preview":"경계 넘는 실행력","mustSee":false},{"clipId":"PplmzlgE0kg:c8:16-20","startSegmentIndex":16,"endSegmentIndex":20,"startTime":4909.8,"endTime":4932.36,"durationSeconds":22.6,"preview":"생각 단어의 취향","mustSee":false},{"clipId":"PplmzlgE0kg:c8:21-28","startSegmentIndex":21,"endSegmentIndex":28,"startTime":4932.36,"endTime":5006.24,"durationSeconds":73.9,"preview":"AGI 이후의 삶","mustSee":false},{"clipId":"PplmzlgE0kg:c8:30-41","startSegmentIndex":30,"endSegmentIndex":41,"startTime":5010.16,"endTime":5102.12,"durationSeconds":92,"preview":"피드백이 성장한다","mustSee":false}],"curatedSegments":[{"segmentIndex":4,"text":">> We want to remove every single barrier to shipping things. The timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to even 1 day.","startTime":17.72,"endTime":27,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"속도 혁신과 기간 단축 통찰이 큼."},{"segmentIndex":10,"text":">> back to product taste. As code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write.","startTime":48.28,"endTime":56.8,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"가치가 코딩보다 판단으로 이동함."},{"segmentIndex":52,"text":"I think the PMs who do the best on AI native products are the ones who can figure out, how can I like shorten the time from having this idea to actually getting the product in the hands of users, and help define what are the most important tasks that need to work out of the box for my product.","startTime":379.24,"endTime":397.64,"durationSeconds":18,"level":"C1","overallScore":7.6,"rationale":"AI PM의 핵심 역량을 선명히 정리함."},{"segmentIndex":61,"text":"What do you think is going on with the PM profession long-term? >> I think all of the roles are merging.","startTime":973.12,"endTime":977.6,"durationSeconds":4,"level":"B2","overallScore":7.4,"rationale":"직무 변화에 대한 통찰이 있음."},{"segmentIndex":78,"text":"Like as code becomes much cheaper to write, the thing that becomes more valuable is deciding what to write. Like what is the right UX for this feature?","startTime":1099,"endTime":1105.64,"durationSeconds":7,"level":"C1","overallScore":7.8,"rationale":"가치 판단의 본질을 설명함."},{"segmentIndex":2,"text":"I think the most important thing is to be able to have this like first principles thinking, where you can figure out how the tech landscape is changing, what the team really needs from you, and to like jump in and fix that hole, because I think the work is becoming more amorphous, which means that a great PM is able to understand what all the gaps are, to figure out what the highest priority ones are, and then to just like figure out, okay, how do I learn that skill set, or what is like the skill set that I have that I can like apply to this challenge.","startTime":1210.64,"endTime":1252.28,"durationSeconds":42,"level":"C1","overallScore":8.2,"rationale":"원칙적 사고와 문제 해결법을 구체화함."},{"segmentIndex":21,"text":"But I think you just have to acknowledge that there's only so much that you can do, that you need to sleep well so that you can make good decisions next day, and just like brutally prioritize where you spend your time, what's the most important thing to get right, and be okay letting things go.","startTime":1422.19,"endTime":1457.52,"durationSeconds":35,"level":"C1","overallScore":8,"rationale":"핵심 원칙과 실행 조언이 명확함."},{"segmentIndex":11,"text":">> I think the hardest skill is being able to define what the product should look like a month from now.","startTime":3095.04,"endTime":3105.48,"durationSeconds":10,"level":"C1","overallScore":7.6,"rationale":"핵심 역량을 한 문장으로 정의함."},{"segmentIndex":14,"text":"And the best PMs can sense that, can set a direction, and can steadily execute towards it, and change the path if the model capabilities are much better than or worse than what they'd originally expected.","startTime":3121.36,"endTime":3135.64,"durationSeconds":14,"level":"C1","overallScore":7.6,"rationale":"좋은 PM의 판단·실행 과정을 설명함."},{"segmentIndex":30,"text":"A lot of times just like being very curious about why the model made the decision that it did will show you what misled it, so that you can fix the harness in order to close this gap.","startTime":3259.08,"endTime":3271.56,"durationSeconds":12,"level":"C1","overallScore":7.6,"rationale":"관찰→원인파악→개선의 흐름이 뚜렷함."},{"segmentIndex":62,"text":"So that when you do see a task that isn't done to your liking, you can give it feedback and the model will know for every future run to incorporate that feedback so it never makes that mistake again.","startTime":4027.68,"endTime":4039.16,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"피드백 학습 원리를 설명하는 실용적 문장."},{"segmentIndex":19,"text":"I would really push people towards building apps that you're actually using every single day cuz I think only through that usage are you actually getting the value.","startTime":4337.32,"endTime":4346.16,"durationSeconds":9,"level":"B2","overallScore":7.6,"rationale":"실사용 중심의 분명한 조언임."},{"segmentIndex":37,"text":"I think that big shift is that the 2024 generation of products were chat-based and the cloud code generation of products is action based and the like big aha moment people have is when Claude can just like do things on your behalf.","startTime":4478.84,"endTime":4495.96,"durationSeconds":17,"level":"C1","overallScore":7.4,"rationale":"제품 패러다임 변화를 짚는 통찰."},{"segmentIndex":78,"text":">> lot of value in like first principles thinking and if you like if you know what you're optimizing for and you have like strong first principles, then you can normally deduce what the right like course of action is and be able to clearly articulate that to all the stakeholders and then you should just like do it.","startTime":4778.68,"endTime":4795.64,"durationSeconds":17,"level":"C1","overallScore":7.8,"rationale":"원칙 기반 의사결정의 핵심을 설명함."},{"segmentIndex":7,"text":"The thing that is extremely important for building AI native products is iterating so quickly.","startTime":35.52,"endTime":40.92,"durationSeconds":5,"level":"B2","overallScore":6.2,"rationale":"AI 제품의 핵심 원칙을 직접 말함."},{"segmentIndex":48,"text":"Um I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from 6 months to 1 month and sometimes to 1 week or even 1 day.","startTime":326.919,"endTime":343.88,"durationSeconds":17,"level":"C1","overallScore":6.4,"rationale":"AI로 속도와 주기가 바뀐 점이 핵심."},{"segmentIndex":50,"text":"And what that means is as a PM, there should be less emphasis on making sure that you're aligning your like multi-quarter roadmaps with your partner teams, and more emphasis on, okay, how can we figure out the fastest way to get something out the door?","startTime":349.76,"endTime":362.56,"durationSeconds":13,"level":"C1","overallScore":6.6,"rationale":"PM 우선순위 전환을 명확히 제시함."},{"segmentIndex":51,"text":"How can we figure out how to make like a concept corner of our product suite where we can just an engineer has an idea or a PM has an idea, and like by the end of the week, we are able to get into our users' hands.","startTime":362.56,"endTime":379.24,"durationSeconds":17,"level":"C1","overallScore":6.8,"rationale":"빠른 실험·출시 방식이 잘 드러남."},{"segmentIndex":56,"text":"Because LLMs are so general, that actually creates a lot of ambiguity in who we're building for, what problems we're trying to solve, what the top use cases are.","startTime":420.88,"endTime":429.08,"durationSeconds":8,"level":"C1","overallScore":6.8,"rationale":"AI가 목표를 흐리게 만든다는 통찰이 좋음."},{"segmentIndex":78,"text":"And this includes who our key users are, why those are our key users, and the reason that we articulate all of this is so that everybody on the team feels like they understand how our business works, they understand what's important to us, and what we're willing to trade off, and it lets people make decisions by themselves without feeling like they're blocked on PM or any other stakeholder.","startTime":573.24,"endTime":595.2,"durationSeconds":22,"level":"C1","overallScore":7.2,"rationale":"원칙의 목적과 효과를 잘 설명함."}],"generatedAt":"2026-06-22T14:59:08.506Z","keyClipsTotalSec":1331}]}