{"success":true,"count":7,"items":[{"videoId":"R-zCfLQD_84","chunkIndex":0,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 1 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["ai","product-management","linkedin","full-stack-builder","future-of-work","organizational-design","automation","human-ai-collaboration","leadership"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 리더","why":"AI가 제품 개발 체계와 역할 분업을 어떻게 바꿔야 하는지 보여줌"},{"who":"조직 혁신 담당자","why":"새 도구 도입보다 변화관리와 인센티브 설계가 중요함을 시사함"},{"who":"예비 창업자","why":"AI 시대에 어떤 팀 구조와 빌딩 방식이 경쟁력이 되는지 힌트를 줌"}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 영상은 LinkedIn CPO Tomer Cohen이 AI 시대에 맞춰 제품을 만드는 방식을 근본적으로 다시 설계해야 한다고 주장하는 대화를 담고 있다. 핵심은 'full-stack builder' 모델로, 직무 경계와 역할 분업을 줄이고 누구나 아이디어를 제품 출시까지 밀어붙일 수 있게 만드는 것이다. 그는 AI가 단순히 생산성을 조금 높이는 도구가 아니라, 빌딩의 구조와 조직 운영 방식 자체를 바꾸는 계기라고 본다.\n\n또한 그는 왜 이런 변화가 필요한지에 대해, 기술 변화 속도가 조직의 반응 속도보다 훨씬 빠르다는 점과 2030년까지 필요한 역량이 70% 바뀔 수 있다는 점을 근거로 든다. 문제는 일이 본질적으로 복잡해서가 아니라 프로세스와 조직이 과도하게 복잡해졌다는 데 있으며, AI는 그 복잡성을 다시 압축해 더 적은 인원으로 더 빠르게 만들 수 있는 기회를 제공한다고 설명한다. 다만 도구를 배포하는 것만으로는 변화가 일어나지 않으며, 인센티브·사례·문화 같은 변화관리 설계가 필수라고 강조한다.","insights":["AI의 본질은 생산성 향상보다 역할 구조의 재설계다.","일이 복잡한 게 아니라 프로세스와 조직이 복잡해진 것이다.","변화 속도가 대응 속도보다 빠르면 기존 분업은 금방 낡는다.","도구를 주는 것만으로는 안 되고, 채택을 설계해야 한다.","AI는 평균보다 뛰어난 사람의 역량을 더 크게 증폭시킨다."],"keyClips":[{"clipId":"R-zCfLQD_84:c0:1-6","startSegmentIndex":1,"endSegmentIndex":6,"startTime":1.71,"endTime":37.16,"durationSeconds":35.4,"preview":"왜 다시 설계해야 하나","mustSee":true},{"clipId":"R-zCfLQD_84:c0:8-10","startSegmentIndex":8,"endSegmentIndex":10,"startTime":42.28,"endTime":56.12,"durationSeconds":13.8,"preview":"도입보다 채택설계","mustSee":false},{"clipId":"R-zCfLQD_84:c0:14-17","startSegmentIndex":14,"endSegmentIndex":17,"startTime":81.8,"endTime":116.72,"durationSeconds":34.9,"preview":"풀스택 빌더 모델","mustSee":false},{"clipId":"R-zCfLQD_84:c0:47-59","startSegmentIndex":47,"endSegmentIndex":59,"startTime":334.76,"endTime":418.92,"durationSeconds":84.2,"preview":"변화의 압력과 필요","mustSee":true},{"clipId":"R-zCfLQD_84:c0:60-80","startSegmentIndex":60,"endSegmentIndex":80,"startTime":418.92,"endTime":566.56,"durationSeconds":147.6,"preview":"복잡성은 누적된다","mustSee":false}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:07:38.539Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":1,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 2 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["artificial-intelligence","product-management","leadership","engineering","automation","organization-design","startup","agents","digital-transformation"],"normalizedKeywords":["프로덕트","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI로 제품 개발 방식이 어떻게 재편되는지 이해하는 데 직접적이다"},{"who":"엔지니어","why":"AI 친화적 플랫폼과 툴링을 어떻게 설계해야 하는지 배울 수 있다"},{"who":"조직 리더","why":"팀 구조와 생산성 모델을 AI 시대에 맞게 바꾸는 관점을 얻는다"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자"],"summary":"이 영상은 AI가 전통적인 제품 관리와 조직 운영 방식을 어떻게 바꾸는지 설명한다. 핵심 메시지는 앞으로 중요한 것은 대규모 분업이 아니라, 인간과 AI가 함께 작동하는 '풀스택 빌더' 모델이며, 그 안에서 인간은 비전·공감·커뮤니케이션·창의성·판단에 집중하고 나머지는 가능한 한 자동화해야 한다는 것이다.\n\n또한 LinkedIn이 실제로 어떤 방식으로 AI를 도입하는지 구체적으로 보여준다. 단순히 외부 도구를 붙이는 것이 아니라, 플랫폼을 AI가 추론할 수 있게 재구성하고, 조직의 맥락에 맞는 전용 에이전트를 만들며, 소규모의 pods 형태로 팀을 재편해야 속도와 적응력을 확보할 수 있다고 주장한다.","insights":["AI 시대의 핵심 경쟁력은 분업이 아니라 재조합 능력이다.","인간은 판단과 비전을 맡고, 반복 작업은 적극 자동화해야 한다.","외부 AI 툴은 그대로 꽂아서는 안 되고 내부 맥락에 맞게 재설계해야 한다.","큰 팀보다 작은 pods가 변화 속도에 더 잘 대응한다.","조직이 살아남으려면 변화 속도보다 응답 속도를 빠르게 만들어야 한다."],"keyClips":[{"clipId":"R-zCfLQD_84:c1:3-13","startSegmentIndex":3,"endSegmentIndex":13,"startTime":621.16,"endTime":710.16,"durationSeconds":89,"preview":"기술 변화의 충격","mustSee":false},{"clipId":"R-zCfLQD_84:c1:16-25","startSegmentIndex":16,"endSegmentIndex":25,"startTime":723,"endTime":825.88,"durationSeconds":102.9,"preview":"풀스택 빌더 정의","mustSee":true},{"clipId":"R-zCfLQD_84:c1:27-40","startSegmentIndex":27,"endSegmentIndex":40,"startTime":829.96,"endTime":963.56,"durationSeconds":133.6,"preview":"작은 팀의 우위","mustSee":false},{"clipId":"R-zCfLQD_84:c1:45-65","startSegmentIndex":45,"endSegmentIndex":65,"startTime":996.079,"endTime":1142.72,"durationSeconds":146.6,"preview":"AI 도입의 현실","mustSee":true},{"clipId":"R-zCfLQD_84:c1:68-75","startSegmentIndex":68,"endSegmentIndex":75,"startTime":1157.6,"endTime":1205.28,"durationSeconds":47.7,"preview":"신뢰 에이전트 필요","mustSee":true}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:08:05.409Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":2,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 3 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["artificial-intelligence","product-management","product-design","enterprise-software","agentic-workflows","growth","user-research","data-strategy","trust-and-safety","product-development"],"normalizedKeywords":["프로덕트","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI 에이전트를 제품 개발 프로세스에 어떻게 넣는지 배울 수 있음"},{"who":"기획자","why":"요구사항·리스크·성장 기회를 사전에 검토하는 방법이 유용함"},{"who":"엔지니어","why":"에이전트 오케스트레이션과 데이터 준비의 현실을 이해할 수 있음"},{"who":"디자인 리더","why":"디자인 도구와 작업 흐름이 팀별로 다르게 흘러가는 문제를 볼 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자","디자인 리더·CXO"],"summary":"이 구간은 LinkedIn이 사내에 여러 종류의 AI 에이전트를 구축하며 제품 개발 방식을 어떻게 바꾸고 있는지를 보여준다. 핵심은 단순히 외부 LLM을 붙이는 것이 아니라, 각 부서의 도메인 지식과 과거 사례, 금지해야 할 리스크까지 반영해 에이전트를 ‘맞춤형’으로 학습시키는 데 있다. Trust agent, growth agent, research agent, analyst agent 같은 도구가 각각 특정 업무를 맡고, 실제로 사내 의사결정과 spec 검토를 더 빠르게·더 날카롭게 만들고 있다.\n\n동시에 이 영상은 AI 도입의 본질이 연결성보다 데이터 선별과 맥락 설계에 있다는 점을 강하게 말한다. 모든 지식을 그냥 드라이브에 넣는 방식은 잘 작동하지 않고, ‘golden examples’를 골라 정제된 컨텍스트를 줘야 효과가 난다. 또 디자인 도구나 워크플로우처럼 팀마다 선호가 달라 표준화가 쉽지 않다는 현실, 그리고 아이디어 단계부터 코드-출시 단계까지 전반을 재편해야 진짜 생산성 향상이 나온다는 점도 강조한다.","insights":["AI 에이전트의 성능은 모델보다 회사의 맥락 설계가 좌우한다.","모든 지식을 넣는 것보다, 골든 예시를 선별하는 게 더 중요하다.","Trust와 Growth처럼 도메인별 에이전트가 더 강한 판단을 만든다.","도입 난점은 기술보다 팀별 도구 선호와 워크플로우 차이다.","코드 자동화보다 앞단의 기획·검증·리서치가 더 큰 레버리지다."],"keyClips":[{"clipId":"R-zCfLQD_84:c2:1-10","startSegmentIndex":1,"endSegmentIndex":10,"startTime":1200.63,"endTime":1260.6,"durationSeconds":60,"preview":"Trust 에이전트의 힘","mustSee":false},{"clipId":"R-zCfLQD_84:c2:12-18","startSegmentIndex":12,"endSegmentIndex":18,"startTime":1264.2,"endTime":1325.56,"durationSeconds":61.4,"preview":"성장 판단 자동화","mustSee":false},{"clipId":"R-zCfLQD_84:c2:19-27","startSegmentIndex":19,"endSegmentIndex":27,"startTime":1325.56,"endTime":1389.08,"durationSeconds":63.5,"preview":"리서치와 분석의 재편","mustSee":false},{"clipId":"R-zCfLQD_84:c2:33-49","startSegmentIndex":33,"endSegmentIndex":49,"startTime":1411.88,"endTime":1529.6,"durationSeconds":117.7,"preview":"도구보다 통합","mustSee":true},{"clipId":"R-zCfLQD_84:c2:50-71","startSegmentIndex":50,"endSegmentIndex":71,"startTime":1529.6,"endTime":1671.24,"durationSeconds":141.6,"preview":"작업을 쪼개라","mustSee":false},{"clipId":"R-zCfLQD_84:c2:72-89","startSegmentIndex":72,"endSegmentIndex":89,"startTime":1671.24,"endTime":1807.68,"durationSeconds":136.4,"preview":"데이터가 먼저다","mustSee":true}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:08:39.368Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":3,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 4 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["ai-adoption","product-management","change-management","internal-tools","full-stack-builder","org-transformation","team-productivity","leadership","career-growth"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 리더","why":"AI 도입을 조직에 확산시키는 방식과 지표 설계가 직접적 힌트가 됨"},{"who":"실무형 PM","why":"도구를 주는 것보다 업무 흐름과 피드백 루프를 설계하는 법을 배울 수 있음"},{"who":"디자인·개발 협업자","why":"디자이너와 PM이 더 빨리 실험하고 직접 기여하는 변화가 핵심이기 때문"},{"who":"주니어 인재","why":"APM 대신 풀스택 빌더형 교육으로 바뀌는 커리어 흐름을 이해할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","학생·주니어","디자인 리더·CXO"],"summary":"이 영상은 LinkedIn이 AI 도구를 사내에 도입하면서 겪는 실제 변화와, 그걸 조직 전체로 확산시키는 방법을 다룬다. 핵심 메시지는 단순히 툴을 배포하는 것으로는 아무것도 바뀌지 않고, 초기 학습 시간, 강한 피드백 루프, 팀 단위의 파일럿, 그리고 문화적 change management가 함께 가야 한다는 것이다.\n\n또한 AI의 효과가 평균적인 사람보다 상위 성과자에게 더 크게 나타날 수 있다는 관찰이 중요하다. LinkedIn은 이를 바탕으로 기존 APM을 대체할 풀스택 빌더형 APB 프로그램을 만들고, PM·디자이너·엔지니어가 한 pod 안에서 더 자율적으로 제품을 만들도록 조직 구조 자체를 바꾸고 있다.","insights":["AI 도입의 성패는 툴보다 change management에 달려 있다.","초기엔 속도보다 학습 시간 투자와 피드백 수집이 먼저다.","좋은 툴은 평균보다 상위 인재의 생산성을 더 크게 밀어준다.","조직 확산은 전사 배포보다 pod 단위 실험이 효과적이다.","APM의 미래는 코드·디자인·PM을 함께 다루는 빌더형 인재다."],"keyClips":[{"clipId":"R-zCfLQD_84:c3:1-2","startSegmentIndex":1,"endSegmentIndex":2,"startTime":1800.27,"endTime":1835.64,"durationSeconds":35.4,"preview":"초기 학습의 대가","mustSee":false},{"clipId":"R-zCfLQD_84:c3:14-24","startSegmentIndex":14,"endSegmentIndex":24,"startTime":1912.56,"endTime":1998.36,"durationSeconds":85.8,"preview":"파일럿의 실제 성과","mustSee":true},{"clipId":"R-zCfLQD_84:c3:25-32","startSegmentIndex":25,"endSegmentIndex":32,"startTime":1998.36,"endTime":2058.72,"durationSeconds":60.4,"preview":"pod형 확산 전략","mustSee":false},{"clipId":"R-zCfLQD_84:c3:34-39","startSegmentIndex":34,"endSegmentIndex":39,"startTime":2067.359,"endTime":2116.72,"durationSeconds":49.4,"preview":"실무가 먼저 바뀐다","mustSee":false},{"clipId":"R-zCfLQD_84:c3:41-53","startSegmentIndex":41,"endSegmentIndex":53,"startTime":2122.52,"endTime":2211.84,"durationSeconds":89.3,"preview":"풀스택 빌더 인재","mustSee":false},{"clipId":"R-zCfLQD_84:c3:57-76","startSegmentIndex":57,"endSegmentIndex":76,"startTime":2231.44,"endTime":2388.48,"durationSeconds":157,"preview":"변화관리의 본질","mustSee":true}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:09:11.363Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":4,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 5 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["ai-adoption","product-management","leadership","organizational-change","career-development","work-culture","enterprise-ai","product-strategy"],"normalizedKeywords":["리더십·매니지먼트","프로덕트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 리더","why":"AI 도입을 팀과 조직에 정착시키는 문화·평가 설계를 배울 수 있음"},{"who":"프로덕트 매니저","why":"PM 역할이 AI 시대에 어떻게 바뀌는지와 필요한 역량을 확인할 수 있음"},{"who":"사내 혁신 담당자","why":"툴 배포보다 행동 변화를 이끄는 운영 방식이 핵심임을 알 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자"],"summary":"이 대화는 AI 도구를 조직에 도입할 때 단순히 플랫폼과 툴을 준비하는 것만으로는 부족하다는 점을 강조한다. 실제 변화는 기대치 설정, 성과평가, 채용, 교육, 성공 사례 공유 같은 문화적 장치가 함께 작동할 때 일어난다고 말한다. 또한 LinkedIn에서는 일부 팀이 먼저 AI로 실제 성과를 내 보이고, 이를 조직 전체에 확산시키는 방식으로 행동 변화를 만들고 있다.\n\n화자는 모든 사람이 똑같이 '풀스택 빌더'가 될 필요는 없지만, 더 많은 사람들이 AI 도구를 직접 만지고 문제를 해결하는 방향으로 사고해야 한다고 본다. 오프 더 셸프 툴은 잘 안 맞고, 레거시 정보와 코드베이스 때문에 도입 난이도도 높지만, 기다리기보다 직접 시도하며 학습하는 조직이 결국 앞서게 된다는 메시지다. 모바일 전환기에 요구되던 변화와 비슷하게, 이번 변화도 시간이 걸리지만 일단 임계점을 넘으면 빠르게 확산된다고 본다.","insights":["AI 도입은 툴 설치가 아니라 행동 변화의 문제다.","성과평가와 채용 기준이 바뀌어야 사용이 늘어난다.","작은 성공 사례를 보여줘야 조직이 따라온다.","기다리기보다 직접 써보고 고치는 문화가 확산을 만든다.","전원 풀스택은 불필요하지만, 더 넓은 책임감은 필요하다."],"keyClips":[{"clipId":"R-zCfLQD_84:c4:3-13","startSegmentIndex":3,"endSegmentIndex":13,"startTime":2408.72,"endTime":2471.8,"durationSeconds":63.1,"preview":"문화가 먼저다","mustSee":false},{"clipId":"R-zCfLQD_84:c4:14-23","startSegmentIndex":14,"endSegmentIndex":23,"startTime":2471.8,"endTime":2515.88,"durationSeconds":44.1,"preview":"기대치와 평가변경","mustSee":false},{"clipId":"R-zCfLQD_84:c4:24-31","startSegmentIndex":24,"endSegmentIndex":31,"startTime":2515.88,"endTime":2570.04,"durationSeconds":54.2,"preview":"내부 성공사례 확산","mustSee":true},{"clipId":"R-zCfLQD_84:c4:33-45","startSegmentIndex":33,"endSegmentIndex":45,"startTime":2577.28,"endTime":2641.92,"durationSeconds":64.6,"preview":"직무 경계가 흐른다","mustSee":false},{"clipId":"R-zCfLQD_84:c4:55-74","startSegmentIndex":55,"endSegmentIndex":74,"startTime":2683.16,"endTime":2802.28,"durationSeconds":119.1,"preview":"제도와 자율의 결합","mustSee":true},{"clipId":"R-zCfLQD_84:c4:77-86","startSegmentIndex":77,"endSegmentIndex":86,"startTime":2813.2,"endTime":2880.32,"durationSeconds":67.1,"preview":"직접 써보게 하라","mustSee":false},{"clipId":"R-zCfLQD_84:c4:87-109","startSegmentIndex":87,"endSegmentIndex":109,"startTime":2880.32,"endTime":2998.6,"durationSeconds":118.3,"preview":"도입의 현실과 한계","mustSee":false}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:09:51.171Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":5,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 6 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["artificial-intelligence","product-management","leadership","organization-design","digital-transformation","career-growth","product-design","workflow","enterprise-ai"],"normalizedKeywords":["리더십·매니지먼트","프로덕트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 리더","why":"AI 도입이 제품 조직 구조와 역할을 어떻게 바꾸는지 배울 수 있음"},{"who":"조직 전환 담당자","why":"큰 조직에서 새 도구와 문화를 어떻게 확산할지 참고할 수 있음"},{"who":"PM/디자이너","why":"역할 경계를 넘나드는 커리어 전환과 역량 확장 관점을 얻을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","디자인 리더·CXO","지식노동자 일반"],"summary":"이 부분에서는 AI가 전통적인 제품 관리와 조직 운영 방식을 어떻게 바꾸는지에 대해, Tomer Cohen이 실제 조직 경험을 바탕으로 설명한다. 그는 엔지니어링·디자인·PM·BD 같은 기존 기능의 경계를 넘어, 이미 조직 안에 있는 사람들 중 누가 더 유연하게 역할을 넘나들 수 있는지 찾아야 한다고 말한다. 특히 디자인은 새 도구를 익히는 데 상대적으로 어려움이 있지만, 전반적으로는 직무 라벨보다 성장 마인드셋과 실행 의지가 더 중요하다고 강조한다.\n\n또한 대규모 조직 변화를 성공시키려면 플랫폼과 도구에 대한 투자뿐 아니라, 사람들을 변화 과정에 어떻게 끌어들이는지에 대한 문화 설계가 핵심이라고 조언한다. 작은 팀으로 시작하되 조직 전체에 충분한 가시성을 주고, 성과를 한 번에 기대하지 말고 장기적 진화로 접근해야 한다는 점도 반복해서 강조한다. 마지막으로 그는 기다리지 말고 지금 시작하되, 목표는 크고 과정은 꾸준히 측정·공유하라고 권한다.","insights":["AI 시대의 역할 전환은 직무보다 마인드셋이 더 중요하다.","조직 안에는 이미 여러 기능을 넘나들 수 있는 인재가 있다.","대규모 변화는 도구보다 문화와 확산 방식이 성패를 가른다.","생산성 혁신은 단기간 성과가 아니라 장기 투자로 온다.","경쟁력은 완성된 상태가 아니라 지속적 개선 속도에서 나온다."],"keyClips":[{"clipId":"R-zCfLQD_84:c5:1-21","startSegmentIndex":1,"endSegmentIndex":21,"startTime":3000.07,"endTime":3166.24,"durationSeconds":166.2,"preview":"역할 경계가 무너진다","mustSee":false},{"clipId":"R-zCfLQD_84:c5:22-40","startSegmentIndex":22,"endSegmentIndex":40,"startTime":3166.24,"endTime":3305.52,"durationSeconds":139.3,"preview":"변화는 문화가 만든다","mustSee":true},{"clipId":"R-zCfLQD_84:c5:44-54","startSegmentIndex":44,"endSegmentIndex":54,"startTime":3326.64,"endTime":3403.44,"durationSeconds":76.8,"preview":"지금 시작하라","mustSee":true},{"clipId":"R-zCfLQD_84:c5:59-74","startSegmentIndex":59,"endSegmentIndex":74,"startTime":3422.16,"endTime":3573.64,"durationSeconds":151.5,"preview":"책이 말하는 원리","mustSee":false}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:53:33.661Z","keyClipsTotalSec":1527},{"videoId":"R-zCfLQD_84","chunkIndex":6,"totalChunks":7,"title":"Why AI is disrupting traditional product management | Tomer Cohen (LinkedIn CPO) — Part 7 of 7","thumbnail":"https://i.ytimg.com/vi/R-zCfLQD_84/maxresdefault.jpg","duration":4052,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=R-zCfLQD_84","keywords":["product-management","ai","voice-ai","leadership","career-change","growth-mindset","linkedin","consumer-tech","product-thinking"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 매니저","why":"AI가 제품 경험을 어떻게 바꾸는지와 제품 감각을 배울 수 있음"},{"who":"창업자","why":"새로운 문제를 찾고 다음 커리어/사업을 설계하는 관점을 얻음"},{"who":"지식노동자","why":"성장 마인드와 커리어 전환을 바라보는 태도를 참고할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","지식노동자 일반"],"summary":"이 구간은 일상 속 제품 아이디어를 어떻게 떠올리고, AI가 실제 제품 경험을 어떻게 바꾸는지에 대한 Tomer Cohen의 관점을 담고 있다. 그는 차 안에서 음성 AI를 쓰는 경험을 예로 들며, 버튼 하나로 'AI 친구'를 호출하는 식의 마찰 제거가 사용자 경험을 크게 바꿀 것이라고 본다. 동시에 Tesla의 Grok 탑재 사례를 보고 AI가 이미 현실에 들어왔지만, 아직은 브랜드·성격·사용 맥락에 따라 경험이 갈린다고 짚는다.\n\n후반부에서는 성장 마인드셋, 'becoming is better than being'이라는 태도, 그리고 14년간의 LinkedIn 여정을 돌아보며 다음 도전을 준비하는 마음가짐을 말한다. 그는 커리어를 직함이 아니라 학습의 밀도로 보고, 변화에 대한 선호와 지속적 성장 자체를 삶의 기준으로 삼는다. 전체적으로 제품 감각, AI 경험 설계, 그리고 장기 커리어 전환의 태도를 함께 보여주는 인터뷰다.","insights":["좋은 제품 아이디어는 '마찰 제거'에서 시작된다.","AI의 가치는 정보가 아니라 상호작용의 자연스러움에 있다.","새 기능이 아니라 사용자 습관에 붙을 때 제품이 된다.","커리어는 직함보다 학습량과 성장의 속도로 평가할 수 있다.","오래 한 일을 끝낼 때는 성취보다 애착을 먼저 정리해야 한다."],"keyClips":[{"clipId":"R-zCfLQD_84:c6:7-15","startSegmentIndex":7,"endSegmentIndex":15,"startTime":3640.72,"endTime":3703.84,"durationSeconds":63.1,"preview":"마찰 없는 AI 경험","mustSee":true},{"clipId":"R-zCfLQD_84:c6:16-25","startSegmentIndex":16,"endSegmentIndex":25,"startTime":3703.84,"endTime":3758.4,"durationSeconds":54.6,"preview":"AI는 이미 차 안에","mustSee":false},{"clipId":"R-zCfLQD_84:c6:32-40","startSegmentIndex":32,"endSegmentIndex":40,"startTime":3786.76,"endTime":3852.96,"durationSeconds":66.2,"preview":"성장은 상태가 아니다","mustSee":false},{"clipId":"R-zCfLQD_84:c6:41-55","startSegmentIndex":41,"endSegmentIndex":55,"startTime":3852.96,"endTime":3973.32,"durationSeconds":120.4,"preview":"LinkedIn 이후의 선택","mustSee":true},{"clipId":"R-zCfLQD_84:c6:56-59","startSegmentIndex":56,"endSegmentIndex":59,"startTime":3973.32,"endTime":4013.76,"durationSeconds":40.4,"preview":"빌더의 애착과 집착","mustSee":true}],"curatedSegments":[{"segmentIndex":59,"text":"And then you apply that to building products, and you realize that in order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":407.92,"endTime":418.92,"durationSeconds":11,"level":"C1","overallScore":9,"rationale":"핵심 주장과 고급 표현이 모두 뛰어남."},{"segmentIndex":71,"text":"You never see success in the launch itself.\"So, really, the work itself is not complex, but the process we made very complex.","startTime":500.76,"endTime":507.88,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"성공 지점과 복잡성 본질을 찌름."},{"segmentIndex":65,"text":"That is a really interesting insight that the top performers are finding the most success cuz there's always been this question, is AI going to just make people that are not amazing more amazing or is it going to make amazing people even more amazing?","startTime":2292.08,"endTime":2302.56,"durationSeconds":10,"level":"C1","overallScore":8.8,"rationale":"AI 효과의 핵심 질문을 던짐."},{"segmentIndex":70,"text":"So, one of the things I've said is like if you're looking for a formal re- org or declaration to start building differently, you're waiting too long.","startTime":2767.08,"endTime":2775.64,"durationSeconds":9,"level":"B2","overallScore":9,"rationale":"변화는 기다리지 말라는 핵심 조언."},{"segmentIndex":34,"text":"But when you are trying to transform a large organization you want to have this impatient about the goal and you have to have a high ambition but being very thoughtful and patient about how you bring it to life and the key things you have to invest in.","startTime":3251.44,"endTime":3267.24,"durationSeconds":16,"level":"C1","overallScore":9,"rationale":"변혁의 속도와 실행 태도를 깊게 짚음."},{"segmentIndex":73,"text":"Like really finding great explanations for how things happen and then building on top of that uh your next uh iterations and this book really pushes on the idea of explanations that only once we have a clear understanding of why things happen then we can have breakthroughs on top of that.","startTime":3545.48,"endTime":3561.88,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"설명 이해와 혁신의 관계를 제시."},{"segmentIndex":1,"text":"When we look at the skills required to do your job, by 2030, they will change by 70%. So, whether or not you're looking to change your job, your job is changing.","startTime":1.71,"endTime":5.4,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"미래 변화 통찰이 크고 표현도 유용함."},{"segmentIndex":3,"text":"In order to stay competitive, you actually have to go back to some first principles, go back to the drawing board, and reimagine what it means to be building.","startTime":8.96,"endTime":15.68,"durationSeconds":7,"level":"C1","overallScore":8.2,"rationale":"원칙 재고를 제시해 통찰·표현 모두 높음."},{"segmentIndex":5,"text":">> We call it the full-stack builder [music] model. The goal itself is to empower great builders to take their idea and to take it to market, regardless of their role in the stack and which team they're on.","startTime":24.08,"endTime":33.36,"durationSeconds":9,"level":"C1","overallScore":8.2,"rationale":"모델 핵심 설명과 실무 표현이 풍부함."},{"segmentIndex":11,"text":">> There's always been this question, is AI going to just make people that are not amazing more amazing, or is it going to make amazing people even more amazing?","startTime":56.12,"endTime":61.44,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"AI 효과의 본질적 질문을 던짐."},{"segmentIndex":48,"text":"It's not about what it does for us, it's about what it enables us to do. And now we have this amazing opportunity, in my mind, to make it about meritocracy.","startTime":338.68,"endTime":343.48,"durationSeconds":5,"level":"C1","overallScore":8,"rationale":"대조 구조로 기술 철학을 선명히 제시함."},{"segmentIndex":49,"text":"And now we have this real opportunity to collapse the stack back up, go back to craftsmanship, rethink the product development life cycle, which is where the full-stack builder model comes to life.","startTime":343.48,"endTime":347.28,"durationSeconds":4,"level":"C1","overallScore":8.2,"rationale":"핵심 비전과 고급 실무 표현이 풍부함."},{"segmentIndex":51,"text":"And I want to put this in context where we're entering this phase where the time constant of change is far greater than the time constant of response.","startTime":351,"endTime":360.04,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"변화 속도 프레임이 통찰적이고 표현도 좋음."},{"segmentIndex":64,"text":"That's kind of that's basically it. But what happens at many at-scale companies, LinkedIn included and many other companies, over time, that process became very complex very quickly. So, what happened?","startTime":440.84,"endTime":452.84000000000003,"durationSeconds":12,"level":"C1","overallScore":7.8,"rationale":"대기업에서 복잡성 증가 원인 제시."},{"segmentIndex":70,"text":"But when you add the whole thing together, you're like,\"Oh my god, this is why it takes to build a small feature multiple teams, multiple code bases, multiple sprints, just to get it out to launch, and not talk about iterating, which is actually where you see success.","startTime":487.44,"endTime":500.76,"durationSeconds":13,"level":"C1","overallScore":8.2,"rationale":"복잡성의 비용을 생생하게 드러냄."},{"segmentIndex":73,"text":"Because somebody has to do all those sub-steps. So, what happened is you actually move from process complexity to organizational complexity as well.","startTime":511.92,"endTime":521.08,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"과정 복잡성이 조직 복잡성으로 확장됨."},{"segmentIndex":25,"text":"And then uh ultimately what I think is the most important trait for a builder is judgment. That's, you know, some people call it test making but it's making high quality decisions in what is complex, ambiguous situations.","startTime":813.8,"endTime":825.88,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"핵심 덕목을 정의하는 통찰 문장."},{"segmentIndex":37,"text":"We assemble a team ideally a full-stack builder is coming together and you know, it's less about can I have an engineer, design, PM working together and trying to combine this trio, looking to folks who can flex across and then they tackle something for a quarter or so and then we kind of reassemble those to different pods.","startTime":908.959,"endTime":925.8389999999999,"durationSeconds":17,"level":"C1","overallScore":8.2,"rationale":"운영 방식 설명이 구체적이고 실용적."},{"segmentIndex":40,"text":"Yeah, it's not that you have to break the model. I think the model is broken. It's just this uh pace of change is helping us realize it.","startTime":956.16,"endTime":963.56,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"강한 한줄 통찰로 인상적임."},{"segmentIndex":49,"text":"And what you'll see that ultimately, I don't think there's going to be a winner takes all because the starting point of, you know, the customer or the user will dictate a lot how simple they are for that use case. Super interesting.","startTime":1517.8,"endTime":1529.6,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"시장 구조와 사용자 적합성 통찰이 큼."}],"generatedAt":"2026-06-25T00:10:25.390Z","keyClipsTotalSec":1527}]}