Inside Meta’s Threads Launch
Naomi Nix and Will Oremus, reporting for The Washington Post:
With a mandate from Zuckerberg to take a big risk, Mosseri
assembled a lean, engineer-heavy team of fewer than 60 people to
hack together a bare-bones app on a breakneck timetable more
reminiscent of a start-up than an entrenched tech giant. Speaking
to investors this week after Meta reported strong earnings,
Zuckerberg held up Threads as vindication of his “year of
efficiency,” in which he sheared tens of thousands of jobs
in a bid for more agile teams that would ship products quickly.
That Threads was created by such a small group in such a short
amount of time has become something of a marvel inside Meta,
according to current and former employees who spoke on the
condition of anonymity to discuss internal matters, as well as
private messages viewed by The Post. Many see its __ quick rise
as a reminder that well-executed product launches might not need
all the bureaucratic trappings that a company with some 66,000
employees had grown accustomed to.
“Quick execution. Nothing fancy,” one person wrote on Blind, an
anonymous workplace app. “Just solid engineering that most of our
ICs [individual contributors] can do but unfortunately are
shackled.”
It continues to astound me that anyone with any experience whatsoever would express surprise that a small-ish talented team was so effective. (I say “ish” because 50-60 people isn’t all that small.) Fred Brooks’s The Mythical Man-Month is somehow simultaneously famous and widely-ignored. A larger team would likely have delayed Threads, not accelerated its launch. A much larger team might have doomed the project to failure.
To keep things moving, the Threads team punted thorny decisions
and eschewed difficult features, including private messages and
the ability to search for content or view the feeds of people you
don’t follow. The company also opted not to launch in the European
Union, where regulators are preparing to enforce new rules next
year requiring tech companies to provide more information to
regulators about their algorithms.
“You do the simple thing first,” Mosseri said. “And I think
that also helps reduce the scope, because often what happens is
scope creep and you want to add all these things because
they’re all great.”
Get something good out, even if it’s missing obvious important features, and start iterating. That’s the recipe. I’m very curious what the story is going to be for private messages on Threads, though — yet another new messaging silo, or something tied to Instagram’s? Whatever it is, I sure hope it uses E2EE.
(Twitter DMs, infamously, do not use E2EE, so every single ostensibly private message ever sent on Twitter is readable by Twitter employees with access privileges, and thus potentially exposable to the public by either a bug or spite. The same goes for Mastodon, which offers “mentioned people only” messaging, a feature that should not exist, in my opinion, because it creates the illusion of privacy. Better to offer no private messaging at all than offer it without E2EE.)
★
Naomi Nix and Will Oremus, reporting for The Washington Post:
With a mandate from Zuckerberg to take a big risk, Mosseri
assembled a lean, engineer-heavy team of fewer than 60 people to
hack together a bare-bones app on a breakneck timetable more
reminiscent of a start-up than an entrenched tech giant. Speaking
to investors this week after Meta reported strong earnings,
Zuckerberg held up Threads as vindication of his “year of
efficiency,” in which he sheared tens of thousands of jobs
in a bid for more agile teams that would ship products quickly.
That Threads was created by such a small group in such a short
amount of time has become something of a marvel inside Meta,
according to current and former employees who spoke on the
condition of anonymity to discuss internal matters, as well as
private messages viewed by The Post. Many see its __ quick rise
as a reminder that well-executed product launches might not need
all the bureaucratic trappings that a company with some 66,000
employees had grown accustomed to.
“Quick execution. Nothing fancy,” one person wrote on Blind, an
anonymous workplace app. “Just solid engineering that most of our
ICs [individual contributors] can do but unfortunately are
shackled.”
It continues to astound me that anyone with any experience whatsoever would express surprise that a small-ish talented team was so effective. (I say “ish” because 50-60 people isn’t all that small.) Fred Brooks’s The Mythical Man-Month is somehow simultaneously famous and widely-ignored. A larger team would likely have delayed Threads, not accelerated its launch. A much larger team might have doomed the project to failure.
To keep things moving, the Threads team punted thorny decisions
and eschewed difficult features, including private messages and
the ability to search for content or view the feeds of people you
don’t follow. The company also opted not to launch in the European
Union, where regulators are preparing to enforce new rules next
year requiring tech companies to provide more information to
regulators about their algorithms.
“You do the simple thing first,” Mosseri said. “And I think
that also helps reduce the scope, because often what happens is
scope creep and you want to add all these things because
they’re all great.”
Get something good out, even if it’s missing obvious important features, and start iterating. That’s the recipe. I’m very curious what the story is going to be for private messages on Threads, though — yet another new messaging silo, or something tied to Instagram’s? Whatever it is, I sure hope it uses E2EE.
(Twitter DMs, infamously, do not use E2EE, so every single ostensibly private message ever sent on Twitter is readable by Twitter employees with access privileges, and thus potentially exposable to the public by either a bug or spite. The same goes for Mastodon, which offers “mentioned people only” messaging, a feature that should not exist, in my opinion, because it creates the illusion of privacy. Better to offer no private messaging at all than offer it without E2EE.)