Anecdotally, my job trained every office employee on AI tools back in March, encouraging everyone to think of ways to incorporate the tools into their standard work. As of last week, they’re asking us to get prior authorization to use their AI portal as a way to limit requests.
So some Fortune 500s must be feeling the squeeze on AI.
yep. everyone at mine was being praised for creating an agent that turned meetings into JSON and then the JSON into Asana tasks and the Asana tasks into a report and the report into an internal and external email and the email into a slack message and the slack messages and emails into weekly summary.
Burning thousands of credits for what could be replaced by…
I created a PoC to have an event parse an employees emails, summarize them, then check the calendar and recommend meetings and follow up based on context. It ended up working okay, but it was such a waste of time. This was a C Suite employee that requested, who gets a high volume of junk email. Why would you want AI to (initially requested) auto create meetings for you? That sounds like my nightmare. In the end, it never hit prod thankfully, but, the dev work to get to where I did was awful. Developing AI agents is like guessing and checking until you get close enough. Debugging is brutal and the work is extremely uninspiring.
I was put in a position to start building and deploying copilot agents in our company. I discovered in the first day how unprepared our environment was for anything copilot. The default state when you get licenses and an environment to work in, is the wild west. It’s really bad and as is tradition, half cocked and rushed to market. I wrote out pages of notes of things we had to do as a company before even the most simple agents are created for security and governance. I never got the support to implement any changes, so I drug my feet as much as I could on anything I could. For 6 months I successfully never deployed any AI stuff and got out to do full stack dev instead. I created PoC agents, but with hard caveats that none of it was usable in the current state in prod.
Now prices are increasing and our drive to force agentic has softened a little company wide. I like to think that my semi malicious yet justified slow walking saved us a whole shit load of headache and expenses over the next couple of months as the new copilot pricing hits on June 1.
Now that they’ve poured zillions into it, they are starting to realize that they’ll never get their return on that investment, so now they have to manage the draw down so it doesn’t all crash.
Anecdotally, my job trained every office employee on AI tools back in March, encouraging everyone to think of ways to incorporate the tools into their standard work. As of last week, they’re asking us to get prior authorization to use their AI portal as a way to limit requests.
So some Fortune 500s must be feeling the squeeze on AI.
yep. everyone at mine was being praised for creating an agent that turned meetings into JSON and then the JSON into Asana tasks and the Asana tasks into a report and the report into an internal and external email and the email into a slack message and the slack messages and emails into weekly summary.
Burning thousands of credits for what could be replaced by…
listening
The only thing companies aren’t willing to pay is attention
I created a PoC to have an event parse an employees emails, summarize them, then check the calendar and recommend meetings and follow up based on context. It ended up working okay, but it was such a waste of time. This was a C Suite employee that requested, who gets a high volume of junk email. Why would you want AI to (initially requested) auto create meetings for you? That sounds like my nightmare. In the end, it never hit prod thankfully, but, the dev work to get to where I did was awful. Developing AI agents is like guessing and checking until you get close enough. Debugging is brutal and the work is extremely uninspiring.
I was put in a position to start building and deploying copilot agents in our company. I discovered in the first day how unprepared our environment was for anything copilot. The default state when you get licenses and an environment to work in, is the wild west. It’s really bad and as is tradition, half cocked and rushed to market. I wrote out pages of notes of things we had to do as a company before even the most simple agents are created for security and governance. I never got the support to implement any changes, so I drug my feet as much as I could on anything I could. For 6 months I successfully never deployed any AI stuff and got out to do full stack dev instead. I created PoC agents, but with hard caveats that none of it was usable in the current state in prod.
Now prices are increasing and our drive to force agentic has softened a little company wide. I like to think that my semi malicious yet justified slow walking saved us a whole shit load of headache and expenses over the next couple of months as the new copilot pricing hits on June 1.
Christ I am only realising now they probably see me asking copilot “why are you so shit” or “Just fuckoff, I’ll do it myself”. They pay for that.
Love to see reality setting in.
Unfortunately that reality is going to quickly turn to “we have to cut staff and freeze salaries this year due to AI spending”.
Now that they’ve poured zillions into it, they are starting to realize that they’ll never get their return on that investment, so now they have to manage the draw down so it doesn’t all crash.
At least some are recognizing it.