Ask HN: What problem did AI create at your company that didn't exist before? I've worked on a few AI-heavy projects recently and it feels like every team develops a new headache that didn't exist before AI.
What was it for your company?What did you end up doing about it? |
Agentic systems being deployed and adding more work in places: Slack messages now being picked up by workflows and AI integrations that automatically create messages, tickets, 'action items'; alerts triggering additional agentic investigation adding noise instead of reducing it (If you couldn't figure out actionable alerts before I'm not sure how an agentic system is going to help with that problem).
The removal or avoidance of individual accountability or ownership in many places: developer contributions that aren't understood by the person submitting them; loss of ownership and accountibility in work ("I asked Claude to...", "I worked with Claude to...", "Claude decided to...", "I don't know, Claude did it..."); destruction of trust between colleagues.
[1] https://hbr.org/2025/09/ai-generated-workslop-is-destroying-...
Oh that's easy. Someone needs to review and approve edits and commands.
Its hard to discern the kernel of truth that the author is trying to communicate. So much of documentation is now AI generated and rarely does it help in understanding code bases or diagnosing issues in production.
This was my experience at MSFT for the past year or so.
Officially we are only allowed to use Microsoft Copilot, which is great if you do not work in IT but utterly useless for development.
Therefore, every developer uses their own AI model / subscription, and we have a varying amount of slop being shipped. This leads to some developers, who adhere to the rules, being accused of falling behind because they can obviously not keep up with the developers who just push slop into the review.