๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Tamar Yehoshua
@TYehoshua
CPO/CAIO at @Atlassian. Previously CPO at @SlackHQ, VP @Google and @Amazon
๊ฐ€์ž… March 2013
79 ํŒ”๋กœ์ž‰ ์ค‘    1.1K ํŒฌ
We've been hearing that AI is collapsing PM, design, and engineering into one 'AI builder' role. This can work in a small company. Inside a 10,000+ person company, the story is more nuanced. When you have complex codebases, lots of dependencies, and hundreds of thousands of customers, the roles don't converge - they expand. The goal of the PM job is unchanged: set direction, exercise judgment, hold the quality bar, drive outcomes. What's changed is how PMs get there. AI changes how fast you move and how much more you can do. At Lenny & Friends Summit, I shared real examples from inside Atlassian: what's working, what's not, and where we're still figuring it out. Thanks to @lennysan for bringing PM leaders together! Check it out here: ๐Ÿ“ท
๋” ๋ณด๊ธฐ