{"success":true,"count":8,"items":[{"videoId":"eh8bcBIAAFo","chunkIndex":0,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 1 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","ai","product-design","engineering","prototyping","workflow","design-leadership","future-of-work"],"normalizedKeywords":["디자인","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"프로덕트 디자이너","why":"AI로 인해 디자이너의 역할과 작업 방식이 어떻게 바뀌는지 직접 다룸"},{"who":"디자인 리더","why":"채용, 역할 재정의, 팀 내 디자인 방향 설정에 대한 시사점이 큼"},{"who":"엔지니어","why":"엔지니어링 속도 변화가 디자인 협업 방식에 미치는 영향을 이해할 수 있음"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","엔지니어·개발자"],"summary":"이 영상은 AI 시대에 디자인 프로세스가 어떻게 무너지고 다시 재편되는지에 대한 Jenny Wen의 관점을 다룬다. 그녀는 전통적인 '리서치-발산-수렴' 중심의 디자인 프로세스가 더 이상 유효하지 않다고 보고, 이제 디자이너는 아름다운 목업을 만드는 사람보다 엔지니어의 빠른 실행을 돕고 방향을 제시하는 사람에 가까워졌다고 말한다.\n\n또한 디자인 일은 점점 두 갈래로 나뉜다고 설명한다. 하나는 구현과 런칭을 밀어주는 실행 보조 역할이고, 다른 하나는 2년짜리 장기 비전 대신 3~6개월 단위의 방향성을 만드는 역할이다. 핵심은 기술 변화가 너무 빨라져서 디자인이 더 이상 고정된 절차를 지키는 직업이 아니라, 빠르게 바뀌는 시스템 안에서 우선순위와 방향을 정하는 직업이 되고 있다는 점이다.","insights":["전통적 디자인 프로세스는 AI·코딩 속도에 맞지 않는다.","디자이너의 가치는 목업보다 실행 정렬과 방향 제시에 있다.","미래 비전은 장기 청사진보다 짧은 프로토타입이 더 유효하다.","속도가 빨라질수록 디자이너는 '무엇을 만들지'를 결정해야 한다.","디자인 툴보다 엔지니어링 툴 변화가 먼저 디자인을 바꾼다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c0:47-55","startSegmentIndex":47,"endSegmentIndex":55,"startTime":295.12,"endTime":392.639,"durationSeconds":97.5,"preview":"프로세스의 붕괴","mustSee":true},{"clipId":"eh8bcBIAAFo:c0:56-59","startSegmentIndex":56,"endSegmentIndex":59,"startTime":392.639,"endTime":436.08,"durationSeconds":43.4,"preview":"실행 보조로의 이동","mustSee":false},{"clipId":"eh8bcBIAAFo:c0:60-68","startSegmentIndex":60,"endSegmentIndex":68,"startTime":436.08,"endTime":516.08,"durationSeconds":80,"preview":"짧아진 비전의 시대","mustSee":true},{"clipId":"eh8bcBIAAFo:c0:71-74","startSegmentIndex":71,"endSegmentIndex":74,"startTime":530.24,"endTime":584.64,"durationSeconds":54.4,"preview":"디자이너의 새 무기","mustSee":false}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T11:52:04.074Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":1,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 2 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","product-design","ai-tools","enterprise-ai","prototyping","user-research","engineering","workflow","claude","human-ai-collaboration"],"normalizedKeywords":["디자인","엔지니어링","프로덕트"],"targetAudience":[{"who":"프로덕트 디자이너","why":"AI 시대에 디자인 프로세스와 디자이너 역할이 어떻게 바뀌는지 직접 배울 수 있음"},{"who":"디자인 리더","why":"팀의 실행 방식, 협업 구조, 역할 재편을 어떻게 설계할지 참고가 됨"},{"who":"엔지니어","why":"디자이너와 함께 제품을 빠르게 만들고 다듬는 협업 방식이 구체적으로 나옴"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","엔지니어·개발자"],"summary":"이 영상은 Anthropic의 Jenny Wen이 말하는 '디자인 프로세스의 재편'을 다룬다. 전통적인 디자인 작업(리서치, 목업, 프로토타이핑)에만 머무는 방식은 AI 모델의 비결정성과 빠른 실험 환경에서는 한계가 있으며, 실제 모델과 실제 사용자 데이터를 바탕으로 빠르게 만들고 배우는 방식이 더 적합하다고 주장한다.\n\n또한 디자이너의 역할이 단순히 mock을 전달하는 데서 끝나지 않고, 엔지니어와 함께 방향을 맞추고, 화면을 다듬고, 때로는 코드까지 직접 만지는 쪽으로 확장되고 있음을 설명한다. Anthropic 내부에서의 일상도 함께 보여주는데, 모델 개발·프로토타입·리서치·사내 토론이 매우 빠르게 돌아가서 디자이너가 계속 정보를 따라가며 우선순위를 잡아야 한다는 점이 강조된다.","insights":["AI 시대엔 목업보다 실제 모델로 빨리 검증하는 쪽이 유리하다.","비결정적 시스템은 미리 다 설계할 수 없고, 써보며 배워야 한다.","디자이너의 핵심 역할은 이제 '전달'보다 '함께 실행'에 가깝다.","디자인 일의 비중은 목업 중심에서 협업·구현 중심으로 이동했다.","좋은 AI 제품은 처음 의도보다 실제 사용 패턴에서 정의된다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c1:2-6","startSegmentIndex":2,"endSegmentIndex":6,"startTime":602.399,"endTime":705.519,"durationSeconds":103.1,"preview":"디자인 프로세스의 균열","mustSee":true},{"clipId":"eh8bcBIAAFo:c1:9-13","startSegmentIndex":9,"endSegmentIndex":13,"startTime":715.6,"endTime":762.72,"durationSeconds":47.1,"preview":"실제로 써봐야 안다","mustSee":false},{"clipId":"eh8bcBIAAFo:c1:17-24","startSegmentIndex":17,"endSegmentIndex":24,"startTime":791.12,"endTime":893.44,"durationSeconds":102.3,"preview":"내부 정보가 곧 경쟁력","mustSee":false},{"clipId":"eh8bcBIAAFo:c1:32-37","startSegmentIndex":32,"endSegmentIndex":37,"startTime":946.32,"endTime":1019.279,"durationSeconds":73,"preview":"기획과 구현의 결합","mustSee":false},{"clipId":"eh8bcBIAAFo:c1:40-52","startSegmentIndex":40,"endSegmentIndex":52,"startTime":1029.76,"endTime":1207.039,"durationSeconds":177.3,"preview":"클로드 중심의 작업 방식","mustSee":true}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:46:40.062Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":2,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 3 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","ai","product-design","figma","coding-tools","ux","design-systems","workflow","taste","leadership"],"normalizedKeywords":["디자인","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"프로덕트 디자이너","why":"AI 시대에도 Figma와 디자인 판단이 왜 여전히 중요한지 배울 수 있음"},{"who":"디자인 리더","why":"빠르게 쌓이는 출시 속도 속에서 품질과 신뢰를 지키는 법을 얻을 수 있음"},{"who":"엔지니어","why":"디자이너와 협업하며 디자인 원칙을 코드로 옮기는 방법을 참고할 수 있음"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","엔지니어·개발자"],"summary":"이 영상은 AI가 디자인과 제품 개발의 많은 부분을 빠르게 흡수해 가는 상황에서, 디자이너의 역할이 무엇으로 남는지에 대한 대화를 중심으로 진행된다. Jenny Wen은 Figma가 여전히 중요한 이유를 '여러 방향을 빠르게 탐색하고, 미세한 시각·인터랙션 차이를 실험하는 공간'이라는 점에서 설명하며, 코드 기반 도구가 아직 그 탐색을 잘 대체하지 못한다고 말한다.\n\n또한 디자이너가 엔지니어를 통제하는 게 아니라 원칙과 맥락을 전달해 더 나은 결정을 돕는 방향으로 바뀌어야 한다고 강조한다. 품질과 신뢰는 모든 것을 완벽하게 통제해서가 아니라, 연구 프리뷰처럼 기대치를 명확히 하고 빠르게 피드백을 반영하며 계속 개선하는 방식으로 만든다고 주장한다. 마지막으로 AI가 taste와 judgment를 더 잘하게 되더라도, 무엇을 만들지 결정하고 사람들 사이의 충돌을 조정하는 판단은 여전히 인간의 몫으로 남는다고 본다.","insights":["AI가 강해질수록 디자인의 본질은 '탐색'과 '판단'으로 남는다.","코드 도구는 선형적이라 여러 방향을 동시에 보는 데 약하다.","품질은 완벽함보다 빠른 공개와 빠른 개선으로 신뢰를 만든다.","디자이너의 역할은 통제가 아니라 원칙을 전파하는 것이다.","AI가 제안해도 무엇을 만들지 정하는 최종 판단은 인간 몫이다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c2:1-19","startSegmentIndex":1,"endSegmentIndex":19,"startTime":1202.07,"endTime":1344.559,"durationSeconds":142.5,"preview":"Figma가 남는 이유","mustSee":false},{"clipId":"eh8bcBIAAFo:c2:20-35","startSegmentIndex":20,"endSegmentIndex":35,"startTime":1344.559,"endTime":1459.36,"durationSeconds":114.8,"preview":"엔지니어와 협업법","mustSee":false},{"clipId":"eh8bcBIAAFo:c2:36-55","startSegmentIndex":36,"endSegmentIndex":55,"startTime":1459.36,"endTime":1656.72,"durationSeconds":197.4,"preview":"신뢰는 속도로 만든다","mustSee":true},{"clipId":"eh8bcBIAAFo:c2:56-69","startSegmentIndex":56,"endSegmentIndex":69,"startTime":1656.72,"endTime":1803.039,"durationSeconds":146.3,"preview":"인간 판단의 자리","mustSee":true}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:47:07.632Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":3,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 4 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["ai-design","chatbot","user-interface","product-design","leadership","management","generative-ai","workflows","claude","career"],"normalizedKeywords":["디자인","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 디자이너","why":"AI 시대에 디자인 프로세스와 인터페이스가 어떻게 바뀌는지 직접적 통찰을 준다"},{"who":"디자인 리더","why":"IC와 매니저 역할 변화, 팀 방향 설정 방식이 핵심 주제다"},{"who":"프로덕트 매니저","why":"AI가 판단과 의사결정 레이어를 어떻게 바꾸는지 이해하는 데 유용하다"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","프로덕트 매니저·기획자"],"summary":"이 영상은 AI가 제품 설계와 디자인 업무의 방식을 어떻게 바꾸고 있는지, 그리고 그 변화 속에서 디자이너와 매니저의 역할이 무엇으로 재정의되는지를 다룬다. 화자는 AI가 점점 더 좋은 판단과 추천을 내릴 수 있게 되더라도, 최종적인 책임과 방향 설정은 여전히 사람에게 남을 가능성이 크다고 본다. 동시에 챗봇과 터미널이 완전히 사라지기보다는, 특정 작업을 위한 더 직접적인 UI와 함께 공존할 것이라고 전망한다.\n\n또한 자신이 Anthropic에서 IC와 매니저 역할을 오가며 느낀 점을 공유하면서, 지금의 디자인 팀은 예전보다 훨씬 빠르게 변화하고 있기 때문에 관리자는 단순한 사람 관리자가 아니라 팀의 방향과 작업을 함께 이해하는 존재여야 한다고 말한다. 그래서 디자인 리더는 오히려 현업 IC처럼 손을 더럽혀야 현재의 도구와 흐름을 제대로 이해할 수 있다는 메시지가 강하게 드러난다.","insights":["AI가 좋아질수록 '판단 책임'의 중요성은 더 커진다.","챗봇은 임시 UI가 아니라 유연성을 여는 핵심 인터페이스다.","미래의 유용한 매니저는 사람관리와 방향제시를 함께 해야 한다.","좋은 디자인 리더는 지금의 도구를 직접 써보며 감각을 유지해야 한다.","IC 경험은 관리 역량을 약화시키지 않고 오히려 강화할 수 있다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c3:1-12","startSegmentIndex":1,"endSegmentIndex":12,"startTime":1800.31,"endTime":1899.919,"durationSeconds":99.6,"preview":"AI 판단과 책임","mustSee":false},{"clipId":"eh8bcBIAAFo:c3:13-33","startSegmentIndex":13,"endSegmentIndex":33,"startTime":1899.919,"endTime":2082.8,"durationSeconds":182.9,"preview":"챗봇의 다음 형태","mustSee":true},{"clipId":"eh8bcBIAAFo:c3:43-59","startSegmentIndex":43,"endSegmentIndex":59,"startTime":2136.069,"endTime":2285.76,"durationSeconds":149.7,"preview":"IC로 돌아간 이유","mustSee":false},{"clipId":"eh8bcBIAAFo:c3:60-70","startSegmentIndex":60,"endSegmentIndex":70,"startTime":2285.76,"endTime":2400.079,"durationSeconds":114.3,"preview":"미래의 매니저상","mustSee":true}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:48:00.179Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":4,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 5 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","product-design","leadership","hiring","ai-assistants","workflow","career-growth","management","ux"],"normalizedKeywords":["디자인","리더십·매니지먼트","커리어·성장"],"targetAudience":[{"who":"프로덕트 디자이너","why":"디자인 역할 변화와 필요한 역량을 구체적으로 배울 수 있음"},{"who":"디자인 리더","why":"IC 복귀, 피드백 문화, 채용 기준 변화가 직접적으로 다뤄짐"},{"who":"학생·주니어","why":"초기 커리어에서 어떤 태도와 역량이 가치 있는지 파악 가능"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","학생·주니어"],"summary":"이 영상은 Claude의 디자인 리더 Jenny Wen이 디자인 역할의 변화와 그에 맞는 일하는 방식, 채용 기준을 이야기한다. 특히 리더에서 IC 디자이너로 돌아가며 느낀 어려움(비판을 반복적으로 받는 일, 크리틱의 취약함)을 바탕으로, 디자인이 더 이상 순수한 시각 작업이나 사람 관리에만 머물 수 없다고 본다.\n\n또한 Claude의 co-work 경험을 예로 들어, 좋은 제품은 우연히 10일 만에 나온 것이 아니라 긴 프로토타이핑과 탐색 끝에 적절한 순간에 출시된 것이라고 설명한다. 마지막으로는 앞으로의 디자인 채용에서 필요한 사람을 '강한 제너럴리스트', '깊은 스페셜리스트', '배움이 빠른 초년차 인재'로 나누어 제시하며, 변화가 빠른 환경에서는 유연성과 학습 능력이 핵심이라고 강조한다.","insights":["디자인은 이제 사람관리보다 적응력과 다기능성이 중요하다.","크리틱을 견디는 능력은 디자이너의 핵심 근육이다.","성공한 제품 뒤에는 긴 탐색과 짧은 실행이 함께 있다.","채용은 '경력'보다 변화 속에서의 학습력과 회복력을 봐야 한다.","초년차 인재의 빈칸 같은 유연성이 오히려 큰 자산이 된다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c4:1-5","startSegmentIndex":1,"endSegmentIndex":5,"startTime":2401.91,"endTime":2462.8,"durationSeconds":60.9,"preview":"IC 복귀의 어려움","mustSee":false},{"clipId":"eh8bcBIAAFo:c4:9-19","startSegmentIndex":9,"endSegmentIndex":19,"startTime":2488.96,"endTime":2582.319,"durationSeconds":93.4,"preview":"10일의 진짜 의미","mustSee":false},{"clipId":"eh8bcBIAAFo:c4:21-31","startSegmentIndex":21,"endSegmentIndex":31,"startTime":2586.8,"endTime":2671.119,"durationSeconds":84.3,"preview":"co-work의 본질","mustSee":false},{"clipId":"eh8bcBIAAFo:c4:42-60","startSegmentIndex":42,"endSegmentIndex":60,"startTime":2771.52,"endTime":2964.079,"durationSeconds":192.6,"preview":"새 채용 기준","mustSee":true},{"clipId":"eh8bcBIAAFo:c4:61-64","startSegmentIndex":61,"endSegmentIndex":64,"startTime":2964.079,"endTime":3000.4,"durationSeconds":36.3,"preview":"깊이의 여러 형태","mustSee":false}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:49:08.894Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":5,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 6 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","leadership","management","career-growth","product-design","creative-work","team-culture","ai-design"],"normalizedKeywords":["디자인","리더십·매니지먼트","커리어·성장"],"targetAudience":[{"who":"주니어 디자이너","why":"실제 작업을 만들고 공유하며 눈에 띄는 성장 전략을 얻을 수 있음"},{"who":"시니어 디자이너","why":"기술 도구를 어디까지 익혀야 하는지 판단하는 데 도움 됨"},{"who":"디자인 리더","why":"저레버리지처럼 보이는 행동이 리더십의 신뢰를 만드는 법을 배울 수 있음"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","학생·주니어"],"summary":"이 구간은 디자인 인재가 어떻게 성장하고, 어떤 리더십이 팀을 강하게 만드는지에 대한 조언을 중심으로 전개된다. 주니어 디자이너에게는 이론보다 실제로 만들고 공유하는 태도, 커뮤니티 속에서 작업을 드러내는 방식이 중요하다고 강조한다. 시니어 디자이너에게는 코딩을 완전히 배워 개발자가 되기보다, 구현 도구와 기술 언어를 이해하는 수준으로 툴킷을 넓히는 것이 유효하다고 말한다.\n\n또한 관리자의 시간 사용에 대한 관점을 뒤집는다. 흔히 저레버리지로 분류되는 잡무라도 리더가 직접 제품을 테스트하고, 버그를 재현하고, 로그를 보며 팀과 같이 파고들면 오히려 신뢰와 제품 감각을 높이는 고레버리지 행동이 될 수 있다고 본다. 마지막으로 팀원끼리 가벼운 농담과 로스팅이 오가는 분위기는 불안이 없는 심리적 안전감의 신호이며, 좋은 팀 문화의 징후라고 설명한다.","insights":["주니어는 이론보다 실제 작품으로 차별화된다.","디자이너는 코더가 되기보다 도구 감각을 넓혀야 한다.","리더의 '잡무'는 직접 하면 가장 큰 신뢰 자산이 된다.","제품을 몸으로 아는 리더가 팀의 안전감도 만든다.","편하게 농담할 수 있는 분위기가 팀 신뢰의 신호다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c5:6-15","startSegmentIndex":6,"endSegmentIndex":15,"startTime":3032.559,"endTime":3171.119,"durationSeconds":138.6,"preview":"주니어 성장의 핵심","mustSee":false},{"clipId":"eh8bcBIAAFo:c5:16-18","startSegmentIndex":16,"endSegmentIndex":18,"startTime":3171.119,"endTime":3242.8,"durationSeconds":71.7,"preview":"디자이너와 기술감각","mustSee":false},{"clipId":"eh8bcBIAAFo:c5:24-39","startSegmentIndex":24,"endSegmentIndex":39,"startTime":3282.48,"endTime":3473.52,"durationSeconds":191,"preview":"저레버리지의 반전","mustSee":true},{"clipId":"eh8bcBIAAFo:c5:40-53","startSegmentIndex":40,"endSegmentIndex":53,"startTime":3473.52,"endTime":3606.72,"durationSeconds":133.2,"preview":"심리적 안전의 신호","mustSee":false}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:49:48.713Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":6,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 7 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["leadership","management","design","product-design","ai","frontend","vc","frameworks","startup","career"],"normalizedKeywords":["리더십·매니지먼트","디자인","비즈니스·전략"],"targetAudience":[{"who":"디자인 리더","why":"심리적 안전과 높은 기준을 함께 만드는 매니지먼트 감각을 배울 수 있음"},{"who":"프로덕트 디자이너","why":"불명확한 아이디어를 UX와 스토리로 구체화하는 관점을 얻을 수 있음"},{"who":"투자자","why":"초기 아이디어의 잠재력을 보는 'legibility' 사고법이 유용함"}],"normalizedAudience":["디자인 리더·CXO","프로덕트 디자이너","투자자·VC"],"summary":"이 영상은 Anthropic의 디자인 리더 Jenny Wen이 팀을 이끄는 방식과, AI 시대의 디자인이 어떻게 바뀌고 있는지를 중심으로 이야기한다. 좋은 매니저는 팀원과 친해지는 것보다 심리적 안전을 만들되, 동시에 매우 높은 기준을 분명히 해야 하며, 두 가지는 오히려 서로를 강화한다고 말한다. 또한 'legibility framework'를 통해, 겉으로는 잘 안 보이지만 에너지가 있는 불명확한 아이디어를 포착하고, 이를 스토리와 UX로 번역하는 것이 디자이너의 중요한 역할이라고 주장한다.\n\n후반부에서는 Anthropic 디자인팀의 문화와 채용 방향, 그리고 자신이 추천하는 책을 짧게 소개한다. 전체적으로 이 영상은 좋은 리더십의 원리와, frontier lab에서 디자이너가 어떤 감각으로 제품의 형태를 만들어야 하는지에 대한 실전적인 통찰을 제공한다.","insights":["좋은 매니지먼트는 친밀함보다 심리적 안전과 고기준의 결합이다.","팀이 안전하다고 느낄수록, 피드백은 더 직접적이어도 된다.","디자이너는 명확한 아이디어보다 '잘 안 보이는 에너지'를 먼저 봐야 한다.","불명확한 프로토타입은 무시할 대상이 아니라 해석할 대상이다.","AI 시대의 디자인은 결과물만이 아니라 사고방식의 번역이다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c6:1-9","startSegmentIndex":1,"endSegmentIndex":9,"startTime":3601.589,"endTime":3707.359,"durationSeconds":105.8,"preview":"심리안전과 고기준","mustSee":true},{"clipId":"eh8bcBIAAFo:c6:13-18","startSegmentIndex":13,"endSegmentIndex":18,"startTime":3723.44,"endTime":3837.92,"durationSeconds":114.5,"preview":"불명확한 아이디어 읽기","mustSee":false},{"clipId":"eh8bcBIAAFo:c6:19-28","startSegmentIndex":19,"endSegmentIndex":28,"startTime":3837.92,"endTime":3946.559,"durationSeconds":108.6,"preview":"프로토타입에서 본질 찾기","mustSee":true},{"clipId":"eh8bcBIAAFo:c6:30-38","startSegmentIndex":30,"endSegmentIndex":38,"startTime":3948,"endTime":4041.68,"durationSeconds":93.7,"preview":"초기 신호를 보는 법","mustSee":false},{"clipId":"eh8bcBIAAFo:c6:41-51","startSegmentIndex":41,"endSegmentIndex":51,"startTime":4058,"endTime":4151.279,"durationSeconds":93.3,"preview":"팀 문화와 채용","mustSee":false}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:52:17.679Z","keyClipsTotalSec":1822},{"videoId":"eh8bcBIAAFo","chunkIndex":7,"totalChunks":8,"title":"The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — Part 8 of 8","thumbnail":"https://i.ytimg.com/vi/eh8bcBIAAFo/maxresdefault.jpg","duration":4645,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=eh8bcBIAAFo","keywords":["design","product-design","ai-tools","career","leadership","creativity","memoir","lifestyle","product-feedback"],"normalizedKeywords":["디자인","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"프로덕트 디자이너","why":"디자인 감각, 크래프트 평가, 도구 활용법을 현실적으로 배울 수 있음"},{"who":"디자인 리더","why":"채용 기준과 디자인 기준을 명문화하는 방법이 직접적으로 나온다"},{"who":"지식노동자 일반","why":"노트와 기록을 AI로 분석해 자기 이해와 의사결정에 쓰는 법이 유용함"}],"normalizedAudience":["프로덕트 디자이너","디자인 리더·CXO","지식노동자 일반"],"summary":"이 영상은 Jenny Wen이 최근에 감명 깊게 본 책, 영화, 제품, 삶의 태도, 그리고 Co-work의 활용법을 차례로 소개하는 대화다. 표면적으로는 가벼운 추천 리스트처럼 들리지만, 실제로는 디자인 리더가 무엇을 중요하게 보는지, 그리고 좋은 도구가 사람의 기록과 생각을 어떻게 학습 가능한 형태로 바꾸는지에 대한 관점이 드러난다.\n\n특히 Retro처럼 시간이 지나야 가치가 보이는 제품의 경험, 'it is what it is'라는 태도에서 드러나는 통제 불가능성의 수용, 그리고 흩어진 인터뷰 노트·메모를 분석해 채용용 평가 루브릭을 만드는 사례가 핵심이다. 결국 이 대화는 디자인을 잘하는 사람의 취향과 판단 기준이 어떻게 축적되고, AI가 그 축적물을 재구성해 더 나은 판단으로 바꾸는지를 보여준다.","insights":["좋은 취향은 소비가 아니라 반복된 관찰에서 쌓인다.","시간이 지난 기록은 자기 이해를 가장 선명하게 만든다.","채용 기준은 말로 즉흥 생성하기보다 기록에서 추출해야 한다.","통제 불가능한 현실에서는 '수용'이 오히려 전진의 기술이다.","AI의 진짜 가치는 새 정보를 만드는 것보다 맥락을 정리하는 데 있다."],"keyClips":[{"clipId":"eh8bcBIAAFo:c7:3-9","startSegmentIndex":3,"endSegmentIndex":9,"startTime":4217.199,"endTime":4267.76,"durationSeconds":50.6,"preview":"책이 드러내는 관점","mustSee":false},{"clipId":"eh8bcBIAAFo:c7:11-22","startSegmentIndex":11,"endSegmentIndex":22,"startTime":4272.88,"endTime":4340.8,"durationSeconds":67.9,"preview":"좋은 콘텐츠의 조건","mustSee":false},{"clipId":"eh8bcBIAAFo:c7:23-30","startSegmentIndex":23,"endSegmentIndex":30,"startTime":4340.8,"endTime":4408.88,"durationSeconds":68.1,"preview":"Retro가 주는 가치","mustSee":false},{"clipId":"eh8bcBIAAFo:c7:31-38","startSegmentIndex":31,"endSegmentIndex":38,"startTime":4408.88,"endTime":4455.52,"durationSeconds":46.6,"preview":"수용의 힘","mustSee":false},{"clipId":"eh8bcBIAAFo:c7:39-49","startSegmentIndex":39,"endSegmentIndex":49,"startTime":4455.52,"endTime":4580.4,"durationSeconds":124.9,"preview":"AI로 기준 만들기","mustSee":true}],"curatedSegments":[{"segmentIndex":63,"text":"And then >> yeah okay so you had this sense that middle management might not last what's your current feeling do you think manage design management is a thing that persists long term or do you think everyone turns into IC >> I think as long as there is a team of people it helps to have somebody who is managing a team like I think there is there's like real value in managers it depends kind of like what the shape of the manager is and what they actually do but the way I think about like what a helpful manager is these days is somebody who is not just like I think pure people management like oh like just somebody to sort of set you up help you in your career have one-on- ones make sure you're feeling like good at work I think that is kind of not a thing as much anymore but I think somebody who can really function as like giving the team direction as well as doing some of the people management stuff like that tied together I think is the future of what managing looks like at least for now um like somebody who can really engage with the team in terms of like the work and giving direction there.","startTime":2301.839,"endTime":2363.04,"durationSeconds":61,"level":"C1","overallScore":9,"rationale":"관리자의 역할 변화에 대한 풍부한 통찰."},{"segmentIndex":66,"text":"And so there is something about like deciding what actually goes into the things we build which I guess is taste in some way but maybe not taste in like the way we think about like aesthetic taste or whatnot.","startTime":1766.48,"endTime":1779.76,"durationSeconds":13,"level":"C1","overallScore":7.8,"rationale":"디자인 판단의 본질을 정교하게 정의함."},{"segmentIndex":8,"text":"Yeah, I think someone will still have to decide like oh we want to build this kind of product or like given what the AI is presenting us like someone still needs to be accountable for the decision you know the same way that like even though cloud can write all this code for you today it is still an engineer who's accountable for like does that code actually work does this actually make sense in the product so I think there's that like decision-making/judgment layer which feels like maybe one day we won't have to do that but it's uh it still falls on us.","startTime":1847.36,"endTime":1877.76,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"책임과 판단층에 대한 통찰이 큼."},{"segmentIndex":3,"text":"Um, and I think these two things can feel like they're at tension, but I think they're actually they work really well together because it's like once you have that psychological safety, you have people trusting each other and you applying the high standards actually I think becomes potentially easier because you can do it without fear.","startTime":3624.64,"endTime":3643.44,"durationSeconds":19,"level":"C1","overallScore":7.8,"rationale":"두 원칙이 함께 작동한다는 핵심 통찰."},{"segmentIndex":16,"text":"And by illegible he means like oh it's sort of like really you know on the frontier people might not get it yet or like the way it's being told it just doesn't it's not like being told in the way that makes the most sense to people and I think this is obviously a good way for a VC to operate because you're trying to look for the opportunities that people don't see and put them out there in the world but I also think that like part of the role of the designer at least um at least at a frontier lab at anthrop topic is kind of spotting the ideas that are illeible and trying to understand what's there and how to take that and like transform it whether it's through storytelling or whether it's through like the actual UX and the form factor and put it out there.","startTime":3771.92,"endTime":3817.839,"durationSeconds":46,"level":"C1","overallScore":8.2,"rationale":"디자이너 역할을 깊게 정의하는 문장."},{"segmentIndex":14,"text":">> Where will human brains continue to be valuable? >> At the end of the day, someone has to decide what is actually going to get built and what [music] actually matters.","startTime":61.199,"endTime":68.88,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"의사결정의 본질을 짚는다."},{"segmentIndex":66,"text":"And I think this kind of work is like still really important in this world because in a world where people can spin off their seven claws, make whatever features they want in any direct in any kind of like direction or implementation, you need to point them towards something.","startTime":486.319,"endTime":501.599,"durationSeconds":15,"level":"C1","overallScore":6.6,"rationale":"새 도구 시대의 설계 역할을 주장함."},{"segmentIndex":71,"text":"It's engineering and the fact that you can build so quickly just forces uh the role of a designer to change because as you said engineers can just ship and what you're finding here is like you're better off not blocking that letting them cook as they say and uh and then there's kind of this mode of helping them along as they ship bring it together make sure it all kind of connects guide them a little bit. >> Yeah, I think so.","startTime":530.24,"endTime":556.72,"durationSeconds":26,"level":"C1","overallScore":7,"rationale":"역할 변화와 협업 방식을 잘 정리함."},{"segmentIndex":6,"text":">> And a big part of this is like you could argue like the question is what leads to the best most successful products and companies and you could argue it's spending time doing discovery user research mocks iterating beta testing or it could be just engineer ship is stuff that's okay not amazing good enough we learn iterate build iterate.","startTime":689.36,"endTime":705.519,"durationSeconds":16,"level":"C1","overallScore":7.2,"rationale":"두 작업 방식의 원리를 비교하는 통찰임."},{"segmentIndex":13,"text":"sort of have to use the actual models underneath and you have to sort of see people try it out with their use cases because with these models like you discover you can design them for different use cases but you don't you have to discover use cases as you see people using them. So yes >> the other thing I always hear and building on what you just said is just you don't know what people will do with AI.","startTime":747.68,"endTime":762.72,"durationSeconds":15,"level":"C1","overallScore":7,"rationale":"사용 사례 발견의 핵심을 잘 설명함."},{"segmentIndex":34,"text":"like we have been in a lot of like execution mode for co-work and now I want to set aside some time to think about hey what do the next like 3 months look like and where does that act where could that actually go given where the market's at where the models are at and what could that be because I think it's still really helps to visualize that and show that to the team and point everyone in the same direction um and then I also spend a bunch of my day just jamming on stuff with engineers like a lot of it is just a conversation or like whiteboarding or going through something that they built and giving them feedback on it and being a designer in that kind of way where we're like consulting.","startTime":959.36,"endTime":998.32,"durationSeconds":39,"level":"C1","overallScore":7.2,"rationale":"업무 방식 변화와 협업 방식이 풍부함."},{"segmentIndex":44,"text":"I think as a designer a few years ago I would say like maybe 60 to 70% of it was like mocking and prototyping stuff up and then spending you know the last 20 or so some of the last 20 or so like doing the sort of like jamming with engineers consulting with them and the last like 10% maybe doing you know coordination meetings etc. Uh but now I feel like the mocking up part of it is like 30 to 40% and then there's that other 30 to 40% there that is now jamming and pairing directly with engineers and then there's like a slice I don't know how much I have left but like there's a slice of it that is now like implementation as well.","startTime":1078.48,"endTime":1124,"durationSeconds":46,"level":"C1","overallScore":7,"rationale":"역할 비중 변화를 구체적으로 비교함."},{"segmentIndex":9,"text":"Um, I think the best design happens when you're able to just like throw a bunch of ideas at the wall and curate and just like and push yourself to come up with a bunch of these different directions.","startTime":1252.159,"endTime":1263.039,"durationSeconds":11,"level":"B2","overallScore":6.6,"rationale":"창작 프로세스에 대한 강한 통찰이 있습니다."},{"segmentIndex":47,"text":"You have to respond to people's feedback and you have to show that you are continuously shipping and improving it because I think the way that you really lose trust around quality and releasing something early is if you release it early and then nothing ever happens.","startTime":1567.919,"endTime":1583.6,"durationSeconds":16,"level":"C1","overallScore":6.6,"rationale":"신뢰가 깨지는 조건을 명확히 설명합니다."},{"segmentIndex":58,"text":"Boris on the podcast recently was saying cloud code is now helping him come up with ideas and decide what to build which is like okay wow look at that look at it go the whole product workflows the product development process slowly get eaten up by AI.","startTime":1684.48,"endTime":1697.84,"durationSeconds":13,"level":"C1","overallScore":6.4,"rationale":"AI가 침투하는 범위를 넓게 짚습니다."},{"segmentIndex":62,"text":"Someone has to decide like what is actually going to get built and what actually matters.","startTime":1733.52,"endTime":1739.12,"durationSeconds":6,"level":"B2","overallScore":6.4,"rationale":"무엇을 만들지 결정하는 핵심을 짚음."},{"segmentIndex":63,"text":"And when I think about people saying like, oh, you know, like AI is just going to build this software for us, a lot of the hard parts of building software are actually like not building it.","startTime":1739.12,"endTime":1749.679,"durationSeconds":11,"level":"C1","overallScore":6.4,"rationale":"AI 한계와 소프트웨어의 본질을 대비함."},{"segmentIndex":1,"text":"engineers in the world trust it so much they're not even looking at the code anymore. Like that's where we kind it just made me re-evaluate all these assumptions I've had about okay AI will never be as good as really good PMs designers at judging what is great and deciding what to build. >> Okay.","startTime":1800.31,"endTime":1806.88,"durationSeconds":7,"level":"C1","overallScore":6.6,"rationale":"가정 재고를 이끄는 통찰이 있음."},{"segmentIndex":10,"text":">> But like the human is mostly useful for signing off on the decision because someone needs to be liable if they're wrong.","startTime":1886.559,"endTime":1892.08,"durationSeconds":6,"level":"B2","overallScore":6.6,"rationale":"책임 소재를 짚는 통찰형 문장."},{"segmentIndex":20,"text":"But at the same time when we really leaned into this like chatbot paradigm like I think that just gave us this whole world of flexibility that we didn't get with these sort of like baked in UIs.","startTime":1970.799,"endTime":1975.36,"durationSeconds":5,"level":"C1","overallScore":6.8,"rationale":"채팅 UI의 장점을 구체적으로 설명."}],"generatedAt":"2026-06-22T14:53:27.161Z","keyClipsTotalSec":1822}]}