zlacker

[parent] [thread] 3 comments
1. diggan+(OP)[view] [source] 2025-05-21 11:37:03
> Depends on team but seems management is pushing it

The graphic "Internal structure of tech companies" comes to mind, given if true, would explain why the process/workflow is so different between the teams at Microsoft: https://i.imgur.com/WQiuIIB.png

Imagine the Copilot team has a KPI about usage, matching the company OKRs or whatever about making sure the world is using Microsoft's AI enough, so they have a mandate/leverage to get the other teams to use it regardless of if it's helping or not.

replies(1): >>linza+M1
2. linza+M1[view] [source] 2025-05-21 11:52:10
>>diggan+(OP)
Well, what you describe is not terrible way to run things. Eat your own dogfood. To get better at it you need to start doing it.
replies(1): >>sgarla+l3
◧◩
3. sgarla+l3[view] [source] [discussion] 2025-05-21 12:05:01
>>linza+M1
Sure, but if the product in question is at best tangential to your core products, it sucks, and makes your work flow slow to a crawl, I don’t blame employees for not wanting to use it.

For example, if tomorrow my company announced that everyone was being switched to Windows, I would simply quit. I don’t care that WSL exists, overall it would be detrimental to my workday, and I have other options.

replies(1): >>linza+nL
◧◩◪
4. linza+nL[view] [source] [discussion] 2025-05-21 16:38:48
>>sgarla+l3
True. i didn't mean "not terrible for employees" i meant "not terrible for company goals". Yes, these are intertwined, but assuming not everyone quits over introducing AI workflows it could make Microsoft a leader in that space.

Personally i would also not particularly like it.

[go to top]