←back to thread

492 points Lionga | 3 comments | | HN request time: 0.002s | source
Show context
ceejayoz ◴[] No.45672187[source]
Because the AI works so well, or because it doesn't?

> ”By reducing the size of our team, fewer conversations will be required to make a decision, and each person will be more load-bearing and have more scope and impact,” Wang writes in a memo seen by Axios.

That's kinda wild. I'm kinda shocked they put it in writing.

replies(34): >>45672233 #>>45672238 #>>45672266 #>>45672367 #>>45672370 #>>45672398 #>>45672463 #>>45672519 #>>45672571 #>>45672592 #>>45672666 #>>45672709 #>>45672722 #>>45672855 #>>45672862 #>>45672949 #>>45673049 #>>45673060 #>>45673501 #>>45673549 #>>45673723 #>>45673795 #>>45674537 #>>45674817 #>>45674914 #>>45675187 #>>45675194 #>>45675426 #>>45675612 #>>45676161 #>>45676264 #>>45676418 #>>45676920 #>>45678165 #
dekhn ◴[] No.45673060[source]
I'm seeing a lot of frustration at the leadership level about product velocity- and much of the frustration is pointed at internal gatekeepers who mainly seem to say no to product releases.

My leadership is currently promoting "better to ask forgiveness", or put another way: "a bias towards action". There are definitely limits on this, but it's been helpful when dealing with various internal negotiations. I don't spend as much time looking to "align with stakeholders", I just go ahead and do things my decades of experience have taught me are the right paths (while also using my experience to know when I can't just push things through).

replies(8): >>45673157 #>>45673217 #>>45673223 #>>45673278 #>>45675276 #>>45675476 #>>45675842 #>>45678613 #
noosphr ◴[] No.45675276[source]
Big tech is suffering from the incumbents disease.

What worked well for extracting profits from stable cash cows doesn't work in fields that are moving rapidly.

Google et al. were at one point pinnacle technologies too, but this was 20 years ago. Everyone who knew how to work in that environment has moved on or moved up.

Were I the CEO of a company like that I'd reduce headcount in the legacy orgs, transition them to maintenance mode, and start new orgs within the company that are as insulated from legacy as possible. This will not be an easy transition, and will probably fail. The alternative however is to definitely fail.

For example Google is in the amazing position that it's search can become a commodity that prints a modest amount of money forever as the default search engine for LLM queries, while at the same time their flagship product can be a search AI that uses those queries as citations for answers people look for.

replies(9): >>45675751 #>>45675757 #>>45676217 #>>45676220 #>>45676332 #>>45676648 #>>45677426 #>>45678143 #>>45680082 #
nradov ◴[] No.45677426[source]
Setting up a separate insulated internal organization to pursue disruptive innovations is basically what Clayton Christensen recommended in "The Innovator's Dilemma" back in 1997. It's what IBM did to successfully develop the original PC.

https://www.hbs.edu/faculty/Pages/item.aspx?num=46

Every tech industry executive has read that book and most large companies have at least tried to put it into practice. For example, Google has "X" (the moonshot factory, not the social media platform formerly known as Twitter).

https://x.company/

replies(1): >>45677960 #
1. dekhn ◴[] No.45677960[source]
but X isn't really an insulated org... it has close ties with other parts of Google. It shares the corporate infra and it's not hard to get inside and poke around. it has to be, because it's intended to create new products that get commercialized through Google or other Alphabet companies.

A better example would be Calico, which faced significant struggles getting access to internal Google resources, while also being very secretive and closed off (the term used was typically an "all-in bet" or an "all-out bet", or something in between. Verily just underwent a decoupling from Google because Alphabet wants to sell it.

I think if you really want to survive cycles of the innovator's dilemma, you make external orgs that still share lines of communications back to the mothership, maintaining partial ownership, and occasionally acquiring these external startups.

I work in Pharma and there's a common pattern of acquiring external companies and drugs to stay relevant. I've definitely seen multiple external acquisitions "transform" the company that acquires them, if for no other reason than the startup employees have a lot more gumption and solved problems the big org was struggling with.

replies(2): >>45678320 #>>45679149 #
2. nradov ◴[] No.45678320[source]
There are varying degrees of insulation. I'm not convinced that Calico is a good example of Christensen's recommendations. It seems like a vanity research project sponsored by a Google founder rather than an internal startup intended to bring a disruptive innovation to market.
3. com2kid ◴[] No.45679149[source]
MSFT were the masters of this technique (spin off a startup, acquire it after it proves viable) for decades, but sadly they stopped.

Even internal to MS I worked on 2 teams that were 95% independent from the mothership, on one of them (Microsoft Band) we even went to IKEA and bought our own desks.

Pretty successful in regards to getting a product to market (Band 1 and 2 all up had iirc $50M in funding compared to Apple Watch's billion), but the big company politics still got us in the end.

Of course Xbox is the most famous example of MS pulling off an internal skunk works project leading to massive success.