This reminds me a lot of bits of https://www.hackyourbureaucracy.com/. Step one of any attempt to do something useful for any organization is; get familiar with what the organization actually does. Ideally at not just the top level, but also at the grass-roots level, because often upper management doesn't really know how things are actually done.
Going back to the SRE theme, I think a large part of the reason Google SRE was so successful is it empowered/enabled the people who really understand the problems of running services to fix them, instead of spinning up a separate dev team to fix them (which I've seen fail multiple times).
A useful tactic building IT stuff for a business is to steal/borrow someone with even rudimentary IT skills from that business and put them on your dev team. Their lack of IT skills will be more than compensated for by their knowledge of the business, and they can learn the IT bits on the way.
Here's a 2 min audio version of "Be in a business" from Wednesday Wisdom converted using recast app.
https://app.letsrecast.ai/r/a4f36317-013a-4da9-ab78-9bebe4dd31f1
This reminds me a lot of bits of https://www.hackyourbureaucracy.com/. Step one of any attempt to do something useful for any organization is; get familiar with what the organization actually does. Ideally at not just the top level, but also at the grass-roots level, because often upper management doesn't really know how things are actually done.
Going back to the SRE theme, I think a large part of the reason Google SRE was so successful is it empowered/enabled the people who really understand the problems of running services to fix them, instead of spinning up a separate dev team to fix them (which I've seen fail multiple times).
A useful tactic building IT stuff for a business is to steal/borrow someone with even rudimentary IT skills from that business and put them on your dev team. Their lack of IT skills will be more than compensated for by their knowledge of the business, and they can learn the IT bits on the way.
So many "products" — and this applies particularly to the AI hysteria — are features.
Among other things, your idea should be:
Painful
Popular
Frequent
Urgent
Growing
Unavoidable
Source: Antler