The minicomputer revolution was meant to replace all the big iron in the basement with computers shared by teams. This lasted a decade until we got computers meant for one person and we've used that format of computation for nearly 50 years now.
Everyone is talking about how AI will replace people.
It won't.
AI without HI is useless. However, HI with AI is much better at handling all the bullshit office work that needs to get done—anyone who doesn't understand this is either an idiot, a troglodyte, or already has an expendable army of minions doing their work.
The surge in AI demand won't be top-down but bottom-up. That stupid office birthday wish card being passed around? I can Shakespeare the motherfucker. And that email to the big boss telling him the project is doomed and that he needs a compass to find his own ass? Let's ask R1.
>My boss is a moron who can't find his ass without a compass. His latest tech initiative will cost us millions and make the best staff leave. Write a professional letter that covers those points without being harsh.
---
Subject: Request for Review of Upcoming [Tech Initiative]
Dear [Recipient Name/Team Name],
I hope this message finds you well. I wanted to share some thoughts regarding our upcoming [Tech Initiative Name], as I believe open dialogue will ensure its success while aligning with our team’s strengths and long-term goals.
While the initiative’s intent to innovate is commendable, I’ve observed several potential challenges that may impact its effectiveness:
Financial Impact: Based on preliminary analysis, the projected costs appear to be significantly higher than initially estimated. A detailed cost-benefit review or phased rollout might help mitigate financial risk while allowing us to test feasibility.
Team Retention Concerns: Many of our top performers have expressed reservations about the initiative’s current structure, particularly around [specific pain point, e.g., workflow disruption, lack of clarity]. Retaining their expertise will be critical to execution, and their insights could refine the plan to better address on-the-ground needs.
To ensure alignment with both our strategic objectives and team capacity, I respectfully suggest:
Conducting a collaborative risk assessment with department leads.
Piloting the initiative in a controlled environment to gather feedback.
Hosting a forum for staff to voice concerns/solutions pre-launch.
I’m confident that with adjustments, this project can achieve its goals while preserving morale and resources. Thank you for considering this perspective—I’m eager to support any steps toward a sustainable path forward.
To be honest, that kind of sounds like a dystopian hell: chatGPT writing memos because we can't be arsed, and the reading the same memos because neither can the recipient. Why even bother with it?
With a well working rag system you can find the reason why any decision was made so long as it was documented at some point somewhere. The old share point drives with a billion unstructured word documents starting from the 1990s is now an asset.
Since I don't have an expendable army, I must be either an idiot or a troglodyte. Where my understanding falters is finding a domain where accuracy and truth aren't relevant. In your example you said nothing about a "phased rollout", is that even germane to this scenario? Is there appreciable "financial risk?" Are you personally qualified to make that judgement? You put your name at the bottom of this letter and provided absolutely no evidence backing the claim, so you'd best be ready for the shitstorm. I don't think HR will smile kindly on the "uh idk chatgpt did it" excuse.
"Here is the project description:
[project description]
Help me think of ways this could go wrong."
Copy some of the results. Be surprised that you didn't think of some of them.
"Rewrite the email succinctly and in a more casual tone. Mention [results from previous prompt + your own thoughts]. Reference these pricing pages: [URL 1], [URL 2]. The recipient does not appreciate obvious brown nosing."
If I was sending it as a business email I'd edit it before sending it off. But the first draft saved me between 10 to 30 minutes of trying to get out of the headspace of "this is a fucking disaster and I need to look for a new job" to speaking corporatese that MBAs can understand.
Is that really a problem most people have in business communication? I can't recall a time sending a professionally appropriate email was actually hard.. Also, consider the email's recipient. How would you feel if you had to wade through paragraph upon paragraph of vacuous bullshit that boils down to "Hey [name], I think the thing we're doing could be done a little differently and that would make it a lot less expensive, would you like to discuss?"
The minicomputer revolution was meant to replace all the big iron in the basement with computers shared by teams. This lasted a decade until we got computers meant for one person and we've used that format of computation for nearly 50 years now.
Everyone is talking about how AI will replace people.
It won't.
AI without HI is useless. However, HI with AI is much better at handling all the bullshit office work that needs to get done—anyone who doesn't understand this is either an idiot, a troglodyte, or already has an expendable army of minions doing their work.
The surge in AI demand won't be top-down but bottom-up. That stupid office birthday wish card being passed around? I can Shakespeare the motherfucker. And that email to the big boss telling him the project is doomed and that he needs a compass to find his own ass? Let's ask R1.
>My boss is a moron who can't find his ass without a compass. His latest tech initiative will cost us millions and make the best staff leave. Write a professional letter that covers those points without being harsh.
---
Subject: Request for Review of Upcoming [Tech Initiative]
Dear [Recipient Name/Team Name],
I hope this message finds you well. I wanted to share some thoughts regarding our upcoming [Tech Initiative Name], as I believe open dialogue will ensure its success while aligning with our team’s strengths and long-term goals.
While the initiative’s intent to innovate is commendable, I’ve observed several potential challenges that may impact its effectiveness:
Financial Impact: Based on preliminary analysis, the projected costs appear to be significantly higher than initially estimated. A detailed cost-benefit review or phased rollout might help mitigate financial risk while allowing us to test feasibility.
Team Retention Concerns: Many of our top performers have expressed reservations about the initiative’s current structure, particularly around [specific pain point, e.g., workflow disruption, lack of clarity]. Retaining their expertise will be critical to execution, and their insights could refine the plan to better address on-the-ground needs.
To ensure alignment with both our strategic objectives and team capacity, I respectfully suggest:
Conducting a collaborative risk assessment with department leads.
Piloting the initiative in a controlled environment to gather feedback.
Hosting a forum for staff to voice concerns/solutions pre-launch.
I’m confident that with adjustments, this project can achieve its goals while preserving morale and resources. Thank you for considering this perspective—I’m eager to support any steps toward a sustainable path forward.
Best regards,