Cook: Atlassian acquired Loom because asynchronous video became internally essential
Megan Cook · Lessons from Atlassian | Megan Cook (Head of Product, Jira) · Feb 4, 2024 · at 24:04
Megan Cook (Head of Product, Jira) discusses the rationale behind Atlassian's acquisition of Loom for distributed work.
0:00 / 0:02exact quote · 2.5s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“That's a big part of why we bought Lib.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Megan Cook
Atlassian research shows intentional in-person meetups boost remote productivity by 30%
“We found that connection and productivity, they both get boosted by about 30% when you bring people together, but then intentionally, and it lasts for months.”
Cook: Team hesitation and silence emerge when work streams hit 15 people
“So I think that was probably around, even, even around 15, we started to see a little bit of that.”
Cook: Product managers require three to four uninterrupted hours for creative flow
“You know, as PMs, we need time for creative work. We need that deep work time, and that doesn't happen when you've got all of these meetings with 30 minutes in between each of them. You need sort of, you know, three to four hours to get that going, to get into…”
Cook: Aligning three or four separate team roadmaps is basically impossible
“I don't know if you've ever tried to align, you know, three or four different roadmaps so that the timing is just right to get some improvement through, but it's basically impossible.”
Cook: Half or fewer of all Jira Software users are developers
“Then actually it's more like 50% or maybe just shy of 50% are developers. And the rest is this huge mix of support and operations and sales and marketing, finance, design, HR, Legal, just this massive mix of everybody, all the roles you could think of in a com…”
Jira leadership holds weekly 'Fight Club' meetings for direct product conflict
“What we put into place is something we called fight club... It's 30 minutes every week, and it's just for myself, my engineering, and my design leader, and we get together, and we know that we're going in there to have a conflict.”