—
no predictions resolved yet
0 pending · 0 expired
That is a constant complaint about Slack. And Slack has spent a lot of time building sophisticated tools for notifications that nobody understands, nobody reads, and create massive chaos, I find.
I think I I think it might be related to the adoption pattern. So Google can fast track a huge huge adoption just by the presence and the and the the as you as
I think the fact that Google Plus did not have its own domain name and brand and destination where they had 100% of the marketing uh space and interface. I think was a challenge. And I think that plus.google.com or you know, however the domain structure was was a bit of a mistake because you never had this ability for it to stand alone as the in the way YouTube or Instagram do
there was visibility into the possibility of what what Google could do, and there was excitement about um the type of product we could build.
we had this 100-day 100-day sprint to to to ship something, and it was just like a a huge effort. At one point, we had 280 people contributing code to the same JavaScript binary
some of the theory I think was then to go off and create a separate product which had some of the properties of Google Buzz, but then also integrated features that were previously in Google I go in I in I Google.
I think it's I think it it's difficult to figure out how to backpedal and whether the the trust was um completely broken at that point
the most sort of public example is the real names policy... internally there's a huge amount of furor and a lot of Googlers really were against the real names policy... it was an executive decision to stick with it
I think the values and the vision of the people on the ground building the product diverged from the vision and values of the people leading
Google had been built out of a very different it was a very technical culture. They didn't really understand social in the way that Mark does.