Enterprise inertia. Similar to Teams > Slack "because it comes with the Microsoft license or O365 tenant." Once an org grows beyond a certain size, vendor onboarding and management friction becomes real.
Fair enough, our users are a broad range of severely non-technical to technical. We have our IT team manage the admin portals for these kinds of things, so not sure there's a huge difference between IT managing the copilot admin vs chat admin.
Have you asked what the process and effort looks like to onboard OpenAI as a vendor? Ask questions to decompose the system to understand the system. Be curious, it will guide you to understanding.
These are helpful reminders, appreciate it. Right now I'm also just navigating through testing myself before sharing with our leadership team. Asking deeper questions during this process is of course helpful, I plan to dig into each problem they want to solve with AI and why.
I really was just curious about any interesting gotchas anyone else has run into. Historically, Microsoft is a balance between "this is great because it's already here, we just need to turn on a button to enable it" and the quality or reliability being not what we expected, to put it mildly. That and onboarding is a headache for external tools, but is often a tiny fraction of long-term maintenance so isn't necessarily the highest-weighted issue.
Enterprise inertia. Similar to Teams > Slack "because it comes with the Microsoft license or O365 tenant." Once an org grows beyond a certain size, vendor onboarding and management friction becomes real.
Fair enough, our users are a broad range of severely non-technical to technical. We have our IT team manage the admin portals for these kinds of things, so not sure there's a huge difference between IT managing the copilot admin vs chat admin.
Have you asked what the process and effort looks like to onboard OpenAI as a vendor? Ask questions to decompose the system to understand the system. Be curious, it will guide you to understanding.
https://en.wikipedia.org/wiki/Five_whys
https://fs.blog/chestertons-fence/
These are helpful reminders, appreciate it. Right now I'm also just navigating through testing myself before sharing with our leadership team. Asking deeper questions during this process is of course helpful, I plan to dig into each problem they want to solve with AI and why.
I really was just curious about any interesting gotchas anyone else has run into. Historically, Microsoft is a balance between "this is great because it's already here, we just need to turn on a button to enable it" and the quality or reliability being not what we expected, to put it mildly. That and onboarding is a headache for external tools, but is often a tiny fraction of long-term maintenance so isn't necessarily the highest-weighted issue.
This