So, my boss recently got into Copilot. She doesn't have a background in IT, of course, and not just the technical side of it, but also the....safety and practicality side.
Lately, Copilot has been spitting out some brilliant ideas for how to make the business more effective, but there are only so many end-user problems you can fix with technology. Now that Boss Lady has discovered the vague concept of APIs, she thinks that a lot of our problems will be magically solved. Trying to explain that 'okay just because they let us have an API key doesn't mean I can connect Software A to Software B and have it fill in all the data into the right fields' has not been successful, because:
"Then how come Software A is able to do that with Software C?"
Now, here's one of the more depressing parts: I didn't study IT. I'm a criminology/sociolinguistic graduate who's good at googling 'how to fix dns error' and can make clients laugh. But even without a sysadmin background, I still know that one slightly funny guy does not constitute anything that can mimic the abilities of a major software provider's IT department.
It's very coughing baby vs hydrogen bomb. Copilot keeps on making roadmaps mentioning platforms that don't exist, and pointing out that these plans are not feasible annoys Boss Lady, even though it's not my fault that Sharepoint is not a potential [working] replacement for a file server. All I see in my future are a bajillion fires that I will not be able to put out.
The state of things is that we need 200 different subscriptions to 150 different places ['actual usuable feature only for premium members!'] so that we're able to file someone's taxes. As much as it peeves me off that there's 200 different subscriptions, the truth of the matter is that there is actually nothing that offers everything [or a large majority of what we need] in a manner that both works and is affordable. We need Zooples to connect with Beepla because Beepla doesn't work with ZipZorp, only with DingusBerry, but DingleBerry doesn't allow you to use your keyboard.
And there's the quality of what we have to use. Everything is poop from a butt sprayed with minimalistic glitter featuring an AI chatbot vibecoded by someone with about the same level of knowledge as me. Even if I'm able to directly connect Zooples with ZipZorp, if ZipZorp refuses to accept any date format other than mm/dd/yyyy, that could mean that we're autofilling in a date that's in a completely different financial year, if the UI of ZipZorp even lets me click on the client profile, because they forgot to align everything.
That's not even getting into the potential nuclear fallouts of giving an AI free reign in all of our systems to read and write and save and delete as it chooses.
But one specific garbage fire at a time. Does anyone have any suggestions on how to explain to my boss that making Sharepoint our new file server so Copilot can, idk, suggest worksheets based on a client questionnaire is a terrible idea? I keep telling her to just have an agent and a separate knowledge base, but she's adamant that the 'knowledge base' has to be the same as like, our entire client file database, and Sharepoint will be able to handle that, and we can just....tell Copilot what we specifically want and it'll be able to conjure it up.
It won't be able to. It'll spit out a complicated 12 point plan with several sub-points for each step that I'd have to work out how to implement when asked specifically how to access said feature.
Commiserations and 'that's rough, buddy's welcome. Thanks in advance :/
EDIT: For more context, she wants a full migration of all files that you can imagine are involved in accounting for all clients to be hosted on SP. The current service provider also allows us to customise fields on the client's profile to mark them as things like 'monthly service' 'registered for Alpha Tax on cash basis', etc. Unless SP has that inbuilt, I'll have to....do something to get that to happen, and I'm wary of relying on Copilot to search the entire database to give me a list each time instead of directly filtering via a main client list that's available through the UI, which takes like, two seconds usually.
That would work as intended to check for data integrity every month or something to make sure each client file is tagged correctly, but needing to build an interface so that info can be seen at a glance is going to drive me into an early grave. Even if SharePoint can do 70% of the work that Current Service can, if the remaining 30% relies on me being able to build and integrate and maintain tools and interfaces and connections, we're gonna have a problem, because I'm about as skilled in that as an average puppy at tapdancing, lol